> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zas.red/llms.txt
> Use this file to discover all available pages before exploring further.

# Domain Proof: How Zas Verifies Organization Ownership

> Domain is the sole source of organization power in Zas. Prove ownership with a DNS TXT record, re-checked on schedule. If proof lapses, powers lapse.

Domain is the sole source of organization power in Zas. You prove ownership by publishing a DNS TXT record. Zas re-checks this record on a schedule. If the proof lapses, your organization's powers lapse.

## How to prove your domain

<Steps>
  <Step title="Get your proof string">
    In Zas organization settings, go to **Domain proof** and copy the TXT record value.
  </Step>

  <Step title="Add the TXT record">
    In your DNS provider, create a TXT record at `_zas.yourdomain.com` with the value provided.
  </Step>

  <Step title="Verify in Zas">
    Return to Zas and click **Verify**. Zas checks the DNS record and activates your domain powers.
  </Step>
</Steps>

## What domain powers unlock

* Custom subdomain or your own domain for Zas access
* Domain-locked channels (Enterprise)
* Org-wide policies tied to verified membership
* SCIM provisioning scoped to the domain

## Re-checking and lapses

Zas re-checks your DNS TXT record on a schedule. If the record is removed or changed, your domain powers are suspended. Members can still access Zas, but admin features that depend on domain proof are disabled until the record is restored.

<Warning>
  Do not remove the TXT record after verification. Keep it in place for continuous proof.
</Warning>

## What to read next

* [Org policies](/en/enterprise/policies)
* [Identity model](/en/enterprise/identity-model)
* [Team vs Enterprise comparison](/en/enterprise/team-vs-enterprise)