Organisations, members and account security
Organisations
Every project, database, domain, wallet and invoice belongs to an organisation. When you sign up you get a personal organisation. For a company or a team (inviting members, assigning roles, separate invoices):
- Account menu → Account → New organisation.
- Switch between organisations with the Organisations menu in the top left corner.
Each organisation has its own wallet, plan and invoice details. A suspended organisation shows the banner "This organisation is suspended. Please contact support."
Roles
| Permission | Owner | Admin | Developer | Billing | Viewer |
|---|---|---|---|---|---|
| View projects, logs, metrics and usage | ✓ | ✓ | ✓ | ✓ | ✓ |
| Deploy, change environment variables, scale, roll back; view database data (read-only) | ✓ | ✓ | ✓ | ||
| Create/delete projects, databases, buckets and domains; edit DNS and Cloudflare; run SQL that writes | ✓ | ✓ | |||
| Top up, change the plan, invoices; buy domains and e-mail | ✓ | ✓ | ✓ | ||
| Invite and remove members | ✓ | ✓ | |||
| Get a domain's transfer-out code, transfer ownership, close the organisation | ✓ |
Only an Owner can grant or remove the Owner role; an organisation must always keep at least one Owner.
Inviting members
- Members section → Invite someone.
- Enter the e-mail, choose a role (Admin, Developer, Billing, Viewer) and click Create invitation.
- ZoCloud sends the invitation by e-mail and the portal shows the invitation link. The link is shown only once, is valid for 7 days, and only works with the e-mail that was invited.
- The invitee signs in (or signs up) with that e-mail, verifies the e-mail, then clicks Join. An account whose e-mail is not verified cannot accept the invitation.
An invitation not yet accepted is shown as pending. Change a role with the role field next to the member's name; Remove takes them out of the organisation. To leave yourself: Leave.
Transferring ownership
An owner hands the organisation to someone else with the Transfer ownership card under Members: pick the member (their e-mail must be verified), enter your password (and your 2FA code if you have it on) and confirm. They become the Owner, you stay on as Admin; both of you get an e-mail and the change is recorded under Activity. Through the API: POST /v1/orgs/{org}/transfer with email, password and code.
Requiring 2FA
Turn on Require two-factor authentication in the Members section: members without 2FA cannot act in the organisation (even with an API token) until they turn on 2FA in their account. The members list shows 2FA on / no 2FA.
Google Workspace
The Google Workspace card (when ZoCloud has turned Google sign-in on) links the organisation to your company's Google Workspace domain.
- Sign in to ZoCloud with a Google Workspace account on that domain (to prove the domain is yours).
- Choose who may join on their own: Nobody joins by signing in, or people on the same domain join with the Developer / Viewer role.
- Optionally Require Google sign-in.
Account security
Account menu → Account:
- Password: enter your Current password and a New password. Changing the password signs out your other sessions.
- Two-factor authentication: click Turn on two-factor authentication, add it to an authenticator app (Google Authenticator, 1Password…) and enter the first code. From then on every sign-in needs the 6-digit code.
- Forgotten password: on the sign-in page click Forgot your password? → Send the link (valid for 1 hour).
Access tokens (API token)
For the zo CLI, CI and AI agents. Account menu → Account → Access tokens:
- Enter a Name and the number of Days it is valid, then click Create token.
- Copy it now: the token is shown only once. Tokens have the form
zc_pat_…. - Revoke it at any time. The list shows when it was Last used.
A token has exactly your permissions in each organisation (by role). Use it with the API: Authorization: Bearer zc_pat_… against https://api.zocloud.io/v1.
Activity (log)
The Activity section: what members, ZoCloud and the system have done in the organisation, newest first (deployments, variable changes, domains added, plan changes, database queries run…). Filter by Apps, Databases, Domains, Storage, Billing and Members. Actions by ZoCloud staff are marked ZoCloud staff. Click Older to see more.
Notifications (Slack, Discord, webhook)
Notifications section → Add a notification:
- Send to: Slack, Discord or Webhook (HTTPS).
- Name and Webhook address (an incoming webhook from Slack/Discord, or your own HTTPS endpoint on port 443 or 8443).
- Project: one project or All projects.
- Events: Deployment live, Deployment failed, Service crashed.
- The Language of the messages.
Click Test to check it; Deliveries shows every delivery.
Your own webhook: when you create it, the portal shows the endpoint's signing secret, only once. Every request carries the headers X-ZoCloud-Timestamp and X-ZoCloud-Signature: sha256=<hex>, where the signature is HMAC-SHA256(secret, timestamp + "." + body). Check the signature and refuse old timestamps.
import crypto from "node:crypto";
function verify(req, rawBody, secret) {
const ts = req.headers["x-zocloud-timestamp"];
const sig = req.headers["x-zocloud-signature"];
const want = "sha256=" + crypto.createHmac("sha256", secret).update(ts + "." + rawBody).digest("hex");
const fresh = Math.abs(Date.now() / 1000 - Number(ts)) < 300;
return fresh && crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(want));
}
ZoCloud also sends e-mail for the important things: e-mail verification, invitations, top-up receipts, plan renewals (successful or not), apps paused for non-payment, failed deployments.
Support (tickets)
Support section → New ticket:
- Topic: Technical, Billing, Account, Report abuse, Other.
- Subject and Message: name the project, the service and what you saw (the error, when it happened). Never send passwords.
- Click Send.
You get an e-mail when there is a reply; answer in the ticket and click Send. The first-response time depends on your plan. When it is resolved, Close the ticket; a closed ticket cannot be reopened, so open a new one if you need to.
Status page
https://app.zocloud.io/status (no sign-in needed) shows the system's state ("All systems operational", or the level of disruption), open incidents, scheduled maintenance and Past notices. Ongoing incidents and maintenance also appear as a banner on the portal.