Tenant
An isolated organization, account, or workspace within a multi-tenant system.
Definition
A tenant is a single organization, customer, or account that operates within a multi-tenant system, with its own data, users, and configuration kept separate from every other tenant sharing the same underlying application and infrastructure. A tenant might be a company, a team, or a project, depending on how a given platform defines the boundary. The tenant is the unit that isolation, billing, and access control are typically built around, and it is the concept that makes multi-tenancy a meaningful architectural pattern rather than an abstract label.
How it works
Every resource created in a multi-tenant application, such as a project, a credential, or a piece of generated content, is associated with exactly one tenant identifier. Access control checks use that identifier to confirm a request is allowed to touch a given resource, and data queries are filtered by it so that cross tenant reads are not possible through normal application paths. A single human user account can often belong to more than one tenant, in which case the application tracks which tenant is currently active for that user's session and requires an explicit switch to change it. Some platforms use the term "workspace" or "organization" interchangeably with tenant in their user facing terminology, even though the underlying architectural concept is the same.
Why it matters for AI agent systems
In an agent platform, a tenant boundary determines which agents, credentials, and conversation histories belong together and are isolated from other customers. This matters because agents accumulate access to real systems and real data over the course of long running tasks, so a tenant boundary that leaked would expose one organization's agent activity, and potentially its credentials, to another organization entirely. Agenhood models this as a workspace: every agent, credential, and role assignment is scoped to a workspace, and a user's membership and role can differ from one workspace to the next.
Related concepts
- Multi-tenancy: the architectural pattern that defines and enforces tenant boundaries.
- Role-based access control: usually applied per tenant, so a role granted in one tenant does not carry over to another.