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/custom-approval.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ feature_name: CUSTOM_APPROVAL
5
5
6
6
<TutorialBlockurl="/docs/tutorials/database-change-management-with-risk-adjusted-approval-flow"title="Database Change Management with Risk-Adjusted Approval Flow" />
7
7
8
-
<iframewidth="675"height="380"src="https://www.youtube.com/embed/K_RWlqdplZQ"title="YouTube video player"className="w-full"frameBorder="0"allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"allowFullScreen></iframe>
8
+
<iframewidth="675"height="380"src="https://www.youtube.com/embed/K_RWlqdplZQ"title="YouTube video player"className="w-full"frameBorder="0"allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"allowfullscreen="allowFullScreen"></iframe>
9
9
10
10
In **Settings > Custom Approval**, you can choose which approval flow to use for a [risk level](/docs/administration/risk-center) and define approval flows.
1. Go to **IAM&Admin > Users&Groups**, click **+Add User**.
45
45
1. Choose `Service Account` as the **Type**, fill in the **Email** with `api-sample@service.bytebase.com`, choose `Workspace DBA` as **Roles**, and click **Confirm**.
@@ -63,30 +63,30 @@ There are two ways to configure the data masking based on the classification lev
63
63
1. Choose **Masking Level** as `Partial` and click **Confirm**.
64
64
1. The same way, we can add another masking rule for `Level 2` with **Masking Level** as `Full`.
1. Find the [data masking configuration file](https://github.com/bytebase/api-example/blob/main/data-security/masking/global-masking-rule.json) within the `data-security` repository.
71
71
1. Generate the token for the service account user:
@@ -122,121 +122,126 @@ There are two ways to configure the data masking based on the classification lev
122
122
123
123
1. Use the API `/v1/instances/${instance}/databases/${database}/metadata` to fetch the database schema information. In this demo, the instance is hardcoded as `test-sample-instance` and the database is `test-sample-database`.
0 commit comments