> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/account-setup-and-administration/managing-your-org/verified-domains.md).

# Verified Domains

Verified domains help your organization establish ownership of your company’s domain (e.g., yourcompany.com) within Docupilot. Once verified, your domain can be used to streamline user management, set-up and enforce Single Sign-On (SSO), and ensure secure access across your workspace.

#### Why Verify a Domain?

Verifying your domain ensures:

* Administrators can **enable SSO** for existing and new users under the verified domain.
* Only users with emails from verified domains can **join your Docupilot Organization via SSO**.
* Your organization maintains control over who can access Docupilot using your company domain.

#### How to Verify a Domain?

* Go to **Organization > Domains** in your org dashboard.
* Click **Add Domain** and enter your domain name (e.g., yourcompany.com).
* Copy the **TXT record** displayed on screen.
* Configure the TXT record in your DNS console (GoDaddy, Cloudflare, Name Cheap, etc).
* Once configured, return to Docupilot and click **Verify**.

  > *It could take up to 48 hours for the DNS records to be propagated based on your DNS caching settings.*

<figure><img src="/files/Z4TxzXP3JdNARiY1pxV8" alt=""><figcaption></figcaption></figure>

#### Locking a domain

After verification, you can **lock** the domain to prevent unauthorized account creation using your company’s email domain.

When a domain is locked:

* Only **Organization Admins** can invite users with emails from the locked domain.
* New sign-ups using that domain are blocked.
* If someone tries to create a new Organization using the same domain, it will **not be allowed**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.docupilot.app/account-setup-and-administration/managing-your-org/verified-domains.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.