The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Design a Salesforce security model around user personas (opens in a new tab)

You will learn how to map business personas to a User Field, a Custom Metadata Type, a Permission Set Group and Apex automation, so access stays consistent as features are added.

Why read this

The piece also explains when to use functional versus persona-based Permission Sets and why Profiles should be kept minimal.

  1. Persona set on User record
  2. Custom Metadata Type maps persona
  3. Permission Set Group for persona
  4. Permission Sets grant access
  5. Apex assigns access on save
How a persona assigns a user's access, from the User record through to Apex

The article argues that Salesforce security models often become a fragmented patchwork, and that features can fail on release because users lack the access they need. Its remedy is to build the security model around personas: groups of users who share a functional role and baseline access. The business defines which persona needs which access (create, read, edit, delete) for a feature, and IT implements that access consistently, so the same framework can serve later releases. Shared understanding between IT and the business is treated as essential to making this work.

The approach rests on five pieces. A persona picklist on the User record, whose edits are tightly restricted to administrators, stores each user’s persona. A Custom Metadata Type acts as a maintainable mapping table from each persona to its profile, role, public groups and Permission Set Group, and automation fails if a persona lacks a mapping record. Each persona gets one Permission Set Group, which has no access of its own, so changing a persona’s access means changing its Permission Sets. Those Permission Sets can be organized either by functional capability, which suits features spanning many objects such as Field Service, or by persona, which suits cases with few personas and complex functions, such as a Partner Relationship Management Experience Cloud site. Temporary cross-role duties are handled through an approved exception process, such as an ITSM workflow, while permanent combined roles should become new personas.

The article also recommends keeping profiles minimal: each user gets a custom “Minimum Access” profile, one per license type, with most permissions moved to Permission Sets, since profiles are still needed only for edge cases such as page layouts, login hours and IP ranges. Assignment is automated with Apex through the organization’s trigger framework, which the author prefers over Flows for consistent performance at scale. For teams not ready for the full design, the author suggests starting with Permission Set Groups for the personas a feature and its successors will need, assigned manually at first, and adding the persona field and automation later. The article frames this as a way to meet the Salesforce Well-Architected Framework’s goals of scalability and predictability.

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

Worth reading?

Recommended

Choosing between Record Types, Profiles and Permission Sets (opens in a new tab)

You will learn what each of Record Types, Profiles and Permission Sets is for, and how to decide which one fits a given requirement.

Why read this

The article also explains why Record Types are not a security control.

Record Type

  • Different business processes
  • Controls picklist values per process
  • Not a security control

Permission Set

  • Grants additional access
  • Assigned to selected users
  • Field and object permissions
Each tool solves a different problem, so match the requirement to the right one

This Salesforce Ben article helps admins decide between Record Types, Profiles and Permission Sets when a new requirement arrives. It explains that Record Types support different business processes for the same object, controlling available picklist values through Sales Processes and working with Page Layouts. It stresses that Record Types are not a security mechanism, since assigning one does not govern which records or fields a user can see or edit, and that restricting Record Types does not block access to existing records using other types.

Profiles, which every user has exactly one of, are described as the baseline for a user’s experience, covering login hours, IP ranges, password and session settings, default apps, default Record Types and Page Layouts. Permission Sets add access on top of that baseline, and a user can hold several of them; Permission Set Groups bundle commonly paired sets together. The article notes Permission Sets generally grant rather than remove access, and that a muting Permission Set inside a group only suppresses permissions from other sets in that same group, not those from the Profile or outside the group.

A decision table maps requirements to starting tools, and the article warns that one requirement may need several tools working together. It walks through worked examples: sales-process picklists suit Record Types, a handful of users needing a feature suits a Permission Set, and hiding fields from a Page Layout does not secure them, so field-level security is needed. It closes with five anti-patterns to avoid, including creating a Profile per department, using Record Types for security, duplicating Profiles in Permission Sets, ignoring Record Types in layout design, and letting Permission Sets sprawl, along with a set of questions to ask before configuring. The article also notes that Salesforce’s retirement of Profile-based permissions was cancelled in June 2026, while it still recommends a permission-set-led approach.

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

Worth reading?

Architecting Salesforce orgs for user adoption and phased rollouts (opens in a new tab)

You will learn how to embed adoption criteria into your design phase, optimize Lightning Record Pages and Validation Rules for primary personas, and structure phased rollouts to minimize friction.

The article argues that user adoption failures stem from early architectural choices rather than training gaps. It recommends establishing explicit adoption criteria during the design phase, including identifying primary personas for each object, limiting required fields to initial entry points, and ensuring critical actions require three clicks or fewer. The piece highlights the updated Salesforce Well-Architected Framework, which now emphasizes making design trade-offs visible and documenting their rationale.

To align system workflows with natural user behavior, the author suggests using Dynamic Forms with visibility rules to tailor Lightning Record Pages per role, applying stage-based Validation Rules instead of blanket requirements, and routing approvals without halting progress. Designs should be validated by having representative end users complete common tasks cold, treating any hesitation as a signal to adjust the architecture before configuration begins.

Post-launch success relies on built-in feedback loops and phased rollouts. The author advises capturing adoption signals through Field History Tracking, stage duration reports, and the Lightning Usage App, then shipping corresponding dashboards on day one. Rollouts should avoid big bang deployments by keeping phases independent, using Permission Set Groups for granular feature access, and restricting navigation tabs to only show active waves, thereby containing friction and enabling continuous improvement.

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

Worth reading?

Must-read

Configuring permissions and security guardrails for Agentforce and Prompt Builder (opens in a new tab)

Readers will learn how to structure Permission Sets and groups for different AI roles, understand how field-level security applies at runtime, and implement human-in-the-loop controls for autonomous agents.

Generative AI Security Setup

  • License and Permission Set Allocation
  • Field-Level Security Inheritance
  • Agentforce Action Boundaries
Breakdown of the three core pillars for AI governance

The article outlines a structured approach to managing generative AI access by separating feature availability through Permission Set Licenses from functional capabilities via Permission Sets and Permission Set Groups. It defines four core roles, including an AI System Administrator, Prompt Template Author, Standard End-User, and Agentforce Runtime User, emphasizing that bundling permissions into groups prevents security drift when users change departments.

When prompts execute on record pages, Prompt Builder enforces security before data reaches the large language model. The system validates object read access, applies field-level security by nullifying restricted merge fields, and respects Sharing Rules. A practical example shows how a customer support representative without access to a profit margin field receives a blank value, ensuring sensitive financial data never leaves the organization or enters the model cache.

For autonomous execution, Agentforce supports three action modes ranging from full autonomy to requiring explicit user approval. The piece recommends starting with safe defaults that allow read-only lookups while triggering human confirmation for write operations. It demonstrates a human-in-the-loop pattern where an agent drafts an email via a flow, leaving the final review and send capability restricted to a human user.

Finally, the guide provides a deployment checklist covering permission group assembly, field security verification, action boundary configuration, and Einstein Trust Layer settings like zero data retention and data masking to ensure compliance before production rollout.

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

Worth reading?