Tenancy and workspaces
Tenant → Environment → Workspace → Workflow / Agent
Tenant
A tenant is your organization, the top-level unit. When you accept an invite, Culvii provisions a tenant with three environments (dev, sandbox, prod) and makes the first user its Owner. Tenants share infrastructure but never share data, runs, or audit log.
Owner and roles
The Owner can access all three environments, create workspaces anywhere, invite members, and manage tenant settings. There can be more than one Owner. If the original leaves, another can be promoted.
Below Owner, roles are admin, operator, developer, and viewer. See Authentication for the roles and Permissions for exactly what each one grants. Custom roles beyond these five aren't available yet.
Environment
Every tenant has exactly three environments, dev, sandbox, and prod, and they can't be added, removed, or renamed. See Environments.
Workspace
A workspace is a container for workflows and agents inside an environment, used to scope access and group related work. Common shapes: one per business domain (procurement, customer-support), one per team, or one per developer in dev. culvii dev provisions a dev-{username} workspace automatically if you don't have one.
Workspace structure isn't shared across environments. You might run two scratch workspaces in dev, one shared workspace in sandbox, and three production workspaces split by team.
Member access
Members are invited at the tenant level; the Owner (or an admin) then grants access to specific workspaces in specific environments. A typical developer has access to their own dev workspace, the team's sandbox workspace, and nothing in prod. Access changes take effect immediately. There's no key rotation involved, since permissions resolve per request.
What lives where
| Resource | Scope |
|---|---|
| Tenant | top-level |
| Environment | inside a tenant (always 3) |
| Workspace | inside an environment |
| Workflow / Agent | inside a workspace |
| Audit event | tenant-level, queryable per workspace |
What's not there yet
Workspaces are flat. There are no sub-workspaces or folders. Each workspace is a closed unit too: a workflow in procurement can't reference an agent in support directly. Custom roles beyond the five built-in ones, and cross-tenant federation for organizations with subsidiaries, are both on the roadmap.