Salesforce Experience Cloud Consultant

The template sets what you start with and what you cannot easily change. You compare the available templates, adapt themes, use Experience Builder to shape pages, and weigh the trade-off between speed and flexibility.

• Template families and what each suits
• Choosing a template for a use case
• Themes and theme layouts
• Pages, components and Experience Builder
• Switching templates and its cost
• Previewing across devices

You build A template recommendation for a customer, with a prototype in Experience Builder.

A site should feel like it belongs to the organization and speak to each audience. You apply a brand, target content to groups of users, and personalize what different visitors see without building separate sites.

• Branding sets and style controls
• Logos, fonts and color
• Audiences and targeting rules
• Personalizing pages and components
• Keeping branding consistent across pages

You build A branded site section that shows different content to two audiences.

Content ages if no one owns it. You use Salesforce CMS to author, organize and publish content, share it across sites, and decide who may create and who may approve it.

• CMS workspaces and channels
• Content types and authoring
• Publishing and scheduling content
• Sharing content across sites
• Roles for authors and approvers
• Translating and localizing content

You build A CMS workspace with content published to a site and a review route.

External users are not employees, so their path in matters. You create them by registration or by invitation, set the login experience, and connect single sign-on or social sign-in when the audience expects it.

• Self-registration compared with invitation
• Creating users from contacts
• Login pages and their branding
• Single sign-on for external users
• Social sign-in options
• Password reset and account recovery

You build A registration and login flow for one audience, with sign-on options.

License choice shapes both capability and cost. You compare the license families for external users, match them to the objects and sharing each audience needs, and recognize when a requirement forces a larger license.

• License families for external users
• What each license allows on objects
• Member-based and login-based models
• Matching license to audience
• Limits that force a license change
• Estimating license need

You build A license recommendation for three audiences, with the reasoning for each.

External users must never see what is not theirs. You set who can see other users, which objects they can reach, and how records are shared to them through sharing sets, groups and rules, including limits on guest access.

• User visibility settings
• Object visibility through profiles and permission sets
• Sharing sets for account-based access
• Share groups and sharing rules
• Guest user access and its restrictions
• Testing as an external user
• Troubleshooting why a record is hidden

You build A sharing design for a partner site, tested with two sample external users.

Support is a common reason to build a site. You let customers raise and follow cases, publish knowledge they can search, and add an agent-driven service experience, and you decide where each one belongs.

• Case creation and tracking for customers
• Publishing knowledge to a site
• Search and recommendations
• Adding Agentforce Service to a site
• Escalating from self-service to a person

You build A self-service support flow from article search to case creation.

Launching is the beginning. You administer a site day to day, configure its settings, moderate content and members, manage domains and publishing, and move changes from sandbox to production without losing work.

• The administration workspaces
• Settings that affect performance and security
• Moderation of members and content
• Custom domains and publishing
• Moving a site between environments
• Handling support requests about the site

You build A site administration guide for a team that will run it after launch.

A site proves its value in use. You choose the metrics that show whether people arrive, return and get things done, read the analytics, and plan the actions that raise adoption when numbers are weak.

• Choosing adoption metrics
• Reading site analytics
• Reports on member activity
• Finding where users drop off
• Planning adoption actions

You build An adoption dashboard and a short improvement plan.

Every platform has an edge. You learn what can be customized with clicks, components and code, where the template or licensing draws the line, and how to tell a customer honestly when a request costs more than it is worth.

• What can be changed without code
• Custom components and where they fit
• Limits tied to templates and licenses
• Performance considerations
• Telling a customer what is not worth building
• Documenting trade-offs

You build A fit-and-gap analysis for a customer’s ten feature requests.

Turn a customer’s need into a design. You pick the template, plan the branding, choose licenses and design sharing and sign-in, then present the plan with its limits stated openly.

• Reading the customer’s audience and goals
• Choosing template, license and sign-in
• Designing sharing and content
• Planning adoption and support
• Presenting the site design and its limits

You build A site design package for one customer: structure, access model and rollout plan.