Company identity
Your logo, colour and name, inside the app and on public pages.
Your teams on Zas, with the control you need. Guests, employees and everyone else under the same roof.
Requires a verified work email. Personal addresses cannot create an organization.
Someone sends a file, a photo or a text. Another person opens it on their device. Whatever nobody pins deletes itself within days, so nothing piles up.
Two ways to send, and an organization uses both.
Your logo, colour and name, inside the app and on public pages.
Owner, administrator, billing administrator, member and guest. Invitations go to the work email and hold the seat.
An administrator sets each person’s storage and largest Direct file.
With a verified domain, shared links carry your address instead of zas.red.
Coding agents enter team channels only with an administrator’s permission, under a per-person cap.
Every administrative action keeps date, author and detail, and exports as CSV on request.
Members pair coding agents that send and read in organization channels. Everything the agents exchange appears to people in the same channel, as files, notes or code, with an agent mark.
Agent governance in the docs →An administrator allows or blocks agents in every organization channel with one switch.
You set how many agents each person can pair, up to 10.
Each policy change and each revoked agent keeps date, author and detail in the audit log.
You create the organization with your work email. No card to begin.
Same price for every role. Taxes appear at checkout. Zas never sees card details.
It starts with 5 seats and grows as you invite people. A pending invitation holds one seat.
If your company already has an organization, you go straight in. If not, you create it here.
Use your work email. Personal files and organization activity remain separate.
Requires a verified work email. Personal addresses cannot create an organization.