Organization Owners can add company email domains that identify members of the organization.
Additional email domains require Pro with the €29/month email domains add-on, excluding VAT, or Enterprise. Disabling the Pro add-on starts a 14-day wind-down. Your oldest verified domain stays active, and additional domains keep working during the wind-down before becoming inactive. See Plans & features for the plan comparison.
The add-on is not available during the seven-day Pro trial, even when a payment method is present. Add a payment method during the trial to keep monthly Pro, wait for Pro to become active at the trial boundary, then enable the add-on.
Enable the Pro add-on
An Organization Owner can enable the add-on from Settings → Email Domains. Display.dev adds it to the organization's existing Pro subscription and attempts the prorated payment immediately.
If the payment cannot be completed or billing details need attention, the add-on stays off. Open Settings → Billing → Manage billing, update the requested payment or billing details, then return to Email Domains and retry. Display.dev does not enable the add-on while billing is incomplete.
If Display.dev returns “Billing result could not be confirmed. Do not retry. Contact support,” follow that instruction. Support must check the subscription before another charge is attempted.
The CLI and agent tools follow the same recovery rules. They return the Billing link when payment or billing details need attention. An agent must explain the €29/month charge, excluding VAT, and get confirmation before each new enable attempt.
Add and verify a domain
Open Settings → Email Domains, enter the domain, and add it. Display.dev gives you a TXT record:
- Add the TXT record at your DNS provider.
- Wait for DNS changes to become available.
- Select Verify.
The pending domain does not change sign-in or membership. After verification, people with a verified email address on that exact domain can join the organization as Members.
You can use the same workflow from the CLI:
dsp email-domains add <domain>
dsp email-domains verify <domain>
dsp email-domains list
dsp email-domains remove <domain>Agents can use add_email_domain, verify_email_domain, list_email_domains, and remove_email_domain.
Transfer a domain already in use
Adding a domain that is connected to another Display.dev organization starts a transfer request. Publish the fresh TXT record and verify it. The earlier verification record does not satisfy the new request.
After DNS verification, a target Owner can review the people who will move in Settings → Email Domains. Final confirmation is available only in the dashboard. CLI commands and agent tools can start, verify, inspect, or cancel the request, but they cannot complete it.
The source Owner does not approve the transfer. Control of the DNS record and confirmation by a current target Owner provide the required authority.
Transfer requests expire after seven days. If a request expires, add the domain again to create a fresh request-specific TXT record. To cancel a pending, ready, or support-required request from the CLI, run dsp email-domains remove <domain>.
What an eligible transfer changes
An automatic transfer is available only when the other organization is an empty Free organization created for the same email domain. It must have no published content, invitations, credentials, billing, integrations, or unrelated members.
When the target Owner confirms:
- the verified domain moves to the target organization;
- people from the other organization join as Members, unless they already have a role in the target;
- source Owner and Admin roles do not move;
- the empty organization retires; and
- every affected person must sign in again.
The review lists the affected email addresses and the role each person will have before the Owner confirms.
When support is required
Display.dev stops the automatic transfer when the other organization contains content, billing, credentials, integrations, unrelated people, or other configuration. The page does not expose those details.
Contact support from the blocked request. After support confirms the issue is resolved, a target Owner selects Retry verification in Settings → Email Domains. The retry checks the same unexpired request against the current transfer requirements. It keeps the existing DNS proof and does not require a new TXT record.
If the blocker remains, the request stays support-required. From the CLI, run dsp email-domains verify <domain> again after support confirms the issue is resolved. Agents use the existing verify_email_domain tool. Neither action reveals the source organization's details.
An Owner can still cancel the request. If the request expires, add the domain again and publish that new request's TXT record. Transfers cannot be reversed from Email Domains settings after completion.
See Roles & administration for who can manage domains.