Company email domains

Organization Owners can add company email domains that identify members of the organization.

Additional email domains require Pro with the email domains add-on – €29/month or $29/month in your organization's billing currency, 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 and limits for the plan comparison.

The add-on is not available during the seven-day Pro trial, even when a payment method is present. Complete billing setup during the trial to keep monthly Pro, including the billing name, address, and tax ID if applicable. Then wait for Pro to become active at the trial boundary before enabling the add-on.

Enable the Pro add-on

An Organization Owner can enable the add-on from Settings → Organization → 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 → Organization → 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 do not enable or disable the add-on. A current Owner manages it in Settings → Organization → Email domains.

Add and verify a domain

Open Settings → Organization → Email domains, enter the domain, and add it. Display.dev gives you a TXT record:

1. Add the TXT record at your DNS provider.
2. Wait for DNS changes to become available.
3. 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.

Invite members from other email domains

An Owner can turn on Allow invitations to any email address in Settings → Organization → Security → Member invitations. This setting is available on every plan. It saves immediately: wait for Saved. If saving fails, the checkbox returns to the saved value; select Try again to retry the change.

Owners and Admins can then use the existing Members invitation form to invite people with Gmail or other email addresses as organization members. Only Owners can invite Admins. Membership gives the invited person access to Company artifacts and the usual publishing, editing, and commenting permissions. Private artifacts still require creator or explicit invited access.

Keep your company email domains attached. This setting changes explicit invitations; it does not claim outside domains or let uninvited people join automatically. Shared academic addresses already support exact-recipient invitations under the default policy.

Turning the setting off keeps existing members. Pending outside invitations that no longer meet the domain policy cannot create membership until the setting is enabled again. To remove someone's existing membership, use the offboarding flow in Members.

Sign-in requirements follow the recipient's email domain. A Gmail member may use an email code even when your organization requires SSO for its company domains. See Sign-in methods.

Remove a verified domain

An Organization Owner can remove a verified domain in Settings → Organization → Email domains, or with dsp email-domains remove <domain>. Existing members keep their membership. People using the removed domain no longer join the original organization automatically. Removing a domain releases its claim: someone with an address at that domain may create a new organization, and later signups at that domain may join it. Regaining the domain may require verification or transfer.

The dashboard warns before removing a verified domain. When invitations to any email address are off, removing all verified and dormant domains also removes the invitation domain restriction. A dormant domain can keep invitations restricted even after the last active verified domain is removed. Use Member invitations in Security to allow outside email invitations while keeping your domains. Domain-based SSO routing and enforcement for a removed domain also stop; check that existing members can still sign in.

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 → Organization → 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 → Organization → 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 Members and roles for who can manage domains.