Create a User Map (Apply Row Level Security)
The Dataset creator can grant access to the specific slices of data (rather than the entire Dataset), aka RLS Row Level Security. This is accomplished via a User Map. The User Map restrictions will also apply to any Reports created from this Dataset.
To understand the Privileges and Permissions Users must have to work with Datasets , see Security section for Datasets
What is a User Map?
In the image below:
- All Data / Dataset: Contains the all the data available to create content from a Dataset. In this example, there are 3 columns of data (country, channel, total order volume)
- User Map: Allows you to grant Users access to limited amount of rows (RLS Row Level Security). It must contain a column with usernames and specific values in the Dataset columns to filter data to a relevant subset. A User Map dimensions the result set with ALL information and makes different mappings available to the designated users.
In this example, User access is restricted to specific Countries. If the User Map is applied to a Dataset, all included users will not see the Dataset with ALL available values but will view the Dataset differently according to the User Map restrictions. The same rules apply to elements created from this Dataset.
In the example below, both Country AND Channel is mapped to the Dataset in order to further restrict the results that are available to each user.
2. [Info tab] Define the basics
- Create a unique and descriptive Name for your User Map
- Save and proceed to the Data tab to define user access
3. [Data tab] Fetching / Uploading data: CSV file example
- Data Source: Select the method of collecting the data for User Map. In this example, data is uploaded via 'CSV or Excel file'. When this method is selected, click Load data below this field and define a date for which you are adding data to the Dataset.
- The Load From File pop-up opens.
- Confirm that the Delimiter character is the same as in your CSV file
- Click Browse and select the CSV file containing data for the User Map. This file must contain a column with usernames and a column (or several ones) with values to which respective users may have access.
Starting in Version 6.2, Metric Insights introduced Wildcard Entries functionality. To learn more, see Wildcard Entries in User Maps
3.1. Successful upload
If the file data is successfully processed:
- A Dataset Columns table with respective values is displayed below
- Validation Rows Preview section displaying the values uploaded pops up at the bottom of the screen
- Dataset User Name Field: select the name of the column which lists usernames in this field
4. [5.6+] User Map as a source of Filter defaults
This functionality is supported for External Reports only.
In addition to access constraints, a User Map can work as a source of Filter presets for External Report data. This means that viewing defaults can be configured for multiple Users with a single User Map.
For more information on pre-filtering, refer to:
In order to set User Map as a source of Filter defaults:
- Go to External Report Editor > Configuration tab
- Manage Filters section > select Apply based on User Map
- Choose a User Map with presets to specific Filters/Filter Values
- Map Filters to available User Map Columns