Isolation exists. A team product does not.
Organizations need shared context and controlled access. Today each person has a private workspace. There is no invite flow, role model, or workspace switcher.
How this audience would use the workspace
Individuals in an organization can each create an account. Row-level security keeps those workspaces author-private. Shared projects and administration are planned.
What would matter here
Module status is the same as on the product page. An audience brief cannot mark a planned capability as available.
Account
AvailableCreate a free account, sign in, and complete language onboarding.
Conversation history
AvailableThreads persist in your personal workspace. You can rename, archive, restore and delete them.
Shared workspaces
PlannedInvites, roles and a workspace switcher are planned. Conversations are author-private today.
Limits that apply today
Membership tables exist in the schema; they are not a product. There is no organization dashboard and no deployment option to purchase.
Start as a person, not as a tenant
Create an account for yourself. Organization-wide features remain planned.