In addition to assigning users to permission groups (see Assigning Users to Permission Groups), you can also grant access to Development Testing Platform functionality to users on an individual basis.
- Open a user's profile page; see Editing a User.
- Click the Permissions & Groups tab.
- Choose a functionality from the Tool drop-down list.
- Choose a permission setting from the Name drop-down list that describes the range of permissions to grant.
- Choose true or false from the Value drop-down box to grant or deny access to the tool.
- Click Add to finish the configuration. You can also click the remove button (x) to remove native permissions.
- Click Save to add native permissions.
Permissions
The following tables describe permissions available in DTP.
PST Permissions
| Permission Name | Value | Description |
|---|---|---|
| basicAccess | true false | Required to login, but additional permissions are necessary to specify what DTP features the user can access. |
| administration | true false | Grants access to the Development Testing Platform Control Center so that the user can deploy and manage DTP applications. |
PSTSEC Permissions
| Permission Name | Possible Values | Description |
|---|---|---|
| basicAccess | true false | Required to login to the Development Testing Platform Security application (User Administration component). Provides ability to modify one's own personal data, but no one else’s. |
| administration | true false | Grants right to edit and modify user and permission groups data. |
GRS Permissions
| Permission Name | Possible Values | Description |
|---|---|---|
| basicAccess | true false | Required to login to Report Center, but additional permissions are necessary to specify which features the user can access. |
| administration | true false | Grants access to Report Center administration pages |
| project | [project name] regex pattern | Grants access to the data associated with a specific project. You can use a regular expression to grant access to related projects. For example, if grs:project:Core provides access to a project called Core, you can use the regular expression grs:project:Core \d\.\d to provide access to Core 1.0, Core 1.1, etc. projects. |
| prioritizeAll | [project name] regex pattern | Enables the user to set the priority of violations associated with the project. Team default permission: Leader (leader inherits permissions from member) |
| prioritizeOwner | [project name] regex pattern | Enables the user to set the priority of violations assigned to the user. |
| viewSourceCode | [project name] regex pattern | Enables the ability to view source code associated with the project.Team default permission: Member. |
| testSessionStatusChange | [status value to status value] regex pattern | Specifies what status transitions can be made for test sessions in Project Center (strict mode only). See “Controlling Permissions and Status Transitions with Strict Mode” in the Project Center documentation for additional information. |
| reqStatusChange | [status value to status value] regex pattern | Specifies what status transitions can be made when working with requirements in Project Center (strict mode only). See “Controlling Permissions and Status Transitions with Strict Mode” in the Project Center documentation for additional information. |
| defectStatusChange | [status value to status value] regex pattern | Specifies what status transitions can be made when working with defects in Project Center (strict mode only). See “Controlling Permissions and Status Transitions with Strict Mode” in the Project Center documentation for additional information. |
| testStatusChange | [status value to status value] regex pattern | Specifies what status transitions can be made when working with tests in Project Center (strict mode only). See “Controlling Permissions and Status Transitions with Strict Mode” in the Project Center documentation for additional information. |
| scenarioDeleteRestore | [status value to status value] regex pattern | Enables users to delete and restore test scenarios in Project Center (strict mode only). See “Controlling Permissions and Status Transitions with Strict Mode” in the Project Center documentation for additional information. |
| scenarioStatusChange | [status value to status value] regex pattern | Specifies what status transitions can be made when working with test scenarios in Project Center (strict mode only). See “Controlling Permissions and Status Transitions with Strict Mode” in the Project Center documentation for additional information. |
LS Permissions
| Permission Name | Possible Values | Description |
|---|---|---|
| basicAccess | true false | Grants access to view License Server configuration pages. |
| administration | true false | Grants access to License Server administration pages to manage licenses (add, remove, reserved, and so on). |
TCM Permissions
| Permission Name | Possible Values | Description |
|---|---|---|
| basicAccess | true false | Grants access to view Team Server configurations. |
| administration | true false | Grants access to Team Server administration pages to manage stored data, such as grant/limit access to Team Server data, created sandboxes, and load test configuration. |
EM Permissions
| Permission Name | Possible Values | Description |
|---|---|---|
| role | administration | Grants access to all Environment Manager activities: testing privileges, provisioning environments, defining systems and environments, controlling access permissions, and test data management. See the Environment Manager User Guide for additional information. |
| role | system | Grants the ability to provision environments and to create and execute test jobs in Environment Manager. Appropriate permissions to the resources is required for both actions. This role also grants the ability to execute all repository actions on test data. See the Environment Manager User Guide for additional information. |
| role | provision | Grants the ability to provision environments for sources the user has access to in Environment Manager. This role also grants read-only access to test data. See the Environment Manager User Guide for additional information. |
