With our blog entries we would like to give you quick and easy access to the respective topics. Whether we succeed in this, we would like to learn at firstname.lastname@example.org. We are looking forward to your suggestions and criticism, Claudia
General User Roles in Klaros Test Management
The test management software offers four different user roles, which are assigned when the user is created and can be changed later if necessary:
An Administrator always has access to all functions in Klaros-Testmanagement. In addition to the test-specific activities, this also includes user administration, backups and recovery as well as system-wide settings.
2. Test Manager
Test Managers have full read and write access to all data of a project. They can create and delete objects and manage project settings. This also includes creating, editing and deleting users with the "Tester" role.
Testers can run tests, edit test results and issues, and generate reports. Beyondt his, they have read-only access.
The Guest role is intended for Project Managers, Customers or Reviewers, for example. The Guest has complete but read-only access to all data and can display, save and export reports in other formats.
The general user roles apply to all existing projects. If required, however, further project-specific role changes can be made per user.
Project specific User Roles in Klaros Test Management
In addition to the global assignment, it is possible to reassign the user roles per project or to exclude users from individual projects. The user retains his global role, but receives extended or restricted rights or no access in the selected project.
This is useful, for example, when integrating external employees who may only be active in a specific project. On the other hand, a tester may need test manager rights in certain projects and can receive the corresponding assignment.
Restricting Access to Pages in Klaros-Testmanagement
Klaros-Testmanagement allows the creation of bookmarks for saved detail pages, which can be transferred as a link to Jira or another issue tracker. If access to these pages is to be restricted to registered users, the check mark for "Anonymous Project Access Disabled" must be set.