Administration
Workspace and access setup
Provision workspaces, plans, modules, and access carefully so teams only see the surfaces they should use.
Use this guide when you are responsible for tenant setup, plan entitlements, or who can operate sensitive areas like AI, integrations, or exports.
Flow
Recommended order
1. Create the workspace
Open /admin/workspaces and configure the tenant identity, hostname, status, and base plan.
2. Assign the right plan
Open /admin/plans or /admin/access and make sure the workspace receives the correct module bundle.
3. Apply overrides carefully
Overrides are useful for exceptions, but they also make support and troubleshooting harder. Use them only when the default plan truly does not fit.
4. Confirm elevated access
Sensitive areas such as automation runs, integrations, BI tokens, and export controls should be limited to the right operators.
Common mistakes
- giving a workspace the wrong plan and then debugging “missing pages”
- using many manual overrides instead of fixing the plan
- granting elevated admin access wider than necessary