Workspace Management
Manage workspace identity, roles, feature availability, and operational ownership.
Workspace Management
Use this page when you create a workspace, adjust team access, change feature availability, or prepare a handoff between operators.
Operating Model
Workspaces are the boundary for content, commerce, community, events, and integrations. Keep workspace changes tied to a named owner and a launch or support reason.
| Area | Owner to confirm | Check before changing |
|---|---|---|
| identity | workspace owner | workspace name, slug, domain, and support contact |
| roles | tenant-admin | least-privilege access for every user |
| features | product or operations owner | plan availability and readiness blockers |
| credentials | technical owner | key rotation, CORS, and webhook receivers |
| billing | finance or owner | active subscription and payment status |
Select the intended workspace before changing workspace records. A super-admin must also select a workspace before updating or deleting; a missing selection is denied.
Change Flow
Confirm the workspace record
Check that the workspace name, slug, and ownership metadata match the workspace you intend to operate.
Review role assignments
Use tenant-admin for workspace administrators, tenant-editor for permitted day-to-day content or commerce work, and tenant-viewer for review-only access. super-admin is the platform role. Confirm the assignment on this workspace; membership in another workspace is not enough.
Align features with the plan
Enable only features allowed by the current plan, then assign an operating owner for each enabled feature.
Re-run readiness checks
After access, feature, credential, or billing changes, run readiness checks before treating the workspace as launch-ready.
Membership And Ownership Changes
A tenant-admin manages membership only for workspaces where they hold that role. Select the intended active workspace before writing; a missing, stale, or unauthorized selection must be corrected before retrying. A tenant-editor or tenant-viewer cannot grant themselves admin access.
Only the current workspace owner or a super-admin can transfer ownership. The recipient must already be a member; a completed transfer also grants tenant-admin without removing their existing roles. Use the ownership transfer action, rather than editing owner metadata. Before removing an operator who owns workspaces, transfer those workspaces first.
Customer support actions below apply to customer accounts, not Console operator membership. For app-side sign-in and identity readback, use the Customers task guide.
Feature Guardrails
Plan-by-plan feature availability lives on Feature Planning — enable only what the current plan allows.
Do not enable customer-facing features unless support, moderation, and credential ownership are assigned.
Customer Suspension
The Account suspension panel at the top of the customer edit view shows the current suspension state. Only super-admins can suspend an account or lift a suspension with its button; saving the customer form never changes the suspension state.
A suspension can be lifted only after session revocation finishes.
If unsuspend returns 409, retry after processing finishes. If it persists,
contact support.
Customer Consent
For direct customer signup, the workspace collects required legal acknowledgement and keeps its own evidence. Customer acceptsTos and tosVersion are workspace self-reports, not platform consent receipts.
Hosted required consent defaults off. Hosted consent required is turned on by the platform operator on request; contact support. Current terms and privacy-policy versions and valid terms links for enabled OAuth clients must be configured before activation.
When enabled, hosted password, email-code, and social login compare the customer’s latest receipt with the workspace’s current versions before issuing an authorization code. A missing or different version requires acknowledgement of the current documents; acceptance appends a new receipt. Direct login and already-issued session refresh remain outside this gate. With the setting off, existing login behavior is preserved.
Customer Self-withdrawal
Customers with a local password can reauthenticate and immediately archive
their own account through the SDK. An incomplete, trialing, active, or
past_due membership blocks withdrawal, including a scheduled cancellation
until the status ends. The API does not cancel memberships automatically.
Customers without a local password should contact their workspace administrator.
The account records its withdrawal time and a structural audit entry. Existing
archive session revocation applies; orders, payments and membership charges
remain intact. Personal-data erasure remains a separate operator action.
Operator restoration follows the existing archive rules and retains the
withdrawal timestamp. Restoration returns 409 while session revocation is
incomplete; retry after processing finishes. If the 409 persists, contact support.
The archived account continues to reserve its email.
Next Actions
- Set the base workspace state in Workspace Setup.
- Choose the launch scope in Feature Planning.
- Validate blockers in Launch Readiness.