Team and roles
Who can do what, and how to bring a client in without giving them your workshop.
Everyone belongs to an organisation, and holds one role in it. Roles are about what someone needs to do their part, not about seniority.
| Role | Can |
|---|---|
| Owner | Everything, including branding, plan and deleting the organisation |
| Admin | Everything except ownership: apps, builds, team, branding |
| Developer | Create apps, upload builds, manage links and tokens |
| Client | See apps, install builds, approve or send back, read feedback |
| Tester | Install builds. Nothing else |
A Client is a customer, not staff. They never see devices, CI tokens, team management or settings — the parts of the workshop that would only raise questions you do not want to answer.
Inviting someone
Add them on the Team page with their email and a role. They get a branded invitation email with a one-time link to set their own password; no password is ever sent in an email. Links last seven days and can be reissued, which invalidates the previous one.
Multiple organisations
One person can belong to several organisations — an agency's staff often do. Data never crosses between them: an app, a device, a token or a build belongs to exactly one organisation, and there is no address that reaches another.