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. That token is left waiting 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
A token's roles can only be migrated by a wallet that holds DEFAULT_ADMIN on that token. That is the wallet the original migration could not act through, so the final grant has to be signed by the admin who owns it. 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. When advanced accounts is enabled and at least one participant still holds roles on their signing address that are not mirrored to their smart account, the token page shows a warning:
Roles not migrated to smart accounts. Some participants on this token still hold roles on their signing addresses that haven't been migrated to their smart accounts.
What you can do next depends on the wallet you are connected 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 warning is derived live from current role membership, so it disappears on its own once every participant's roles are mirrored, whoever 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 how many roles will be granted to their smart account. Existing signing-address roles are left unchanged, so the migration only adds the missing roles to the smart account and there is no risk of locking anyone 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 some participants fail while others succeed, the sheet stays open and reports how many could not be migrated. The participants that already succeeded keep their granted roles, so you can simply retry to finish the remaining ones. When every participant reaches Done, the token is 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. Whoever can view the Advanced accounts settings usually cannot sign these grants, so the list surfaces the outstanding work rather than running it. Use it to find each token's admin and ask them to complete the migration from the token's own 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 | How many participants on the token still have 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. Because the list reflects current role membership, a token drops off as soon as its last affected participant is migrated.
Where this fits
This token-level migration is the asset-side counterpart to the platform-level Sync permissions action 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 action, 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 Account abstraction.
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.