Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 5.account-management.md #1623

Merged
merged 1 commit into from
Sep 15, 2022
Merged

Update 5.account-management.md #1623

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs-2.0/nebula-dashboard-ent/5.account-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ The relationship between system roles and cluster roles and their descriptions a

| Roles | Permission | Description |
| ------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
| admin | 1. Create accounts.<br>2. Modify the role of an existing account.<br>3. Perform platform settings, system-level alert settings.<br>4. Delete accounts. | 1. There can be multiple `admin` roles, i.e. system administrators.<br/> 2. An `admin` is the `operator` of all clusters by default, i.e. an `admin` can manage all clusters. <br/>3. Displayed in the cluster member list by default. An `owner` cannot remove an `admin` unless the `admin` is converted to `user`, and the system will automatically remove the `admin` from the cluster member list. |
| admin | 1. Create accounts.<br>2. Modify the role of an existing account.<br>3. Perform platform settings, system-level alert settings.<br>4. Delete accounts. | 1. There can be multiple `admin` roles, i.e. system administrators.<br/> 2. An `admin` is the `operator` of all clusters by default, i.e. an `admin` can manage all clusters. <br/>3. An `admin` can assign a `user` to be the `operator` of a cluster.<br/>4. Displayed in the cluster member list by default. An `owner` cannot remove an `admin` unless the `admin` is converted to `user`, and the system will automatically remove the `admin` from the cluster member list. |
| user | 1. Has read-only permissions for the system dimension. <br/>2. After an `admin` creates a new account with the `user` role, the `user` account cannot view any clusters if the corresponding cluster is not assigned to the account. <br/>3. Can create clusters and become the `owner` of the clusters. | 1. General role. <br/>2. There can be multiple `user` roles. |


Expand Down