ENS Subnames for Teams: Setup, Control and Costs

ENS subnames let a team organize identities beneath a parent name, such as a hypothetical pay.yourproject.eth or member.yourproject.eth. The useful decision is the control policy: who may create names, edit their records, reassign them and keep the parent registration active.

Choose a task that benefits from a shared name

Start with a concrete job: a project’s receiving address, a recognizable contributor identity or a community profile. Write the full identifier and the app action beside it. A shared suffix may communicate affiliation, but an organization must decide how to communicate a person’s actual authority.

For example, a studio might use separate pay and support labels for public instructions. That does not mean anyone reading those labels should infer that every holder can sign contracts or approve spending. Keep the meaning of a name clear in the instructions people see.

Prepare the parent and allocation policy

Ordinary parent-controlled subnames should not be presented as independent permanent ownership. ENS’s basic creation guidance describes parent control; other wrapped arrangements can restrict that control. Inspect the actual configuration before promising a holder that a name cannot be reclaimed.

Create a basic subname in the ENS App

1. Open app.ens.domains with the wallet permitted to manage the parent.
2. Find the parent name and open Subnames.
3. Choose + New subname and enter the intended label.
4. Review the optional profile records and proposed transactions.
5. Approve the matching request, then check the confirmed subname and its records.

The current guide says creation has no separate ENS registration fee, but Mainnet gas applies. Preloading profile records can require another transaction. A third-party issuing service may add its own terms and fees, so distinguish that service from the basic app route.

Verify one complete pilot

Use one noncritical pilot identity before a larger rollout. Record the full name, expected receiving address and intended manager. Have another maintainer independently check the confirmed records and the exact app lookup.

Ask the recipient to perform the action you intend them to use, within the appropriate approval process. Record whether you checked a read-only lookup, profile display or completed payment. These are different observations. Our address-record guide and compatibility guide help define the test.

Also rehearse the organizational handover on paper: who requests a change, who can authorize it, what should be updated and who verifies the result. That exercise can reveal a missing maintenance role before the name is public.

Understand wrapped permissions and expiry

The ENSv1 Name Wrapper can restrict transfer, parent control and other actions through fuses. Its current guidance warns against locking names or burning fuses because upgrade limitations may follow. Burned restrictions cannot simply be reversed during the live wrapped term; the relevant expiry matters.

For wrapped subnames, the issuing documentation distinguishes expiry and renewal rights from the parent’s own registration. A holder’s ability to extend depends on the actual permissions. Review that configuration before describing the name as owned for good.

A community program needs more than manual creation

Creating a few team names and selling registrations to the public involve different operating work. ENS’s issuance documentation describes registrar contracts for self-service registration or renewals. Price collection, eligibility, expiry policy and support must be designed around that service.

If members pay, explain what they receive and what can change. The community namespace comparison contrasts that operating model with Freename’s TLD royalty program. Neither model supplies customers automatically.

Use the issuing project’s interface when appropriate

A Basename or another project-issued subname follows its issuer’s registration and maintenance rules. ENS support directs those workflows to the project’s own site. Use the Basename guide for that product rather than assuming every .base.eth holder controls base.eth.

For your own team program, keep the control policy beside the maintenance record and revisit it when roles change. These instructions are documentation-based; no subname, transaction or paid registrar was created for this article.