Share this page

# Assign project roles and permissions to users

A project role and its permissions determine what actions a user may perform and what areas they can view.

In this topic:

## About roles and permissions

To protect a project from unauthorized access, you can assign each user to one or more project roles. A user’s role is made up of permissions based on their function, like admin or tester.

Predefined System roles with default permissions are also available. Each role has access to specific tasks. For details, see Predefined project roles.

When a project requires that specific user roles have permissions that are outside the scope of their default permissions, you can add your own customized user roles and assign each role a unique set of permissions.

Site administrators can create roles, edit permissions, and assign or remove roles.

Note:

- You cannot assign multiple roles to a user per project.

- When you change permissions for a role, any users assigned to that role must sign out and sign in again for the change to take effect.

Predefined project roles

You can assign one or more of the following predefined project roles to users.

Role | Description
--- | ---
Performance Tester | Has permissions to perform all the actions under all categories.
Viewer | Has no permissions to perform any actions; can view data only.

Note:

- Predefined roles cannot be customized, and are indicated by "System".

- During Site Admin and LAB migration, all users are automatically set with Viewer role. During project migration, users that belonged to the TDAdmin group in the ALM project are set with Performance Tester permissions in OpenText Enterprise Performance Engineering, and the rest are set with Viewer permissions.

Back to top

## Permission categories

Permissions are assigned to roles, and are organized into functional categories, such as tests, runs, and resources.

The following tables list the permissions available for each category and a link to its API mapping. These permissions indicate:

- How users with the selected role can work with each item in the category.
- In some cases, whether a user with the selected role can perform additional actions related to the category.

Tests and scripts

Permission | API Mapping
--- | ---
Test (Create) | tests
Test (Delete) | tests/{ID}
Test (Update) | tests/{ID}
Test Folder (Create) | testplan
Test Folder (Delete) | testplan/{id}
Test Folder (Update) | testplan/{ID}
Script (Delete) | Scripts/{ID}
Script (Update) |
Script (Upload script / Create new script) | Scripts

Runs

Permission | API Mapping
--- | ---
Run (Delete) | Runs/{run ID}
Run (Update) |
Run (Start Run) | Runs
Test Set (Create) | testsets
Test Set (Delete) | testsets/{id}
Test Set (Update) | testsets/{ID}
Test Set Folder (Create) | testsetfolders
Test Set folder (Delete) |
Test Set folder (Update) |
Run Result (Collate) | runs/{runID}/collate
Run Result (Analyze) | runs/{runID}/analyze
Run Result (Delete file) |
Run Result (Upload file) | Runs/{ID}/Results

Assets

Permission | API Mapping
--- | ---
Monitors (Create) |
Monitors (Delete) |
Monitors (Update) |
Analysis Template (Create) |
Analysis Template (Delete) |
Analysis Template (Update) |
Asset Folder (Create) | resourcefolders
Asset Folder (Delete) | resourcefolders/{id}
Asset Folder (Update) |

Resources

Permission | API Mapping
--- | ---
Host (Update) |
Host (Create Private Host) | hosts
Host (Delete Private Host) | hosts/{hostID}
Host (Check Host) |
Host (Reconfigure) |
Host (Kill Process) |
Host (Reboot) |
Host (Manage DP Queue) |
Host (Configure LR Agent) |
Host (Provision Cloud Host) |
Timeslot (Create) | timeslots
Timeslot (Delete) | timeslots/{id}
Timeslot (Update) |

Application

Permission | API Mapping
--- | ---
Trend Report (Create) |
Trend Report (Delete) |
Trend Report (Update) | TrendReports/{ID} {TrendID}/baselineid (Set baseline)

Note: These mappings also apply to user-defined roles. For example, if a user does not have Run Result permissions, then that user does not have access to the relevant Run Result APIs.

Back to top

## View roles and permissions

Site admins can check which permissions have been assigned to each role for each functional category.

1. In Administration, select Management > Roles and Permissions. The Roles and Permissions page opens.

2. In the Project Roles tab, select a role to expand the list of permissions. The permissions are displayed for each item.

Back to top

## Create project roles

Every user role has a set of permissions which are defined by the project administrator. If you determine that the default user roles do not meet the needs of your project, you can create new project roles with customized permissions.

Example: Suppose a group of users called `Group1` has Viewer permissions. To work more effectively on the project, they need to create Trend reports. As the project administrator, you can assign these permissions to the `Group1` role by specifying permission settings.

1. In Administration, select Management > Roles and Permissions. The Roles and Permissions page opens.

2. Select the Project Roles tab and then click the Add Role button .

3. In the Roll Name box, enter a name for the group.

   Note: A group name cannot include the following characters: ( ) @ \ / : * ? " ` < > | + = ; , %

4. In the Based on Role list, select an existing role that has similar access permissions to the new role you want to create. This minimizes the level of customization you need to do.

   Click OK. The new role name is added to the roles list.

5. Customize the role permissions.

   1. Click an entity tab (Tests and Scripts, Runs, Assets, Resources, Application) to see the permissions for each entity.

   2. Select the check box for the permissions that the selected role requires for each entity.

Back to top

## Assign or unassign project roles

Every user must be assigned at least one role in each project to which he/she is assigned. By default, the Viewer role is assigned.

After adding a user to the project, you can assign roles. For details, see Assign projects and roles to a user.

You can change roles for users or unassign users from roles and projects. For details, see Change the project role assigned to a user and Remove users from a project.

Back to top

## Change the project role assigned to a user

You can change the role of a user assigned to the project from the Projects page.

1. In Administration, select Management > Projects.

2. Select a project from the Projects list (click the link in the Project Name column). The project details page opens in the Main Details view.

3. In the Users view, select the user that you want to change the role.

4. Click the Role dropdown and select a different role.

Back to top

## Edit user-defined project roles

Site administrators can edit permissions and the name of a user-defined project role.

1. In Administration, select Management > Roles and Permissions, and open the Project Roles tab.

2. In the project roles list, expand the user-defined role for which you want to edit permissions. For each item, check or clear the permissions.

3. To edit the name of a user-defined role, hover over the name of the role you want to change, click the Edit button , and edit the name as required.

Back to top

## Delete project roles

You can delete any user-defined project roles provided they do not have users assigned to them.

1. In Administration, select Management > Roles and Permissions, and open the Project Roles tab.

2. In the roles list, select the user-defined role you want to remove and click the Delete button .

   Note: You cannot delete the predefined "System" roles.

3. Click Delete to confirm. The role is removed from the list.

Back to top

See also:

- Manage users in a project
- Create domains and projects
- Manage projects

https://admhelp.microfocus.com Enterprise Performance Engineering,LoadRunner Enterprise 8942
Tips to improve your search results...OpenText™ Enterprise Performance Engineering Help Center OpenText™ Enterprise Performance Engineering Help 26.1 All View Local Help Center View Online Help Center Version: