Functionality to switch access group from the end user portal

I want to implement access group switching in a Constellation application (Pega 25.1.3).

Example:

  • User A has two access groups:
    • App1: Manager (default)
    • App1: Customer

After login, the user lands on the Manager Portal based on the default access group. Since the user also has access to the Customer Portal, they should be able to switch between the Manager and Customer portals from the UI.

I want to display the user’s available access groups in a dropdown and allow them to switch to the selected access group.

I noticed that Constellation allows adding components such as Cards and Table layouts. What is the recommended approach to add a dropdown for this use case? Is there any out-of-the-box Constellation control/component available, or would I need to build a custom DX component? What is the best way to implement access group switching in Pega 25.1.3 Constellation?

@AdityaC8 you can checkout Switching portals and access groups in Constellation for more details but the short version is: You would need to build your own DX component to manage this.

However, we do not have any published examples on our Github for this. I know a few have tried to bring back the legacy UX of “switch access group” and have reached out to see if they can share any guidance.

As you can probably tell from the article, I am not a fan of the switching access group UX. Personally, if you wanted them to see the Customer Portal you could allow them to open that portal (as outlined in the article) OR just add those landing pages to their existing Portal.

Infinity '26

I like this latter option, “add those landing pages to your existing portal” in Infinity '26, as you can now create sub-menu’s, which would allow you to create a “Customer Portal” sub-menu, to open their landing pages.

We found a Pega article, we are currently evaluating persona-switching capabilities within the same application based on the official Pega guidelines. Despite following the documented steps, our POC implementation is not behaving as expected, and users cannot switch personas seamlessly. Could you please review our configuration or advise on any specific prerequisites required to enable this?

We followed below link to enable persona switch functionality.

Switching between applications in a Portal

@AdityaC8 what version are you using? this was enabled for Infinity '26 but I saw from your post back in August that you are on '25? I can not see a doc stating this is available in '25.

One thing to note, I have seen others gets stuck, the editing of pyGetMyApps activity is important.

If the names are the same it won’t show both, you can make them distinct by using pyMyAppSetAccessGroupLabel. You would need to decide how you want the names to show / be distinct in your editing of the activity.

  • By way of example, I have seen others extend it to focus purely on access group name (though this might not be the optimal UX for your use case)

To get Pega Support to review your configuration and debug this, you would need to raise a support ticket (https://support.pega.com/).