For Client Portals

Client portals your customers actually want to log into

Build Experience Cloud sites that carry your brand, not the default look. Give customers a place to check status, submit requests, and self-serve without opening a ticket.

Explore Experience Cloud ComponentsRequest a Demo
40+
Experience Cloud components
Custom
branding built in
85+
across the suite
Northwind Portal
Home
Cases
Documents
Knowledge
RW
Welcome back, Rachel
Here is what is happening on your account
New request
3
Open cases
12
Documents
2
In review
Recent cases
View all
00012845
Invoice discrepancy on March order
Open
00012822
Request for updated contract terms
In progress
00012790
Onboarding for two new users
Resolved
What you build

Three portals, one component suite

CasesAccount
00012845
Open
00012822
In progress
00012790
Resolved

Customer portal

Let customers track cases, view records, and submit requests from a site that looks like yours.

DealsDocs
Account
Stage
Amount
United Oil & Gas
Proposal
$45K
Express Logistics
Review
$28K
Grand Hotels
Won
$61K

Partner hub

Give partners a shared space for deals, documents, and status without exposing your internal org.

Help center
Search for help
?
?
Start a guided request →

Self-service center

Pair knowledge and guided Flows so people solve their own problems instead of opening a ticket.

Add a Chat to your portal →
Where to build it

Three packages, one portal

For portals
The portal surface

Experience Cloud Components

40+ components for the portal itself: navigation, cards, lists, banners, and data views your customers see.

Learn more →
Guided processes

Flow Screen Components

Drop guided Flows into the portal so people complete requests step by step instead of hunting for fields.

Learn more →
Internal side

Dynamic Components

Build the record pages and consoles your team uses to service everything the portal sends in.

Learn more →
Make it yours

A portal that looks like your brand

The headline feature

Match your brand, down to the details

Colors, fonts, spacing, and layout follow your brand instead of the default Experience Cloud template. Customers see your site, not Salesforce's.

Themed components

Style every component with the same tokens so the whole portal stays consistent.

Your content, your way

Arrange records, lists, and knowledge into pages that fit how your customers think.

Responsive by default

Portals work on phones and desktops without a second build.

Why it works

Built on the platform your data already lives on

No sync, no copy

The portal reads and writes your real Salesforce records. There is no second system to keep in step.

Security reviewed

Every component passed the AppExchange security review, so sharing rules and permissions still apply.

One team maintains it

Admins configure the portal with the same tools they use for the rest of the org. No separate stack.

The portal your customers use and the console your team works in are built from the same suite.

From a client-facing team
Avonni has enabled our team to build solutions we could not have delivered otherwise. It is a true gem.
Craig Ashton-Chalmers
Linklaters
In a real org

A partner order desk, built on one Data Table.

Avonni Data Table on an Experience Cloud partner site: orders with an inline edited quantity, uploaded purchase order PDFs, delivery progress rings, status badges, filters and pagination
bottom
Experience Sites

Partner order desk

A distributor edits quantities, drops purchase orders and follows delivery on its own orders, from the partner site, with no Salesforce chrome in sight.

See the configuration
All use cases
FAQ

Questions about portals

How is licensing handled for Experience Sites?

Experience Sites are quoted separately. Portal and community licensing depends on your setup, so reach out and we will scope it with you.

Do the components work with external and customer users?

Yes. They run inside Experience Cloud and respect the sharing rules and permissions you already set for portal users.

Can the portal match our brand?

Colors, fonts, spacing, and layout follow your brand tokens, so the site reads as yours rather than a default template.

Is the data separate from our main org?

No. The portal reads and writes the same Salesforce records your internal team works on, with no sync or copy.

Do we need a developer to maintain it?

Admins configure and update the portal with clicks. A developer is optional, not a requirement.

Give customers a portal worth logging into

Start with the components, keep your data where it is, and ship a branded Experience Cloud site your customers will actually use.

Explore Experience Cloud ComponentsTalk to sales