Organisations and tenancy
QA Sync is multi-tenant. Each customer company works inside its own organisation, and everything your team creates lives in that organisation alone.
What belongs to an organisation
Section titled “What belongs to an organisation”Every piece of product data belongs to exactly one organisation:
- apps, modules and submodules
- milestones and sprints
- tasks, dependencies and planning data
- task requests and their attachments
- QA runs, QA results and evidence
- feedback submissions and developer notes
- approvals, approval rules and release decisions
- comments and mentions
- notifications
- tester groups
- audit log entries
Database Row Level Security enforces the boundary on every read and write, so a member of one organisation can never see or change another organisation’s data, whatever screen or request they use. See Data isolation and security.
Logins, members and roles
Section titled “Logins, members and roles”QA Sync separates who you are from what you can do:
| Concept | Scope | Example |
|---|---|---|
| Login | One per person, identified by email address. | sam@acme.com with one password. |
| Membership | One per organisation you belong to. | Sam is a member of Acme and Acme Labs. |
| Role | One per membership. | Sam is an Admin in Acme and a Viewer in Acme Labs. |
| Status | One per membership. | Sam is Active in Acme, Inactive in Acme Labs. |
| App access and groups | Per membership, inside that organisation. | Sam tests Mobile app in the iOS QA group. |
Switching organisations
Section titled “Switching organisations”If you are a member of more than one organisation, use the organisation switcher in the top bar. QA Sync reloads the workspace for your role in the selected organisation. Nothing you see in one organisation appears in another.
When you sign in, QA Sync opens the organisation you used last. If that isn’t available, it asks you to choose. If your membership in an organisation is inactive, you see Access Pending for that organisation and can switch to your other organisations.
Organisation roles
Section titled “Organisation roles”Every membership has one of seven roles:
| Role | In short |
|---|---|
| Admin | Runs the organisation: members, apps, groups, modules, tasks, task requests, approval rules, releases, audit log. |
| Product Manager | Portfolio, roadmap and release health; completes product manager approvals. |
| Developer | Delivers assigned tasks; triages issue reports; escalates suggestions. |
| Tester | Runs QA on staging tasks; records evidence; requests missing coverage. |
| UI Designer | Follows release readiness and history; comments. |
| Client | Follows release progress and history; comments. |
| Viewer | Read-only view of progress and release readiness. |
The first Admin of a new organisation is the person who requested it. That Admin can make other members Admins. See Roles and permissions.
Platform operators
Section titled “Platform operators”Super Admin is a platform role held by QA Sync staff, not by customer members. Platform operators:
- review access requests submitted on the website;
- create organisations and their first Organisation Admin;
- help with account recovery and organisation-level changes you can’t make yourself.
Platform operators have no standing access to your organisation’s data. Organisation Admins run their own organisation.
Lifecycle of an organisation
Section titled “Lifecycle of an organisation”- Requested on the website through the Get started form. See Request access.
- Provisioned by QA Sync, with the requester as first Admin. See Onboarding a new organisation.
- Active: admins add members and the team works.
Organisations that used QA Sync before it became multi-tenant were each moved into their own organisation. See Existing organisations.