Security

Browse and audit PeopleSoft security configuration: permission lists, roles, and users.

Security

psLens browses PeopleSoft security read-only: permission lists, roles, and users. Use it to audit access without writing SQL against PSOPRDEFN, PSROLEUSER, and PSAUTHITEM. Changes still have to be made in PeopleSoft.

  • Permission Lists — The granular access settings that define menu, component, and page authorizations.
  • Roles — Collections of permission lists assigned to users.
  • Users — User/operator accounts and their associated roles.

How Security Objects Relate

PeopleSoft security flows in one direction:

User → Roles → Permission Lists → Menus/Components/Functions

When investigating access, work from the bottom up:

  1. Start with the permission list that grants the specific access you’re concerned about.
  2. Find which roles include that permission list.
  3. Find which users have those roles.

Or work from the top down:

  1. Find the user whose access you want to understand.
  2. Look at their roles.
  3. Drill into each role to see its permission lists.

User detail pages link out to each role. Role pages link to permission lists and back to assigned users. You can follow an access chain in three clicks without writing a join.

Permission List detail showing properties and menu authorizations

Permission List detail view with properties, menu authorizations, and related data options

Permission Lists

Permission lists (PSCLASSDEFN, sometimes called classes) are the lowest-level grantable security object.

Roles

Roles (PSROLEDEFN) are named bundles of permission lists. Users get roles, not permission lists directly.

Users

Users (PSOPRDEFN, historically called operators) are login accounts.