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: content/admin/permissions.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ weight: 50
4
4
---
5
5
6
6
## Permissions system
7
-
DbGate uses permission system with two dimensional hiearchy.
7
+
DbGate uses permission system with three dimensional hiearchy.
8
8
9
9
One hiearchy dimension is inheritance of permissions from roles.
10
10
- Predefined permission set
@@ -14,6 +14,13 @@ One hiearchy dimension is inheritance of permissions from roles.
14
14
15
15
The second hiearchy dimension is inheritance from parent roles.
16
16
17
+
The third hiearchy dimension are permission for databases and tables. This applies only for [Database permissions](#database-permissions) and [Table permissions](#table-permissions).
18
+
19
+
## Basic permissions
20
+
Basic permissions could be configured in permission tree avaialble in user detail and role detail. If checkbox with permission state is grayed, it means, that permission is inherited.
You could configure permissions related to database on "Databases" tab (in Role detail and in User detail)
19
26
@@ -40,6 +47,8 @@ Tables permissions are not used, unless **"All tables/views/objects"** is permis
40
47
41
48
Each line of databases permission rules table defines permission to matched table. The order of rules is important, permissions at the bottom override permissions at the top.
42
49
50
+
The default table permission is inherited from database permission.
51
+
43
52
**Columns:**
44
53
* Connection - define, on which connection this rule is applied
45
54
* Database names - define database name (by list of names or by regular expression)
0 commit comments