> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://help.sigmacomputing.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.sigmacomputing.com/_mcp/server.

# Sigma Tenants (Beta)

This documentation describes one or more public beta features that are in development. Beta features are subject to quick, iterative changes; therefore the current user experience in the Sigma service can differ from the information provided in this page.

This page should not be considered official published documentation until Sigma removes this notice and the beta flag on the corresponding feature(s) in the Sigma service. For the full beta feature disclaimer, see [Beta features](/docs/sigma-product-releases#beta-features).

Sigma supports multitenancy with Sigma Tenants, allowing you to manage users and resources across multiple Sigma organizations. You might need to separate organizations by region, business unit, environment (development, staging, production), or by customer to isolate data and users.

Sigma Tenants lets you create multiple tenant organizations and manage those tenants separately and independently. A parent organization can coordinate sharing settings and documents to tenant organizations. Meanwhile, tenant organizations, their users, and their connections are completely separate from each other.

This is a premium feature. To enable it for your Sigma organization, contact your Sigma Account Executive.

The use of multitenancy is subject to the following [disclaimer](/docs/notice-for-the-use-of-multitenancy-in-sigma).

## What's possible with Sigma Tenants

* **Management capabilities:** Provision tenants from a parent Sigma organization. See [Create and manage tenant organizations](/docs/create-and-manage-tenant-organizations).
* **Configure tenants:** Set up tenant organizations with dedicated configurations, such as authentication methods, connections, themes and branding, and other settings separate from the parent organization and other tenant organizations. See [Create and manage tenant organizations](/docs/create-and-manage-tenant-organizations).
* **Share content:** Define deployment policies to manage which documents to deploy to which tenants, and automatically swap sources of the documents to tenant-specific connections. Optionally enable users in tenant organizations to deploy content to other tenant organizations. See [Deploy content to tenant organizations](/docs/deploy-content-to-tenant-organizations).

For example, address the following use cases:

* A software development lifecycle (SDLC) use case
* Collaborating business units with a parent company
* Embed content for individual customer tenants (managed service provider)
* Comply with data sovereignty requirements

For end-to-end examples for these use cases, see [Deployment use cases and examples](/docs/deployment-use-cases-and-examples).

## Related resources

* [Deploy content to tenant organizations (Beta)](/docs/deploy-content-to-tenant-organizations)
* [Sigma Tenants deployment use cases and examples (Beta)](/docs/deployment-use-cases-and-examples)
* [Deploy content from one tenant organization to one or more tenants (Beta)](/docs/deploy-content-from-one-tenant-to-other-tenants)
* [Deploy content from a parent organization to one or more tenants (Beta)](/docs/deploy-content-from-parent-organization-to-tenant-organizations)
* [Embed content from a tenant organization (Beta)](/docs/embed-content-from-a-tenant-organization)