PeopleSoft Security by Bala

1. Object level security:
In object level security we define security to PeopleSoft objects like Pages, People tools, Web libraries, Processes, and Component Interfaces.
2. Data security:
In data security we define restrictions on data accessed by a user. Here we see Department level security and PS Query security intern called as Row-level security.

• In PeopleSoft everything is stored in tables. For storing security related information also we have security tables at back-end e.g. PSOPRDEFN, PSROLEUSER, PSROLECLASS, PSAUTHITEM.
• If any user is trying to login into PeopleSoft application, applications server takes all security related information from the tables and it enforces restrictions based on the security that a user has.
Object level security:
The security flow for object level security is
- We define object level security at permission list i.e. create a permission list and assign access to whatever the objects you want, like pages, process groups, component interfaces, web libraries etc.
- Then create roles, assign permission lists to roles.
- Create a user profile and then assign roles to users
Question: Why do we need permission lists, roles why can we assign permissions on objects directly to user profile? What is the use of permission lists and roles?
Following snap shots are for your reference



In above slide you see we have assigned access on different pages to permission list AEPNLS.
Data security:
The concept data security is defined wonderfully in PeopleSoft.
Data level security means restricting a user form some rows of data in table.
E.g. We have a table JOB having 10 rows of data by using Roe-level security you can restrict a user to see only 5 rows based on the security that he/she has.
In PS Query the above example can be done with views.
At component level it is done with Department security.