Permission Inheritance

Version

Application Scenarios

When row and column permissions are set for a table, you can enable Permission Inheritance for the self-service dataset made by the table. In this way, the self-service dataset automatically can inherit the row and column permissions of the parent table without the need for additional settings, which is more convenient.

Therefore, when the sub-table permissions match the parent table's row and column permissions, you can use Permission Inheritance.

Functions

Self-service datasets can be configured to enable or disable Permission Inheritance:

Enable Permission Inheritance: You can directly inherit the row and column permissions of the parent table, without the need to set separately.

Disable Permission Inheritance: The row and column permissions of the parent table will not be inherited, but you can individually configure for this table in Permission.

The table BIdemo_Estate_Product Dimension has two sub-tables: Inventory Data Analysis and Project product sales data.

Setting Row and Column Permissions

The admin assigns the usage permission of the folder Real Estate to Haley and clicks  in the table BIdemo_Estate_Product Dimension to configure row and column permissions.

Set Haley to only be able to see data that belongs to House.

Enabling Permission Inheritance

Enable Permission Inheritance to the sub-table Inventory Data Analysis.

Note: Users with the management permission of Inventory Data Analysis can enable or disable Permission Inheritance.

Log into Haley's account, and you can only see data that belongs to House. The default password for built-in sample accounts is 1.

Disabling Permission Inheritance

Log into an account with management permissions to disable Permission Inheritance for Inventory Data Analysis.

Log into Haley's account again, and you can view that the table does not inherit row permissions from the parent table. Haley can see all types of data.

In this case, admins can assign row and column permissions separately to Inventory Data Analysis.

Invalid Associations After Reenabling Permission Inheritance

You cannot enable Permission Inheritance and set associations manually in a self-service dataset at the same time.

When Permission Inheritance is enabled for a self-service dataset, any previously manually set associations will be automatically removed.

Click the enabling button of Permission Inheritance, and a prompt will pop up: Enabling permission inheritance will invalidate the added association. Are you sure to enable permission inheritance?

2）Click OK. Permission Inheritance is enabled and manually set association is invalid.

Limited by Permissions of the Creator

If the creator of the self-service dataset only has permissions for partial data, the intersection of the viewer's and creator's permissions will be taken.

For example:

1. Eoco has permissions for the data of Australia, America, and Britain in table A. He uses this table to create a self-service dataset and publishes it to the Public Data.

2. The admin assigns row and column permissions to Alice. Alice has access to the data of Australia, America, and Canada.

3. The admin also grants Alice Permission Inheritance for this self-service dataset.

4. Log into Alice's account, and you can see that Alice can only see data from Australia and America in this dataset.

Adding Fields with Row and Column Permissions to Group Box

There are two points to note when inheriting permissions in extract data:

When you create a self-service dataset with Group Summary, the fields with row permissions must be added to the grouping box. After you have enabled Permission Inheritance, self-service dataset will have data, otherwise it will be empty.

Establish a relationship between table A and table B: A table:B table=1:N. When setting row permissions for table A and adding Group Summary in the created self-service dataset through table B, you need to add the fields with row permissions to the grouping box. After you have enabled Permission Inheritance, the self-service dataset will have data. Otherwise, the self-service dataset will display as empty.

Empty Dataset After Up and Down Merging

Use a table with row permissions to create a self-service dataset that includes Group Summary and Up and down merge. Enable Permission Inheritance. In this case, the self-service dataset will always show empty no matter how it is configured.