Existing organisations

If your team used QA Sync before organisations were introduced, your data now lives in its own organisation. This page explains what changed and what, if anything, you need to do.

What changed

• All of your existing data (apps, modules, submodules, tasks, task requests, QA results, evidence, feedback, approvals, comments, notifications, tester groups and audit history) was moved into a single organisation for your company.
• Every existing account became a member of that organisation, keeping the same role, status, app access and tester groups it had before.
• Your data is now isolated from other organisations by the same database rules that protect every new organisation.

What stays the same

• Your login (email and password) is unchanged.
• Your workspace, tabs and day-to-day workflow are unchanged.
• Audit history from before the change is preserved.

What members need to do

Nothing. Sign in as usual.

What admins should do

Review your member list once:

1. Open Users in the admin workspace.
2. Check each member’s role. In particular, confirm who holds Admin: every Admin can manage members and promote releases for the whole organisation.
3. Check that people who left are revoked (they appear under archived users).
4. If anyone held the Super Admin role in your old setup, change them to Admin. Super Admin is now reserved for QA Sync platform operators. See Organisations and tenancy.

See Inviting and managing members for how to change roles.

Note

If your company needs more than one organisation (for example, separate business units that must not see each other’s data), contact QA Sync. Data can’t be split between organisations from inside the app.