Role Management¶

If you need to set different system access permissions for employees to achieve permission isolation, you can use the Role Management feature. Role Management provides an intuitive permission management entry, supports customizing the permission scope of each role, creating new roles, and assigning permissions to roles to meet the permission needs of different users.

Default Roles¶

If different teams in your enterprise need to view or operate different functional modules, you can invite members to join the current workspace and assign role permissions to them, thereby controlling the Guance functional modules that members can access and operate.

The system provides four default member roles:

• Owner

• Administrator

• Standard

• Read-only

Permission Description¶

For the permission scope of different default roles, refer to the document Permission List.

• Owner: The owner of the current workspace has all operation permissions within the workspace and can adjust the role permissions of other members. If the granted role permissions include "Token View", it will trigger the Authorization Review process.

• Administrator: The administrator of the current workspace has read and write permissions in the workspace and supports adjusting the role permissions of other members except the Owner.

• Standard: The standard member of the current workspace has read and write permissions in the workspace.

• Read-only: The read-only member of the current workspace can only view the data in the workspace and has no write permissions.

Custom Roles¶

In addition to default roles, you can create new roles in Role Management and assign permission scopes to roles to meet different permission needs.

1. Go to Management > Role Management.

2. Define the role name and description.

3. Select the functional permission scope.

4. Save.

Manage Roles¶

You can perform the following operations on custom roles:

• Export the permissions of all roles as a list.

• Edit and adjust the permissions of roles.

• If the role is not associated with a member account, it can be deleted.

• Clone an existing role to create a new role.

  • Based on the permissions of an existing role, cloning a role can reduce operational steps, quickly add or remove permissions, and create a role.

• Click any custom role to view its details, including the role name, creation/update time, creator/updater, description, and role permissions. Click the edit button on the right side of the role name above to modify the role permissions.

Permission Change Review¶

When setting role permissions for workspace members, if the granted role permissions include "Token View", the system will send verification information to the Guance Billing Center and initiate the permission change review process.

• If the Billing Center accepts the verification, the permission change is successful.

• If the Billing Center rejects the verification, the permission change fails, and the original role permissions are maintained.

• If the Billing Center does not review, you can modify the member to another role. After successful modification, the original permission change review request becomes invalid.

Promote to Administrator in Commercial Plan¶

1. Go to Management > Member Management.

2. Select the member to be promoted to Administrator.

3. Click the Edit button on the right, and in the pop-up dialog, select Administrator.

4. Confirm.

If you are the Administrator role of the current workspace, when promoting a member, you need to notify the Guance Billing Center administrator to log in to the Billing Center to operate.

If you are the Owner role of the current workspace, you can directly click Go to Billing Center Review to operate without logging in to the Guance Billing Center.

In the member management list, you can view all members whose Administrator role has not been approved. Click the icon on the right side of the member role, and you can click to go to the Billing Center for review in the prompt dialog.

Permission List¶

You can set permissions for custom roles within the workspace to meet the permission needs of different users.

For more details, refer to the document Permission List.