# How tenants & workspaces are structured ### Overview Agentic Studio is organized into two levels of structure, tenants and workspaces, that together define how users, Digital Workers, and resources are separated and shared across an organization. Understanding this structure is important for anyone configuring, managing, or deploying Digital Workers at scale. ### Tenants A tenant is the top-level organizational unit in Agentic Studio. It represents a discrete deployment environment, typically corresponding to a company or a major organizational boundary, and contains everything associated with that environment: workspaces, users, connectors, and Digital Worker assets. Resources and data are isolated at the tenant level. One tenant cannot access the assets or configurations of another. Within a tenant, certain assets have visibility across all workspaces. Templates exported by users from any workspace within a tenant are visible to all other workspaces in that same tenant. This makes it possible to standardize and share Digital Worker patterns across teams without duplicating effort. ### Workspaces A workspace is a scoped environment within a tenant where Digital Workers are built, tested, and deployed. Each workspace provides an isolated context for development work, with its own Digital Workers, tools, skills, and configuration. Workspaces are where the day-to-day work of building and managing Digital Workers happens. Teams can operate within a workspace without affecting other workspaces in the same tenant, which supports parallel development and clean separation between different business functions, products, or use cases. ### Test and Production Environments Within each workspace, Agentic Studio maintains a clear separation between the test environment and the production environment. The test environment is the default working state. It is where Digital Workers are configured, evaluated, and refined before release. All changes to instructions, tools, skills, triggers, and settings are made in test. This keeps iteration separate from live operations and ensures that nothing reaches production without going through a deliberate release step. The production environment hosts deployed Digital Workers that are available for live use. Once a Digital Worker is promoted to production, it operates as a stable runtime artifact and is not directly editable. Any further changes are made in the test environment and promoted through the same controlled release process. This separation reduces the risk of accidental changes to live workers and provides a clear, auditable path from development to deployment. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://kb.theloops.io/agenticstudio/resource-library/hidden-fundamentals/how-tenants-and-workspaces-are-structured.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.