MODULE 7 · Security and Access

Roles, privileges and application access

Original learning guide · Pega ’25 path · Content v1.0.0

Learning objectives

Understand the concept

Roles collect permissions and privileges gate specific behavior. Application access is broader context; it does not by itself authorize every sensitive action. Review permissions against business responsibilities and records.

Authentication establishes identity. Authorization determines allowed actions and data access. Operators identify people or system identities; access groups connect users to application context and access roles. Roles and privileges express permission. Apply least privilege and review the Security Checklist as part of deployment readiness.

Create an approve-loan permission in a role matrix. Test that the same user cannot gain approval capability by calling an action hidden in their interface.

IntakeAssessmentDecisionResolution

A configuration example

A loan officer can collect and submit an application. A credit reviewer can assess it. Only an authorized approver can approve it. Test each role with both allowed and forbidden actions, including direct requests rather than only visible menus.

Application: Loan Origination
Case type: Loan Request
Learning focus: Roles, privileges and application access

Given: a known applicant and a documented policy
When: the configured step or rule executes
Then: compare actual data and routing with the expected outcome

Conceptual configuration plan, not an importable Pega rule. Labels and tools vary by release. Use the official mission environment to inspect current screens.

Try it yourself

Create an approve-loan permission in a role matrix. Test that the same user cannot gain approval capability by calling an action hidden in their interface.

Build a matrix of personas against create, view, assess and approve actions. Mark the minimum permissions. Explain how application access differs from permission to approve a particular case.

For this lesson, focus your notes on roles, privileges and application access. Record the inputs, configuration choice, observed result and one alternative that you rejected.

Common mistake

A logged-in account is not automatically entitled to every record or action. Authorization must be evaluated in context.

Knowledge check

What does successful authentication prove?

Check your understanding

It proves identity under the configured authentication method; it does not grant every application permission.

Go deeper with official resources

Pega Academy System Architect mission
Official ’25 certification objectives