Explanation
Second-person approval
Why large or risky changes wait for a second person, and what that person can and cannot do.
Some changes move money or hide risk. For these, one person asks and a different person approves. The person who asked cannot approve their own request, and the second person cannot change what was asked. This page explains which changes wait, why, and what happens when nobody else is available.
Which changes wait#
An admin sets the limits for the organization. The table shows the defaults.
| Change | When a second person is needed | Who can approve |
|---|---|---|
| Approve or release a hold | The payout is above 5,000 SAR, or approved holds on one owner add up past 10,000 SAR in 24 hours. | Reviewer or admin |
| Reserve | The amount is above the hold limit. | Reviewer or admin |
| Policy change | On by default. | Admin |
| Account change | On by default. | Admin |
| Suppression | On by default. | Reviewer or admin |
| Rule that skips payouts | On by default, under the suppression setting. | Reviewer or admin |
Rejecting a hold never waits, because it moves no money. Owner totals add up so that splitting one payout into smaller holds does not avoid the check. For a partial hold, the limit is checked against the held amount.
What the maker sees#
The request answers 202 with status: pending_approval. Nothing has changed yet. The request expires after 24 hours unless an admin sets another time (1 to 168 hours). The person who asked, or an admin, can cancel it.
What the second person does#
The second person approves or rejects at POST /api/v1/approvals/{id}/decision/. A rejection needs a note. On approval, Yaqeen runs the stored change as the person who asked, so the audit log shows both people. If the change can no longer run, for example because the hold was deleted, the request is marked failed.
When nobody else can approve#
A team with only one person who could approve is not locked out. The change runs at once and the audit log shows it. Without this rule, a one-person team could never change its own policy.
Why this design#
A person who can both ask and approve is a single point of failure for fraud and for mistakes. The default limits are our assumption and should be tuned with each customer.
Related#
- Approve as a second person: the steps
- Settings: where the limits live
- Roles: who counts as a reviewer or an admin