> ## 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.

# Zas for Enterprise

> Zas for Enterprise adds roles, permissions, invites and guests, branding, a custom public domain, and seat billing at USD 8 per seat per month.

Zas for Enterprise puts an organization around the same product. The corridor does not change. Who may use it, and under what limits, becomes yours to set.

## What it adds

<CardGroup cols={3}>
  <Card title="Roles" icon="user-shield" href="/en/enterprise/roles-and-permissions">
    Five fixed roles: owner, admin, billing admin, member and guest.
  </Card>

  <Card title="Permissions" icon="sliders" href="/en/enterprise/roles-and-permissions">
    Who can send, who can receive, whether Direct is on, how large a file may be, and what coding agents may do.
  </Card>

  <Card title="Invites and guests" icon="envelope" href="/en/enterprise/roles-and-permissions">
    Invite by email, renew a guest, remove a member, transfer ownership.
  </Card>

  <Card title="Branding" icon="palette" href="/en/enterprise/branding-and-domain">
    Your name, logo and colour on the pages people outside the company see.
  </Card>

  <Card title="Custom domain" icon="globe" href="/en/enterprise/branding-and-domain">
    Serve your public links from your own domain.
  </Card>

  <Card title="Seat billing" icon="credit-card" href="/en/enterprise/branding-and-domain">
    USD 8 per seat per month, billed through Paddle.
  </Card>
</CardGroup>

## Price

**USD 8 per seat per month.**

A new organization starts with **5 seats** and a **14-day trial**. The owner takes the first seat.

Billing runs through Paddle, which acts as merchant of record.

<Info>
  **When the plan is inactive**, the organization pauses. The plan is inactive when the trial ended without a plan, when a failed payment is still unpaid after 14 days, or when the plan is suspended or cancelled. Nobody can send, invite, join or be reactivated until the owner or a billing admin chooses a plan or pays. People can still sign in and open what is already stored. Members, settings and pending invitations are kept, and every console screen shows the state. The owner and billing admins also get a button to choose a plan. If the plan stays inactive for 90 days, the organization closes on its own. [Read the details](/en/enterprise/branding-and-domain#when-the-plan-is-inactive).
</Info>

## Creating an organization

You claim an organization with a **verified work email address**.

<Steps>
  <Step title="Sign in with your work email">
    Sign in with a one-time email code, or with Google or Apple. The address has to be verified, and Zas reads the domain from it.
  </Step>

  <Step title="Name the organization">
    You choose a display name and a short slug. The slug has to be free.
  </Step>

  <Step title="Zas claims the domain">
    The organization is bound to the domain of your verified address, and only that domain.
  </Step>
</Steps>

<Warning>
  Two rules are strict, and both are refused at creation time rather than later.

  **Public email domains cannot claim an organization.** A gmail.com or outlook.com address will not work.

  **A domain can be claimed once.** If someone at your company already created the organization, ask them to invite you.
</Warning>

## The console

Signed-in administrators get a console with one screen per job:

| Screen | What it holds |
| - | - |
| Overview | The organization, its seats and its state |
| Members | People, roles, and activation |
| Invites | Open invitations and their status |
| Permissions | What members and guests may do |
| Agents | Each coding agent that holds an organization channel: whose it is, how many organization channels it holds, when it was last seen, and a button to revoke that access |
| Branding | Name, logo and colour |
| Custom domain | Your custom public domain |
| Billing | Seats, plan and invoices |
| Audit log | The log of every administrative action |

<Note>
  A screen only appears for a role that may open it. Billing admins see billing; a member reading the console sees what their role allows and nothing else.

  The **Agents** screen stays empty until you turn on **Agents on organization channels** in Permissions. With that switch off, no agent reaches an organization channel, so there is nothing to list.
</Note>

## What Zas for Enterprise is not

We would rather list this than let you assume it.

* **No SSO, SAML or OIDC.** Sign-in is an email code, Google or Apple, the same as everywhere else in Zas.
* **No SCIM or directory sync.** People join by invitation.
* **No DNS TXT domain proof.** Domain ownership comes from your verified email address, not a DNS record.
* **No data residency choice.** Providers can process data outside Argentina.
* **No separate Team tier.** There is one paid product, and this is it.
* **Nothing changes about expiry.** Items still leave on their own.

## Where to go next

<CardGroup cols={2}>
  <Card title="Roles and permissions" icon="user-shield" href="/en/enterprise/roles-and-permissions">
    Who can do what, and the limits you can set.
  </Card>

  <Card title="Branding, domain and billing" icon="palette" href="/en/enterprise/branding-and-domain">
    Your identity on public pages, and how seats are billed.
  </Card>

  <Card title="Agents in an organization" icon="robot" href="/en/agents/enterprise">
    The two levers you have over coding agents, and what they do not cover.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.