Set Up Project Roles
On this page, you can view access rights for pre-defined roles, create new roles and edit role rights.
Predefined roles:
  • ProjectAdmin - full access to all project functionality, including its configuration.
  • TestManager - all project functionality is available, except its settings.
  • TestDesigner - the role for users who work with the test library, access to other functionality is closed (except for Queries). Please note, this role doesn't let the user delete test cases but make changes only.
  • TestEngineer - with this role, the user will have access to all sections, but without the right to delete items.
  • TestExecutor - a role for launching and passing manual tests and autotests. Responsibility area - Test plans / Execution tab.
  • Observer - minimum access to the project, items viewing only.
TestGear sections with configurable access restriction:
  • Project editing – section of project setting and configuration, where modifications and change of project description are available; addition of user and project team attributes; setting of an external server project integration (Jira).
  • Test library – an archive section of the project’s test documentation (test cases, checklists, shared steps).
  • Configurations – section for creating and setting of configurations within the project (Within which tests will be carried out)
  • Test plans – section of archiving project test plans, for creation, filling, and task-allocation between users.
  • Test execution – section for performing test plans which enables to record test case results as well as launch autotests.
  • Test plan report – section of categorized reports on test plan results.
  • Reports - section of consolidated reporting for the project
  • Autotests library – section of automated tests
  • Filters – section for creating filtered queries to search amongst different test cases of the project.
  • Import - section for import test cases from other projects.
  • Webhooks - sections for setting webhooks parameters.
Levels of Access:
Levels of project access can be configured in the table in which rows are sections of TestGear
and columns are roles' names. In order to assign or change the right to a section, choose the value from the drop-down menu of the cell.
  • Forbidden – the user will not have access to the section either via UI or API, the UI will not allow redirecting to the section; when using a direct link, access will also be forbidden. UI elements related to it will be hidden. If you request a forbidden item via API, the access request error will appear
  • View – the user will have access to the section but they won't be able to delete or edit anything; the interface will also include an option to redirect to the section; when using a direct link, access will be granted. UI elements that allow altering the content will be hidden. Errors will occur when trying to edit the data via API (except for GET requests)
  • Editing – allows previewing, creating, and editing sections and work items except for deleting them. The user is granted access to the section, the interface has an option to redirect to it. Direct link transition is allowed. UI elements that enable the creation and editing of the section contents are also enabled. Deleting is not allowed. UI elements that allow deleting section contents will be hidden. For example, the user can edit the text in a step of the test case but they can't delete the whole test case. In the case of configuring the project, there's no way to archive the project or restore it; all other actions are allowed. Errors will occur when trying to delete the data via API (DELETE requests).
  • Full access – includes the right to preview, create, edit and delete sections as well as work items. UI elements that allow creation, editing, and deleting section contents are enabled.
To create a new role, click the Create role button and enter a role name. A role will be created with minimal rights, which can be changed by clicking on a pencil icon next to the role name.
Some rights to items cannot be forbidden, for example, you can't restrict access to the Test library or restrict access to Queries.
Copy link