A Database Rule with the effect Approval does not run the statement right away. The proxy holds it, an approval request is opened, and the statement runs only after an approver allows it.
|
Applies to |
Who can do this |
|---|---|
|
Monopam v2026.10 |
Administrators set the rule. Approvers decide in Requests. |
Set it up
-
In the policy's Database Rules, add a rule with Effect = Approval for the commands or tables to gate, for example UPDATE, DELETE and INSERT.
-
Optionally turn on Show exact impact to approver (dry-run), so the approver sees how many rows the statement would change, and write a Message for the user.
-
Name the approvers on the policy's Approval tab.
What happens
-
In the SQL console, the user sees the denial and can click Send for Approval.
-
From a native client, the denial opens an approval request automatically.
-
The approver decides it under Requests (type Database Query). The approval covers exactly that statement, by default for 60 minutes.
-
On PostgreSQL the statement can be held in the session and run as soon as it is approved; otherwise the user runs it again after approval.
Troubleshooting
|
What you see |
Why |
What to do |
|---|---|---|
|
The approved statement is still blocked. |
The statement sent again differs from the approved one. |
Run exactly the approved statement, or ask for a new approval. |
Related
-
Database Rules
-
Approve and revoke access
-
Requests overview