Manage content deployed in tenant organizations

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

After documents and folders are deployed to tenant organizations, manage the deployed files.

Recreate settings after deploying documents

After a deployment runs to deploy documents and folders to tenant organizations, you might need to recreate configurations:

Materialization schedules are not recreated in deployed documents. If you want to continue materializing data in a deployed document, set up a materialization schedule in each tenant organization. See Schedule materialization for a data model or workbook.
Warehouse views are not recreated in deployed documents. If you use warehouse views in a deployed document, set up a new warehouse view in each tenant organization. See Create and manage warehouse views.
Scheduled exports are not recreated in deployed documents. If you want to continue exporting content from a deployed document on a schedule, recreate the export. See Send or schedule workbook exports.
Links between tables in your data platform are not recreated in a tenant organization. If you use links between tables and those links are not automatically created by primary key / foreign key pairs, recreate the links in the tenant organization.

If you deploy a workbook that uses a stored procedure action, the stored procedure action might fail to run if the stored procedure is not available on the tenant connection. You might need to manually sync the schema that contains the stored procedure in each relevant tenant connection.

To perform a sync in the Sigma UI, see Manually sync your data. To perform a sync programmatically with the API, see Sync a connection by path.

Review deployment status and errors

After deploying documents to a tenant organization, identify any issues with the deployment:

Review the status of each deployed file in the Documents section of the Details tab. If any documents fail to deploy, the Status column displays an error. Review the Deployed version column to identify which version was deployed to tenant organizations.
Review the status of deployments for specific tenants on the Deploy to tab. If a deployment was unsuccessful to a specific tenant, the Status column displays an error. The Last deployment started and Last deployment ended columns show when each deployment ran.
Review all errors on the Errors tab.

Status of a deployed file

In the Documents section of the Details tab, review the Status column to identify deployment errors for a document in the deployment policy:

Status	What it means
Deployed successfully	The document or folder deployed to all tenants in the policy with no errors or warnings.
This file has errors	The document or folder failed to deploy. Select the status to open the Errors tab filtered to this file.
This file has warnings	The document or folder deployed, but something needs attention. Select the status to open the Errors tab filtered to this document.
Dependency errors or warnings	The document or folder deployed successfully, but a document it depends on has an error or a warning. For a folder, a document inside the folder has an error or a warning. Select the status to expand the row and identify the relevant document.
Not deployed	The deployment policy requires a version tag and this document has no version tagged with it, so the document and its dependencies did not deploy. If the untagged file is a dependency, tag the document that uses it instead.

If documents fail to deploy to a tenant:

If the deployment policy requires documents to be tagged with a specific version tag, confirm that the document is tagged with the correct version tag.
Confirm that the connections, source swap policy, and user attributes for the deployment policy and associated tenants are properly configured. A connection must be set up, and the connection sync must complete, before documents can be deployed. Source swap policies must exactly match connection configurations in the source and target organizations.
Confirm that the tenant organization configuration matches the parent organization, and any links between tables, user attributes used by custom SQL statements, and stored procedures used by actions in deployed documents exist in the tenant organization.
Review the Errors tab for a specific deployment policy to identify any issues with the deployment.

For example, identify and repair errors like the following:

A data source in a deployed document uses a connection that is not mapped by the source swap policy associated with the deployment policy. Resolve the error by reviewing source swap policy configuration:
- Determine whether the user attribute is assigned to all the tenants in the deployment policy.
- Determine whether the connection in the parent organization is mapped by the source swap policy.
- Determine whether the connection names or IDs match the connections defined in the parent and tenant organizations.
The deployment policy requires a version tag, but a document in the deployment policy does not have a version tagged with that tag. Resolve the error by doing one of the following:
- Remove the document from the deployment policy.
- Tag a version of the document with the relevant version tag.

After making changes to address the errors, redeploy to a tenant. After updating the deployment policy, review the Errors tab to confirm that no errors appear.

Redeploy to a tenant organization

To redeploy documents and folders to a tenant organization:

In a deployment policy, select the Deploy to tab.
Locate the tenant to which you want to redeploy files.
For the tenant, select More, then select Redeploy to tenant.

The files in the deployment policy are redeployed to the tenant organization.

Manage access to deployed documents

To grant access to the deployed workspace, or specific deployed documents to users or teams in a tenant organization:

Review the access model for folders and documents. See Folder and document access.
Follow the steps for sharing content:
- Share a document, such as a workbook, report, or data model. See Share a workbook, data model, or report.
- Share a folder or workspace. See Share a folder or workspace.

Modify deployed documents

Users in tenant organizations cannot directly edit documents deployed to the tenant.

Instead, users can save a copy of the document, or set a tag on a document version:

Save a document as a new document (workbook, report, or data model) to make changes to the document.

After saving a deployed document as a new document, it is no longer updated by future deployments.
Tag versions of a workbook, report, or data model. See About version tags to workbooks, data models, and reports.

Delete deployed documents

You cannot delete the deployed workspace, or documents deployed by a deployment policy, in a tenant organization. Instead, do one of the following:

Delete the document from all tenants added to the deployment policy by removing the document from the deployment policy.
Delete the workspace and all documents in the workspace from one tenant by removing the tenant organization from the deployment policy.
Delete the workspace and all documents in the workspace from all tenants by deleting the deployment policy.