Using multiple email domains with one Wispr Flow account

Last updated: September 10, 2026

Available on: Flow Pro Team and Flow Enterprise accounts. Domains are added by Wispr support.

If your company uses more than one email domain — after a rebrand, an acquisition, or because teams use different domains — all of them can be linked to one Wispr Flow organization, so everyone shares one plan and one bill. There is no self-serve way to add a domain.

Before you start

  • Admin access: You need to be an admin on a Flow Pro Team or Flow Enterprise account.

  • Full domain list: Send every domain in one request — it is faster than one at a time.

  • Subdomains listed separately: Matching is per-domain and exact, so mail.example.com is not covered by example.com. Request each subdomain as its own entry.

How to request additional domains

  1. Submit a support request with your organization name and the domains you want added.

  2. Include your identity provider if you are setting up SSO, plus any domain that always needs support to register:

    1. .edu, .gov, .mil, and .int domains, and country variants such as .gov.uk and .edu.au.

    2. University and academic institution domains, including those outside the .edu TLD.

  3. Wait for support's confirmation reply. Once it arrives, the domains are linked.

Tip: Mention domains coming online later in the same request so we can plan for them.

Note: Free and disposable email domains (for example, gmail.com or outlook.com) cannot be linked to an organization.

What happens after your domains are added

  • Teammates can join: Anyone with an email at a linked domain can be invited to, or join, the same organization.

  • One plan: All linked domains sit under one plan, one seat count, and one invoice.

  • SSO coverage: SSO applies to users signing in with an email at a registered domain.

  • Enforced privacy settings: If your org enforces zero data retention, cloud sync off, HIPAA BAA, or automatic transcript deletion, members see those toggles locked with a note that the organization (or HIPAA policy) set them. For every setting an admin can enforce org-wide, see the Enterprise-enforced settings article.

  • Where to see them: Linked domains are managed in the web Admin Portal. The desktop and mobile apps do not display your organization's email domains, only your organization or team name in enterprise-related messages.

FAQs

How many domains can I add?

There is no published cap, so send the full list. If a domain cannot be linked, we will tell you why in our reply.

Are subdomains included automatically?

No — see "Before you start."

Do I have to verify each domain with a DNS record?

No. Domains linked by support need no DNS record, and there is no self-serve domain verification step today.

Does adding a domain change my bill?

Linking a domain alone does not. Your seat count changes as people join, since active members and pending invitations count toward billed seats.

Can I remove or change a domain later?

Yes. Send support your organization name and the domain you want changed or removed.

Will SSO work across all our domains?

Yes, once each domain is registered to your organization. Start from the Wispr Flow login screen (or the SSO screen in the mobile apps), enter your work email, and you will be redirected to your identity provider. Starting from your identity provider's dashboard is not supported. See Verify your domain for SSO.

What SSO sign-in errors might my users see?

Users on newly added domains may see:

  • Too many sign-in attempts. Please wait a moment and try again. — Shown after too many sign-in attempts in a short period.

  • Failed to sign in with SSO. Please try again. — Shown under the email field when SSO sign-in cannot be completed.

  • Existing account screen: Shown when the work email is already registered with Google, Apple, or Microsoft sign-in; the user must sign in with that provider instead.

Still need help?

Reach out to support if:

  • Teammates on a newly added domain cannot join your organization.

  • You need domains consolidated from separate Wispr Flow accounts into one organization.

  • Members are blocked from signing in from certain networks — your organization may have an IP allowlist configured.

Include your organization name and the full list of domains involved — that is usually all we need.