All assets lists the tokens your organisation issued on the selected network, across asset classes and templates, halted ones included, and the external tokens it registered there. Open a row to reach the asset's token page: its key figures, holders, activity, documents and features, and the Actions menu for every operation your roles allow. For totals and trends, open Insights. To register a token deployed outside the platform, open External tokens.
The table follows the active organisation and network. When you belong to more than one organisation, or the organisation uses more than one network, you change them in the account menu at the top right. Search and column filters narrow that scope. When the table is empty and several networks are available, a network dropdown appears with the prompt “If your assets are on another chain, switch here.”
One row per issued token, with the search field and filter controls above the table and a shortcut menu on each row.
Steps
Open the list
Open “Assets” in the sidebar, then All assets. Assets appear newest first, 20 to a page.
The columns “Asset”, “Lifecycle status”, “Amount”, “Holders”, “Value”, “Price” and “Created” show by default. Columns that do not fit the window are hidden. “Amount” is the total supply, “Holders” counts the wallets with a positive balance, and “Value” is the total supply at the current price, converted into your organisation's base currency. “Value” stays empty for an asset with no price, or when no exchange rate converts its price. “Holders” stays empty for an external token.
“Token name”, “Asset class”, “Asset type”, “Instrument template”, “Family”, “Network” and “Identifier” start hidden. Select View to show them.
While no search or filter is applied, a deployment that is still running or that failed appears as a row at the top of the list, before the live assets. A running deployment shows “Deploying” with “In progress” under it. A failed one shows “Failed” and “Not created”, with the “Reason” in the row detail. Under its name, a deployment row shows the instrument template it was started from. When the deployment used no template, or that template was deleted, the row shows the asset type instead, such as “Configurable asset”. A failed deployment that created no token offers Discard, which only an Asset manager can complete. Its confirmation says that a failed deployment cannot be retried from this list and that you issue the asset again with “Issue asset”.
Narrow the results
Search by token name, symbol, or contract address. Add filters for “Asset class”, “Asset type”, “Instrument template”, “Family” or “Status” to narrow the results. Selecting an asset class keeps every template of that class. An asset whose type belongs to no asset class is listed under “Unclassified”. The filters and the search run on the server across all pages. Export in the table toolbar saves every matching row as CSV or JSON.
Each asset class also has its own entry under “Assets” in the sidebar. Its page lists the class's assets one template at a time. When the class has more than one template with assets, a Template select names each template with its asset count. The sidebar lists a class only while at least one asset of its templates exists on the selected network.
The “Asset class”, “Asset type” and “Instrument template” menus show only values with matching assets under the current scope and filters. If an expected value is absent, clear the other filters and check the selected network.
The Instrument template column links each token to its template definition for the Permission manager, System manager and Asset designer roles. Every other account sees the name as plain text.
Open the asset or act from the row
Select the asset's row. Its token page shows the logo, the name, a status badge, the Actions menu, a strip of key figures, and tabs. Read the token page describes each part.
On the “Holders” tab, the toolbar Export menu opens the sheet “Export holder register” for organisation owners, platform administrators and holders of a reporting role, on an asset that has the Historical balances feature or had it detached. Its tabs are “Register”, “Registrar file”, “Beneficial owners” and “Deliveries”. “Beneficial owners” files a declaration of the owners behind a nominee wallet from a CSV file and reads the holder register looked through to those owners at the record block, with stale nominee wallets flagged. See Issuer shareholder list.
The row's shortcut menu offers Copy address. “View on Explorer” appears when the selected network has a block explorer configured.
A token whose deployment landed on the network but whose setup stopped part way shows “Setup incomplete” with the step that failed and its reason. Its menu adds “Finish setup” and “Dismiss”. Only the user who issued the token, signed in with the same wallet, can finish the setup, and only an Asset manager can dismiss it. Finish setup asks for your PIN once and runs only the steps that did not complete, such as the role grants, the initial price, unpausing the token, or binding the conversion feature to its yield feature. “Dismiss” removes only the notice. The token stays on the network with the failed steps undone, such as a missing role grant or a token that is still halted.
Edit the holder rule
The “Compliance” tab opens with a Holder rule section when your roles let you read the asset's compliance configuration. It shows the token registry rule, which is the requirement the asset's identity registry checks on every receiving wallet. When the asset has an active identity verification module, the module's rule appears beside it. Both rules apply to transfers and mints. A custodian's forced transfer and a lost-wallet recovery check only the registry rule, so the module rule does not bind them.
An empty registry rule reads No verification requirement. Only wallets registered in the system identity registry and not marked lost can then receive the asset, and no rule can lower that floor.
A holder of the Governance role on the asset also sees Edit holder rule. It opens the expression builder with the current registry rule, and “Save holder rule” asks for wallet verification. Saving an empty rule removes the holder requirement once it applies. A holder rule change waits for a second person only while the “Administration” row under “Approvals” on General protects the “Compliance configuration” group. When the rule excludes a topic a holder can remove from their own identity, the platform refuses the save and the sheet shows its reason with a checkbox. Tick “I accept this warning” and save again to record the acknowledgement, or narrow the rule. An impersonated session cannot accept it.
A topic is a claim type on a holder's identity, such as knowYourCustomer. The topic list in the builder groups topics under Person, Asset, Issuer and Other. It includes the topics of the system and of the asset's own topic schemes, so a capacity topic your compliance team registered, such as intermediary, appears in its group.
When the asset has one active identity verification module and its rule differs from the registry rule, the same Governance role sees Move module rule to the registry. It asks you to confirm two writes: the registry stores the module's rule, then the module is removed from the asset. Wallet verification is asked once. The two writes cannot be sent as one, so the registry is written first. If the removal then fails, the rule sits in both places and the asset behaves as before, because both rules apply. The sheet offers “Retry removing the module rule”.
Write the check every holder must pass outside the OR group that lets a capacity claim through: sanctions. The form (sanctions lets a capacity claim skip sanctions screening.
Read the token page
The header shows the logo, the name, a status badge and the Actions menu, which lists the operations open to you. Most operations that need a role none of your wallets holds are left out. A few stay greyed out with the reason instead, such as “Refresh mark” without the Governance role. An operation whose role sits on another of your wallets is greyed out and names that wallet. A Governance role holder replaces the logo from the header, as Documents describes.
Key figures
“Total supply” and “Holders” sit under the header, followed by “Price” and “Supply cap” when the asset has them. Each figure has an info button. Its popover says how the number is calculated and names its “Source”, which is “Chain indexer” for total supply, holders and supply cap and “DALP API” for the price. “As of” gives the time of the latest indexed block, and a figure read from the indexer also names that block.
Price shows two decimals. When they round the exact price, it reads with ≈, such as ≈1.00 for 0.99725936, as the “Price” column of the asset lists does. A screen reader reads it as approximately that figure, and hovering over or selecting it shows the exact price. A price the two decimals show exactly carries no ≈.
Tabs
“Overview”, “Holders”, “Activity”, “Compliance”, “Features” and “Documents” are always present. “Corporate actions”, “Treasury”, “Governance”, “Blocklist”, “Permissions” and “Transfer pre-check” appear when the asset or your roles allow them. “Permissions” appears on an asset with access management, and “Governance” on an asset with voting power. At most seven tabs show in the row, and the rest sit under More. To review, grant or revoke the roles on the “Permissions” tab, see Roles and permissions.
- Overview opens with the “Needs you” card when an action waits on you, and the “Supply” chart, titled “Supply and reserve” when it draws the reserve line of an asset with a collateral rule. Below them sit the reserve, “Largest holders” with “All holders”, “Recent activity” with “All activity”, and the “Details” card.
- Holders is the holder register. See Holder register.
- Documents holds the asset's documents and notices. See Documents.
- Corporate actions runs corporate events. See Corporate actions.
- Blocklist freezes every token of one address. See Emergency halt and freeze.
- Transfer pre-check tests a transfer against the asset's compliance rules. See Transfers.
Activity
The Activity tab lists, newest first and 20 to a page, the events the token emitted, the events of its feature and identity registry contracts, and the events that name the token. Each row shows the date, the event with its two endpoints, the transaction hash and the amount. The “Contract” column starts hidden. A trade a trading venue settled in this asset shows as one swap row. A mint, burn or transfer shows as one row, without the ERC-20 Transfer to or from the zero address that the token emits beside it.
Filter by “Date”, “Type” or “Contract”. The date filter reads “Dates are in UTC.” and covers whole days in UTC. Its chip shows the chosen day in your language's date format. “Flows by week” at the top of the tab plots the minted and burned amounts and the net issuance of each of the last 13 weeks, with the number of transfers between holders in a small chart beneath, its axis marked in whole transfers. Mints and burns are not counted there. When a range has mints or burns but no transfers, the note reads “No transfers between holders in the last 13 weeks. Mints and burns are shown above.” Select a row to open a sheet titled with the event's name, with the transaction hash, the block, the sender and the event parameters. Export CSV downloads every event that matches the filters and says “Times are in UTC.”
Treasury
On an asset with maturity redemption, the Treasury tab lists the assets its contract holds with their symbol, balance, value and status. A tag next to the asset name, “Redeems at maturity” or “Yield”, marks the asset that pays holders. A contract that holds nothing reads “No assets held yet”.
Instrument structure
An asset that is one class of a multi-class instrument shows the Instrument structure section on its overview, with the instrument id, “This class” and the “On-chain attestation”. The attestation reads “Attested on chain by a trusted issuer”, “Attested on chain, but the issuer is not trusted for this topic”, “The on-chain attestation was revoked”, “The on-chain attestation cannot be read” or “The on-chain attestation does not match this token's pairing record”. The section is absent when the asset carries no instrument structure claim.
Troubleshooting
An asset is not listed
Clear the search and filters, then confirm the organisation and network in the account menu. Search by contract address if you have it. If the table is empty and several networks are available, use the network dropdown in the empty state to check the network where the asset was issued.
Issue asset is missing
Signal: no Issue asset control appears above the table. Cause: the button is shown only for an account that holds the Asset manager role. Fix: ask an organisation administrator to grant it if issuing assets is part of your role.
A filter option you expect is not in the list
Signal: an asset class, type, or template you know exists does not appear as a selectable filter option. Cause: the menus list only options with at least one matching asset under the current scope and the filters already applied. An option with zero matches is left out. Fix: clear the other filters first, and check the active network, since an option returns once assets that would match it are back in view.
A token shows Setup incomplete without Finish setup
Signal: the row shows “Setup incomplete” and its menu offers only Dismiss. Cause: only the user who issued the token, signed in with the same wallet, can finish its setup, and a deployment that started before the platform kept its create request cannot be finished at all. Fix: ask the user who issued the token to finish it. For an older deployment, dismiss the notice. The token stays on the network.
Frequently asked questions
Does All assets show assets that belong to other organisations?
The table lists tokens issued by the active organisation on the selected network, and the external tokens that organisation registered there, which can include a token another organisation issued. Switch organisation in the Organisation submenu of the account menu to view its issued assets.
What does the Created column show?
For an issued token, Created shows when it was created. For a deployment row, it shows when the deployment started. The table lists assets newest first.
Do halted assets stay in the table?
A halted asset stays in the table. Its “Lifecycle status” reads “Halted”, and you open its token page from the row to resume it. Use the Status filter to isolate halted assets during an incident review, or to exclude them from an inventory pass.
API routes
For an integration, use the token collection in the Platform API reference. The pagination guide explains how to page through results.