How Data Source Permissions Are Determined

This applies to: Visual Data Discovery

By default, the creator of a data source configuration always has Data Access, Read, Write, and Delete permissions until those permissions are changed by an administrator or someone with appropriate authorization to change source permissions. If a user is removed from the Symphony environment, data sources created by that user are retained and the supplied Supervisor user becomes the creator of these orphaned data sources.

The default supervisor user is no longer installed; add users to the Supervisors group instead.

Data Access is a separate permission for data sources. It can be set directly on data sources for users, groups, and accounts, and is enabled for users, groups, and accounts when you assign Read permission for a visual that uses that data source. Unless they are granted Read permission to the source as well, they can't see the data source listed on the Source page, or select the source to create a new visual (for users with the Create Visuals or Administer Visuals  privilege).

If conflicting data sources permissions are specified for the account, the group within the account, and the user within the account, the permissions granted to the users are determined using a most permissive model. Users are granted the highest level of permission specified for the account, group, and user. For example, if the account is granted read and write permissions, but Group A is granted write and delete permissions, users in Group A will be able to read, write, and delete the data source. However, users in any other groups in the account will only be able to read and write the data source.

Here's another example. If the account is granted data access, read, write, and delete permissions, but the groups are only granted data access permissions, all users in the account will have data access, read, write, and delete permissions for the data source.

If you try to delete a visual, dashboard, dashboard link, data source, or data source field, Symphony displays an error message naming any objects dependent on the item you’re trying to delete. You can delete the item after you’ve removed the association from the dependent object.