What resolver roles do
Names have resolvers. A resolver is a contract on the Ethereum network that answers questions about the name. It stores the name's records, and those records make up its ENS profile.
A resolver also has roles. Roles decide which wallets can change which records. You can give a wallet every role, or only a few, so it works for individuals, organisations and teams.
If you used ENS v1, this does the job a separate Manager did then.
For example, keep your name's owner on a cold wallet that stays offline, and give your everyday hot wallet the roles it needs to update your profile.
Give a wallet roles
Connect the wallet that owns the name, or one with Admin on the roles you want to give. Saving is a transaction, so you need a little Sepolia ETH for network fees (gas).
 |
 |
Open your name, select the Roles tab, open the resolver's roles (View and manage) and select Add user.
Enter the other wallet's ENS name or address.
Choose the Scope. See Scope below.
Tick the roles it needs at User level, such as Set Address or Set Text. Keep Admin with your owner wallet.
Select Save and approve in your wallet.
How resolvers are set up
The first time your wallet gets an ENSv2 name, by registering or upgrading, a resolver is set up for it. Names you get after that use the same resolver, so any roles you've set apply to them too. The resolver's Nodes tab in ENS Explorer lists every name that uses it.
You can also set up another resolver: on the name's Resolver tab, select Change resolver, then Deploy new permissioned resolver. Give it the roles you choose. That way you can keep different set-ups for different needs, and give each name the resolver that suits it.
A resolver set up when you registered already has two rows: your wallet and your smart account (HCA). Both hold every role over All names. Leave them in place.
Admin and user
Each role has two levels:
User: the wallet can do that job, such as set text records.
Admin: the wallet can do that job and decide which other wallets hold the role.
Roles can be changed later by any wallet with Admin on that role.
Scope
When you add a wallet, you also choose a scope. It sets how far that wallet's roles reach:
All names: its roles apply to every name that uses this resolver.
One text key: Set Text for one key only, such as the avatar, on every name.
One coin type: Set Address for one chain only, on every name.
The roles
Give only the roles the wallet needs. The Add user panel describes each one:
Set Address: "Can set address records".
Set Text: "Can set text records".
Set Content Hash: "Can set content hash records".
Set ABI: "Can set ABI records".
Set Interface: "Can set interface implementer records".
Set Name: "Can set reverse name records".
Set Data: "Can set data records".
Link: "Can link names to shared records".
Name Contract: "Can set the contract name of this resolver".
Upgrade: "Can upgrade the resolver contract".
Take access away
Open the wallet's row in the resolver's roles and remove its roles. This removes its access on every name that uses the resolver.
Don't remove your own wallet. If no wallet holds a role or its Admin, no one can grant it again.
Roles for one name only
Roles reach every name on the resolver. To give access to one name only, give that name its own resolver first. See Why do all my names share one resolver?
Upgraded from ENS v1?
If your name had a separate manager, the upgrade gives that wallet no record access. Follow the steps above to give it roles. Why ENSv2 has no Manager: What happened to the Manager role?
For roles on the name itself rather than its records, see Grant registry 'roles' to manage your name.