Pagelet Security

Similar to page access, you control pagelet security at the component level by associating it with a permission list (which is then associated with a role); each pagelet has its own component to enable more granular access. (You can ascertain a pagelet's component name in PeopleSoft Application Designer by searching for definition references to the page's system, or object name.)

PeopleSoft groups pagelets into functional roles as an example of how to organize access. You must create the proper permission lists and associate them with actual role definitions before users can access them, or use the permission list definitions that PeopleSoft provides its delivered sample data. PeopleSoft delivers sample data security objects (roles and permission lists) that you can use as an example of how to set up pagelet access.

Sample Pagelet Organization

Role groupings provide examples of how to organize pagelet access by function.

PeopleSoft eBill Payment organizes pagelets by these sample roles:

• Broker

• Customer

• Customer service representative

• Customer service manager

• Salesperson