Complete token role migration
Finish migrating a token's participant roles to smart accounts when advanced accounts skipped that token, using the token-page warning and the pending-tokens list.
When you turn on advanced accounts, each participant's access-manager roles move from their signing address onto the smart account that now transacts for them. The platform can only complete that move for tokens whose top-level admin authorised it. For any other token, the participant's signing address keeps the roles and their smart account holds none, so the smart account cannot act on that token. The token waits for its own admin to finish the migration.
Recognise that state, run the migration as the token's admin, and track outstanding tokens across your organisation by following the sections below.
Who can finish the migration
Only a wallet that holds DEFAULT_ADMIN on the token can migrate its roles. The original migration could not act through that wallet, so the admin who owns it must sign the final grant. Anyone else who opens the token sees the warning but cannot run the migration. They can only identify the admin and ask them to act.
Recognise a token that needs migration
Open the token from its asset page. With advanced accounts enabled, check for this warning banner:
Roles not migrated to smart accounts. Participants on this token hold roles on their signing addresses that the platform has not yet migrated to their smart accounts.
The banner appears when at least one participant still holds roles on their signing address without a mirror on their smart account.
What you can do next depends on the wallet you connect with:
- If your connected wallet is the token's admin, the warning offers a Migrate roles button.
- If it is not, the warning instead names the responsible party: the token's admin (
DEFAULT_ADMIN) must open the token and run the migration. Pass that on to whoever holds the admin wallet.
The platform derives the warning live from current role membership. It disappears once every participant's roles are mirrored, regardless of who completes them.
Run the migration as the token admin
- Open the token while connected with the wallet that holds its admin role.
- On the role-migration warning, select Migrate roles.
- Review the Roles to migrate summary. It lists each affected participant and the number of roles the platform will grant to their smart account. Existing signing-address roles stay unchanged. The migration only adds the missing roles to the smart account, so no one gets locked out.
- Confirm with your wallet verification method to sign the migration.
The migration grants each participant's missing roles to their smart account one participant at a time, and shows per-participant progress as Pending, Migrating, Done, or Failed.
If any participants fail while others succeed, the sheet stays open and reports the count that the platform could not migrate. Participants that already succeeded keep their granted roles. Retry to finish the remaining ones. When every participant reaches Done, the platform marks the token fully migrated and the warning clears.
Track outstanding tokens across the organisation
The Tokens needing role migration list on the Advanced accounts settings page shows every token in your organisation that still has participants waiting on migration. Open it from Organisation settings > Operations > Advanced accounts.
This list is read-only: viewers cannot sign these grants. Use it to find each token's admin and ask them to complete the migration from the token page.
| Column | What it tells you |
|---|---|
| Token | The token still waiting on migration. |
| Symbol | The token's symbol, to disambiguate similarly named tokens. |
| Affected participants | The number of participants on the token with unmirrored roles. |
| Token admins | The admin wallets that can finish the migration for this token. |
When the list is empty, it reports "All tokens migrated": no tokens are waiting on role migration. The list reflects current role membership. A token drops off as soon as the platform migrates its last affected participant.
Where this fits
This token-level migration is the asset-side counterpart to the platform-level Sync permissions step on the Admins & roles table. Both bring roles held on a signing address onto the matching smart account so it can act under advanced accounts.
- For platform administrator roles, see Change admin roles.
- For asset-level role changes and the per-participant sync, see Change asset admin roles.
- For the infrastructure behind advanced accounts and the settings page that hosts the pending-tokens list, see the Advanced accounts control center.
- For the conceptual model of how a signing address and a smart account relate, see Advanced accounts.
Advanced accounts control center
Review and fund the gas reserves behind advanced accounts from Organisation settings, including the submission reserve, sponsorship reserve, signer key, and recent on-chain activity.
Gas reserves
Understand how DALP's two gas reserves serve distinct roles in advanced-account transaction processing, and what each reserve's depletion means for platform operations.