> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.finrock.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Approve Account Changes with Governance Policies

> Decide who must approve sensitive changes to your Finrock workspace, such as new users, whitelist addresses, exchange keys and AML settings, and how requests are approved.

Governance policies decide which changes to your Finrock workspace need approval before they take effect, and who gives it. The rule of thumb is simple:

* **Changes that loosen** (add access, add a way to move money, relax a control) wait for approval.
* **Changes that tighten** (remove access, tighten a control) take effect at once.

> [!NOTE]
>
> Withdrawals themselves are controlled by [spending rules](https://apidocs.finrock.io/guides/spending-rules.md). Governance policies cover the changes around them: who can use the workspace, where funds can go, and which safety settings apply.

## How changes are grouped

Every change belongs to one of three tiers. The tier decides whether it needs approval.

> [card] Tier 1: at once
>
> Ordinary operations, and changes that only tighten a control. No approval; recorded in the audit log.

> [card] Tier 2: your policy
>
> Changes that loosen a control or change who can move funds. Approved as that change's row says.

> [card] Tier 3: every Owner
>
> Changing a governance policy row, and adding an Owner. Always all active Owners; you can't change it.

## Changes that need approval

Each Tier 2 change has its own row in your governance policy, so you can choose who approves each one. Every row starts at **All Owners**.

### Across your workspace

> [!NOTE]
>
> Where a workspace row includes Admins, every active Admin counts.

**People and access**

* Add an Admin, an Approver or an API key.
* Add an MPC signer (MPC workspaces only).
* Unblock a user.
* Reset someone else's app pairing. Resetting your own needs no approval.

**Keys, signers and IP addresses**

* Change an API key's IP whitelist. The same row covers a Cloud Signer's server IP once the signer is installed. See [Whitelist IPs](https://apidocs.finrock.io/guides/whitelist-ips.md).
* Refresh MPC keys (MPC workspaces only).
* Reset a cloud signer's IP, or disable a signer.

**Settings**

* Exchange account: add or change keys, or enable it. Disabling or removing one needs no approval.
* AML settings that loosen screening. See [When an AML change needs approval](#when-an-aml-change-needs-approval).

### In each sub-account

> [!NOTE]
>
> Each sub-account has its own rows. Owners always count as approvers; Admins count only if they are assigned to that sub-account.

* **Add an address to a whitelist.** Gas-tank auto-refill destinations use this row too. Removing an address needs no approval. See [Whitelist Addresses](https://apidocs.finrock.io/guides/whitelist-addresses.md).
* **Add a spending rule.** Deleting a rule needs no approval. See [Spending Rules](https://apidocs.finrock.io/guides/spending-rules.md).
* **Set up an auto-forward address**, in the dashboard or with `PATCH /dac/v1/wallet`.
* **Assign a user to the sub-account.** Unassigning needs no approval.
* **Unfreeze an address.** See [Unfreeze Address](https://apidocs.finrock.io/api-reference/aml/unfreeze-address.md).

### When an AML change needs approval

An AML change loosens screening, and needs approval, when it does any of these:

* Turns deposit or withdrawal screening off.
* Removes a risk level from the levels that block transactions.
* Changes or removes the provider or the provider token while a provider is set.

> [!NOTE]
>
> Any other AML change, such as adding a risk level or turning screening on, takes effect at once. A change that both loosens and tightens is sent for approval as a whole. See [Configure AML](https://apidocs.finrock.io/api-reference/aml/manage-aml.md).

### Changes that take effect at once

These only remove access or tighten a control, so they need no approval:

* Adding a Viewer, and resetting your own app pairing.
* Blocking a user.
* Unassigning a user from a sub-account.
* Deleting a spending rule, and removing a whitelist address.
* Disabling or removing an exchange account.
* AML changes that only tighten screening.
* Setting a Cloud Signer's server IP before the signer is installed.

> [!TIP]
>
> Blocking a user also rejects every pending request that user was asked to approve, so those requests can be asked again without them.

## Who can approve

Set each Tier 2 row to one of these options:

| Option | Value | Who must approve |
| - | - | - |
| **All Owners** (default) | `AllOwners` | Every active Owner. |
| **Any Owner** | `AnyOwner` | One Owner. |
| **All Owners and Admins** | `AllOwnersAndAdmins` | Every active Owner and Admin. On a sub-account row, only Admins assigned to that sub-account. |
| **Any Owner or Admin** | `AnyOwnerOrAdmin` | One Owner or Admin. |
| **Specific** | `Specific` | A minimum number of people you name, for example "Any 2: Emma Taylor, James Wilson, Olivia Brown". |

* **Only Owners and Admins approve governance requests.** Approvers and Viewers never do.
* **For a Specific row**, everyone you name must be an active Owner or Admin. On a sub-account row, any Admin you name must be assigned to that sub-account.
* **New workspaces and sub-accounts** start with every row at **All Owners**.

## How a request is approved

When someone makes a change that needs approval, Finrock creates a request and sends each approver a task in the **Finrock mobile app**, with a push notification. The task shows what is changing, who asked, and everyone who was asked to approve.

* **The requester doesn't approve their own request.** If they're the only eligible approver, they confirm on their own device.
* **The person the request is about is left out too**, for example the user being unblocked.
* **Any single rejection rejects the request.**
* **A request that isn't approved within 24 hours expires**, and has to be made again.

> [!NOTE]
>
> Two Tier 3 changes work differently:
>
> * **A governance policy change** goes to every active Owner, **including the requester**. Each Owner confirms it on their own device.
> * **Adding an Owner** needs every other active Owner. The requester's request counts as their consent.

### Good to know

> [accordion] The approvers are fixed when a request is created
>
> The people asked and the number of approvals needed don't change after a request is made. To keep it that way, a governance policy row can't be changed while requests it decides are waiting for approval.

> [accordion] One pending request per thing
>
> While a request about a user, an address, an API key or a policy row is waiting, a second request about the same thing is refused with `ANOTHER_REQUEST_PENDING`.

> [accordion] Nothing is applied if the state changed
>
> An approval applies only if nothing has changed since the request. For example, if the address is no longer frozen, or the IP whitelist was already changed, the approved change isn't applied, and it has to be requested again.

> [accordion] If an approver can no longer decide
>
> If an approver can no longer decide, for example because they were blocked, their task is dropped and the request is counted again. That can complete it, or reject it if the approvals needed can no longer be reached.

> [accordion] Tasks never show secrets
>
> A request to change exchange keys or AML settings doesn't carry the keys or the provider token, only what is changing.

## Change a governance policy

Only Owners can change a governance policy row. It's a Tier 3 request, so it takes effect once every active Owner has approved it in the Finrock mobile app.

**1. Open Governance Policies**

In the Finrock dashboard, go to **Policy** and select **Governance Policies**. Workspace rows and each sub-account's rows are listed separately.

**2. Choose who approves**

Pick the row for the change you want to control, and choose an option. For **Specific**, name the people and the number of approvals needed.

**3. Get approval**

Save the change. Every active Owner, including you, gets a task in the Finrock mobile app. The row changes once all of them approve.

> [!WARNING]
>
> A **Specific** or **All Owners and Admins** row depends on the people it counts. If too few of them are active when a request is made, the request is refused. Name enough people that approvals can still happen when someone is away.

## Requests made through the API

These API calls make changes that need approval. Each returns `{"code": 1000}` when the request is created, and the change takes effect once it's approved.

| Endpoint | Change |
| - | - |
| `POST /dac/v1/spending-rule` | Add a spending rule |
| `POST /dac/v1/whitelist-address` | Add an address to a whitelist |
| `PATCH /dac/v1/wallet` with `forwarding` | Set up an auto-forward address |
| `POST /dac/v1/unfreeze-address` | Unfreeze an address |
| `POST /dac/v1/aml` | AML changes that loosen screening (other AML changes apply at once) |

> [!NOTE]
>
> Because the requester is your API key, no Owner or Admin is left out of the approvers.

### Errors

| Code | Error | Returned when |
| - | - | - |
| `1437` | `INVALID_APPROVERS` | The governance policy can't be met, because too few eligible approvers are available. `info` says which row decided it, what it needs, and how many approvers are eligible. |
| `1020` | `ANOTHER_REQUEST_PENDING` | A request about the same thing is already waiting for approval. |

```json 400 theme={null}
{
  "code": 1437,
  "error": "INVALID_APPROVERS",
  "info": "WhitelistAddress (sub-account Treasury) needs 2 of the named approvers; 1 eligible approver(s) available (the requester is left out)."
}
```

> [!TIP]
>
> Show `info` to the person who made the request, but don't parse it: the wording can change.

## Good practice

> [card] Keep money movement strict
>
> Leave rows that let funds move, such as whitelist addresses, spending rules and auto-forward, at **All Owners** or a **Specific** group.

> [card] Plan for absences
>
> Rows that need everyone stop working when one person is unavailable. Use **Specific** with a minimum below the number named if someone is often away.

> [card] [Pair with spending rules](https://apidocs.finrock.io/guides/spending-rules.md)
>
> Governance policies control who can change your setup. Spending rules control each withdrawal. Use both.

> [card] Review the audit log
>
> Every request, decision and immediate change is recorded, so you can see who changed what and when.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.