Your organization
Verify a domain
Prove your organization owns an email domain with a DNS TXT record, so sign-in can route people at that domain to your identity provider.
Before ChecklistSquad sends anyone to your identity provider, your organization proves it owns their email domain. You publish a TXT record at the domain; ChecklistSquad looks it up.
Add the domain
In SSO & security, open the single sign-on setup or Domains, type the domain your people's addresses end with (for example acmeproperty.com) and choose Add domain. ChecklistSquad shows the record to publish:
| Field | Value |
|---|---|
| Type | TXT |
| Name | _checklistsquad-verify.acmeproperty.com |
| Value | checklistsquad-domain-verification=… (yours is shown in the app) |
Copy each value with the button beside it, or use Share setup details to send them to whoever manages your DNS.
Publish the record
Add the TXT record at your DNS host (Cloudflare, Route 53, GoDaddy, Google Domains, Azure DNS or wherever your domain is managed). Some hosts add your domain to the name for you: if yours does, enter only _checklistsquad-verify.
Check it
Choose Check DNS. Records usually show up within a few minutes, sometimes up to an hour. Until then the domain says why it wasn't found. When the record is found the domain is Verified, and you can remove the record or leave it.
Things to know
- One organization per domain. Once a domain is verified, no other organization can verify it.
- Personal email domains can't be verified. Gmail, Outlook.com, iCloud and other public mail services belong to nobody's organization.
- Subdomains are separate. Verifying
acmeproperty.comdoesn't covermail.acmeproperty.com; add each one people use. - Removing a domain sends people at it back to email codes, and lets another organization claim it.