Add organization domains and finish SSO setup
Last updated: November 19, 2026
Available on: Web admin portal for administration; Mac, Windows, iOS and Android for SSO sign-in.
Link your company email domains to the right Flow organization, verify ownership by DNS, and connect SSO so eligible teammates can join and sign in.
Request domain changes
Wispr must add, change or remove domains; admins cannot edit the domain list themselves. Each active domain belongs to one organization. Matching is exact: mail.example.com is not covered by example.com. Capitalization and surrounding spaces do not affect matching or bypass restrictions.
Supply a bare domain such as example.com: at least three characters, including a dot, with no @, internal whitespace, web-address prefix or path.
Warning: Removing a domain hides it from settings, stops automatic joining for that domain and removes it from your SSO configuration. You cannot remove the last active domain. Removal preserves verification and domain-joining settings for restoration, but restoration is blocked if another organization has since claimed the domain. Repeating an add or restore request does not create a duplicate.
The signed-in account determines which organization you manage.
Sign in to the Flow admin portal with an organization admin account.
Email enterprise@wispr.ai with the complete domain list (including domains planned for later), the organization name and its admin email, your identity provider if you are setting up SSO, and the reason for the change — rebrand or acquisition, replacing or removing a domain, or consolidating organizations. No domain-count limit is published; support can confirm any restrictions.
Follow any verification or sales-assistance instructions provided for your organization.
Wait for confirmation before testing affected users.
Domain additions, restorations and removals are recorded in the organization audit log. Only DNS-verified domains are added to SSO; without an SSO configuration, they wait until setup. If an SSO update fails, the Flow domain change still applies and support can retry the update. Separately added SSO domains are left unchanged unless removed through Flow.
Restricted or sales-assisted domains
A domain owned by another organization cannot be added. Support must resolve any availability-check failure before adding a domain.
Educational, government, military and treaty-organization domains — .edu, .gov, .mil, .int, .ac.in, including country variants such as .gov.uk and .edu.au — are restricted unless pre-approved. Approval covers only the exact domain, not its subdomains. University restrictions can also apply to domains with other endings. Free or disposable email domains and their subdomains cannot normally be attached; Wispr assistance is required for an exception.
An explicitly entered restricted domain produces Cannot create organization with a public domain in the web admin portal. Mac and Windows instead use a generic Failed to create team message, possibly with details. Creating a team without explicitly entering a restricted domain can succeed, but that domain is not attached and cannot enable domain-based joining.
Commercial domains can separately require sales-assisted onboarding; send the exact domain and message to support, your sales or customer-success representative, or talk to sales. This is distinct from the public-domain refusal: .edu, .gov and free-email restrictions do not produce the sales banner. Desktop onboarding may show Your domain requires sales-assisted onboarding. Please reach out to sales.
Verify domain ownership
Only organization admins can verify domains or view verification status. If none are linked, the portal says Your organization is not linked to any domains. Contact enterprise@wispr.ai to add one.
In Settings, find Require users on your domains to join your organization. The label uses team instead of organization for accounts without departments.
Open Manage domains.
Select Start verification, or Continue verification if you already started it during this page session.
Copy the DNS details using Copy host and Copy value after Verification token generated appears.
Publish the TXT record at _wispr-verify.<domain> with Flow's exact wispr-verify=<token> value.
Wait for DNS changes to become available; this can take an hour or longer.
Select Check verification.
Success shows Domain verified successfully; the domain changes from Unverified to Verified with its verification date. The TXT value is shown only while unverified, and Check verification is unavailable until a value exists. Verified domains need no further check.
If you see TXT record not found yet. Try again in a minute., check the host and full value, wait, then retry manually. Checks are not automatic; DNS lookup problems also leave the domain unverified. Last checked identifies the last attempt. Rapid repeated checks can be limited, so wait before retrying.
After reloading the page, an unfinished domain shows Start verification again; it reuses the same token. Tokens do not expire, and support cannot bypass the exact TXT match. Verification is required before enabling the requirement for domain users to join your organization or team.
Finish the SSO connection
Note: SSO setup requires Enterprise SSO access and an Admin, SuperAdmin or IT Admin role. Non-admin members do not see the Single sign-on card. Without SSO access, admins see an Enterprise badge and disabled Configure SSO button in the SSO / SAML authentication row; the row stays hidden while access loads.
SSO setup does not register domains or include unverified domains, including older ones. An existing SSO link is reused even if no domains are verified. Continue from your saved identity-provider configuration rather than starting over.
Open Settings → Universal controls → Single sign-on in the admin portal.
Choose Configure SSO (new), Finish setup (in progress), or Manage SSO (connected).
Follow the identity-provider instructions in the separate setup portal window.
Configure the SAML application and assign the users or groups that should have access.
Complete test authentication if offered.
Select Refresh your SSO connection beside the SSO button in Flow.
Success shows Single sign-on is active. Wait for a check to finish before refreshing again. Flow also checks once when the organization loads if a connection or unfinished setup is not already known; a completed connection can also be recognized during sign-in.
Hover over or keyboard-focus the icon beside the SSO row label to read connection-status details. If you deleted or replaced your identity-provider connection, refresh to clear the old connection so sign-ins use its replacement.
Warning: Enforcing SSO blocks other sign-in methods for covered email domains on all clients; communicate the change first. Enforcement requires active billing and does not block sign-in if the domain or organization cannot be identified, or if an unexpected error prevents the check.
Members can use SSO without enforcement. Enable the Enterprise-only Enforce SSO for all members setting only if required; it appears below SCIM provisioning once SSO is active. Configure SCIM remains disabled until SSO is connected and active.
SSO setup is unfinished or the connection fails
Setup failures show Failed to set up SSO. Please try again. Connection failures show Unable to connect to your SSO provider. Check your SSO configuration and try again.
Confirm the provider configuration belongs to this organization and includes a linked, verified domain.
Complete the portal instructions; an inactive connection offers Finish setup.
Refresh the connection again after completing setup.
Use the success message above to confirm completion. If no matching connection exists, finish setup before retrying. If the domain or SSO configuration belongs to another organization, the update cannot proceed; contact support.
Test member access
Confirm a user with each exact email domain can join and sign in. Members enter their full work email address for SSO; sign-in from an identity-provider dashboard also works.
Mac and Windows
Choose SSO in the browser, not inside the desktop app.
Select Sign in via browser.
Enter your full work email on the browser sign-in page.
Select Continue with SSO.
Complete authentication with your identity provider.
Select Open Wispr Flow to return to the app; this does not happen automatically.
If the browser cannot open, use copy the sign-in link and paste it into a browser. Desktop shows a timeout after five minutes of waiting; restart sign-in. An unused copied link is cleared from the clipboard when the attempt ends. To change accounts on the return page, select Log in with another SSO account.
Android
SSO opens an external browser tab; your entered email is preserved when you return.
Select Continue with SSO.
Enter your full work email.
Select Continue, or the keyboard's Done action, once the email is valid.
Complete authentication in the browser.
While waiting, use Cancel to stop. After a browser failure, choose Try again or Use another method to return to the sign-in options.
iOS
Continue stays disabled until you enter a valid full email address.
Select More options.
Select Continue with SSO.
Enter your full work email.
Select Continue to authenticate with your identity provider.
Note: Linking a domain does not guarantee automatic joining. Exact-domain mismatches, automatic-add settings, seat caps, membership in another organization and billing conditions can prevent it. Directory-sync organizations skip domain joining and automatic invite acceptance; IT must add users through the identity provider. Linking a domain never changes account emails or merges individual account data.
SSO, Google, Apple and Microsoft sign-in attempt to accept a pending invite and apply eligible domain-based joining before checking members-only access. A successful join can add a paid seat immediately on per-seat plans. If a multi-team organization has no live team specified by an invitation, the user must pick a team before a seat is billed.
Without active organization billing, a user with a personal subscription receives an invitation to accept explicitly instead of automatically joining. Invitations for organizations whose billing has ended remain pending for explicit acceptance.
Resolve member sign-in errors
On an error page, use Back to login if offered; otherwise restart from the app or site where you began.
No organization or unfinished SSO
SSO Requires Being A Part Of An Organization means no organization matches the email's exact domain. Use another sign-in method, and ask support to confirm the exact domain is linked to the intended organization.
Your Organization Has Not Configured SSO instead means the domain belongs to an organization whose SSO connection is not ready. Retrying sign-in can recognize a completed connection; if the page remains, it requires an admin to finish the connection using the recovery steps above.
Android shows both cases inline beneath the email field as SSO isn't available for this email. Try another sign-in method, or contact your administrator if your company uses SSO.
Verified Email Required on Android
If Android shows Verified Email Required, the Microsoft, Google, Apple or SSO account has no email address or an unverified one. This page is limited to recognized app sign-ins that have not completed email-code verification; other cases return an error instead.
Select Return to Wispr Flow to return to the app and sign in another way; verify an email address with the identity provider, or ask IT to add one, before retrying.
Organization access or sign-in method is restricted
You were not invited to this organization means the email domain is associated with an organization, but the account is not a member. This can affect SSO, Google, Apple and Microsoft sign-in. Ask your administrator to invite the account or link the domain.
Account Managed by Your Organization means directory sync controls access: ask IT to add the account. This restriction is separate from SSO enforcement and does not require active billing.
Organizations can restrict sign-in to members only while billing is active, through a verified-domain requirement to join or an organization access restriction. Public email domains are excluded; unexpected errors leave sign-in allowed.
If your organization requires SSO, other methods cannot complete sign-in. Restart from the app or website, choose Continue with SSO and enter your work email; ask IT to resolve an enforcement mismatch.
Other access restrictions
After too many sign-in attempts, wait before retrying; repeated attempts can prolong the wait. Activity from others on a shared network can also trigger a sign-in limit. Restart an invalid or expired attempt.
If your organization blocks mobile sign-in, contact your administrator. Where this restriction applies, it requires active billing and does not block sign-in when its check fails. If your IP address is blocked, connect from an approved network or contact your administrator.
An account being deleted cannot sign in. If sign-in is temporarily unavailable, try again shortly.
Still need help?
Contact support if a domain conflicts with another organization, or if access still fails after verification and connection checks. Send the organization name, full domain list, affected email address, identity provider, platform and device, the exact error, and the steps you tried.