Verifying domains
Verifying a domain tells Flynt that your organisation owns it. When someone whose work email is on a verified domain requests access, their request is routed straight to your org's admins instead of into the general sales queue. Because verification is by a DNS record, only the real domain owner can claim a domain.
You verify domains from Admin → Domains. You need the organisation admin role to manage them.
Add and verify a domain
- Go to Admin → Domains and enter a bare domain (for example
acme.com), then choose Add domain. Flynt creates a pending claim and shows you a DNS TXT record to add. - At your DNS provider, add the TXT record exactly as shown:
- Type:
TXT - Host / name:
_flynt-challenge.acme.com - Value:
flynt-verify=...(a unique token for your org)
- Type:
- Back in Flynt, choose Verify. Flynt looks up the TXT record and, when it finds the token, marks the domain verified.
DNS changes can take a few minutes (sometimes longer) to propagate. If verification reports that the record was not found yet, wait a short while and try Verify again -- nothing is lost, the claim stays pending.
Status badges
- Pending -- the claim exists and the TXT instructions are shown, but the record has not been confirmed yet. A pending domain does not route access requests.
- Verified -- ownership is confirmed. The domain now routes matching access requests to your admins.
Removing a domain
Use Remove on any domain to stop it routing access requests. You can re-add and re-verify it later if you need to.
Notes
- A domain can belong to only one organisation. If another org has already verified it, your claim is rejected -- contact support if you believe the domain is yours.
- Operators can also register a verified domain on your behalf. Either way the effect is identical: verified domains route access requests to your org.