FineBI Version
Functional Change
6.0
/
It is inconvenient for you to assign permissions based on Dept. or Role when you meet the following scenarios:
Some users need to temporarily view a certain template.
A Leader who holds multiple positions has permissions to view some templates, but their department and roles do not have such permissions.
It is necessary to create a corresponding role before assigning report permissions to specific individuals.
In this case, permissions can be assigned individually to certain special personnel (users), without the limitations of Dept. or Role.
Here, users refer to those who have been added in the platform.
Admins log into FineBI and go to Manage > Permission > General permission configuration > User final authority to assign permissions for users.
Admins log into FineBI and go to Manage > Permission > General permission configuration > User final authority. All users who can be assigned permissions are listed.
All users are displayed by default. You can also click to filter part of users.
Note: Departments and directories are displayed in a tree structure. You can click to view specific positions and templates.
For users who are not assigned permissions separately, they will inherit the permission union of Dept., Role, and Position.
For users who are assigned permissions separately, child templates will inherit the permissions set in parent directories.
For instance, the user Lisa belongs to sales department, which has the permission of viewing the directory Business Application.
Click User final authority > Lisa (Lisa) and you can view that Lisa has the permission of viewing the directory Business Application. The permission is from Dept. > Sales department.
Admins can assign permissions for each user separately.
Click Manage > Permission > General permission configuration > User final authority and assign permissions for users.
After you finish the settings, there will be indicating that the user is assigned permissions separately and indicating that the permission is assigned for its parent node.
Note:
1. There will be icons so long as you change permissions.
2. So long as there still are icons, the user will inherit permissions assigned separately, rather than permissions of Dept. and Role, no matter whether they are consistent with each other.
3. You can also assign permissions separately for users and restore permission inheritance in Manage > Template Authentication > Role.
Note: It is only available for the super admin.
The super admin can click Restore Inherited Permissions to clear all individual permissions and restore permissions from Dept. and Role.
The super admin can click beside some node to clear all individual permissions and restore permissions from Dept. and Role.
Note: Provided that a user has permissions of both the parent node and the child node:
1. The system will restore inherited permissions of the parent node and will become if you only click beside the child node.
2. The system will restore inherited permissions of both the parent node and the child node if you click beside the parent node.
Because an employee may have multiple departments, positions, or roles and there are hierarchic structures among departments, you need to follow relevant permission logic when assigning permissions.
Scenario One
If you have assigned individual permissions for some user, a prompt will pop up when you assign different permissions for the user's department and role.
Click the link in the prompt, jump to the new tab in a browser to open the permission page, and you can view/restore the user's permission.
Scenario Two
If you have firstly assigned permissions of a child node for a user, then permissions of the parent node for the user's child department, and lastly permissions of the child node for the user's parent department, a prompt will pop up when you cancel the permissions of the parent department for the child node.
滑鼠選中內容,快速回饋問題
滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy