The Permission Management page is used to configure agent frontend usage permissions and admin console operation permissions for specified users, implementing fine-grained permission control.
The platform supports the following two permission configuration methods:
Unified assignment: Enable permissions for a department, position, or role, allowing users under the corresponding department, position, or role to inherit the related permissions.
Separate assignment: Users inherit the permissions of their departments, positions, and roles by default. To add or adjust specific permissions for a user, you can switch to Set Separately for the corresponding permission resource.
(1) You are advised to preferentially assign permissions by department, position, or role, and use Set Separately only when specific users have special permission requirements, to reduce permission maintenance costs.
(2) Different permission resources for the same user can have different permission sources. For example, the Skill permission is inherited from a department, position, or role, while the Agent permission is set separately.
Dora Version
Functional Change
V0.6
/
V1.5
Allowed permissions to be assigned by department, position, role, and user.
Log in as a super administrator and choose Admin Console > Permission Management to assign permissions by department, position, role, and user on the platform.
The page is divided into an authorization object selection area and a permission configuration area:
The left area is used to select a department, position, role, or user.
The right area is used to configure the Agent Frontend Usage and Admin Console permissions for the selected object.
You can quickly locate the permissions you need to configure using the permission resource search box.
Switch between different tabs on the left side of the page to locate the object you want to authorize.
Authorization Object Type
Selectable Object
Department/Position
Role
User
Users, namely, platform members
To uniformly assign permissions to a category of users, you can follow the following steps:
(1) Switch to the Department/Position or Role tab on the left.
(2) Select the department, position, or role to be authorized.
(3) Switch to Agent Frontend Usage or Admin Console on the right.
(4) Locate the permission resource you need to configure and toggle the corresponding permission switch on or off.
After the configuration is complete, users who belong to this department, position, or role and whose corresponding permissions are in an inherited state will inherit the permissions configured here.
After selecting a user on the User tab page, the permission list on the right will display Permission Source, which indicates whether the user's permissions are inherited from a department/position/role, or set separately.
Users' permission resources have the following two states. The same user can have multiple permission sources at the same time. For example, the Skill and Data permissions are inherited from a department/role, while the Agent and Knowledge permissions are set separately for a user.
Permission Source
Description
Executable Operation
Inherited from Department/Role
This permission is obtained based on the user's department, position, or role.
For personalized adjustments, you can switch to Set Separately.
Set Separately
This permission is configured directly by the administrator for the current user and will no longer be subject to the corresponding permission of the user's department, position, or role.
You can directly toggle the permission switch on or off, or restore the permission to the inherited state.
If users need additional permissions, or if their permissions need to be different from those of their departments, positions, or roles, you can follow the following steps:
(1) Select the target user on the User tab page and locate the permission resource that needs to be adjusted.
(2) In Permission Source, click the configuration icon next to the inherited state and switch to Set Separately.
(3) Toggle the permission switch corresponding to the permission resource on or off.
To cancel users' personalized permission configuration, click Restore All Inheritances in the upper right corner of the page.
After restoration, the permission resources that have been set separately for the current user will be recalculated according to the permission configuration of the user's department, position, and role.
You can configure two types of permissions (Agent Frontend Usage and Admin Console) for departments, positions, roles, and users.
Agent Frontend Usage: It controls whether the corresponding user can use agents.
Admin Console: Only developers require additional configuration to be assigned personal development or public management capabilities for using the corresponding modules.
The following table lists configurable modules and permission scopes in the admin console.
Module
Personal Development Permission
Management Permission
Agent
You can create, edit, delete, or publish your own agents.
You can publish agents as visible to some users or all users.
Skill
You can create, edit, or delete skills for personal use.
You can add or delete public skills.
Data
You can create, edit, or delete data for personal use.
You can add or delete public data.
Knowledge
You can create, edit, or delete knowledge for personal use.
You can add or delete public knowledge.
Model
You can add or delete models for personal use.
You can add or delete public models.
Agent Supervision
You can view the supervision data of agents on which you have management permissions.
Open Integration
You can view and use the Open Integration page.
(1) Viewers cannot be configured with management backend permissions.
(2) Personal Development Permission: Users can perform development-related operations.
(3) Public Management Permission: Users can manage globally-shared resources.
The platform's data permissions are consistent with those on the FineBI platform. The range of data that users can access in the Agent depends on their data directory permissions on the FineBI platform.
(1) Under Management Backend > Data, developers can add only data resources on which they already have permissions on the FineBI platform.
(2) If users lack the permission on a certain data source on the FineBI platform, they will not be able to query that data in the Agent.
(3) The above data permission restrictions apply only to FineBI platform data sources. The following data is not subject to data permissions. Even if users lack FineBI platform permissions, they can still query the data normally in the Agent.
Uploaded local Excel data sources
Analysis subjects using Excel data