Program Management Security
This section describes how to use licenses, access grants and security groups to give users access to Program Management information and processes. For a detailed description of PPM security, see the Security Model Guide and Reference.
Table 4-1. Security features lists the settings you use to control the data and process security in PPM.
Table 4-1. Security features
|
Security Feature
|
Definition
|
|
Licenses
|
Each user is assigned one or more licenses that determine which set of PPM product-related screens and functions is available to that user. Use the licenses in conjunction with access grants to give users access to specific fields and functions.
|
|
Access grants
|
Linked to users through security groups, access grants determine the windows and functions in which users can view or edit information or perform actions. Access grants also provide different levels of control over some entities and fields.
|
|
Entity-level restrictions
|
Use entity settings to:
-
Control who can create, edit, process, and delete PPM entities such as requests, packages, and projects.
-
Control which request types and object types can be used with certain workflows.
You can set up these restrictions in the configuration entities (workflows, request types, and object types).
|
|
Field-level restrictions
|
For each custom field that you define in PPM, you can specify the conditions under which it is visible (or not) and editable (or read-only). You can also specify the users who can view or edit some fields.
|
|
Configuration-level restrictions
|
Use ownership groups settings to specify who can modify configuration entities. For example, to ensure that only designated users can change your PPM–controlled processes, select the users who can edit an existing workflow.
|
Security Groups of this section provides the steps to perform to configure security groups and users for Program Management.
