You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: product_docs/docs/edb-postgres-ai/1.2/hybrid-manager/using_hybrid_manager/managing_users/user_roles_authz/roles.mdx
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,63 +14,63 @@ The two main categories of roles are organization-level and project-level.
14
14
15
15
You can assign these roles to human or machine users using the **User Management** option of your user profile menu at the top-right of the navigation bar in the HM console.
16
16
17
-
### Organization administrator (admin)
17
+
### Organization Administrator
18
18
19
19
This role provides read access at the organization level, allowing the user to view information and settings in the organization as a whole.
20
20
21
-
### Organization owner (owner)
21
+
### Organization Owner
22
22
23
23
The purpose of this role is to manage the organization at a high level.
24
24
Organization owners can create projects and assign organization-level roles to other users.
25
25
26
-
### Platform administrator (platform admin)
26
+
### Platform Administrator
27
27
28
28
This role is for users who need to access and manage the underlying platform components of HM.
29
29
They can access platform management and monitoring tools.
30
30
31
-
### GenAI Builder user (GenAI Builder user)
31
+
### GenAI Builder Editor
32
32
33
33
This role is for users who work with the GenAI Builder feature of HM, granting them full access to its functions.
34
34
35
35
## Project-level roles
36
36
37
37
These roles can be assigned to human or machine users (except for estate ingester). Select **Users** in the left navigation when viewing a project.
38
38
39
-
### Project owner (owner)
39
+
### Project Owner
40
40
41
41
In a specific project, the project owner has the highest level of authority.
42
42
They can take all actions in that project and are responsible for assigning project-level roles to other users.
43
43
44
-
### Project editor (editor)
44
+
### Project Editor
45
45
46
46
This role is for users who need to actively work with the data in a project.
47
47
Project editors have data read and write access.
48
48
49
-
### Project viewer (viewer)
49
+
### Project Viewer
50
50
51
51
For users who only need to observe the data in a project, the project viewer role provides data read-only access.
52
52
53
-
### Estate ingester (estate ingester)
53
+
### Estate Ingester
54
54
55
55
This role is for machine users and provides access to perform estate ingests in a project.
56
56
57
-
### Catalog data reader (catalog data reader)
57
+
### Catalog Data Reader
58
58
59
59
Users with this role can read the Iceberg namespace/table/view of project-scoped catalogs.
60
60
61
-
### Catalog data writer (catalog data writer)
61
+
### Catalog Data Writer
62
62
63
63
This role allows users to read, write, and delete the Iceberg namespace/table/view of all project-scoped catalogs in a project.
64
64
65
-
### Migration Portal projects owner
65
+
### Migration Portal Projects Owner
66
66
67
67
This role is for users who manage Migration Portal projects in an HM project.
68
68
They can create, read, update, and delete these projects.
69
69
70
-
### Migration Portal projects editor
70
+
### Migration Portal Projects Editor
71
71
72
72
Users with this role can read and update Migration Portal projects in an HM project.
73
73
74
-
### Migration Portal projects viewer
74
+
### Migration Portal Projects Viewer
75
75
76
-
This role provides read-only access to Migration Portal projects in an HM project.
76
+
This role provides read-only access to Migration Portal projects in an HM project.
0 commit comments