The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Custom sharing reasons now roll out for standard objects alongside a setting to preserve manual shares (opens in a new tab)

You will learn how to use the new custom sharing reason feature on standard objects and configure the org-wide setting that keeps manual shares intact during record transfers.

Why read this

The article provides exact metadata and Apex examples so you can implement these changes immediately.

Keep Manual Shares

  • Available immediately in Sharing Settings
  • Keeps user manual shares after ownership changes
  • Best for teams relying on manual distribution

Custom Row Causes

  • Rolls out via Metadata API through October
  • Defines programmatic sharing reasons in code
  • Best for developers using Apex or Flow
Two new Salesforce sharing features help records keep access after owner changes

Salesforce is introducing two enhancements to the sharing model that eliminate long-standing workarounds for standard object access control. The first is an org-wide toggle called Keep Manual Shares when Transferring Records, which is available immediately in Sharing Settings. Enabling it ensures that manual shares survive ownership changes without requiring custom code or triggers.

The second enhancement rolls out through October and allows developers to define custom row causes on standard objects using the Metadata API. Previously, Apex managed sharing was restricted to Custom Objects. The update lets you declare a sharing reason like On Call Expert directly in the CustomObject metadata, then reference it in Apex share records or Flow actions. This separation keeps programmatic shares distinct from user manual shares and prevents automatic deletion when owners change.

The guidance recommends evaluating existing code that creates CaseShare, AccountShare, or similar records. Teams building shares via Apex or Flow should migrate to custom row causes to maintain auditability and stability. Those relying purely on manual distribution can simply enable the preservation setting. Both features arrive ahead of November updates that will bring management capabilities to Agentforce and Setup.

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

Worth reading?

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?

Use the account record to anchor identity, access, and onboarding in Experience Cloud (opens in a new tab)

You will learn how to structure Experience Cloud implementations around the account record to automate authentication routing, enforce consistent data access, and simplify multi-organization onboarding without additional deployments.

Introduces the challenge of scaling Experience Cloud portals for multiple independent organizations, each managing its own identity infrastructure and security standards. Relying on separate login paths and manual configurations quickly creates bottlenecks during onboarding.

Proposes using the account record as the central anchor for external user management. The user to contact to account relationship provides a stable context for storing identity provider preferences, authentication configurations, and onboarding status. This design keeps organization scoped policies centralized and easily retrievable.

Details the implementation steps, including configuring Login Discovery to route users based on account level settings instead of presenting multiple login buttons. Data access follows this same model by aligning lookup relationships with appropriate sharing mechanisms like Sharing Sets or standard Sharing Rules. These choices directly impact community license selection and must align with least privilege principles.

Concludes that treating onboarding as a configuration exercise rather than a deployment project allows administrators to bring new organizations online predictably. The approach reduces architectural complexity while maintaining secure, scalable access controls across the portal.

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

Worth reading?