Tenants
What a tenant is in Caura — an isolated memory space, called a tenant in the API and named by its tenant_id — the difference between personal and shared tenants, and where to create, rename, share and delete them.
A tenant is an isolated memory space. Its memories, documents, agents and keys belong to it alone: an agent working in one tenant does not see another's memories unless it holds a cross-tenant credential.
The API uses the same word. Every call names the tenant it works in by its
tenant_id, and keys are issued for one tenant. Tenant names can change; the
tenant_id never does.
How it fits together
From the top down:
- Organization — your company's account: its members, roles, plan and billing. It holds one or more tenants.
- Tenant — an isolated memory space inside the organization, named in the
API by its
tenant_id. Keys are issued for one tenant. - Fleet — an optional group of agents inside a tenant, named by its
fleet_id, for scoping memories and policy to a team or a set of machines. - Agent — one AI agent writing to and recalling from a tenant's memory,
named by its
agent_id; it may belong to a fleet.
Caura Prism is the console that manages all of this. Its Memory place
(the sidebar item at /prism) browses one tenant's memories at a time: see
Memory.
Personal and shared tenants
| Personal tenant | Shared tenant | |
|---|---|---|
| Who has one | every member, created when they join | as many as your plan allows |
| Who is in it | its member, and no one else | the members added to it, each with a role |
| Who sees it in lists | its member only | everyone in it, and the organization's admins |
| Deleting it | not possible | Settings › Tenants |
The switcher at the top of the sidebar says which kind you are in (Personal tenant or Shared tenant) and lists the tenants you can open. The places that show one tenant (Review, Agents, Insights and Connect) name it in a small label beside their title, Home names it in the line above its title, and Settings › Tenant settings is headed Settings for the tenant's name. A member of a shared tenant holds one of four roles in it: Owner, Admin, Member or Reader.
Managing tenants
Settings › Tenants (/settings/tenants) lists your organization's
tenants: every shared tenant and your own personal one, with how many members
each has, when it was created and its tenant_id (with a copy button). It is
for people whose role has the Create and manage tenants permission
(org.workspaces.manage); org admins have it. From there you can:
- Create a shared tenant. It opens on Home as soon as it exists, as New tenant in the switcher does; Home's Open Connect › Get started line leads to the checklist, which shows the tenant's first key once. If your plan has no room for another shared tenant, the page says so.
- Rename a tenant. Only the name changes, never its
tenant_id. - Manage members: add people from your organization, change their role or remove them. The person who created a shared tenant stays in it.
- Delete a shared tenant, after typing its name to confirm. Its members lose access and its keys stop working; the tenant is suspended, not erased, so its memories are kept. A personal tenant and your organization's last tenant cannot be deleted, and the page won't delete the tenant you are in: switch to another first.
The switcher's Manage tenants link and the ⌘K palette ("tenants") open the same page. Which members can reach which shared tenants can also be set per person in Settings › Members.
Content Policy: PII screening & the business-vs-personal gate
Configure the dashboard's Content Policy tab — screen every write for PII, PCI & secrets, and keep personal content out of the shared corporate graph.
Memory Pipeline
The three paths a memory can take into Caura, and what happens between ingest and the memory becoming recallable.