Skip to main content
This page covers the three things an organization controls about how it looks and what it pays.

Branding

When someone outside your company opens a link your team sent, they land on a Zas page. Branding makes that page yours. You set:
  • A display name.
  • A logo, with separate light and dark versions if you want them.
  • A primary colour.
You also choose where that identity appears. Each of these is a separate switch, so you can brand public links without changing anything inside the app: A branded page still carries a small Powered by Zas mark.

Publish and roll back

Branding is not live while you edit it. You publish it, and that publish is written to the audit log. If a publish was wrong, you roll back. That is also written to the audit log, so a change and its reversal are both accounted for.

Custom domain

Your public links can be served from your own domain instead of zas.red. A domain moves through three states:
1

None

No custom domain is set. Links use zas.red.
2

Pending

You have set the domain and hosting is provisioning the certificate. This takes as long as it takes; it is not instant.
3

Verified

The domain serves your links. Every state change is written to the audit log.
Removing a domain also starts a process rather than flipping a switch, and it is logged the same way.
This is separate from claiming your organization. Ownership of your organization comes from your verified work email address, not from a DNS record. The custom domain is only about where links are served from.
A link created inside an organization asks the person opening it to sign in, and to be an active guest, member or administrator of that organization. The link does not create memberships and does not allow anonymous access. Someone with the address and no membership sees a message telling them to switch accounts.

Billing

USD 8 per seat per month, billed through Paddle, which acts as merchant of record.

Seats

An organization tracks three numbers:
  • Seat limit — how many seats you are paying for. A new organization starts with 5.
  • Occupied seats — how many are in use. The owner takes the first one.
  • Reserved seats — seats held for invitations that have not been accepted yet.
Guests consume seats too. That is why Anyone can invite is off by default: an outsider joining through a link becomes a guest and takes a seat.

The states an organization can be in

When the plan is inactive

The plan is inactive when:
  • The trial ended and nobody chose a plan.
  • A payment failed and is still unpaid after 14 days.
  • The plan is suspended or cancelled.
While the plan is inactive, nobody in the organization can send, upload, create a link or an organization channel, invite, join, renew a guest or reactivate a member. Live Directo transfers in organization channels stop. People can still sign in and open what is already stored. The console and the custom domain keep working. Members, settings and pending invitations are kept. Choosing a plan, or paying what is due, ends the pause at once.

Paying during the trial

You can choose a plan before the trial ends. Paddle takes the card at checkout, and the first payment is on the day the trial ends. A coupon keeps that date and lowers the first payment.

Warnings and emails

An inactive plan shows a banner to everyone in the organization. Two warnings show only to the owner and billing admins: the trial ends in 3 days or less, and a failed payment is in its 14-day grace. Zas also sends these emails. Members get no email. Each email is in the recipient’s Zas language: Spanish, Portuguese or English. The Billing screen shows the current state, the seat counts and the invoices. Only the owner and a billing admin can change anything there. A member can read the state but cannot act on it.

Closing an organization

Only the owner can close an organization by hand, and the owner can do it at any time. Closing it is written to the audit log like every other administrative act. Items inside it still follow the normal Zas rules: they were always going to leave on their own.

Automatic close

If the plan stays inactive for 90 days, the organization closes on its own:
  • The subscription is cancelled.
  • The custom domain is removed.
  • Its channels, and the files shared in them, are deleted.
An organization that was already inactive for longer gets at least 30 days of notice. The emails go out 30, 7 and 1 day before the close date. Reactivating the plan before that date stops the close. Once the close has started, it cannot be stopped.