In Metric Insights, content security is achieved through organizing Users into Groups, each assigned distinct access levels. Administrators grant specific Privileges and Permissions to each Group, thereby controlling access to designated areas of content. Establishing this security model requires Administrators to complete a series of configuration steps.
Please follow this detailed playbook to configure your organization's security framework in the most efficient manner.
1. Assign Privileges to Groups
Rather than assigning Privileges individually to each User, it's recommended to create a Privilege Set. By default, Metric Insights provides several pre-configured Privilege Sets for Regular and Power Users, which you may also utilize.
To understand the full range of Privileges available in Metric Insights, please refer to the Privileges List.
2. Give Access to Content
To view and interact with Elements and Datasets, Users must be granted the corresponding Permissions. Open the Group Editor and assign all the necessary Permissions.
Afterward, give the Groups access to corresponding Categories.
2.1. Optionally, Sync Tableau Permissions
If your organization uses Tableau, you can sync user access rights for Tableau content using a custom script. Users and Groups that have access to content in Tableau will receive the same access to that content in Metric Insights, as long as the content has been recreated in Metric Insights.
For details, see Sync Tableau User/Group Permissions with Metric Insights by Using Custom Script.
2.2. Optionally, Sync Power BI Permissions
Metric Insights uses a dedicated System Object to bring in user permissions defined in Microsoft Power BI. System Objects are Power BI datasets that Metric Insights retrieves to enable usage tracking, governance, and lineage analysis. The User Permissions Dataset plays a central role in BI Optimizer’s governance and content cleanup functionality.
For details, see Configure System Objects for Microsoft Power BI Cloud.
3. Manage Access Requests for Content
If Users don't have access to a specific Element or Object, they may submit an Access Request.
All Access Request Processing options are outlined in the Access Request Overview article.
4. Optionally, Apply User Maps
A User Map defines what access each User in a list has and what Values are set as a default for each specific User.
Use an option which is best suited to your needs:
- Dimension-Level Security: By applying a User Map to a Dimension, you can control which specific Dimension Values each User or Group is allowed to see. For more information, refer to the Applying User Map to a Dimension article.
- Row-Level Security: This approach restricts data at the row level in the underlying Dataset, granting Users/Groups access only to the rows that match their assigned values. For setup details, refer to the Creating a User Map article.
5. Check Access
Once all access rights have been granted, verify what the Users have access to. Administrators and Power Users can log in as different Users to confirm they have access to the necessary Categories and Elements.
Please refer to the Logging in to Different User's Account article for details.