Skip to main content

Roles and access control (RBAC)

Orbis Studio uses role-based access control (RBAC) to decide who can see and change what. The RBAC Settings page is where administrators manage the organizational structure — tenants, workspaces, and members — and review the permissions granted to the current user.

Tenants and workspaces​

Access is organized into two levels:

  • Tenant — the top-level boundary for an organization. Each tenant's data is fully isolated; the tenant is derived from the server side on every request, so content never leaks across tenants.
  • Workspace — a working area inside a tenant. A tenant can contain multiple workspaces, and members are added to the workspaces they need.

If you belong to more than one tenant or workspace, use the selectors on the RBAC page to switch your active context. The page also shows summary statistics, such as the number of tenants and workspaces available to you.

Roles​

Each member holds a role that determines what they can do. Roles include:

  • Tenant admin — manages the tenant, its workspaces, and its members.
  • Workspace admin — manages a single workspace and its members.
  • Designer — builds and edits flows within a workspace.

A superuser is a platform-level administrator who can manage tenants and users across the system.

Manage the organization​

From the RBAC page, administrators can navigate to dedicated management areas:

  • Users — manage the people who can sign in to the platform. Visible to superusers and tenant admins.
  • Tenants — view and manage tenants. Superusers see the full list; a tenant admin goes directly to their own tenant's members.
  • Workspaces — manage the workspaces inside a tenant.
  • Members — add or remove members of a tenant or workspace and set their roles.
  • Permissions — review the permissions associated with each role.
info

The actions you see depend on your role. A workspace designer, for example, does not see tenant or user management. The backend re-checks every request against your role, so the interface and the server always agree on what you are allowed to do.