
User management
In an enterprise software application, users play a crucial role as they are the primary individuals interacting with the system. As a Lead System Architect (LSA) of an enterprise application design using Pega Platform™, focus on user-centric design. The needs and preferences of users drive the design and functionality of the application, which helps to ensure that it meets their requirements. Operational efficiency is achieved by users interacting with the application effectively. Providing proper roles and permissions is essential. Ensure that only authorize personnel can access sensitive information.
App Studio user management
Pega Platform provides role-based access control for user-centric design, authentication, and authorization. In low-code application development, manage users from App Studio as your first preference. App Studio provides options for user management, organization, and authentication.
The User Management landing page in App Studio provides options to create Personas and People. A Persona is a wrapper on an Access Group, and People are operators or actors in the application. Personas created from App Studio, by default, receive access to all available Case Types, data objects, and Configuration Sets. You can make the required changes on the Persona landing page in App Studio, as shown in the following figure:
After you create a Persona, associate it with Channels. The Channels landing page in App Studio provides an option to associate a Persona on the Configuration tab, as shown in the following figure. You associate Channels with Personas only in App Studio rather than in Dev Studio.
A Persona is an Access Group when you open it from Dev Studio. Perform any complex configuration required on the Access Group in Dev Studio. For example, to add more roles to the Persona, switch to Dev Studio.
The Organization landing page shows the list of organizations, the Divisions, and Unit structures. You can add more Divisions and Units to define the required organizations structure. However, creating a new organizations is not part of user management in App Studio. Creating a new organizationsmakes sense when you create a new application. Otherwise, throughout low-code application development, create divisions, units, or sub-units. The Units created here appear on the People landing page so that you can map an operator (People) with a unit.
The Authentication landing page in App Studio enables you to create new authentication services or associate existing authentication services with the application. If no authentication services are associated with the application, you can access the application with any authentication services that is available on the system. Add one or more authentication services to restrict application access by using a specified list of authentication services. For an enterprise application, manage the authentication services from App Studio. The following figure shows the Authentication Services landing page configurations in App Studio:
Best practices for user management
To help ensure security and compliance, follow these best practices:
- Regularly review user access: Periodically review user roles and permissions to help ensure that they have appropriate access.
- Use role-based access control: Use roles to manage permissions efficiently rather than assigning permissions individually.
- Implement the principle of least privilege: Grant users the minimum level of access that is necessary to perform their jobs.
- Audit and monitor user activities: Keep track of user activities in the application for security and compliance purposes.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?