Experience Cloud login pages, branding and sessions
How to shape what external users see before and after they log in to an Experience Cloud site: the four login page types, Login & Registration branding with dynamic expid URLs, Experience Builder themes and audience-based branding sets, and profile session settings that keep customers signed in.
Describe the capabilities for customizing the user experience for Experience Cloud.
~8 min read · 13 practice questions ·
What the exam expects
- Choose a login page type (Default, Login Discovery, Experience Builder, Visualforce) from the requirement, the site's template and how users must authenticate.
- Know what the Login & Registration page can brand (logo, background, button color, right frame, footer), where it does not apply, and how
expidmakes the logo and right frame dynamic per brand. - Restyle a site with clicks using themes, Generate Palette from Image and audience-based branding sets.
- Configure customer and partner profile session settings: timeout up to seven days, Keep users logged in, device activation.
- Recognize when a login flow, not a page setting, handles a post-login step.
Key terms: Login & Registration page (Administration workspace page that sets page types and point-and-click branding); expid (query parameter that picks a brand at run time); branding set (bundle of colors, images and fonts in Experience Builder's Theme panel); device activation (identity verification on a new browser or device).
Key facts
- Detail
- Username and password only; publish the site first
- Detail
- Aura sites, and LWR sites using it before Summer '23
- Detail
- Not available with an Experience Builder login page
- Detail
- Logo, background, button color, right frame, footer; not Experience Builder pages
- Detail
{expid}in Logo URL and Right Frame URL; set by link, button orSite.setExperienceId
- Detail
- Must match the site's protocol
- Detail
- Aura sites; no record-based criteria; others see the default set
- Detail
- Up to seven days on the cloned customer or partner profile
- Detail
- Password, delegated, SAML and auth provider logins; not API logins
Sources for this section (7)
- Login Page Typeshelp.salesforce.com (opens in a new tab)
- Configurable Self-Reg Pagehelp.salesforce.com (opens in a new tab)
- Brand from the Administration Workspacehelp.salesforce.com (opens in a new tab)
- Set Up Dynamic URLshelp.salesforce.com (opens in a new tab)
- Assign an Audience to a Branding Sethelp.salesforce.com (opens in a new tab)
- Extend Customer Identity Sessionshelp.salesforce.com (opens in a new tab)
- Custom Login Flowshelp.salesforce.com (opens in a new tab)
- Why does a logo uploaded on the Login & Registration page not appear on an Experience Builder login page?
- When can a site use the Visualforce Page login type?
- Why can't a branding set target partners by a field on their account record?
- What does Enable device activation add to a customer profile?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Identity and Access Management Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 25 lessons of the Platform Identity and Access Management Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (13 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams