usable teams Back to TeamsPaid-beta support
These are the current operating limits and support expectations. They are deliberately specific so a beta label never hides an unknown product promise.
Access is limited to approved cohorts. Support targets an initial response within one business day; this is not a contractual 24/7 service commitment. Scheduled pilot event coverage follows the agreed on-call window.
Current Chrome and Edge are the actively tested desktop browsers for paid beta. Mobile responsive journeys are tested at 390px in Chromium, with an automated 320 CSS-pixel reflow check. Safari, Firefox, installability, offline behavior, and iOS push remain best-effort until their candidate matrix is signed.
Teams itself holds no model-provider key. The embedded Usable Chat runs on chat.usable.dev as the signed-in user, is grounded in the selected team workspace, and consumes that user’s Usable generation credits. Weekly briefs and capture suggestions in Teams are deterministic and spend no AI credits.
In-app notifications are primary. Push depends on browser permission and a registered device. Email digest delivery is deferred for the pilot, so queued email is not a guaranteed customer notification channel.
Access changes do not delete team data. Approved export, leave, archive, and owner erasure paths remain available in retained read-only states. Erasure removes readable projections, files, and Teams-owned memory mirrors; immutable Flowcore evidence and separately governed billing/audit records follow their own retention rules.
Paid activation and Marketplace promotion remain blocked until privacy, manual accessibility, production memory/operations, real Havnardalur pilot outcomes, and the named paid-beta go/no-go owners have signed the exact release candidate.
Send the visible support reference and a description of the action that failed. Never send an invite link, access token, private-content export, password, or screenshot of team content.
Email support