Set access to folders and visualizations
A member needs permission to open a shared visualization and permission to read its underlying data. Configure these separately: access to a diagram does not grant access to every asset it contains.
Fine-grained content permissions depend on your plan. Administrators and the Owner configure roles and domains. Editors can change a shared item's domains when their permissions allow it.
Choose the required access
In the rights editor, open a role or domain and select Folders and visualizations. Set the relevant domain/role cell, then use Review and save > Save changes.
| Level | What it authorizes |
|---|---|
| None | No access through this role/domain combination |
| View | Open the content |
| Edit | Edit the content, including its name |
| Delete | Delete it, in addition to editing |
| Change access domain | Change its assigned domains, subject to destination permissions |
The highest applicable permission wins across the member's roles and the item's domains. None does not cancel a permission granted elsewhere. User type remains a separate limit: a Viewer does not become an Editor through this table.
Without fine-grained permissions, Viewers can view shared content; Editors and higher user types can manage it. The domain-editing dialog is unavailable.
Change an item's domains
- In the shared tree, open the folder's Actions menu using its three-dot button. For a visualization, open its Actions menu.
- Choose Update access domains.
- In Access domains, select the intended domains and remove those that should no longer apply.
- For a folder, read any warning listing children with different domains.
- Click Update.
- Check the result with a member who has the intended role, including the data shown inside the visualization.
You need Change access domain on the item's current scope. Adding a domain also requires at least Edit on each added domain. Removing one requires Change access domain on each removed domain.
Leaving the list empty requires Edit on No access domain. Otherwise, at least one domain is required. No access domain applies to unassigned content; it is not a business domain to select in the list.
Adding a domain can broaden access. To remove access, review every remaining domain and role that could still grant it. Use permission diagnosis before changing a whole role for one item.
Folder placement and visibility
A folder and its children each have their own domains. A folder's domains may prefill a newly created item's form, but subsequent folder changes do not update its children.
For example, a folder may use Architecture while a diagram inside it uses Commerce. A Commerce member could have permission to open the diagram through a direct link, yet miss it in the tree because the folder is inaccessible. Check the folder path as well as the diagram.
Changing a visualization's domains within a scenario belongs to that scenario's changes. Folder domain changes are unavailable in a scenario: return to the real repository to change the folder.
Personal content and sharing
Personal content belongs to its author. Changing business permissions does not turn it into shared content, and Administrator status does not automatically reveal another member's personal space.
Use moving and copying to put personal content in the shared catalog. Review the destination and domains during that operation. A sharing link is a separate access path with its own configuration.
After changing permissions, ask the recipient to refresh and check the tree, direct opening, available editing commands and visible data. A successful check with your administrator session alone does not prove the recipient has the intended access.