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/docs/administration/risk-center.md
+16-6Lines changed: 16 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,26 +5,36 @@ feature_name: CUSTOM_APPROVAL
5
5
6
6
In **Settings > Risk Center**, you can define different risk levels for each operation types ([DML, DDL, Create Database](/docs/change-database/change-workflow/), [Request Query](/docs/security/database-permission/query/), [Request Export](/docs/security/database-permission/export/)) with custom rules.
7
7
8
-
Once an issue matches the risk conditions, it will be assigned to the corresponding risk level you've defined.
9
-
If an issue matches more than one risk levels, the highest level will be used.
8
+
Once an operation matches the risk conditions, it will be assigned to the corresponding risk level you've defined.
9
+
If an operation matches more than one risk levels, the highest level will be used.
10
+
11
+
## Usage
12
+
13
+
### Custom Approval
10
14
11
15
You can configure different [custom approval flows](/docs/administration/custom-approval) for each operation types and risk levels.
[SQL review](/docs/sql-review/overview/) returns the associated risk level for the checked SQL statement. Bytebase GitHub action can also surface the risk level under a [PR](https://github.com/bytebase/release-cicd-workflows-example/pull/4).
Name the rule so that you may know what it cares about. Select the operation type of rule. The **Risk** can be defined as **High**, **Moderate** or **Low**.
0 commit comments