Verifying your domain for domain capture

Last updated: June 5, 2026

Available on: Wispr Flow enterprise web app (admin only)

Verify your company's domain to control what happens when someone signs up to Wispr Flow with an email at that domain. Verification is self-serve via a DNS TXT record, and once verified, you can set a domain capture policy from Settings.

Before you start

  • You must be signed in as an enterprise admin (admin, superadmin, or IT admin) in the Wispr Flow enterprise web app. Members can't see the verification UI.

  • Your organization must already be linked to the domain you want to verify. If your Settings page shows "Your organization is not linked to any domains," contact enterprise@wispr.ai to add one.

  • You need admin access to your DNS provider (e.g., Cloudflare, GoDaddy, Namecheap, Route 53) so you can publish a TXT record.

Verify your domain

  1. Open the Wispr Flow enterprise web app and go to Settings. Each linked domain appears with a Verified or Unverified label.

  2. Click Start verification next to the unverified domain. A modal titled Verify [domain] opens and generates a unique TXT record with a Host and a Value.

  3. Copy both fields using Copy host and Copy value. The Host follows the pattern _wispr-verify.<your-domain>, and the Value always starts with wispr-verify=.

  4. Add a new TXT record in your DNS provider using the exact Host and Value, then save the change.

  5. Return to the Wispr Flow tab and click Check verification. If you see "Domain verified successfully," you're done. If you see "TXT record not found yet," wait a few minutes and click Check verification again.

Tip: DNS changes can take up to an hour (sometimes longer) to propagate globally. A failed first check is normal — give it time before troubleshooting.

Note: Check verification uses public DNS resolution, so the record must be publicly resolvable — split-horizon or internal-only DNS won't work. If you close the dialog before finishing, the button changes to Continue verification. Click it to pick up where you left off — your existing TXT record stays valid.

Set your domain capture policy

Once a domain is verified, a policy dropdown appears next to it on the Settings page. Choose what happens when someone signs up with an email at your domain:

  • Off: Do not restrict new sign-ups on this domain.

  • Require team membership: Users signing up with this domain must join this enterprise to use Flow.

You can change the policy at any time, and the new value takes effect immediately. On a successful change, a Domain capture policy updated toast appears. Until you pick one, the dropdown shows Not set and no domain capture rule applies.

Important: A domain must be verified before you can set a policy. The dropdown is unavailable on unverified domains.

Note: Enforcement of Require team membership is currently rolling out. After you set the policy, end users may not see the join prompt until the rollout reaches them.

What new users see during sign-up

When a new user signs up with an email address at your domain, they encounter a team step during onboarding. What they see depends on whether a team already exists for your domain:

  • Existing team detected: Users see a Team Consolidation step that pre-selects current teammates from your domain. They can add additional invite emails before joining.

  • No existing team: Users see a team creation step where they enter a team name (labeled "Create a team name," which can be changed anytime) and their organization name. They can also check Auto-add future @[domain] teammates, which automatically adds colleagues with the same email domain when they next log in. Invited team members are notified by email and added upon their next login.

FAQs

How is this different from verifying my domain for SSO?

They're independent. SSO setup is handled separately and doesn't require a customer-facing DNS step. Domain capture verification uses a DNS TXT record and only controls sign-up behavior on your domain. You can have one without the other. See Verify your domain for SSO for SSO setup.

Does verification ever expire?

No. Once a domain is verified it stays verified, and you can leave the TXT record in your DNS or remove it. We don't auto-recheck.

Can members see or change this?

No. Only admins (admin, superadmin, or IT admin roles) see the domain verification section in Settings, and only admins can start verification or change the policy. Non-admins see the message "Only admins can see domain verification status."

I added the TXT record but Check verification keeps failing. What should I check?

Confirm the following:

  • The Host and Value match exactly what the dialog showed. Extra spaces or quotes can cause failures.

  • DNS has had time to propagate. Up to an hour is normal, occasionally longer.

  • The record is on the correct domain (not on a subdomain by mistake).

If it still fails after an hour, reach out to support.

Can I verify multiple domains?

Yes. Each domain linked to your enterprise shows up as its own row in Settings, with its own verification status, TXT record, and policy. Verify and set a policy on each one independently.

When are invited team members notified?

Invited teammates receive an email notification and are added to the team when they next log in to Wispr Flow.

What does "Auto-add future teammates" do?

When a new user creates a team during onboarding, they can enable Auto-add future @[domain] teammates. With this on, anyone who later signs up with the same email domain is automatically added to the team upon their next login — no manual invite needed.

Still need help?

Reach out to support if:

  • Your Settings page shows your organization isn't linked to any domains and you need one added.

  • DNS has propagated (confirmed with a public DNS lookup tool) but Check verification still fails.

  • You want to remove or change a domain that's already verified.

Include your organization name, the domain you're verifying, and a screenshot of the TXT record in your DNS provider — that's usually all we need.