Tenant Management
Manage tenant identity, roles, feature availability, and operational ownership.
Tenant Management
Use this page when you create a tenant, adjust team access, change feature availability, or prepare a handoff between operators.
Operating Model
Tenants are the workspace boundary for content, commerce, community, events, and integrations. Keep tenant changes tied to a named owner and a launch or support reason.
| Area | Owner to confirm | Check before changing |
|---|---|---|
| identity | workspace owner | tenant 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 |
Change Flow
Confirm the tenant record
Check that the tenant name, slug, and ownership metadata match the workspace you intend to operate.
Review role assignments
Use tenant-admin for workspace operators, tenant-editor for day-to-day content or commerce work, and tenant-viewer for review-only access.
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 tenant as launch-ready.
Feature Guardrails
- Free plans can operate the core content surfaces.
- Starter and higher plans add commerce, customers, videos, community, and events.
- Basic and higher plans add canvas.
- Enterprise can enable every tenant feature, including live-streaming.
Do not enable customer-facing features unless support, moderation, and credential ownership are assigned.
Next Actions
- Set the base workspace state in Workspace Setup.
- Choose the launch scope in Feature Planning.
- Validate blockers in Launch Readiness.