Tenants & membership roles

A tenant is a workspace: a named container for libraries, resources, and the people who work with them. Every user belongs to one or more tenants, switches between them from the workspace menu in the admin panel, and only ever sees data that belongs to the tenant they currently have selected.

Joining a tenant

• Create your own: registering without an invitation creates a tenant for you and makes you its Owner. See Creating an account.
• Get invited: an existing Owner or Admin invites you by email from Tenant settings and assigns you a role. See Accepting a tenant invitation.

Roles

Every membership has exactly one role:

Role	Can do
Owner	Everything an Admin can, plus remove other Owners and delete the tenant. A tenant always keeps at least one Owner: the last one cannot be removed.
Admin	Manage tenant settings (name, AI provider configuration), invite and remove Admins/Members, change their roles, and full access to the tenant's data.
Member	Use the tenant day to day: work with libraries, resources, notes, and their own Personal Access Tokens and Connected Apps. Cannot change tenant settings or manage other members.

Only Owners and Admins can invite people or change roles, and an Admin can only manage Admins and Members, not other Owners. This is enforced server-side regardless of what the admin panel shows.

What lives in Tenant settings

The Tenant settings page (workspace menu → Tenant settings) is where an Owner or Admin:

• renames the tenant,
• optionally overrides the instance-wide AI provider configuration for this tenant specifically (generation, embeddings, transcription, reranking, each independently, with its own base URL, API key and model),
• invites, removes, and manages members and pending invitations,
• and, for Owners, deletes the tenant entirely.

A tenant without its own provider configuration falls back to the instance-wide defaults the operator configured. A tenant is fully functional without ever visiting this page.