Row-Level Security in PeopleSoft Financials

To establish security, you must first decide the level that you want, which key fields to secure, and whether security will be defined through user IDs or permission lists. With row-level support, you can implement security to restrict individual users or permission lists from specific rows of data that are controlled by the following key fields:

• Business unit

• SetID

• Ledger (and ledger group)

• Book

• Project

• Pay cycle

• Planning Instance

You can also limit access to specific subsets of rows. For example, you can specify user ID security to limit an auditor in Paris to the business unit for your European division. Or, if you have a team of auditors, you can assign them all to one primary permission list and then specify permission list security to enforce appropriate limits on the information that they can access.

The sheer volume of users assigned to a level of security can help you determine whether to use security based on user ID or permission list. If 1,000 users have identical access requirements, explore the use of permission list security. By assigning these users to a single role, you can make subsequent changes in their access requirements just once instead of 1,000 times.

Note:

Applying row-level security does not restrict the data selected by batch processes.