> ## Documentation Index > Fetch the complete documentation index at: https://docs.2501.ai/llms.txt > Use this file to discover all available pages before exploring further. # Organizations > Organize your tenant by separating between organizations Organizations provide logical separation of infrastructure within your 2501 account. They enable multi-tenancy, allowing you to partition resources, agents, and operations based on your operational structure. ## What is an Organization? An organization is a scoping boundary that groups related infrastructure and operations. All operational resources are associated with an organization, providing isolation and access control within your account. ## Organization Structure Your tenant is the isolation boundary: nothing is ever visible across tenants, whatever a user's role or scope. Inside the tenant, every resource is scoped in exactly one of three ways. ### Organization-scoped resources These resources always belong to one organization and cannot be made tenant-wide: * **[Hosts](https://docs.2501.ai/0.19/core-concepts/hosts.md)**: target systems, including their gMSA configuration * **[Technologies, applications and tags](https://docs.2501.ai/0.19/core-concepts/hosts.md#technologies-applications-and-tags)**: the entries that describe hosts. A host only ever carries its own organization's entries * **[Agents](https://docs.2501.ai/0.19/core-concepts/agents.md)**: each agent belongs to its host's organization * **[Tasks](https://docs.2501.ai/0.19/core-concepts/tasks.md)** and **[Jobs](https://docs.2501.ai/0.19/core-concepts/jobs.md)**: execution history * **[Job Schedules](https://docs.2501.ai/0.19/core-concepts/job-schedules.md)**: recurring and deferred work * **[Tickets](https://docs.2501.ai/0.19/core-concepts/tickets.md)** and their comments * **Chats** and their messages * **[Gateways](https://docs.2501.ai/0.19/core-concepts/gateways.md)**: ticket routing integrations * **[Webhooks](https://docs.2501.ai/0.19/configure/webhooks.md)**: outbound notifications * **[Network Discovery](https://docs.2501.ai/0.19/configure/discovery.md)**: scans and the nodes they find * **[Knowledge](https://docs.2501.ai/0.19/configure/knowledge.md)**: uploaded documents and the host facts extracted from them ### Shared resources These resources can be scoped to a specific organization or left unscoped, which makes them available across all organizations in your tenant: * **[Credentials](https://docs.2501.ai/0.19/configure/credentials.md)**: authentication secrets * **[Specialties](https://docs.2501.ai/0.19/configure/specialties.md)**: agent domain configurations * **[Operational Rules](https://docs.2501.ai/0.19/configure/operational-rules.md)**: mandatory procedures * **[Blacklists](https://docs.2501.ai/0.19/configure/blacklist.md)**: prohibited commands * **[Plugins](https://docs.2501.ai/0.19/configure/plugins.md)**: MCP integrations and tools * **[Providers](https://docs.2501.ai/0.19/configure/providers.md)**: LLM endpoints, tenant-wide unless **Scoped to current organization** is ticked when creating one. [Models](https://docs.2501.ai/0.19/configure/models.md) belong to a provider and take its scope: an organization-scoped provider's models are available only to that organization * **API keys**: scope is chosen when the key is created and cannot be changed afterwards * **Verifier exceptions**: one tenant default plus one override per organization, managed by administrators When a shared resource is organization-scoped, only agents and operations within that organization can use it. When unscoped, it is available to every organization. An organization can also hold a credential with the same name as a tenant-wide one: the organization's own is used first and the tenant-wide one is the fallback, so a shared default can be overridden per organization. > [!NOTE] > > Creating or editing a tenant-wide shared resource requires [tenant-level access](https://docs.2501.ai/0.19/configure/users.md). Users restricted to specific organizations can read tenant-wide resources but only write within their own organizations. Tenant-wide providers and the model catalog are further limited to tenant-level administrators. Verifier exceptions are the one exception to the read rule: an organization-restricted administrator sees and edits only their organization's override, not the tenant default it replaces. ### Tenant-level resources These have no organization at all - they describe the tenant itself: * **Organizations** and **[Users](https://docs.2501.ai/0.19/configure/users.md)**, including which organizations each user belongs to * **[Licensing](https://docs.2501.ai/0.19/configure/licensing.md)**: plan and usage limits ## Creating Organizations Organizations can be created from **Command Center > Settings > Organizations**. Click **New Organization**, enter a name, and save. For the initial organizations at the first deployment, edit `organization.yaml` before deploying. See [Users & Organizations](https://docs.2501.ai/0.19/deployment/users-organizations.md) for the bootstrap workflow. ## Archiving Organizations Organizations are archived rather than deleted. In **Settings → Organizations**, a tenant administrator clicks **Archive** on an organization. An archived organization: * is hidden, and its members and organization API keys lose access to it * is read-only: its resources cannot be changed until it is unarchived * stops its running jobs and tasks * stops receiving tickets and alerts from its gateways and webhooks * pauses its schedules, which resume when it is unarchived Nothing is deleted. An archived organization's name is free for a new organization; if one takes it, rename one of the two before unarchiving. Archived organizations are listed under **Archived organizations**, where **Unarchive** restores them. A tenant always keeps at least one active organization. ![Archived organizations list with an unarchive action](https://mintcdn.com/2501/Nw-5R3i4HUHiTxUb/images/organizations_archived_019.png?fit=max\&auto=format\&n=Nw-5R3i4HUHiTxUb\&q=85\&s=eec6b6a6ebf406193eb8531b9f1952ad) The archived list keeps the organization visible to administrators and provides an unarchive action. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.