From 8a93232cbc531969c20279ba484e04c3bb9805b0 Mon Sep 17 00:00:00 2001
From: "abby.huang" <78209557+abby-cyber@users.noreply.github.com>
Date: Thu, 15 Sep 2022 15:10:35 +0800
Subject: [PATCH] Update 5.account-management.md (#1623)
---
docs-2.0/nebula-dashboard-ent/5.account-management.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs-2.0/nebula-dashboard-ent/5.account-management.md b/docs-2.0/nebula-dashboard-ent/5.account-management.md
index e604b804549..ee4677af8f1 100644
--- a/docs-2.0/nebula-dashboard-ent/5.account-management.md
+++ b/docs-2.0/nebula-dashboard-ent/5.account-management.md
@@ -54,7 +54,7 @@ The relationship between system roles and cluster roles and their descriptions a
| Roles | Permission | Description |
| ------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| admin | 1. Create accounts.
2. Modify the role of an existing account.
3. Perform platform settings, system-level alert settings.
4. Delete accounts. | 1. There can be multiple `admin` roles, i.e. system administrators.
2. An `admin` is the `operator` of all clusters by default, i.e. an `admin` can manage all clusters.
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.
2. Modify the role of an existing account.
3. Perform platform settings, system-level alert settings.
4. Delete accounts. | 1. There can be multiple `admin` roles, i.e. system administrators.
2. An `admin` is the `operator` of all clusters by default, i.e. an `admin` can manage all clusters.
3. An `admin` can assign a `user` to be the `operator` of a cluster.
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.
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.
3. Can create clusters and become the `owner` of the clusters. | 1. General role.
2. There can be multiple `user` roles. |