11.3 Channels, Personas, Portals & Landing Pages
Key Takeaways
- A persona is a user profile the application is designed for; each persona is paired with the channels through which that persona reaches the application.
- Channels include web portals, mobile portals and apps, email, messaging or chat services, and voice services, and are configured in App Studio alongside personas.
- Portal templates set the screen layout and required features for a portal, support responsive development, and include a mobile-only layout option.
- Landing page templates include Default page, Tabbed page, Dashboard page, and Inline Dashboard page, and landing pages can display widgets, views, and insights.
- Pega ships out-of-the-box landing pages such as Dashboard, Home, Explore Data, My Work, and the Self-service main page, with Home supporting widgets including App announcements, Pulse, and Todo.
11.3 Channels, Personas, Portals & Landing Pages
Chapters 6 and 11 have covered what a view looks like and how mobile and web delivery work. This section covers the layer above both: who the application is built for, how they reach it, and what they land on when they arrive.
1. Personas: The Anchor for Everything Else
A persona is a profile of a user the application serves — Customer, Claims adjuster, Branch manager, Field technician. Personas are first-class configuration in App Studio, not documentation. Defining them is one of the four pillars of application setup, alongside case types, data, and release milestones.
Each persona carries two attachments that the exam tests:
- An access group, which determines what the persona may see and do. Persona definition and the security model in Chapter 8 are the same conversation viewed from two ends.
- One or more channels, which determine how the persona interacts with the application.
Because personas drive both, changing a persona is a design act with security and UX consequences. A scenario that adds a new user type to an application is asking you to add a persona, map an access group, and select channels — not to clone a portal.
2. Channels: How a Persona Reaches the Application
Customers and employees interact with Pega applications through several channels:
| Channel | Nature | Typical persona |
|---|---|---|
| Web portal | Browser-based workspace for internal or authenticated external users | Claims adjuster, branch manager |
| Mobile portal / mobile app | Responsive portal or a packaged mobile app built from the Mobile channel | Field technician, driver |
| Inbound mailbox that creates or updates cases | Customer contacting support | |
| Messaging / chat | Conversational interface, optionally AI-assisted | Self-service customer |
| Voice | Telephony-integrated interaction | Call center caller |
The relationship the objective asks about is direct: a persona is the "who," a channel is the "how." One persona can have several channels — a customer might use both a self-service web portal and email — and one channel can serve several personas.
3. Portals and Portal Templates
A portal is the custom web interface designed for a persona. Rather than authoring a portal from raw layout components, you select a portal template.
Portal templates:
- Set the screen layout and the required features of the portal — where navigation lives, whether there is a utility area, what the header contains.
- Support responsive application development, so a single portal adapts across viewport sizes.
- Include a mobile-only layout option for personas who work exclusively on a handset.
Comparing templates is a design judgment about the persona's work pattern. A caseworker who lives in a worklist all day needs prominent work navigation and case switching. A manager who mostly reads metrics needs dashboard real estate. A self-service customer needs a small number of clear actions and no internal navigation at all.
4. Landing Pages
A landing page is a full page inside a portal that is not tied to a single case. Pega ships several out of the box:
- Dashboard — operational metrics and KPIs.
- Home — the default entry page, which supports purpose-built widgets including App announcements, Pulse, and Todo.
- Explore Data — the authoring surface for insights (covered in Chapter 10).
- My Work — the user's assignments.
- Self-service main page — the entry page for external, unauthenticated or lightly authenticated users.
Landing Page Templates
To create a custom landing page you start from a page template. Page templates are responsive layouts that assemble into a full web page:
| Page template | Shape | Use when |
|---|---|---|
| Default page | Single content region | A simple page of views or widgets |
| Tabbed page | Content split across tabs | Several related content sets under one page |
| Dashboard page | Grid of metric tiles and charts | A dedicated metrics page |
| Inline Dashboard page | Dashboard content embedded within a broader page | Metrics plus surrounding content on one page |
Landing pages display three kinds of content: widgets (purpose-built components such as Pulse, App announcements, and Todo), views (data and case content), and insights (the chart and table rules created from Explore Data).
5. Themes and Branding
Visual identity in Constellation is applied through the Constellation design system and its design tokens rather than by editing stylesheets. Tokens define color, typography, spacing, and elevation centrally; components consume them. Changing a brand color is a token change that propagates everywhere, which is why custom CSS overrides are a guardrail violation rather than a shortcut.
6. Localization Best Practices
Localization is an explicit blueprint item, and the practices are consistent across portals, landing pages, and case views:
- Never hard-code display text in a view. Labels, instructions, and button captions should resolve through field value rules so a language pack can translate them.
- Use language packs and the Localization wizard to generate the translation set rather than cloning rules per locale.
- Let the platform format dates, numbers, and currency from the user's locale instead of formatting them in expressions.
- Leave room in the layout. Translated strings are frequently longer than English; fixed-width labels break.
- Localize correspondence and email templates too — outbound communication is part of the user experience, not an exception to it.
7. Exam Framing
Questions here usually give you a new user type and a delivery requirement and ask what to configure. Work the chain in order: persona → access group → channel → portal template → landing pages and widgets. If the scenario is about branding, the answer is design tokens. If it is about a second language, the answer is field value rules and a language pack, never duplicated views.
An insurer is adding a new external user type — independent brokers — who will submit and track quotes from a browser and receive status updates by email. What is the correct configuration sequence in App Studio?
A team must build a custom landing page that presents three distinct content sets — open quotes, recent decisions, and reference documents — inside a single page without forcing users to scroll between unrelated blocks. Which landing page template is the natural fit, and what content can it host?
A Pega application must be delivered in English and Brazilian Portuguese. A developer proposes copying every view and replacing the labels with Portuguese text in the copies. What is the correct guidance?