Reusable compliance templates for DALP assets

Create, publish, and reuse compliance templates that group DALP compliance modules for asset creation.

Compliance templates group compliance modules for reuse during asset creation. Operators can keep a template in draft, publish the template when ready, and then select the published template in the Asset Designer.

Use this guide when you need to turn a repeatable policy pattern into something asset creators can apply without rebuilding the same country, identity, transfer, supply, or collateral controls for every asset.

What are compliance templates?

A compliance template is a collection of compliance modules with predefined configurations. When you apply a template to an asset, DALP copies the template modules into the asset's compliance configuration.

How template types fit together

DALP separates reusable asset setup into three template areas:

Template type	Defines	Usage
Compliance template	Compliance modules, jurisdictions, required controls, and draft or published status.	Selected in the Asset Designer compliance step when an asset should reuse a policy pattern.
Token template	Token-level behaviors the issued asset should include, such as maturity, fees, yield, conversion, or permit support.	Managed through instrument templates as required token features and feature configuration.
Metadata template	Asset data fields the Asset Designer should collect, including field key, label, type, required status, mutability, and constraints.	Managed through instrument templates and completed during asset creation.

These template types compose with each other. An instrument template can require token behaviors and metadata fields, while a compliance template supplies the policy controls selected during the compliance step.

Why use templates?

Reusability: Apply the same compliance module pattern to multiple assets
Consistency: Keep assets in the same category aligned to the same configured controls
Efficiency: Configure compliance modules once and reuse them across your portfolio
DALP library templates: Start with pre-built templates designed for common compliance patterns

Template detail page

When you open a compliance template, you see the template detail page with all the key information at a glance.

Inline metadata bar

The top of the template detail page displays an inline metadata bar showing:

Status: Whether the template is published or in draft mode
Jurisdiction: The regulatory jurisdiction the template is designed for (or "Global" for multi-jurisdictional templates)
Version: The current version number of the template
Last updated: When the template was last modified

This information helps you quickly identify the right template for your needs without opening each one.

Template content

Below the metadata bar, the page displays all compliance modules included in the template, organized by category:

Eligibility: Modules that control who can hold your assets (identity verification, allow lists, block lists)
Restrictions: Geographic and address-based restrictions
Transfer controls: Rules governing asset transfers
Issuance and supply: Limits on token supply and investor count
Time-based rules: Holding periods and time locks
Settlement and collateral: Collateral requirements for asset issuance

Module classification tags

Each compliance module in a template displays classification tags that help you understand its purpose:

Tag categories

Tag	Meaning
Eligibility	Controls who can hold or receive assets based on identity verification
Identity	Validates investor identity through verified credentials
Restrictions	Limits asset ownership based on geography or specific addresses
Security	Enforces security measures like transfer approvals
Limits	Caps the number of holders or total supply
Transfer	Controls how and when transfers can occur

Viewing enforced rules

When you expand a module's information, you can see exactly what rules it enforces. This helps you understand the full impact of each compliance module before enabling it.

Filtering templates

The templates index page offers multiple filters to help you find the right template quickly:

Search

Type in the search box to find templates by name or description.

Jurisdiction filter

Filter templates by regulatory jurisdiction. Select a specific country or "Global" for templates that work across jurisdictions.

Source filter

Filter by template source:

DALP library: Pre-built templates provided by DALP for common compliance patterns
Organisation: Custom templates created by your organisation

Status filter

Filter by template status:

Published: Active templates ready to apply to assets
Draft: Templates still being configured

Creating a new template

To create a new compliance template:

Navigate to Platform Settings → Compliance → Templates.
Use the page-level Version filter to choose the generation you want to work with. Current lists current-generation templates, Legacy lists legacy templates, and All lists both.
Click Create template and select:
- From scratch to build a new policy from the ground up.
- From existing to copy an existing template.
When you create from an existing template, choose a Source Template. The source list follows the page-level Version filter. In All mode, legacy source rows are marked so you can tell same-named templates apart.
Choose the module generation for the template. From-scratch templates start on the current generation by default. Templates copied from an existing template start with the source template's generation, but you can still change the generation before saving. If copied modules or required controls are not available in the generation you select, DALP asks you to confirm and removes the incompatible items from the new template.
Configure the compliance modules and required controls you need.
Set the template status to Published when ready.

Required controls

Required controls define which compliance controls must be present when the template is applied to an asset. Use them when a template should make a policy control mandatory, but the final parameters still need to be completed during asset creation or later governance.

Required controls are saved as compliance control IDs. They must match the template's module generation, so do not mix legacy and current-generation controls in the same template. If a control is not compatible with the selected generation, DALP rejects the create, update, or publish action instead of saving a template that asset creators cannot apply safely.

When you select required controls, the selector shows a generation marker next to each control name. Use the marker to distinguish controls with similar names and to select the generation that matches the template you are creating. The marker is display guidance only: the saved template stores the selected raw control IDs, not the badge text.

Which controls can a template require?

A compliance template can require the same control families that DALP can attach to an asset.

Use this table to decide whether the policy should be fixed on the template or left for the asset creator to complete.

Control family	Example controls	What the template can standardise
Geographic restrictions	Country allow list, country block list	The allowed or blocked jurisdictions for a product family.
Identity and address lists	Identity allow list, identity block list, address block list	The identities or addresses that must be allowed or blocked before the asset starts operating.
Verification requirements	Identity verification	The claim topics holders must satisfy, such as KYC or accreditation. Claim-policy managers still configure trusted issuers and topics.
Holder and supply limits	Investor count, token supply limit, capital raise limit, issuance volume limit	Caps and thresholds that must be present for the asset.
Transfer controls	Time lock, transfer approval	Holding-period rules or approval requirements that should apply before transfers execute.
Collateral controls	Collateral requirement	The backing-evidence rule that must be present before minting assets that depend on collateral verification.

Required controls describe token-compliance rules that the asset must carry after the template is applied. They can require the rule family, but they do not replace claim-policy management: a claim-policy manager still owns trusted issuer setup, claim topics, and issuer-topic permissions for verification-based controls.

Current-generation templates use the current control set by default. Legacy-only controls stay available for legacy templates, but DALP does not let a current-generation template require a legacy-only control.

Decide what stays configurable

Each module can either carry fixed values from the template or leave selected values configurable in the Asset Designer. Use this split deliberately:

Policy decision	Keep fixed on the template when	Leave configurable during asset creation when
Jurisdiction or country list	Every asset created from the template must use the same allowed or blocked jurisdictions.	The asset's market, investor base, or distribution region changes per issuance.
Identity and address controls	The same allow list, block list, or identity-verification policy applies to the whole asset family.	The policy is mandatory, but the exact list or verification setup is chosen for each asset.
Transfer approval	The same approval model and authority set applies to every asset created from the template.	The asset needs transfer approval, but the authority list or approval window is asset-specific.
Holder, supply, or capital-raise limits	The limit is part of the product policy and should not vary between assets.	The limit depends on the individual offering, issuance size, or governance decision.
Collateral controls	The same collateral rule applies to the whole product family.	Collateral terms are set per asset or per issuance program.

Before publishing, review each required control and module setting from the point of view of the asset creator. If the asset creator must provide the value to complete issuance, keep that value configurable. If changing the value would break the intended policy pattern, keep it fixed in the template.

Applying templates to assets

When creating a new asset using the Asset Designer, select a compliance template on the compliance step. DALP copies the template's modules into the asset's compliance configuration.

Review the compliance module index before publishing or applying a template. The index shows which controls apply to transfers, minting, burns, pre-checks, and lifecycle accounting hooks. Use it to confirm that the template matches the asset's policy before holders depend on it.

You can also change the compliance template for existing assets if you have the governance role, though this should be done carefully to avoid disrupting existing holders.

Draft templates are hidden from the template selector during asset creation
Published templates are available to apply to new assets

This lets you prepare templates in advance without making them available until ready.

Compliance templates