Role Management

A role is a collection of individual permissions you can assign to a user.
Testiny has built-in roles (e.g. Administrator, Editor, Run Executor, ...) to cover the most common use cases.
In the Role Management section, you can manage custom roles.

tip

Start by duplicating one of the built-in roles.

Permissions

• Can read
  All roles, even custom ones, have at least the Can read permission. It gives read-only access to all project specific data such as test cases, test runs, automation test runs, etc.
  To prevent users from accessing data of certain projects, assign them the built-in role No access for those projects.

• Can create test cases

  • Creating test cases.
  • Editing test cases.
  • Adding attachments to test cases.
  • Adding/removing requirements to/from test cases.
  • Export test case to csv/excel (if available in your current billing plan)

• Can delete test cases

• Can create test plans

  • Creating test plans.
  • Editing test plans.
  • Creating test plan report.

• Can delete test plans

• Can manage test runs

  • Creating manual test runs.
  • Editing manual and automation test runs.
  • Closing/reopening manual and automation test run.
  • Pinning/unpinning automation test run & setting running/complete state.
  • Deleting manual and automation test runs.
  • Adding and removing test cases to/from a manual test run.
  • Export of results.
  • Creating test run and test plan reports.

• Can execute test runs

  • Executing test cases (assigning test results) within a test run.
  • Adding/removing defects.
  • Export of results.
  • Creating test run and test plan reports.

• Can manage milestones

  • Creating milestones.
  • Editing milestones.
  • Deleting milestones.

• Can manage automation

  • Editing automation sources.
  • Deleting automation sources.

• Can import automation

  • Importing automation data (automation results) using the Testiny CLI. Thus, creates automation test runs and automation test run results.

• Can manage comments

  • Adding comments to/from test cases, test results and automation test results.
  • Editing own comments to/from test cases, test results and automation test results.
  • Deleting own comments to/from test cases, test results and automation test results.

• Can manage organization (organization-wide permission)

  • Configuring organization wide settings and managing integrations, custom fields, automation fields and permission roles.
  • Changing organization name, delete organization, and transfer ownership. On Testiny Server, can apply a license.
  • Viewing auditlog.
  • Creating new projects.
  • Managing comments from all users.

Note: Can manage organization cannot be applied without all other organization-wide permissions and Can manage projects.

• Can manage billing (organization-wide permission)

  • Changing plans.
  • Buying/returning seats.
  • Downloading invoices and changing billing information.

• Can manage users (organization-wide permission)

  • Inviting, enabling/disabling and deleting users.
  • Assigning and changing roles.

  Note: Users with the Can manage users permission can only assign roles that have equal or fewer organization-wide permissions. For example, a custom role such as User Administrator cannot assign the Administator role to other users, since the Administrator role includes additional permissions - Can manage billing and Can manage organization - beyond Can manage users.

• Can manage projects

  • Editing projects.
  • Activating/deactivating custom fields and integrations for projects.
  • Override global organization settings for projects.
  • Assign roles to users having a project-specific role assignment enabled.

  Note:

  • If a role containing Can manage projects permission is assigned organization-wide, the user will be also project administrator for newly created projects. If the role is assigned project-specific, the user will have no access to newly created projects.
  • Users with the Can manage projects permission can only assign roles at project-level that have equal or fewer permissions.
    Therefore, a custom role containing Can manage projects typically should have all project-specific permissions to avoid limiting the roles the user can assign.

Good to know:

• Without any explicit write permissions, users can still manage their own user profile and account.
• Management of own API keys is possible when having more than the viewer permission set - meaning at least one permission beyond Can read and Can manage comments.

Organization-wide vs project-specific roles

Organization-wide permissions manage access to features that aren’t tied to a specific project. These are mostly administrative permissions (like Can manage organization) and cannot be assigned per project.

Therefore, roles containing organization-wide permissions also cannot be assigned per project.

Seat types

A role having no more permissions than Can read and Can manage comments is counted as a Viewer, otherwise it is counted as a User. See the pricing section for more details.