---
title: "Verify a domain for your workspace"
description: "Prove ownership of your company's email domain with a DNS record to unlock SSO, automatic user provisioning, SCIM, and branded app URLs."
---

> Documentation Index
> Fetch the complete documentation index at: https://rshift.helpcent.re/llms.txt
> Use this file to discover all available pages before exploring further.

# Verify a domain for your workspace

<p>Verified domains let you prove to RShift Sites that your organization owns an email domain, such as <code>acme.com</code>. Verification happens once, through a DNS record, and unlocks the identity and provisioning features that depend on knowing which users belong to your company.</p>
<p>Once a domain is verified, RShift Sites can treat anyone signing in with an email on that domain (for example <code>jane@acme.com</code>) as a member of your organization, and apply your workspace's authentication and provisioning rules to them.</p>
<ul>
<li><strong>Available on:</strong> Business and Enterprise plans</li>
<li><strong>Access:</strong> Workspace admins and owners</li>
<li><strong>Location:</strong> <a href="https://lovable.dev/settings/identity">Identity</a> (<strong>Settings → Access → Identity → Verified domains</strong>)</li>
</ul>
<h2>Why verify a domain</h2>
<p>You need at least one verified domain before you can use most workspace identity features:</p>
<ul>
<li><strong>SSO</strong>: connect a SAML or OIDC identity provider for your workspace. See <a href="/sites/features/business/sso/">Set up workspace single sign-on (SSO)</a>.</li>
<li><strong>Enforce SSO</strong>: require all workspace members to sign in through your identity provider.</li>
<li><strong>Domain lock</strong>: combine Enforce SSO with the domain-wide Require SSO and <strong>Block workspace creation</strong> settings so everyone on the domain signs in through SSO and works only in your workspaces. Available on the Enterprise plan. See <a href="/sites/features/workspace-identity/#restrict-a-domain-to-sso-domain-lock">Restrict a domain to SSO (domain lock)</a>.</li>
<li><strong>Verified email sign-up</strong>: automatically add users who sign up with an email on your verified domain to your workspace, with a default role you choose. No SSO needed.</li>
<li><strong>SSO sign-in provisioning</strong>: automatically add users to your workspace the first time they sign in through your SSO provider.</li>
<li><strong>Add existing users</strong>: a one-time action that adds existing RShift Sites users with verified-domain emails to your workspace.</li>
<li><strong>SCIM provisioning</strong>: sync users and groups from your identity provider on the Enterprise plan. See <a href="/sites/features/business/scim/">Set up SCIM user provisioning</a>.</li>
<li><strong>Branded app URLs</strong>: publish apps under a workspace subdomain derived from your verified domain. See <a href="/sites/features/branded-workspace-urls/">Publish apps with branded URLs</a>.</li>
<li><strong>External publish invites</strong>: restrict email invites to internally published apps to your company's verified domains. See <a href="/sites/features/privacy-and-security-settings/#who-can-receive-external-invites">Who can receive external invites</a>.</li>
</ul>
<p>The provisioning options above are configured on the same Identity tab. See <a href="/sites/features/workspace-identity/">Manage workspace identity and user provisioning</a> for how they work and interact.</p>
<h2>Prerequisites</h2>
<ul>
<li>A workspace on the Business or Enterprise plan.</li>
<li>An owner or admin role in the workspace.</li>
<li>Access to your domain's DNS settings (through your DNS provider, such as Cloudflare, GoDaddy, or AWS Route 53).</li>
</ul>
<h2>Verify a domain</h2>
<p><strong>Add your domain in RShift Sites</strong></p>
<p>Go to <a href="https://lovable.dev/settings/identity">Identity</a> (<strong>Settings → Access → Identity</strong>), and under <strong>Verified domains</strong>, click <strong>Add domain</strong>. Enter your domain, for example <code>acme.com</code>. Wildcards are not supported.</p>
<p><strong>Create the DNS TXT record</strong></p>
<p>RShift Sites shows a DNS record to create. In your DNS provider, add a record with:</p>
<pre><code>| Setting   | Value                                                                 |
| :-------- | :-------------------------------------------------------------------- |
| Type      | TXT                                                                   |
| Host/Name | `@` (some providers want this blank, or want the domain name itself)  |
| Value     | The `lovable_verification=` token shown in the dialog, copied exactly |
</code></pre>
<p><strong>Wait for DNS propagation</strong></p>
<p>DNS changes can take anywhere from a few minutes to 72 hours, though most providers apply them within minutes.</p>
<p><strong>Verify the domain</strong></p>
<p>Back in RShift Sites, click <strong>Verify domain</strong>.</p>
<blockquote>
<p><strong>Tip</strong></p>
<p>When the check succeeds, you see a <strong>Domain Verified!</strong> confirmation, and the domain appears in your <strong>Verified domains</strong> list with a <strong>Verified</strong> badge.</p>
</blockquote>
<blockquote>
<p><strong>Note</strong></p>
<p>If this is the first domain you verify, RShift Sites automatically turns on <strong>Verified email sign-up</strong> with the default role set to editor, so colleagues who sign up with a company email join your workspace automatically. You can change the default role or turn this off under <strong>User provisioning</strong> on the same page.</p>
</blockquote>
<h2>How domain verification works</h2>
<ul>
<li><strong>Verification is a one-time check.</strong> RShift Sites checks the DNS record when you click <strong>Verify domain</strong>. Verified domains do not expire and are not re-checked later.</li>
<li><strong>You can verify multiple domains.</strong> Add each domain your organization uses, for example <code>acme.com</code> and <code>acme.co.uk</code>.</li>
<li><strong>Verifying a domain does not reserve it.</strong> Another workspace can verify the same domain. If your organization runs several workspaces, each one verifies the domain separately.</li>
<li><strong>Changes are audited.</strong> Adding and removing verified domains is recorded in your workspace <a href="/sites/features/audit-logs/">audit logs</a>.</li>
</ul>
<h2>Remove a verified domain</h2>
<ol>
<li>Go to <a href="https://lovable.dev/settings/identity">Identity</a> (<strong>Settings → Access → Identity</strong>).</li>
<li>In the <strong>Verified domains</strong> list, click the trash icon next to the domain.</li>
<li>Confirm in the <strong>Delete verified domain</strong> dialog.</li>
</ol>
<blockquote>
<p><strong>Danger</strong></p>
<p>Removing a domain disables SSO authentication for that domain. If you remove your <strong>last</strong> verified domain, RShift Sites also automatically turns off <strong>Enforce SSO</strong> and <strong>Verified email sign-up</strong>, since both depend on having a verified domain. To use the domain again, you must verify it again with a new DNS check.</p>
</blockquote>
<p>Removing a domain does not remove existing workspace members or end their sessions. Users who already joined through that domain keep their access.</p>
<h2>Troubleshooting</h2>
<p><strong>Could not find TXT record for domain</strong></p>
<p>The DNS record is not visible to RShift Sites yet. This usually means one of:</p>
<pre><code>* **The record has not propagated.** DNS changes can take up to 72 hours, though minutes is typical. Wait and try again.
* **The record is on the wrong host.** The TXT record must be on the root of the domain (`@`), not on a subdomain like `www`.
* **The value does not match.** The value must be the full `lovable_verification=` token exactly as shown, with no extra characters or quotes added by your DNS provider.
</code></pre>
<p><strong>Could not lookup TXT record for domain</strong></p>
<p>RShift Sites could not query DNS for the domain at all. Check that the domain is spelled correctly and is a real, registered domain with active DNS.</p>
<p><strong>The domain shows as already verified</strong></p>
<p>The domain is already in your workspace's verified list. You do not need to do anything.</p>
<h2>FAQ</h2>
<p><strong>Do I need a verified domain to set up SSO?</strong></p>
<p>Yes. Verifying a domain is the first step of SSO setup, and the SSO configuration flow walks you through it if you have not done it yet.</p>
<p><strong>Does domain verification expire?</strong></p>
<p>No. RShift Sites checks the DNS record once, when you click <strong>Verify domain</strong>. A verified domain stays verified until you remove it from your workspace.</p>
<p><strong>Can I remove the TXT record after verification?</strong></p>
<p>Verification is checked once, so removing the record does not un-verify the domain. Keeping the record in place is recommended so you can verify again easily if you ever remove and re-add the domain.</p>
<p><strong>Can two workspaces verify the same domain?</strong></p>
<p>Yes. Verification proves ownership to a workspace. It does not claim the domain exclusively. If your organization runs several workspaces, each one verifies the domain separately and configures its own identity settings. Require SSO and <strong>Block workspace creation</strong> are domain-wide, so they apply to every workspace that has verified the domain and you only need to enable them once.</p>
<p><strong>What happens to members if I delete a verified domain?</strong></p>
<p>Nothing immediately. Existing members keep their access and their sessions stay active. The domain stops working for SSO sign-in, and if it was your last verified domain, <strong>Enforce SSO</strong> and <strong>Verified email sign-up</strong> turn off automatically.</p>
<p><strong>Can I restrict sign-ups on my domain to SSO only?</strong></p>
<p>Yes. Require SSO restricts account creation on a verified domain so new users must sign up through your SSO provider instead of email/password or social login. It applies domain-wide across all of RShift Sites and requires an SSO provider with <strong>SSO sign-in</strong> provisioning. Contact <a href="https://help.rshift.com/contact/">RShift Sites support</a> to enable it for your domain. See <a href="/sites/features/workspace-identity/#restrict-a-domain-to-sso-domain-lock">Restrict a domain to SSO (domain lock)</a> for how it fits with <strong>Enforce SSO</strong> and <strong>Block workspace creation</strong>.</p>
<h2>Related topics</h2>
<ul>
<li><a href="/sites/features/business/sso/">Set up workspace single sign-on (SSO)</a></li>
<li><a href="/sites/features/business/scim/">Set up SCIM user provisioning</a></li>
<li><a href="/sites/features/workspace-identity/">Manage workspace identity and user provisioning</a></li>
<li><a href="/sites/features/custom-emails/">Send branded emails from your own domain</a></li>
<li><a href="/sites/tips-tricks/launch-on-a-custom-domain/">Launch your site on a custom domain</a></li>
</ul>

Source: https://rshift.helpcent.re/sites/features/verified-domains/index.mdx
