Global controls

Global controls let a compliance manager enforce one rule across every token in the system at once. You configure the control once at the platform level, and every bound token inherits it, including tokens created later. This removes the gap a per-token setup leaves: a control you cannot accidentally forget to add to a new instrument, and a single place an auditor can read to confirm the platform-wide policy. Reach for global controls when a rule must hold everywhere, such as a sanctions block list or an investor-eligibility check that no token should be allowed to skip.

Use this guide when you want a control to apply everywhere by default, rather than adding the same module to each token's own compliance policy.

Global controls vs token controls

A token's own compliance modules apply only to that token. A global control applies to every token bound to the system. The two layers stack: a transfer passes only when the token's own modules and the inherited global controls all approve it.

You still configure the same control families in both places. The difference is reach: a global control is inherited by every token instead of being added to each one.

Prerequisites

• You hold the Compliance manager role for the system. The platform rejects global control changes from any other role.
• Your wallet is verified. The platform asks you to confirm with your verification method before it submits the change.
• The control you want to add is available in the system's compliance module registry. Global controls draw from the same module catalog as token controls.

Open the Global controls page

Go to Organisation settings → Compliance & verification → Global controls. The page lists the controls currently enforced across the platform and lets you add, configure, scope, or remove them.

Add a global control

1. On the Global controls page, choose the control you want to apply across the platform from the available compliance modules.
2. Enter the control's parameters, the same parameters you would set when adding the module to a single token.
3. Confirm with your wallet verification.

The platform queues an on-chain transaction. When it confirms, the control is active and every bound token inherits it. A token's Compliance tab marks the control as inherited so operators can see it applies even though it was not added to that token directly.

A single control type can hold more than one global rule. Use Add rule when you need the same control to behave differently for different transfers, such as one rule for most activity and a second, scoped rule for a defined set of senders or receivers. To change a rule you already created, edit that rule rather than adding a duplicate of it.

Narrow a control with scope

A global control applies to every bound token and every transfer by default. When a rule should reach most activity but not all of it, give the rule a scope. Set a scope when you add a rule, or change the scope of an existing rule at any time. The rule still lives at the platform level; its scope narrows where it takes effect along two dimensions.

Which tokens inherit the rule

The token dimension decides which tokens carry the control. A token that matches the token scope inherits the rule and shows it on its Compliance tab. For a token outside the token scope, the rule skips validation and does not appear on the token's Compliance tab. If the operator has enabled "Track transfers outside this scope" for the rule, the platform still runs accounting and state hooks for that token so excluded activity is recorded; otherwise the rule is fully dormant for that token. Because the token dimension keys on token classification rather than a fixed list of addresses, a token that later matches begins inheriting the rule automatically, with no per-token change.

Which transfers the rule checks

The sender and receiver dimensions decide which transfers the rule evaluates on a token that inherits it. Use them to include or exclude transfers by the sender or receiver, or by their country, so a rule visible on a token can still apply to only the transfer parties you intend. Leave these dimensions open to check every transfer on the inheriting tokens.

Update a global control

To change a control's parameters, open it on the Global controls page, edit the values, and confirm with your wallet verification. The platform queues an on-chain transaction and the new parameters take effect when it confirms.

The capital raise limit control is the exception. Its configuration is fixed once the control is created and cannot be edited afterward. To change a capital raise limit, remove the existing control and add a new one with the parameters you want.

Remove a global control

Open the control on the Global controls page and remove it. The platform queues an on-chain transaction. When it confirms, tokens stop inheriting the control. Removing a global control does not change any control a token configured on its own policy.

Operating considerations

• Global controls apply forward. Adding a control changes which future operations pass; it does not retroactively reverse balances that already settled. Coordinate any remediation of existing holders through your operating runbook.
• A control you soft-disable or scope out of a token no longer reads as inherited on that token's Compliance tab. Validation stops immediately. Accounting and state hooks stop only when out-of-scope tracking is disabled for the rule.
• Global controls and token controls are evaluated together. When you debug a blocked transfer, check both the token's own policy and the inherited global controls.

What stays external

DALP enforces the controls you configure. The policy decision behind each control, the provider relationships, and the legal approval to operate stay with your compliance team. Global controls make a policy easier to apply consistently; they do not replace the policy.

Troubleshooting

Read next

• Compliance overview for the full compliance module catalog.
• Policy templates to reuse a configured set of controls across asset issuances.
• Configure trusted issuers for the issuers whose claims compliance controls read.