Definition Security Authorization Rules

To set up definition security properly, it’s helpful to understand how the system interprets definition security settings. The system applies the following rules to determine whether a user is authorized to update a definition:

Rule	Description
1	Is the definition type assigned to any definition group? If not, then anyone has update access to it. For this reason, you should add all definition types to at least one definition group.
2	Is the definition type a part of a definition group assigned to the user’s primary permission list? If not, the system denies access and displays a message, such as “definition_name is not a definition that you are authorized to access.”
3	Do all the definition groups of which the definition type is a member have the display-only option enabled? If so, then the system displays the message “definition_name is not a definition that you are authorized to update.” The definition type appears with the Save command disabled.

If the definition passes these system checks, the user is allowed to access and update it—unless it’s a PeopleSoft Application Designer definition, in which case several other security checks are performed first. PeopleSoft Application Designer definitions are also controlled by the PeopleTools in permission lists.

Important:

A user gets definition security permissions through the primary permission list, not through roles. Access to definition types is granted through roles.