Tenants, projects and people
Olympusx AI is one platform shared by many customers. Three nouns decide who sees what and who pays for what: the tenant, the project and the person. This page explains each one, what it guarantees, and where it is managed.
The tenant
Section titled “The tenant”A tenant is one isolated customer of the platform: a business unit, a subsidiary, a public body, a client of yours. Everything a tenant makes belongs to it alone: its deployments, knowledge collections and vector databases, agents, tools, skills, assistants, keys, budgets, conversations, runs, traces, scores and its share of the audit log.
What a tenant is guaranteed:
- No other tenant can read its records. Every tenant-owned record carries its tenant, and the platform’s database itself refuses a read that crosses tenants, so the separation does not depend on every query remembering to filter.
- Its workloads run apart. Its model servers run in its own project namespaces on each cluster, behind network policies that deny traffic by default.
- Its knowledge has its own store. Each vector database belongs to one tenant.
- Its spend is its own. Its usage is metered to it, and its budgets and bill are its own.
Only a platform administrator creates tenants, grants them models and capacity, and sets the tenant’s own budget. See Tenants.
The project
Section titled “The project”A project is a division of a tenant’s work: a team, an application, an environment. A tenant starts with one project and can have several. A project:
- Holds API keys. Every key belongs to one project, and its usage is reported against that project.
- Holds budgets. A project’s token budget divides the tenant’s, and its keys’ budgets divide the project’s.
- Holds a quota on each cluster. A project’s quota on a cluster divides the tenant’s capacity there. Setting it is what creates the project’s namespace on that cluster, where its model servers run.
- Has an environment label: production, staging or development.
Platform administrators create projects; tenant admins set the quotas and budgets inside them. See Projects.
Two envelopes, never mixed
Section titled “Two envelopes, never mixed”A tenant has two separate allowances, and neither draws on the other:
| Envelope | Unit | Who sets it | What it limits |
|---|---|---|---|
| Capacity | CPU cores, memory, storage, GPUs per GPU flavour, on one cluster | A platform administrator grants it to the tenant; a tenant admin divides it into project quotas | What the tenant can deploy: model servers and vector databases |
| Token budget | Tokens per day or per month | A platform administrator sets the tenant’s; a tenant admin divides it into project and key budgets | What the tenant’s callers can spend through the models |
A child can never exceed its parent: a project quota fits inside the tenant’s capacity, and a key budget fits inside its project’s. See Keys, budgets and metering.
People
Section titled “People”A person is an account in your identity provider. Olympusx AI keeps no separate user directory: it reads the person’s tenant and role from the token the provider issues at sign-in.
- One account belongs to one tenant. The username is the person’s email address, so one address is one account in one tenant. Someone who works in two tenants needs two addresses.
- A person has a role in that tenant. Admin, Builder, End user, Reviewer or Auditor. A new invitation is an End user unless the admin chooses otherwise. See Roles and permissions.
- A platform administrator belongs to no tenant. They run the platform and can act in every tenant. It is not a tenant role.
- A tenant admin manages the tenant’s people: invites them, changes their role, disables them, resends an invitation or sets a temporary password. See Users and roles.
People who use a published assistant through its share link have no account at all. They are identified only by the reference the embedding application passes, or by one Olympusx AI issues for the conversation. See Agents and assistants over the API.