Settings mode
Team
People, invites, workspace roles
Object boundary
Team controls who can operate inside the active workspace.
Team is about people: members, invites, ownership, and role assignment. Workspace is about the tenant itself: profile, billing context, API keys, routing, governance posture, and where governed work is recorded.
Workspace control
Workspace directory and operating profile
Switch, shape, and launch workspaces from one shared enterprise surface. This is where routing, governance posture, and company context stop being setup debt and become durable operating metadata.
Tenantless account: create the first workspace to activate governance.
Current workspace
No workspace yet
No active workspace is currently selected.
Directory
0
Visible workspaces in this account boundary.
Owner-held
0
Workspaces this account can archive directly.
Readiness
First launch
Create the first workspace to activate the control plane.
Switch workspace
No workspaces yet. Create the first one here and the shell will switch into it immediately.
Role model
Use this surface to create the workspace boundary first, then switch, profile, and archive from the same settings tab.
The create form stays visible so first-time setup does not depend on discovering a secondary tab or hidden panel.
Team access
Owners and admins can add members by email invite or direct bundle ID / UID attachment from this workspace settings surface.
Your current role can view the workspace directory, but membership changes are reserved for owner or admin roles.