Experience CloudCustomer portalPartners

Experience Cloud: your customer and partner portals, what you can really do and how to scope it

Clément Richard · Founder, Amplee • • 9 min read
In short

Experience Cloud opens part of your Salesforce data to your customers and partners: self-service support, account space, partner portal, public help center. Three scoping decisions determine success: the site template (Aura or LWR), the external licenses and the sharing model, so that everyone sees only their own data.

A customer calls to ask where their request stands. Another emails to get a manual they have already received twice. On the channel side, a distributor sends a spreadsheet of open deals every Monday, which someone retypes into Salesforce, late and with errors. All of this information already exists in your CRM. What is missing is secure access for the people outside your company. That is the job of Salesforce Experience Cloud: customer portals, partner spaces and help centers connected directly to your data. Here we cover what the product actually does, the licenses and sharing rules that decide whether it succeeds, and how we scope these projects.

100 sitesmaximum per Salesforce org, counting active, inactive and preview sites
6 licensesprovided by Salesforce for external users
50 rulescriteria-based sharing rules per object, a limit that includes guest user sharing rules

01The problems a portal solves

The projects we scope almost always start from one of these situations:

  • A support team flooded with simple questions. Request status, a document to find, a procedure to follow: the information is in the CRM, but only an agent can read it.
  • Partners working outside the system. Leads sent by email, deals declared in a spreadsheet, sales collateral sent as attachments: sales leadership cannot see the indirect pipeline in real time.
  • Customers who cannot update anything themselves. Changing an address means a phone call.
  • An invisible knowledge base. Your teams have written good answers that are only available internally.

Each time, the point is to open a chosen part of your data to an external audience, with the right permissions.

02What Experience Cloud is

Salesforce describes an Experience Cloud site as a branded digital experience connected to your CRM. That is the key point: sites live in your org, the data is not copied elsewhere, and the administrator decides what is visible from outside.

Sites are built in Experience Builder, starting from templates. According to the Salesforce documentation on templates, you can do a lot without code: edit the template's components, add images and content, then go further with custom pages, custom Lightning components and additional Salesforce objects.

Aura or LWR: an architecture decision

Two approaches coexist. The ready-made templates (Customer Service, Partner Central, Customer Account Portal, Help Center) come with their own pages and flows, and the Build Your Own template exists in both an Aura and an LWR version. The LWR templates (Build Your Own and Microsite) run on Lightning Web Runtime. According to the LWR Sites developer guide, they deliver better page performance, but Build Your Own (LWR) only provides the essential pages and components: it is meant for teams comfortable with Lightning Web Components, Salesforce DX, User Interface API and Apex. The choice depends on what you are prepared to develop and maintain.

03Main use cases and their templates

The official page "Which Experience Cloud Template Should I Use?" maps each use case to a template:

  • Customer support portal (Customer Service). Users view articles, post questions to the community and create cases. The template relies on Knowledge, Chatter Questions and cases; Chatter must be enabled in the org.
  • Customer account space (Customer Account Portal). A private space where customers view and update their account information, see and pay invoices and search the knowledge base.
  • Partner portal (Partner Central). Designed for channel sales: lead distribution, deal registration, marketing campaigns, sharing training and sales collateral, and pipeline tracking with reports and dashboards. These processes run on your Sales Cloud leads and opportunities; see our Sales Cloud expertise.
  • Public help center (Help Center). A public-access site that exposes your knowledge base articles to reduce the load on support.
  • Forum. There is no standalone "forum" template: discussion between users runs through community questions, built into the Customer Service template in particular.

Several sites can coexist in the same org. To place Experience Cloud among the other Salesforce products, our article Salesforce clouds explained gives the big picture.

04Licenses and external access

Creating a site is not enough: every person who logs in uses an external user license. The page Experience Cloud User Licenses lists six: Customer Community, Customer Community Plus, Partner Community, External Apps, External Identity and Channel Account. The word "Community" has stayed in the names: Experience Cloud sites use community user licenses.

  • Customer Community targets consumer experiences with large numbers of external users who need cases or knowledge.
  • Customer Community Plus is for users who need reports, dashboards and standard sharing.
  • Partner Community serves business-to-business experiences that need sales data, typically partner relationship management. It cannot be used with person accounts.
  • Channel Account counts usage by number of partners rather than individual users; each licensed partner account gets up to 40 partner users, in a shared pool.
  • External Apps covers custom experiences for any external stakeholder, with limited access to CRM objects.
  • External Identity is a standalone license to deliver identity services (single sign-on, passwordless login) to your customers and partners.

There are two ways of counting: member-based licenses, assigned to a specific person, and Login licenses, which consume one login per user per day, however many sites they visit. Salesforce also states that licenses are tied to users, not to a site, and strongly discourages using internal licenses for external use cases. The right choice depends on how many people, how often they log in and what they need to see; we have it validated by your Salesforce account executive.

05Security and sharing: where projects are won or lost

A successful portal shows each external user their own data, and only theirs. This is the most technical part of the project, and the one we scope first.

  • Separate default access for external users. External organization-wide defaults let you set a more restrictive access level for external authenticated users than for your own teams, on accounts, contacts, cases, opportunities, custom objects and more. The external level can never be more permissive than the internal one.
  • No roles for high volumes. High-volume users (External Apps and Customer Community licenses in particular) don't have roles: they see their own account and contact, and cannot be added to public groups, account teams or owner-based sharing rules.
  • Sharing sets. This is the mechanism that gives these users access to records related to their account or contact, for example all of their company's cases. You can define only one sharing set per profile.
  • A hierarchy for partners. When the first partner user is enabled, Salesforce creates a three-role hierarchy (Partner User, Partner Manager, Partner Executive) rolling up to the account owner. Salesforce recommends reducing this to a single role and granting super user access when a partner needs to see colleagues' data: without that precaution, the number of roles weighs on performance.

In practice, we build a "who sees what" matrix before any configuration: for each type of external user, every exposed object, read or edit, and through which mechanism. A poorly designed sharing model cannot be fixed at the end of a project.

06Login and guest access

A site combines two kinds of access: authenticated users, who log in, and unauthenticated guests. Each site comes with default pages for login, logout, password management and self-registration, which you can customize in Experience Builder. On sensitive pages, Salesforce recommends using only standard components or components you have vetted.

Guest access deserves particular care. The secure guest user record access setting is enabled in every org with sites and cannot be disabled: guests have private access to all objects, cannot receive manual sharing or be added to groups, and only get read access through dedicated sharing rules. Salesforce warns that these rules open access to anyone, without credentials. Yet this is the mechanism behind a public help center: for a knowledge base readable without logging in, no community license is needed.

07What still needs to be scoped

  • The exact audience. Consumers, business accounts, distributors, installers: each calls for a different license and sharing model. One site can host several license types.
  • Account creation. Open self-registration, invitation or creation from a contact: the admin workload and the risk change.
  • What is done without code. A well-configured ready-made template often covers the essentials; a custom LWR site requires a development team and long-term maintenance.
  • Reference data. Duplicate accounts or misattached cases become visible to your customers: we address data quality before go-live.
  • Content. A help center is only as good as its articles: keeping them up to date is a process to organize.
  • Adoption. A partner portal only gets used if it saves the partner time.

08Our approach

We apply our usual three phases to Experience Cloud.

  • Assess. We start from the calls and exchanges you want to reduce, then build the matrix of audiences, exposed objects and permissions. It leads to the choice of site template, the license families to validate with Salesforce, and the sharing model. If your org already exists, a Salesforce audit (in French) checks that its default access and data are ready to be opened up.
  • Build. We configure sharing and profiles first, then pages. Each user type is tested with a dedicated test account: we check what it sees and, above all, what it must not see, including in guest browsing.
  • Adopt. Your teams learn to create external accounts, publish content and articles, and evolve the site in Experience Builder without depending on us for every change.

The table below summarizes the mappings we use during scoping.

Use caseSite templateTypical external license (to validate)CRM data involved
Customer self-service supportCustomer ServiceCustomer Community; Customer Community Plus if reports or standard sharing are neededCases, Knowledge, community questions (Service Cloud)
Customer account spaceCustomer Account PortalCustomer Community or Customer Community Plus, depending on required accessAccount, contacts, invoices, knowledge base
Partner and distributor portalPartner CentralPartner Community, or Channel Account to count by partnerLeads, opportunities, campaigns (Sales Cloud)
Public help centerHelp CenterNo community license for guests reading articlesKnowledge articles
Custom experience, performance firstBuild Your Own (LWR)Depends on the audience; External Apps for an external stakeholder with limited CRM accessTo be defined; development in Lightning Web Components

If you want to know what Experience Cloud would change for you, we start with a Health Check of your org and your exchanges with the outside world.

Your portal

Planning a customer or partner portal?

Tell us who needs to log in and what they need to see. We tell you which site template, which licenses and which sharing model will hold up, and what needs to be decided before building.