Built-in Permissions
Administrators can assign the following permissions.
PST Permissions
PST permissions (Parasoft permissions) provide basic access to the core system. The PST permissions are:
| Permission | Description | Values |
|---|---|---|
| administration | Grants access to the DTP License so the user can deploy and manage DTP applications. | true / false |
| basicAccess | Required to login, but additional permissions are necessary to specify which features the user can access. | true / false |
PSTSEC Permissions
PSTSEC permissions (Parasoft security) provide access to User Administration functionality. The PSTSEC permissions are:
| Permission | Description | Values |
|---|---|---|
| administration | Grants right to edit and modify user and permission groups data. | true / false |
| basicAccess | Required to log into User Administration. Provides ability to modify one's own personal data, but no one else’s. | true / false |
GRS Permissions
GRS permissions (group reporting system) provide access to Report Center data, dashboards, source code, and so on. The GRS permissions are:
| Permission | Description | Values |
|---|---|---|
| administration | Grants access to Report Center administration pages. | true / false |
| basicAccess | Required to login to Report Center, but additional permissions are necessary to specify which features the user can access. | true / false |
| editGlobalTestConfig | Setting to false prevents users from editing global test configurations. If the permission is not set, project leaders will be able to edit global test configurations, but users with basic permissions will not be able to edit global test configurations. | true / false |
| prioritizeAll | Enables the user to set the priority of violations associated with the project. Team default permission: Leader (leader inherits permissions from member). | <project name> / <regex pattern> |
| prioritizeOwner | Enables the user to set the priority of violations assigned to the user. | <project name> / <regex pattern> |
| project | 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, and so on projects. | <project name> / <regex pattern> |
| viewSourceCode | Enables the ability to view source code associated with the project. Team default permission: Member. | <project name> / <regex pattern> |
License Server Permissions
License Server permissions provide access to License Server functionality (see License Server). License Server is available as an integrated feature in DTP or as a standalone application. The License Server permissions are:
| Permission | Description | Values |
|---|---|---|
| administration | Grants access to License Server administration pages to perform license management functions, such as adding, removing, and reserving licenses. | true / false |
| basicAccess - Deprecated | This permission has been deprecated and will be removed in a future version of DTP. |
EM Permissions
EM permissions (Environment Manager) provides access to Continuous Testing Platform and/or Environment Manager (legacy). Permissions for EM are role-based. Choose Role from the Name menu and assign one of the following roles:
- administration: Grants access to all CTP activities: testing privileges, provisioning environments, defining systems and environments, controlling access permissions, and test data management. See the CTP User Guide for additional information.
- system: Grants the ability to provision environments and to create and execute test jobs in CTP. 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 CTP User Guide for additional information.
- provision: Grants the ability to provision environments for sources the user has access to in CTP. This role also grants read-only access to test data. See the CTP User Guide for additional information.
Built-in User Groups
To ease user and group configuration, DTP provides a set of built-in groups that contain common permissions. We recommend using the built-in groups as parents when you create your own groups.
Built-in groups cannot be edited
You can create and manage custom groups (see Creating and Managing Groups), but the built-in groups cannot be changed.
PST Basic Access
This group defines basic permissions. Each newly created user is automatically assigned as a member of this group. The membership of this group allows users to login to Report Center, but it does not allow access to the administration controls within these modules. Additional permissions are required to perform any actions.
PST Administration
This group defines administration permissions. Members of this group are granted administration permissions for applications within DTP (Report Center, License Server, and User Administration) and can manage data available through administration pages.
GRS Administrators
This group defines administration permission for Report Center. Members of this group can access administration pages for edits, modifications, and management.
