Your tenant¶
Status: Current | Last reviewed: 2026-09-29
A tenant is your isolated workspace inside TrueServe. Everything you build — agents, workflows, integrations, prompts, catalogs — belongs to a tenant. Other tenants cannot see your data, and you cannot see theirs.
What a tenant looks like¶
Every tenant has:
- A name — what shows up in the UI ("Acme Insurance").
- A slug — a URL-safe identifier ("acme") used in workspace paths and integration names. Slugs are immutable once a catalog or workspace is bound to the tenant.
- A set of users with roles inside this tenant.
- Its own agents, workflows, integrations, prompts, and catalogs.
- Its own encrypted secrets vault. Even tenant administrators in another tenant cannot read your tokens.
Switching tenants¶
The profile menu in the bottom-left shows the active tenant. Open it and choose a tenant to switch. The app returns to the Agents page and reloads tenant-scoped data, including agents and integrations.
You can only see tenants you've been invited to. If a tenant is missing from the list, ask its administrator to add you.
Platform administrators are the exception: their switcher lists every active tenant, even when they do not have a separate membership in each tenant. They must still switch to the tenant that owns an agent before opening or editing it.
Tenant administrators¶
An administrator is assigned through tenant membership. Tenant Admins can:
- Add users, change tenant roles, and remove memberships through Settings → Access → Members.
- Manage tenant settings, integrations, telephony/provider configuration, allowed origins, legacy embed clients, and tenant tokens.
- Configure the tenant-wide service connections under Settings → Tenant Settings: Knowledge and Telemetry. This group is Admin-only.
- Create and delete agents, workflows, tools, surfaces, and catalogs when their role includes those permissions.
- View conversations, transcripts, traces, logs, and observability when their role includes agent management.
Builders and Viewers have narrower access — see User roles.
What tenants do not share¶
- Users are tenant-scoped. The same email can be in multiple tenants and have different roles in each.
- Integrations are tenant-scoped. Connecting Salesforce in tenant A does not also connect it in tenant B; each tenant authorizes the integration independently.
- Encryption keys are tenant-scoped at the data layer. A leak in one tenant does not expose another.