Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Granting personas access to channels and pages

Updated on April 5, 2022

Start your Microjourney by giving the personas that you create access to relevant portals and pages. By defining different types of access, you can monitor the actions that your team performs. For example, you can ensure that only the personas that represent managers can access the Case Manager portal.

By default, a persona has access to all pages in your application.
Before you begin: Create personas for your application. See Creating personas.
  1. In the navigation pane of App Studio, click Users, and then click Access.
  2. Locate the column of a persona that you want to edit.
  3. In the Portals section, in the Default channel row, in the list, select a default portal for the persona.
    A user that you associate with the persona sees the default channel every time they log in to your application.
  4. Optional: To provide access to more channels, in the row that contains another channel, select one or more check boxes.
  5. In the Pages section, select the check boxes for the pages that you want to be available for the user with the associated role.
    For example: If you select the A new case type, Documents, and Reports pages for a role, the users with this role can access only these pages.
  6. Click Save.
What to do next: Invite users to your application and associate them with personas. See Inviting collaborators to your application.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us