# Global controls

Source: https://docs.settlemint.com/docs/console/compliance/global-controls
Configure compliance controls that apply to every token bound to your organisation's compliance engine, whatever product line issued it.

A global control is a compliance module installed on your organisation's system compliance engine rather than on one token. Each control holds one or more rules pairing module parameters with a scope, and every bound token on the active network inherits those checks. See compliance policy for how the global and token layers combine.

Use this screen for baseline rules every token must enforce. **Issue asset** cannot remove an inherited global control, and policy templates or token-level rules only add checks on top.

| Where the rule lives | What it reaches | Choose it when |
| --- | --- | --- |
| Global control | Every bound token, including ones issued after the rule lands, minus the rule's own carve-outs. | Every token must follow it. |
| [Policy template](https://docs.settlemint.com/docs/console/compliance/policy-templates) | Tokens issued from a template that carries the policy. | It defines one product line, not every one. |
| The token's **Compliance** tab | One token, on top of everything it inherits. | Only that instrument needs it. |

![Global controls with the Wallet restriction rule the platform installs, its switch and Remove, and the Add control button](https://docs.settlemint.com/docs/screenshots/console-global-controls-rules.light.en.webp)

[Screenshot] Before you install a rule, the "Global controls" page lists the "Wallet restriction" rule the platform installs itself, with no "Edit", and an "Add control" button.

## Before you start [#before-you-start]

- **Compliance manager role.** Only Compliance manager can add, edit, toggle, or remove rules here. Permission manager and System manager view the page read-only ("Only a Compliance manager can change global controls."). System manager can register or replace control contracts, which affects every rule of that type.
- **Active organisation and network.** Rules belong to the active organisation and network. Switch organisation or network first if you manage more than one.
- **Wallet verification.** Every install, edit, toggle, and removal submits an on-chain transaction confirmed with your wallet verification and recorded in the [audit trail](https://docs.settlemint.com/docs/console/reporting/audit-trail).
- **Second approver, when required.** If **Compliance configuration** approvals are enabled under [Approvals](https://docs.settlemint.com/docs/console/organisation-settings/general#approvals), every change waits on [Actions](https://docs.settlemint.com/docs/console/essentials/actions#decide-an-administrative-change) until another user approves it.

## Steps [#steps]

### Add or edit a global rule [#add-or-edit-a-global-rule]

1. Open **Compliance** → **Global controls**.
2. Select **Add control** to install a new rule (or select **Edit** on an existing rule's row). Controls already installed are badged "Added", and selecting one again adds a second rule of the same kind.

![The Add control sheet open over Global controls, listing eligibility, restriction and transfer controls with a search box and category filters](https://docs.settlemint.com/docs/screenshots/console-global-controls.light.en.webp)

[Screenshot] The "Add control" sheet lists the controls, grouped by category, starting with "Eligibility", "Restrictions" and "Transfer controls".

3. Under **Configuration**, enter the module's parameters. Check [Compliance modules](https://docs.settlemint.com/docs/concepts/compliance-and-identity/compliance-modules) before saving because some parameters lock once active: Issuance volume limit locks its period length and window mode, and Capital raise limit locks its limit and period (to change them, add a replacement rule and remove the old one, starting counters at zero).
4. Under **Applies to**, keep **All transfers** or choose **Selected transfers** to filter across three dimensions:
   - **Sender** and **Receiver:** **Include** and **Exclude** cards filtered by **Verification topics** and **Countries**. An empty **Include** card matches everyone.
   - **Token:** **Include** and **Exclude** cards filtered by **Verification topics** only (tokens cannot be filtered by name).
   - **Track transfers outside this scope:** Decides whether stateful modules still count transfers outside their enforcement scope. Leaving it cleared can cause supply, holder, or quota counters to drift because missed transfers are never replayed.
5. Select **Save & enable** (or **Save** for an existing rule) and confirm with your wallet verification in **Confirm compliance change**.

A toast ("Compliance control enabled" or "Compliance control updated") confirms the rule is live. If **Compliance configuration** approvals are active, the toast reads "Sent for approval" and a "Change waiting for approval" banner links to [Actions](https://docs.settlemint.com/docs/console/essentials/actions#decide-an-administrative-change) until another approver decides it.

## Turn a rule off or remove it [#turn-a-rule-off-or-remove-it]

To pause checking while preserving configuration and counters, toggle the rule's switch off. Toggle it back on to resume.

Note (Removing a rule is permanent, and a replacement starts from zero): Removing a rule permanently deletes its configuration and tracking counts ("stops checking transfers on every asset and its counts are deleted."). Completed operations keep their outcomes, and adding the same control type later creates a fresh instance whose quotas and issuance windows start from zero.

1. Select **Remove** on the rule's row.
2. Read the warning dialog and confirm with your wallet verification.

Removal is permanent for every rule except Wallet restriction, which the next System update restores.

## The wallet restriction rule [#the-wallet-restriction-rule]

DALP installs the Wallet restriction rule automatically on networks whose release directory includes the module: new systems receive it at creation, and [System updates](https://docs.settlemint.com/docs/console/organisation-settings/system-updates#the-wallet-restriction-row) installs it on existing systems and backfills every active [wallet restriction](https://docs.settlemint.com/docs/console/participants/restricted-wallet-on-chain#on-chain-enforcement). It blocks transfers from any restricted wallet across every token in the system and, on DALP 3.2 token contracts, ordinary burns from that wallet. **Add control** and token **Compliance** tabs never offer it.

The row has no **Edit** action. Its switch and **Remove** button act as emergency overrides:

- **Toggle switch off:** Stops on-chain checks immediately while retaining the wallet list, and stays off across System updates until turned back on.
- **Remove:** Ends on-chain enforcement until the next System update reinstalls the module and writes active restrictions back.

Neither action lifts a restriction record in DALP or unfreezes tokens frozen by a restriction. Both follow **Compliance configuration** approval rules and write to the audit trail. A direct on-chain call to the compliance contract by a Compliance manager bypasses approvals and the audit trail, so review who holds that role. While the rule is disabled or scoped down via the API, **System updates** marks its row "Not fully enforced".

## When a change takes effect [#when-a-change-takes-effect]

Compliance checks evaluate on chain at execution time, not at submission. Adding, editing, pausing, or removing a global control takes effect immediately for all pending and future executions in scope without revisiting completed transfers. See [When a module refuses](https://docs.settlemint.com/docs/concepts/compliance-and-identity/compliance-module-refusals#when-a-module-refuses) for refusal reason codes.

## You should see [#you-should-see]

- After refreshing **Global controls**, the rule shows its expected parameters, scope, and active switch.
- On any bound token's **Compliance** tab, the rule appears with the "Global" badge in the **Rules** table.
- On the token's **Transfer pre-check** tab, one allowed transfer passes and one violating transfer fails as expected.

## Troubleshooting [#troubleshooting]

**A token's compliance tab says Set in Compliance › Global controls**

Token **Compliance** tabs list inherited global rules with the "Global" badge and no local edit controls. Edit or
remove the rule on **Compliance** → **Global controls**.

**The page is read-only**

The notice "Only a Compliance manager can change global controls." means your account lacks Compliance manager in the
active organisation. Permission manager and System manager cannot write rules here. Request Compliance manager in
[Admins and roles](https://docs.settlemint.com/docs/console/organisation-settings/admins-and-roles), then reload.

**A control is missing from Add control**

Only current-generation modules (plus Issuance volume limit) registered in the system's module registry appear here.
Have a System manager register a missing module via the Platform API. Wallet restriction is platform-installed and
never appears in **Add control**.

**A rule says its scope failed to load and saving is blocked**

When the Console cannot load on-chain scope filters ("Its settings could not be read."), it blocks saving ("Cannot
save: rule scope failed to load. Refresh the page and try again.") to prevent wiping unseen filters. Refresh the page
and reopen the rule.

**A change affected the wrong transfers or tokens**

Edit the rule's parameters or **Applies to** filters and save. The correction applies to future checks immediately.
Completed transfers remain unchanged.

**Capital raise limit rejects new parameter values**

The limit and period lock once active, leaving only **Applies to** editable. Add a new Capital raise limit rule with
the desired values and remove the old one (tracking restarts at zero).

**Mints fail after adding a global capital raise limit**

Capital raise limit converts each mint to fiat via the price resolver and rejects mints if a token's price is missing,
zero, negative, or stale. Configure a price feed for the token, or exclude it under **Applies to**.

## Frequently asked questions [#frequently-asked-questions]

### What skips a global control?

Three paths skip some or all checks: recipients on the system compliance bypass list skip eligibility checks, while Custodian forced transfers and wallet recoveries skip all compliance modules ([Compliance policy](https://docs.settlemint.com/docs/concepts/compliance-and-identity/compliance-policy)).

DALP maintains the bypass list automatically for contracts deployed by registered token and add-on factories (such as settlements, escrows, and token sales). No Console screen or API edits it directly, though a System manager can register or upgrade factories and a Compliance manager can call the compliance contract directly.

## API routes [#api-routes]

The [Platform API reference](https://docs.settlemint.com/docs/api-reference/v2) exposes system compliance module endpoints (all requiring Compliance manager unless noted):

- **Install or reconfigure:** Creates a module instance when `instanceAddress` is omitted (refusing duplicates of the same type) or updates an existing instance when supplied.
- **Scoped install and replace:** Creates a module instance with its scope in one transaction (what the Console uses, allowing multiple rules of the same type) or replaces parameters and scope together.
- **Wallet restriction guard:** Every install endpoint refuses the wallet restriction module with [DALP-12285](https://docs.settlemint.com/docs/api-reference/errors) (`system-installed-only`), while the scope-update endpoint accepts existing instances.
- **Register implementation:** Registers a custom module contract in the system registry (requires System manager, also available in a control's sheet under **Use a custom contract for this control**).