Skip to content
Gamut AI Gamut AI Docs

Workspaces & tenancy

Gamut is multi-tenant. Each organisation operates in its own tenant, an isolated environment whose AI systems, assessments, evidence and users are kept separate from every other organisation. Inside a tenant, each assessment acts as a workspace that work and membership attach to.

Isolation by construction

Section titled “Isolation by construction”

Tenant isolation is a deliberate security property, enforced at the data layer rather than by application filtering alone: each tenant’s records live in their own normalised database schema. Your governance records, evidence and users are never visible to another organisation, and access is always scoped to the tenant you belong to. See Security & data handling.

What lives in a tenant

Section titled “What lives in a tenant”

Assessment-level membership

Section titled “Assessment-level membership”

Within a tenant, membership and roles can be scoped to an individual assessment. A user carries a tenant role for what they can do organisation-wide, and an additive workspace role, Lead Assessor, Contributor, Reviewer or Viewer, on the specific assessments they are added to. This is how you give someone broad read access but write access only where they actually work.

Belonging to more than one tenant

Section titled “Belonging to more than one tenant”

Some people work across more than one organisation or environment, for example advisers and auditors. Where that applies, a user can belong to multiple tenants and switch between them, always acting within the one currently selected and never carrying data across the boundary.

Tenant status

Section titled “Tenant status”

A tenant has a status that controls access. An active tenant operates normally; a suspended tenant is locked out entirely until reactivated. Gamut operators manage this as part of account lifecycle, and provisioning, suspension and reactivation are audited platform actions.

Next

Section titled “Next”