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
refactor: rename "Risk Center" to "Risks" throughout documentation (#862)
- Updated feature name from "Risk Center" to "Risks" to match UI
- Renamed all related files and directories (risk-center → risks)
- Updated all documentation references and navigation links
- Updated image paths to reflect new directory structure
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Claude <[email protected]>
Copy file name to clipboardExpand all lines: mintlify/change-database/risks.mdx
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
-
title: Risk Center
3
-
feature_name: RISK_CENTER
2
+
title: Risks
3
+
feature_name: RISKS
4
4
---
5
5
6
-
In **Settings > Risk Center**, you can define different risk levels for each operation types ([DML, DDL, Create Database](/change-database/change-workflow/), [Request Query](/security/database-permission/request/), [Request Export](/security/database-permission/export/)) with custom rules.
6
+
In **Settings > Risks**, you can define different risk levels for each operation types ([DML, DDL, Create Database](/change-database/change-workflow/), [Request Query](/security/database-permission/request/), [Request Export](/security/database-permission/export/)) with custom rules.
7
7
8
8
Once an operation matches the risk conditions, it will be assigned to the corresponding risk level you've defined.
9
9
If an operation matches more than one risk levels, the highest level will be used.
@@ -20,15 +20,15 @@ Custom Approval is mostly used by [UI workflow](/change-database/change-workflow
20
20
21
21
You can configure different [custom approval flows](/administration/custom-approval) for each operation types and risk levels.
[SQL review](/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/example-gitops-github-flow/pull/6#issuecomment-2731413296).
@@ -38,7 +38,7 @@ Click **Add rule** to create a new risk rule.
38
38
39
39
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**.
@@ -47,12 +47,12 @@ Configure the condition of the rule. You may use a combination of conditions and
47
47
- Condition: An expression with **Factor**, **Operator** and **Value(s)**. For example, the condition "Environment ID == prod" will match issues executed in the "prod" environment.
48
48
- Condition group: A collection of conditions connected by operators "And" and "Or".
0 commit comments