Skip to content
QA SyncQA Sync Docs

Quick start for new organisations

This guide is for the first admin of a newly provisioned organisation. It takes you from your first sign-in to a team that is planning, building and testing in QA Sync. Plan for about an hour, most of it spent describing your product.

  1. Sign in and look around

    Sign in at /app/login. You land on the admin workspace on the Overview tab. It will be mostly empty; that’s expected. Skim Navigating the app to learn the layout.

  2. Create your first app

    Open the Apps tab and select Add App. Give it a name and description, for example Customer web app. Every module, tester group and task belongs to an app, so create one app per product surface you test.

  3. Create tester groups

    Open Groups and select Add Group. Choose the app, then name the group, for example Web QA or Mobile QA. Testers see tasks through their groups, so create groups that match how your QA team divides work.

  4. Describe the product as modules and submodules

    Open Modules & Submodules and select Add Module. Pick the app, name the module, and set platforms, environment and build version. Then add submodules inside it.

    Have a lot to describe? Use Bulk Import in the admin header to paste one JSON document containing apps, groups, modules, submodules and tasks. See Apps, modules and sprints.

  5. Add your team

    Open Users and select Provision User for each person. Choose their role, grant app access, and for testers pick their groups. QA Sync creates the account and shows an initial password once; share it securely. See Inviting and managing members.

    Add at least one Developer and one Tester so you can try the whole flow.

  6. Create tasks

    Open Tasks and select Create Task. Choose the module and submodule, write clear Test Instructions and an Expected Result, assign a developer and tester groups, and set the workflow stage. Fill in planning fields such as priority, due date, sprint and release version if you use them.

  7. Review your approval rules

    Open Tasks → Release. At the bottom of the release board, check the Approval Requirements panel. By default, tasks need Developer Approved and QA Approved, critical and hotfix tasks also need Admin Approved, and apps, modules and submodules need Admin Approved. Adjust them to match how your company signs off releases. See Approvals and releases.

  8. Run one task end to end

    Ask your developer to move a task to Staging (or move it yourself on the Kanban board). Your tester sees it in their Queue, opens it and records a result. A pass moves the task to Ready to Ship, where it appears on the release board for approvals and promotion.

What to do next

Section titled “What to do next”