Salesforce Experience Cloud Consultant: Security, Identity, and Site Design

Salesforce Certified Experience Cloud Consultant remains an active credential in 2026. It is designed for professionals who can design, configure, build, and implement Experience Cloud sites in a customer-facing role while making sound decisions about external users, licensing, sharing, authentication, content, templates, adoption, and administration.

The certification is broader than “build a portal.” Experience Cloud solutions sit at the boundary between Salesforce and external audiences such as customers, partners, members, or other communities. That boundary introduces identity, access, data visibility, branding, content, self-service, partner processes, and operational governance concerns that do not appear in the same way for internal CRM users.

The assessment uses 60 multiple-choice or multiple-select questions in a 105-minute window, may add up to five unscored questions, and requires a 62% passing score. Salesforce Certified Platform Administrator is a prerequisite, and Salesforce recommends roughly six months of hands-on Experience Cloud administration or development experience.

Start with the audience and business model, not with Experience Builder

The first design question is who the experience serves and what those users need to accomplish. A customer support site, partner sales portal, member community, public knowledge site, and account-management experience have different identity, licensing, sharing, content, and navigation requirements. Choosing a template before understanding the audience usually produces rework.

Good preparation begins with personas and journeys. For each external user type, define how the person enters the experience, what records they need, which actions they can perform, what content they consume, and how success is measured. That turns Experience Cloud from a page-building tool into a business solution.

Sharing, visibility, and licensing are foundational design decisions

Sharing, Visibility, and Licensing accounts for 17% of the current blueprint. Candidates need to reason about user visibility, object visibility, external account relationships, declarative sharing, sharing sets, roles, and external license types. This is one of the most important areas because an external experience can expose sensitive information if the security model is poorly designed.

The adjacent Platform Sharing and Visibility Architect domain is useful for deeper study. Experience Cloud candidates do not need the full architect blueprint, but they should understand how external-user models interact with role hierarchy, sharing sets, account relationships, and record ownership.

Authentication is part of the user experience

User Creation and Authentication represents 13% of the exam. Candidates should understand manual provisioning, bulk creation, self-registration, Just-in-Time provisioning, social sign-on, and single sign-on options. Authentication design affects security, support burden, onboarding friction, and the ability to connect a digital experience with an existing customer identity system.

Concepts from single sign-on and federation help because candidates need to distinguish identity-provider and service-provider roles, understand trust, and recognize where SAML, OAuth, OpenID Connect, or social identity patterns fit. The exam does not require deep protocol engineering, but it does expect sound implementation judgment.

Templates and themes should follow the use case

Templates and Themes account for 10% of the blueprint. Candidates must know how to choose a suitable template, apply themes, and understand packaging or importing templates. The important skill is matching the template to the experience rather than choosing based on visual preference.

A partner site may prioritize opportunity, lead, and account collaboration. A customer self-service site may emphasize cases, knowledge, and account information. A public information experience may require very different authentication and content choices. Candidates should be able to explain how the initial template decision affects available components, navigation, and future customization.

Branding, personalization, and content need governance

Branding, Personalization, and Content represents 15% of the exam. Experience Builder makes it relatively easy to change pages and components, but enterprise experiences require consistency. Candidates need to understand audience targeting, Salesforce CMS, search, topics, and knowledge visibility while keeping the experience maintainable.

Personalization should be purposeful. Showing different content to a partner, premium customer, or anonymous visitor can improve relevance, but every rule adds complexity. A good consultant documents who owns the content, how audiences are defined, how changes are tested, and how stale information is retired.

Administration and configuration form the largest exam domain

Administration, Setup, and Configuration accounts for 25% of the current blueprint. It includes enabling and activating experiences, Workspaces, topics, public experiences, delegated external-user administration, deployment and migration, channel sales and PRM, and service capabilities. This weighting reflects how much operational configuration is required after the visual experience is designed.

The Platform Administrator prerequisite matters here. Candidates should already be comfortable with Salesforce administration concepts such as permissions, data access, configuration, automation, and reporting. Experience Cloud adds external-user complexity rather than replacing core platform fundamentals.

Partner relationship management creates a different external-user model

Partner experiences often need channel sales processes, account relationships, lead or opportunity collaboration, and delegated administration. These users are external but may participate directly in revenue processes. That creates a more complex security and data-sharing model than a simple authenticated customer portal.

Practice by designing a partner hierarchy with several companies, partner managers, and sales users. Decide which accounts, leads, opportunities, and cases each user can access, how new users are created, and how partner administrators are delegated. This makes abstract sharing concepts concrete.

Adoption and analytics prove whether the site is working

Adoption and Analytics is only 5% of the exam, but it is important in real projects. A launched experience can fail quietly if customers cannot find answers, partners avoid the portal, or users abandon registration. Consultants need to understand dashboards, insights, moderation, and engagement practices.

Use clear KPI design to define success before launch. Useful measures might include self-service resolution, login activation, case deflection, partner pipeline contribution, search success, content engagement, or task completion. The metric should reflect the experience’s purpose rather than generic page views alone.

Experience Cloud intersects directly with identity architecture

External identities are one of the places where Experience Cloud and the Platform Identity and Access Management Architect domain overlap. Complex projects may involve enterprise identity providers, embedded login, multiple brands, external identity licenses, account linking, or identity federation across several applications.

Experience Cloud consultants should know when a requirement exceeds ordinary configuration and needs architecture support. They should be able to describe the external-user journey and business requirements clearly enough for an identity architect to design the federation, provisioning, trust, and security model.

A strong hands-on project is to build a realistic customer or partner experience. Define personas, choose licenses, configure external accounts, design record sharing, implement registration and authentication, choose a template, add content and search, configure service or partner features, and publish the site. Then test the experience as several different users to verify both usability and data visibility.

Add deployment and operations to the project. Move changes between environments, document ownership, create a support process for registration failures, and define adoption metrics. This reflects the exam’s implementation perspective far better than learning isolated settings.

Salesforce certifications reflect how Experience Cloud sits at the intersection of administration, security, service, sales, identity, and digital experience. Candidates who understand those relationships will be better prepared than candidates who focus only on page layout. The credential is ultimately about delivering a secure, scalable external experience that supports a real business relationship.

Accessibility and content lifecycle are also useful implementation considerations even when they are not the largest blueprint categories. External experiences serve users with different devices, abilities, languages, and levels of familiarity with the organization. Consultants should test navigation, forms, search, and important content with real personas rather than assuming that a site that looks correct in Experience Builder is automatically usable.

Operational support should be designed before launch. Decide who handles registration failures, locked-out users, content issues, partner-access problems, moderation events, and broken integrations. Define which problems belong to Salesforce administrators, identity teams, service teams, content owners, or partner managers. This reduces the common post-launch problem where the site is technically live but nobody owns the user journey when something fails.

For final preparation, walk through the experience as each persona from first visit to completed business outcome. Verify authentication, data visibility, navigation, content, record creation or update, service interactions, and analytics. Then repeat the walkthrough after changing one assumption—such as a new partner tier, a stricter sharing rule, or a different identity provider. That kind of scenario practice develops the implementation judgment the consultant exam is designed to test.

Licensing deserves repeated scenario practice because the choice affects both cost and capabilities. External identity, customer, partner, and other license models can support different access patterns and sharing behavior. Candidates should avoid memorizing a license name without its intended user model. Start with what the external user must see and do, then evaluate the license and sharing design that can support that requirement securely.

Content and search should be tested with the same rigor as record access. An external user may technically have permission to reach a page but still fail to complete a task because labels are unclear, search results are poorly scoped, or important knowledge is hidden behind an unexpected navigation path. Build acceptance tests around user goals rather than components: find an answer, submit a request, update a profile, collaborate with a partner, or complete a transaction. This keeps the implementation focused on the actual experience rather than the number of features configured.