Onboarding a new organisation

This page describes the whole onboarding journey for a new customer company, and who is responsible at each step. If you’re the new admin and want the hands-on checklist, go straight to the Quick start for new organisations.

The journey at a glance

Stage	Who	What happens
1. Request	You	Submit the Get started form on the QA Sync website. Optionally book a demo.
2. Review	QA Sync	The team reviews your request.
3. Provision	QA Sync	Your organisation is created and you become its first Organisation Admin. You receive login details.
4. First sign-in	You	Sign in at /app/login; you land in the admin workspace.
5. Invite your team	You	Add members, assign roles, grant app access, place testers in groups.
6. Model your product	You	Create apps, tester groups, modules, submodules, milestones, sprints and tasks.
7. Configure releases	You	Review approval rules so release sign-off matches your process.
8. Start work	Your team	Developers deliver, testers run QA, product managers and admins approve and release.

1. Request access

Submit the Get started form on the website. There is no self-sign-up; see Request access for why.

2–3. Review and provisioning

QA Sync reviews the request and, if approved, provisions:

• a new, empty organisation for your company;
• your login (or a new membership for your existing login, if you already use QA Sync elsewhere);
• the Admin role for you in the new organisation.

Your organisation starts empty. No data from any other organisation is visible to it.

4. First sign-in

Sign in with the details you received. If you see Access Pending instead of the admin workspace, contact QA Sync: provisioning is not complete. See Signing in.

5. Invite your team

From Users, use Provision User for each person. Decide roles carefully:

• Give Admin only to people who should manage members and approve releases.
• Give everyone except Admins access to the specific apps they work on.
• Put each Tester into at least one tester group, or they’ll have an empty queue.

See Inviting and managing members and Roles and permissions.

6. Model your product

Create apps, then tester groups, then modules and submodules, then tasks. If you already have a test plan in a spreadsheet, convert it to JSON and use Bulk Import. See Apps, modules and sprints.

7. Configure releases

Review the Approval Requirements on the release board (Tasks → Release). The defaults require developer and QA approval on tasks, plus admin approval on critical or hotfix tasks and on apps, modules and submodules. See Approvals and releases.

8. Start work

Share the role guides with your team:

• Product manager guide
• Developer guide
• Tester guide
• Stakeholder guide

Tip

Run one task through the whole lifecycle with a developer and a tester before you roll QA Sync out to everyone. It’s the fastest way to check roles, app access and groups are right.