This page is used for making adjustments to features and functions that affect the way content is stored in the system.
This feature is only available with the Enterprise edition.
Cross Tenant Options
The user-role-tenant model in Pyramid uses the classic multi-tenant approach: users, content and data within a tenancy cannot be accessed by other users in another tenancy. However, this can be altered with "Cross Tenancy" options.
- To lean more about cross tenant content, click here.
This setting allows Enterprise Admins to assign public content to users from different tenants.
Check the option to 'Enable cross tenant content,' and click Apply to save changes.
Allows Enterprise and Domain Admins to assign users from different tenants to roles in another tenant, enabling Admins to grant specified users access to content from multiple (or all) tenants.
Check the option to 'Enable cross tenant user roles,' and click Apply to save changes. Once cross tenant user roles have been enabled, Admins will have the ability to assign multiple roles from different tenants to users in different tenants from the Roles panel.
- For more information about roles, and assigning multitenant roles, click here.
Cross Tenant Content vs Cross Tenant Roles
Cross tenant content is useful for having the same content seen and accessible by different tenants without having to create duplicates. It works by explicitly adding multitenant roles to content or folders and can only be set and managed by ENTERPRISE admins.
Cross tenant roles, on the other hand, delivers similar functionality to cross tenant content, by allowing users to join roles outside of their own tenant - but the settings are attached to the role, rather than the content. As such, it can be extended to data security and any future content and it allows DOMAIN admins to add and remove users, from outside their domain / tenancy, to existing roles without Enterprise admins. This is useful for on-going management of common content and data elements in a deployment at the domain level.
You can also opt to disable folder creation at the top level of the public content domain, in order to more easily govern folder creation.
Select 'Disable write capability privileges for non enterprise user' to disable the ability of users and domain admins to create new databases on the server. Only the enterprise admin will be able to create new databases on the server if this option is selected.
Workflow settings controls access to built-in "Conversations" and other custom workflow applications added to the application.
Conversations , the standard built-in workflow, enables users to write comments and annotations into visualizations, reports and dashboards by starting new threads with one or more users in the system. Custom workflow templates can also be added by developers to use the same infrastructure for other purposes beyond conversations and annotations.
This feature is available in the Enterprise Edition only.
- Enable Workflows: By default, workflows are not enabled. Check the box to enable workflows and the built-in Conversations tools.
- Enable Workflow Snapshots: By default, workflow snapshots are disabled. Check the box to enable snapshots. Workflow snapshots enable users to store query results and the underlying report structures at the time a workflow is started. Workflow participants can then load the snapshots back to view the exact query results and/ or structure at the time the original workflow was submitted. Click here to learn more about snapshots.
- Enable Workflow Templates: This allows developers to load custom workflow templates into the system to supplement the built-in Conversations workflow. Access to the templates in the system is governed by the permissions setting (see below).
- Polling Interval: The Polling Interval is the frequency at which clients are updated with changes in the workflow threads. By default, this is set at 60 seconds. Setting the polling rate too low can have a negative impact on performance.
If custom workflow templates are added to the system, administrators can elect how the custom templates can be accessed.
- Allow All Templates: all custom templates, including the built-in conversation option are universally available
- Templates by Model: each custom template and the standard Conversation workflow need to be enabled for each data model deployed. Since each data model is governed by Tenancy and Role access, this option offers granular control over which users will see which workflow template.
Use this switch to enable or disable the background "snapshot" engine. Snapshots are used in the system to create miniature thumbnail images for use the content management tools and UI. They greatly help users identify content using a visual cue. Disabling this feature will prevent thumbnails from being rendered.
Admins can elect to let "viewer" users see Publish templates in their content explorer tools. When the viewer clicks on the item they are given the opportunity to subscribe to that publication (like a Discover or Present item). By default this option is off.
To secure which Publish templates are exposed to viewers, content developers should ensure the blue publish templates are secured appropriately in the content system and its folders.