The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Design the permission model before the screens in occupational health cases (opens in a new tab)

You will see how to split an occupational health case across objects so an employer sees fitness outcomes but never clinical detail.

Why read this

You will also see why governed picklists, data-driven thresholds and an external community help with privacy and audit.

Occupational health case

  • Case
  • Encounter
  • Exposure event
  • Restriction
  • Surveillance result
  • Employer account
A single case is split into separate objects so each role sees only its own slice

The article frames occupational health case management as a permission problem. Five roles touch each case, and the employer may learn whether a worker can lift or drive but not why. Spreadsheets and shared drives fail because they cannot enforce who sees what or show afterwards who looked.

The author argues against a single large record. The case should be split into objects for the encounter, exposure event, restriction, surveillance result, employer account and worker record, with a junction object where the employer of record differs from the work site. Restrictions carry start and end dates and a review owner, so expiry becomes a tracked state. Record types and field-level security then separate employer-visible outcomes from clinical detail.

Free text classification is treated as a privacy risk as well as a reporting problem, because a diagnosis typed into a notes field escapes every Sharing Rule. Governed picklists close that gap. Regulated rules such as blood lead level monitoring thresholds and testing frequency should live as records rather than code, so regulatory changes become configuration edits and reports draw on the same data as the rules. Correspondence is logged as case activity, and documents carry version history, classification and retention rules.

For employers and referring clinicians, the article recommends an external community rather than a hidden-field copy of the internal app, which also avoids consuming internal user licences. Migration is where legacy duplicates and inconsistent classifications surface, so it should be rehearsed in a full sandbox and validated against historical caseloads. The closing advice is to settle the permission model first, since it is the expensive part to retrofit.

Read the original at dev.to (opens in a new tab)

Worth reading?

Agentforce Coworker is switched on in some orgs, so check it before users ask (opens in a new tab)

The reader will learn what Agentforce Coworker does, how to find out whether it is already enabled in their org, and why sharing and permissions should be reviewed before rollout.

  1. Check whether Coworker is already on
  2. Review sharing and fix over-broad access
  3. Build a few focused agents
  4. Tell users what Coworker can do
A suggested order for rolling out Agentforce Coworker in an org

Agentforce Coworker is described as Salesforce’s AI assistant for employees, sitting in the search bar and routing user requests to specialist agents. Without well-built agents it can still answer questions from org data but can do little else. The article says it reached general availability at Dreamforce and that more than 185,000 people use it.

The article notes that from August 10, 2026, Salesforce automatically turned on Coworker for customers with unmetered user-based AI seats, which can be checked under Setup, Agentforce Coworker. HIPAA, health and life sciences, and government orgs were not auto-enabled, and Coworker is not covered by the HIPAA Business Associate Addendum. Pricing is said to depend on contract terms.

The main warning is that Coworker respects each user’s existing permissions and Sharing Rules, so it will surface any over-broad access quickly. The suggested rollout is to check the enablement setting, review sharing first, build a few focused agents for common requests such as renewal risk and case status, and tell users what the assistant can and cannot do.

Read the original at dev.to (opens in a new tab)

Worth reading?

Winter 27 release adds inline editing, sharing controls, email security, and report previews (opens in a new tab)

You will learn how to configure new Winter 27 capabilities that improve List View editing, preserve manual sharing during record transfers, streamline email domain verification, and enhance Lightning Reports and Dashboards.

The Salesforce Admins Blog has published a launchpad for the Winter ’27 release, which ships three times a year and is 600-plus pages of notes. The author urges admins to focus on the features that matter to their own org rather than reading everything. The post also explains that features move through pilot, beta and generally available (GA) stages, with beta features carrying limited support and best tested in a sandbox.

On the core platform, two new User Interface Settings let users inline-edit any field they can access, even if it is not on the page layout, and let List Views mix record types. Both are off by default. User field history tracking reaches GA, covering up to 20 fields on the User object and retaining history in the UI for 18 months. The standard Follow button can also be shown in the Dynamic Highlights Panel. For sharing, a setting now keeps manual shares when a record’s owner changes, and a forward-looking note says custom row causes for standard objects are targeted for October 10 through the Metadata API.

The security and email section covers a consolidated User Email Domains page in Setup, which shows verified and unverified address counts per domain. Admins can copy verified authorized domains from production into a new sandbox with one click, and set verification to Always, For Updated Addresses Only, or Never for each domain. Secondary sender addresses let sensitive emails route through Salesforce’s own Mail Transfer Agent. Experience Cloud Trusted URLs can now take individual Chrome extension IDs, with wildcards unsupported.

The Reports, Dashboards and Flow sections are the longest. Beta features include record previews in Lightning Reports, a Common Rows Only option for joined reports, and Lightning Reports and Dashboards embedded in LWR Experience Cloud sites. Flow Builder adds version Edit History with restore, element grouping, an Unused resource filter, Agent Action details in the canvas, and a User Context run option for flows using API version 68.0 or later. It also brings auto-generated element labels, persistent end elements, and save-time warnings for missing required fields and field length. Flows can now retry on record lock errors, Screen Flows can run as mass actions from List Views and Related Lists, and a native Time component is available. Beta Test Mode and mock outputs for Action and Subflow elements round out the testing tools.

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

Worth reading?