Roles and permissions

Access is scoped by project, role and action: tester, reviewer, test lead, viewer. Organisations are isolated from one another at the data level.

Roles and permissions

Access is scoped by project, role and action: a person sees what they work with and cannot break what they are not responsible for.

  • Tester, reviewer, test lead, viewer
  • Permissions are granted per project, not across the whole system
  • Viewers and guests are free on every plan
Roles and permissions

Isolated organisations

Organisations do not overlap at the data level. That matters to a contractor with several clients and to a company where departments should not see each other's projects.

  • Data of one organisation is unreachable from another
  • A person belongs to several organisations and switches between them
  • Projects, cases, runs and reports live inside their own organisation
Isolated organisations

How people join the team

  • Invitation by link

    A link goes to the person and the role is assigned at invitation time. No manual account creation.

  • Sign-in through SSO

    Authorisation is built on Keycloak, so a corporate account plugs straight in.

  • Notifications

    Changes on cases and runs reach the interface immediately, with no page reload.

Set up an organisation for your team

Invite colleagues by link, hand out roles and see how it maps onto the way your team already works.