Assigning Partial Data Permission of a Data Table

Version

Application Scenarios

Using Permission of Public Data allows setting data table permissions for users separately.

However, sometimes it is necessary to assign different data permissions of the same data table to different users, so that different users can view different content in the same data table.

Functions

FineBI allows setting row and column permissions for public data tables.

• Row Permissions: Users are limited in using specified rows in the dataset by adding analysis, filtering, and other conditions.

• Column Permissions: Users are limited in using specified columns in the dataset by ticking the corresponding checkboxes.

Scope of row and column permissions: All datasets in Public Data

You cannot directly set row permissions for a folder, but only for a single dataset.

Note:

1. If you set row and column permissions for dataset A, dataset B created based on dataset A will be restricted by the row and column permissions of dataset A when Permission Inheritance is enabled. For details, see Permission Inheritance.

2. Row Permissions can be combined with login username field to bind permissions with system usernames. For details, see Viewing Corresponding Data Based on the Login User's Information — Example One.

3. When configuring adding conditions for Row Permissions, select In/Not in login user information, and you can select fields: system username, the user table in public data, one-end table of the user table, and N-end table of the user table (newly added N-end table).

4. Real-time data does not support cross-database fusion analysis. If the login user information field and the data table for setting row permissions are taken from two separate real-time data tables in different databases, row and column permissions cannot be set.

Row Permissions: Users are limited in using specified rows in the dataset by adding analysis, filtering, and other conditions.

For example, ordinary sales personnel hope to use data in the table BIdemo_Retail_Store Dimension for data analysis, but sales personnel are only responsible for sales in their own stores. Only sales managers are allowed to manage the stores.

Setting Row Permissions can allow only sales personnel to view and use partial content of certain fields.

Example:

Go to Public Data > Industry Data > Retail Industry. There is a data table named BIdemo_Retail_Store Dimension.

Assign the using permission of the data table BIdemo_Retail_Store Dimension to Salesman in Sales department. However, Salesman can only view and use the store data with Shop nature of Self-store.

Assigning Using Permission of Data

The admin logs into FineBI, goes to Manage > Permission > General permission configuration, and selects the permission carrier Dept./Role or users from User List.

This example selects Sales department > Salesman.

Click Data Authorization, and assign the Use permission of the BIdemo_Retail_Store Dimension data table to Salesman.

Setting Row Permissions

In this case, Salesman can use all the data in the BIdemo_Retail_Store Dimension table.

Click  beside the data table, and select Row Permissions.

Click Add Condition, add the Shop nature field, and select In(Field Value) and Self-store.

Demonstration

Salesman hanwen logs into the FineBI system, clicks Public Data > Industry Data > Retail Industry, selects the BIdemo_Retail_Store Dimension table, and can only view store data with Shop nature of Self-store.

Column Permissions can directly control whether personnel with corresponding permissions can use a certain field in the data table.

For example, ordinary sales personnel hope to use data in the table ENdemo_Store_Sales_Statistics for data analysis, but they do not need to view all gross profit data information of the company.

Set Column Permissions to revoke sales personnel's permission to view and use certain fields.

Example:

Go to Public Data > Industry Data > Retail Industry. There is a data table named ENdemo_Store_Sales_Statistics.

Assign the using permission of the ENdemo_Store_Sales_Statistics data table to Salesman in Sales department. However, Salesman cannot view the data of the gross profit column.

Assigning Using Permission of Data

The admin logs into FineBI, goes to Manage > Permission > General permission configuration, and selects the permission carrier Dept./Role or users from User List.

This example selects Sales department > Salesman.

Click Data Authorization, and assign the Use permission of the ENdemo_Store_Sales_Statistics data table to Salesman.

Setting Column Permissions

In this case, sales department employees can use all data of the ENdemo_Store_Sales_Statistics table.

Click  to go to the detailed permission settings interface, and select Column Permissions to display all data tables and fields that sales personnel can use in this business package.

As ordinary sales personnel do not need to view gross profit data, untick the gross profit field, and click OK to save.

Demonstration

Salesman hanwen logs into the FineBI system, clicks Public Data > Industry Data > Retail Industry, and selects the data table ENdemo_Store_Sales_Statistics.

Due to the field restriction set in Column Permissions, hanwen can only view sales data excluding gross profit.

Data Showing ***

The admin creates a dashboard based on the data table ENdemo_Store_Sales_Statistics, and mounts it in the directory that hanwen has permission to view.

When the table component in the dashboard lacks column permissions, the field in the table under that column displays ***. If the chart component loses column permissions, it will prompt: You are currently not authorized to view the component data. An error has occurred, please contact the administrator.

After setting column permissions, hanwen does not have the permission to view the gross profit field, and the dashboard is displayed as shown in the following figure:

Moving a Data Table

• If the permissions of the data table were separately configured before the move, the permissions will remain unchanged after the move.

• If the permissions of the business package and group that store the data table are inherited before the move, the new parent permissions will be inherited after the move.

• Moving a data table does not change its configuration of Row Permissions, while Column Permissions follows the above rules.