Asset detail workspace

The asset detail workspace is the operating view for one issued asset. Start here to confirm the token's status, holder state, configured features, compliance controls, documents, and available operator workflows before you mint, transfer, pause, update pricing or fees, or change control records.

Open the workspace from Asset management. Choose an asset class, open the asset type or template, and select the issued asset.

Use the page in this order:

1. Confirm the asset name, status, and breadcrumb in the header.
2. Use the tabs to review holder balances, workflow history, compliance, documents, feeds, permissions, and denomination details.
3. Open Manage Asset only after the review tabs show the current state.

Manage Asset is context-sensitive. DALP hides menu items that the current asset or system configuration does not support. Visible but unavailable items are disabled, and their tooltip names the permission, feature, or asset-state check that blocks submission.

What the workspace shows

The default tab summarizes the issued asset before you move into a specific workflow. It helps you answer four questions:

Feature tiles link to detail pages when a feature has its own workflow. Maturity, yield, conversion, AUM fee, events, verifications, and metadata open as full pages instead of staying inside the tab frame.

Token tabs

The tab bar is generated from the asset configuration. The common workspace tabs are Token information, Holders, Actions, Compliance, and Documents. Feeds appears only when the feeds directory is installed. Permissions and Denomination asset appear only when the token has the matching extension.

Token documents and metadata routes

The documents route is /token/{assetClassSlug}/{templateSlug}/{tokenAddress}/documents. Open it from the Documents tab to review and manage files associated with the asset.

The metadata detail route is /token/{assetClassSlug}/{templateSlug}/{tokenAddress}/metadata. Metadata opens from the metadata capability tile and uses a full detail page rather than the tab frame.

Compliance lists and frozen holders

Allowlist and blocklist behavior is represented through compliance configuration rather than separate public tabs in the current workspace.

Use the Compliance tab to confirm whether the asset has a list-based compliance module, such as an address, identity, or country blocklist. The module detail shows the configured list values for that control.

Use the Holders tab separately to review balances, available balances, frozen amounts, and fully frozen holders. Frozen holder state is a balance-control signal, not proof that a holder is present in a compliance blocklist.

Treat list changes and holder-freeze changes as compliance-sensitive operator workflows. Before changing either control, confirm the asset, address or identity, restriction reason, and role allowed to submit the change. Keep supporting evidence in your institution's review and audit process outside DALP.

Manage asset workflows

Use Manage Asset for workflows that change the token or open an operator sheet. The menu is permission-gated and context-sensitive.

Depending on the asset and system configuration, the menu can include minting, transfers, pause or unpause, forced transfer workflows, verification, transfer approvals, price updates, collateral updates, and token-sale creation. The menu also includes View events so you can inspect event history from the same asset context.

For conversion assets, use forced conversion only when the configured conversion workflow and your custody role permit a custodian-controlled conversion. For servicing-provider transitions, use exit control portability to plan the role, policy, holder, document, and evidence records that need review before authority changes.

Transfer approvals

If the asset uses the TransferApproval compliance module, approval authorities can use Manage Asset to approve a specific sender, recipient, and amount before the holder submits the transfer. The approval sheet accepts source wallet, recipient wallet, and amount, then shows a confirmation summary before wallet verification. The platform records the approval against the sender and recipient identities used by the module.

Review existing approvals from the Compliance tab. The Transfer approvals table lists the sender identity, recipient identity, approved amount, expiry, and status. Pending approvals can be revoked from that table when your role permits revocation. Consumed and revoked approvals remain visible as review records; create a new approval when the transfer needs a different amount, counterparty, or operating evidence.

For API-driven transfer approval workflows, see Token holders and transfers. For the compliance model, see Transfer approval.

External transaction fee checks

If an asset uses an external transaction fee, mint, burn, and transfer confirmation screens check the connected wallet before you submit when that wallet is the fee payer. The screen shows whether the wallet has enough fee-token balance and enough allowance for the external fee feature to collect the fee.

The readiness check applies when you:

• mint to the connected wallet
• burn from the connected wallet
• transfer from the connected wallet

When the allowance is too low, use Approve fee allowance from the confirmation screen. The approval flow selects the required spender, then the readiness check updates so you can submit the original workflow.

When an operator workflow charges a different wallet, such as minting to another recipient or burning another holder, that third-party wallet is not preflighted in the confirmation screen. Confirm the fee-token balance and allowance with that holder before submitting.

If an expected workflow is missing or disabled, check:

• your token-level role assignments on the Permissions tab
• whether the asset is paused
• whether the required compliance module or token feature is configured
• whether your wallet has enough balance for holder workflows
• whether your wallet has enough fee-token balance and allowance when the asset uses an external transaction fee
• whether the system-level feature and permission for the workflow are enabled
• for verification, whether the asset has a token identity
• for collateral updates, whether the collateral module is configured and the token identity address is available
• for token-sale creation, whether token sales are enabled, your user can create token sales, the asset has a registered token identity, and a token-sale addon factory is available

Related guides

• Create asset
• Register external tokens
• Review address book contacts
• Mint assets
• Pause or unpause an asset
• Force convert holder principal
• Keep control records portable during an exit
• Change asset admin roles
• Token feature catalog