The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Evaluating customer portal architectures by measuring ongoing admin and release overhead (opens in a new tab)

Readers will learn how to evaluate platform versus off-platform portal architectures by comparing their impact on Sharing Rules, API limits, and release testing.

Why read this

The piece provides concrete questions to ask before kickoff so teams understand who owns security and maintenance after launch.

The article outlines three approaches to building customer portals: native Experience Cloud sites, custom off-platform applications using APIs, and third-party pre-built solutions. It argues that the choice should be driven by long-term administrative overhead rather than initial development speed.

Visibility and security behave differently across each path. Platform builds rely on Salesforce Sharing Sets, external roles, and guest user access rules, which can be bypassed by insecure Apex code. Off-platform and pre-built options delegate record filtering to application code or vendor settings, requiring careful control over the integration user permissions.

Ongoing costs diverge significantly after deployment. Native portals consume transaction limits and demand rigorous test coverage during quarterly releases, while external integrations draw heavily from the daily API request pool and must track API version retirements and authentication changes. The author recommends assigning dedicated integration users, requesting written call budgets, and verifying vendor certification timelines before go-live.

Read the original at Salesforce Time (opens in a new tab)

Worth reading?