Manage deployed content

After content is deployed to tenant organizations, manage the content.

Recreate settings after deploying documents

After a deployment runs to deploy content to tenant organizations, you might need to recreate configurations:

• Contents of input tables in deployed documents are not copied over. Any input table in a deployed document is empty in a tenant organization.
• 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.

🚩

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, 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.

• 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 fixing the errors, update the deployment policy to trigger a deployment. For example, remove and add the same source swap policy. After updating the deployment policy, review the Errors tab to confirm that no errors appear.

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 or data model. See Share a workbook or data model.
  • 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 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 or data model. See Add version tags to workbooks and data models.

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.