Deploy content to tenant organizations

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

You can deploy documents and folders to tenant organizations from parent organizations or other tenant organizations. Documents deployed to a tenant organization are automatically updated when the source document is published (or a new version is tagged) in the source organization, and cannot be edited in the receiving tenant organization.

A deployment policy defines which documents and folders get deployed and how to swap the data sources used by deployed documents. You can create multiple deployment policies to manage which documents and folders to deploy to which tenants, and tenants can receive documents and folders from multiple deployment policies.

Each deployment policy creates a workspace in each tenant that receives the deployed documents and folders, so you can manage user access to deployed files by changing permissions on the workspace in the tenant.

What gets deployed to a tenant

Sigma supports sharing documents (workbooks, reports, and data models) with the following contents:

Custom functions
Plug-ins (workbooks only)
Input tables (workbooks only), see How input table data is deployed for more details.
Stored procedure actions (workbooks only)
Metrics, relationships, and column-level security settings (data models only)

Explorations are not deployed. Saved and custom views are not available in tenant organizations.

In addition, documents used by the deployed document are also automatically deployed:

Data models and datasets used as data sources of deployed documents. Data models deployed as data sources of workbooks are visible in tenant organizations, but datasets are unavailable for use.
Documents that are the destination of an Open Sigma doc action in a deployed document. The action is updated to use the deployed document in the tenant organization.

You can visualize these deployed dependencies in the deployment policy.

How dependencies are deployed

When you deploy a document that relies on another document, such as a workbook with an action to navigate to another workbook, or a report that uses a data model as a data source, the dependent documents are also deployed.

By default, those dependent documents are deployed into the same workspace as the documents directly added to the deployment policy.

If you want to keep dependencies separate from deployed files, turn on the Separate dependency workspace toggle on the deployment policy. A separate dependency workspace lets you grant users access to the deployed documents without also granting access to the data models and other files those documents depend on. See Manage access to deployed documents.

Sigma then deploys those dependencies into a second workspace in each tenant, named for the deployment workspace followed by Dependencies. For example, a deployment policy that creates a Starter pack workspace also creates a Starter pack Dependencies workspace.

If a dependent document is also deployed directly as part of the deployment policy, it is not added to a separate workspace. For example, if you deploy a folder with two workbooks, and one workbook includes an action to navigate to the other workbook, both workbooks are deployed to the same workspace.

How folders are deployed

When you add a folder or workspace to a deployment policy, Sigma deploys the folder and the workbooks, reports, and data models it contains, including nested subfolders. Archived documents and other files, such as explorations or shortcuts, are not deployed.

After adding a folder or a workspace to a deployment policy, documents that you add to the folder are deployed without any changes to the policy. If you remove a document from the folder or archive it, the document is no longer deployed and is removed from tenant organizations.

If the deployment policy requires a version tag, each document in the folder must have a version tagged with that tag to be deployed. Folders and workspaces are not versioned, so you cannot tag a folder to deploy its contents as a set. Dependent documents do not need to be tagged.

When a deployment might fail

If a document contains any of the following, the document might fail to deploy:

Links between tables in your data platform. Links between tables in your data platform must be recreated in the tenant organization.
Custom SQL statements that reference user attributes. User attributes referenced in the document must exist, have a default value, and be assigned in the tenant organization. See Configure user attributes.
Tables created from CSV uploads. Instead, create an input table from CSV to use as the source. See Create a CSV input table.
Document tabs with custom page visibility defined. The teams used to restrict page visibility must be created with the same names in the target organizations.

If a workbook contains any of the following, the document might not work as expected in a tenant organization:

Sigma agents with warehouse agents or MCP tools
Call API actions

After a document is deployed, it is automatically updated when the source document is published or a new version is tagged. A deployed document cannot be edited in the tenant organization, but users with the relevant permissions can save a deployed document as a new document in the tenant, or create workbooks that use deployed data models as a data source.

Additional limitations apply when deploying documents. Review Recreate settings after deploying documents.

Manage deployed documents

Before you deploy documents to a tenant organization, make sure that each tenant organization has a connection to one or more data sources, and that the connection has been synced.

How input table data is deployed

When a deployment policy contains one or more documents with an input table, the data entry permissions set on the input table and the option enabled on the deployment policy manage whether the input table data is included when the document is deployed:

Data entry permission	Copy input table data toggle	Details
Editable in draft	Copy input table data toggle turned on	Input table rows from the document in the parent organization are copied to the deployed document when the document is published.
Editable in draft	Copy input table data toggle turned off	Empty input table is copied, and structure of the input table is updated when the document is published. Users in the tenant organization cannot add data to the input table of the deployed document.
Editable in published version	Any	Empty input table is copied, and structure of the input table is updated when the document is published or tagged. Users in the tenant organization can add data to the input table. If you change the data structure, for example by deleting a column, the data in that column is deleted.

If you change the data entry permission of the input table after deploying the document, the following happens:

If you change from Editable in published version to Editable in draft, the data in the input table in the deployed workbook is replaced with the data from the parent organization.

The data in the input table in the deployed document on the tenant organization is deleted and cannot be recovered.
If you change from Editable in draft to Editable in published version, the input table data included when the document was originally deployed is not deleted, and users in the tenant organization can make changes to the input table and its data. If you want to remove data from a deployed input table, you must delete the data in the source document and then publish or tag the document to deploy the empty input table.

When data in an input table is copied to tenant organizations, it is written to a Sigma-owned S3 bucket and deleted within 2 hours. Data is only accessible to the parent organization and its tenants.