Skip to content

Commit 231ae65

Browse files
committed
docs: update database permission
1 parent c62cb9a commit 231ae65

File tree

4 files changed

+32
-37
lines changed

4 files changed

+32
-37
lines changed

content/blog/database-security-read-write-admin-permision-level.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -32,11 +32,10 @@ This post is updated regularly. For the impatience, jump to the [Recommended Set
3232

3333
## Admin
3434

35-
**Admin** is the highest level of access that grants users the ability to manage database users, permissions, and system settings. DBAs use this level to perform tasks such as granting user permissions, setting database level settings, and restarting the database.
35+
**Admin** is the highest level of access. DBAs use this level to perform tasks such as killing the connections.
3636

37-
- Grant user permissions
38-
- System change (e.g. set database level settings, restart database)
37+
## Fine-grained database permissions in Bytebase
3938

40-
## Conclusion
39+
You can configure [Bytebase database permissions](/docs/security/database-permission/overview/) to provide fine-grained control over database operations.
4140

42-
Access control levels are essential for database security, ensuring data protection while enabling authorized users to perform their tasks. Instead of logging in different database engines to configure, modern platforms like [Bytebase](https://www.bytebase.com/) now offer centralized permission management across multiple database engines, improving both security and efficiency.
41+
<IncludeBlock url="/docs/share/database-permission-table"></IncludeBlock>

content/docs/security/database-permission/overview.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,6 @@ Database permission controls individual users' or groups' actions within the dat
1818
| Project Releaser | | | |
1919
| Project Viewer | | | |
2020

21-
You can also pick out specific permissions to build [custom roles](/docs/administration/custom-roles/).
21+
You can also pick out specific permissions to build [custom roles](/docs/administration/custom-roles/). e.g. create a custom role that grants only the [EXPLAIN](/docs/security/database-permission/explain/) permission.
2222

23-
| Action | Permission |
24-
| ------------------------------------------------------ | ------------------------ |
25-
| [Query](/docs/security/database-permission/query/) | `databases.query` |
26-
| [Export](/docs/security/database-permission/export/) | `databases.export` |
27-
| [EXPLAIN](/docs/security/database-permission/explain/) | `databases.queryExplain` |
23+
<IncludeBlock url="/docs/share/database-permission-table"></IncludeBlock>
Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
| Access Level | Operation | Permission |
2-
| ------------ | ------------------------------------------------------ | ------------------------ |
3-
| Read | [EXPLAIN](/docs/security/database-permission/explain/) | `databases.queryExplain` |
4-
| | [Query](/docs/security/database-permission/query/) | `databases.query` |
5-
| | [Export](/docs/security/database-permission/export/) | `databases.export` |
6-
| Write | Data-modifying DML | `databases.queryDML` |
7-
| | DDL | `databases.queryDDL` |
8-
| Admin | [Admin](/docs/sql-editor/admin-mode/) | `instances.adminExecute` |
1+
| Access Level | Operation | Permission |
2+
| ------------------------------------- | ------------------ | ------------------------ |
3+
| [Read](/docs/sql-editor/run-queries/) | EXPLAIN | `databases.queryExplain` |
4+
| | Query | `databases.query` |
5+
| | Export | `databases.export` |
6+
| Write | Data-modifying DML | `databases.queryDML` |
7+
| | DDL | `databases.queryDDL` |
8+
| [Admin](/docs/sql-editor/admin-mode/) | Admin | `instances.adminExecute` |

content/docs/sql-editor/run-queries.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,24 @@ The default query result size is **100 MB**. You can change it under the Workspa
3333

3434
![Query Result Size Limit](/content/docs/sql-editor/query-result-size-limit.webp)
3535

36-
## Explain query
36+
## Export data
37+
38+
<HintBlock type="info">
39+
40+
The exported data still respects the [masking policy](/docs/sql-editor/mask-data/) to mask exported columns if enforced.
41+
42+
</HintBlock>
43+
44+
If you have been granted export access, you can directly export query results in various formats.
45+
46+
![Export Data](/content/docs/sql-editor/export-data.webp)
47+
48+
Otherwise, you can request the exported data
49+
50+
![Request Export](/content/docs/sql-editor/export-request1.webp)
51+
![Request Export](/content/docs/sql-editor/export-request2.webp)
52+
53+
## EXPLAIN query
3754

3855
![Explain Query](/content/docs/sql-editor/explain-query.webp)
3956

@@ -82,20 +99,3 @@ For each database, the query result will show up in its own tab:
8299
You can retrieve anything you want from query results quickly.
83100

84101
![Search Result](/content/docs/sql-editor/search-result.webp)
85-
86-
## Export data
87-
88-
<HintBlock type="info">
89-
90-
The exported data still respects the [masking policy](/docs/sql-editor/mask-data/) to mask exported columns if enforced.
91-
92-
</HintBlock>
93-
94-
If you have been granted export access, you can directly export query results in various formats.
95-
96-
![Export Data](/content/docs/sql-editor/export-data.webp)
97-
98-
Otherwise, you can request the exported data
99-
100-
![Request Export](/content/docs/sql-editor/export-request1.webp)
101-
![Request Export](/content/docs/sql-editor/export-request2.webp)

0 commit comments

Comments
 (0)