Managing User Access

testgrinder service will be discontinued on January 31, 2025

testgrinder allows you to control who has access to projects, target systems, runs, and jobs.

There are four types of testgrinder user roles:

• Owner

• Administrator

• User

• Viewer

Owner

Each testgrinder account belongs to its owner. The owner is the one who pays the subscription fees - and we appreciate that! The ownership may be transferred to another user on the same account if needed.

Administrator

The owner may choose to add administrators to help with account management. Administrators can do everything regular users can, plus they can manage other users.

User

While owner and administrators have full access to all testgrinder records, users need to be granted access. Users start with no access to projects and can be assigned either View, Edit, or Manage access to each project separately. Manage access allows the user manage access to the project for other users. When a user creates a new Project, they gain Manage access to the project automatically. By default, Users get View access to target systems, but may be granted Use, Edit, or Manage as well. With Use access, the user may launch runs on the target system. Manage allows the user to manage access of other users to the Target System. When a user creates a new target system, the user gains Manage access to the target system automatically.

Viewer

Viewers can only view testgrinder records. Initially they have no access to projects, but may be granted View access, which lets them view the project and its runs. Viewers do not count against the subscription user license limit.

Owner and administrators have full access to all projects. Users and viewers initially have no access to projects (unless the project was created by a user, who receives the Manage access automatically). To grant a user or a viewer access to a project, navigate to the project editor, select the project in the tree, and choose the Security tab:

Target systems are visible to everyone on the account. The next higher level of access is Use. The Use access allows launching runs on a target system. Users with Edit access can also edit the target system, and those with Manage access can manage access of other users to the target system. The owner and administrators always have full access. To view or manage user access to a target system, open the target system's Security tab.

In order for a user to see runs for a project, the user has to have at least View access to the project. In addition, those with at least Use access for the target system on the run can launch, pause, resume, retry, and cancel it. Users need to have Edit access to edit run notes or to delete runs.

Minimal rights to launch runs

The minimal rights needed to launch a run are View access to the project, and Use access to the target system.

Jobs are managed similarly to runs. The user's access to the project determines their ability to edit the job, and their access to the target system determines their ability to launch runs from the job.

Reviewer

When setting up someone for reviewing projects or runs, add them as an account user with Viewer role and grant them View access to the project. As viewers, they will not be counted against the subscription user licenses.

Launchers

To give someone the right to launch runs but not edit the project, add them as an account user with User role. Grant them View access to the project, and Use access to the target system.

Editors

Those who will be editing the project should be given Edit access to the project. They should also have at least Use access for the target systems which they will use for testing the changes they make.