Today4 stories · 3 briefs

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 37The independent daily for Salesforce admins, developers and architects4 stories · 3 briefs

Must-readDevOps

Running a seven-stage agent-driven Salesforce lifecycle with the Headless Toolkit (opens in a new tab)

You will learn how to structure a Salesforce project around coding agents, using Skills, hosted MCP Servers and the Salesforce CLI across seven stages from grounding to observation.

Why read this

You will also see how to keep the agent's context lean and feed each mistake back into the project's instructions, checks and specs.

  1. Ground in business and org
  2. Specify what to build
  3. Build with the agent
  4. Verify with tests and checks
  5. Review with a reviewer agent
  6. Release through a human gate
  7. Observe and feed mistakes back
The seven stages of the agent-driven Salesforce lifecycle, each leaving an artifact for the next

This Salesforce Developers Blog post, written by Principal Developer Advocate Mohith Shrivastava, proposes an agent-driven development lifecycle built on the Headless Toolkit: the Salesforce Skills Library (sf-skills), Salesforce Hosted MCP Servers for org context, and the Salesforce CLI for testing and deploying. The author argues that coding agents drift from platform best practices and miss what already exists in an org, so a team should wrap them in its own project layer of skills, instructions, ontology, tools and checks. The linear project model becomes a loop in which each stage leaves an artifact for the next, and every mistake feeds back into the project. The author also stresses keeping the agent’s context lean, since accuracy falls as the context window fills, and notes that the agent’s built-in harness is the same for everyone while the project harness is what makes it effective on a specific org.

The seven stages run as follows. Ground gives the agent the org’s existing metadata through the read-only Metadata Grounding MCP Server (Beta), a feature map and an ontology of business terms. Specify has the agent produce a short, human-approved spec kept up to date alongside the code, recommended as spec-anchored and used only for features that span several metadata types or sessions. Build lets one agent work step by step, or subagents work in parallel in separate git worktrees, with each subagent given only the context it needs. Verify runs independent checks such as Apex tests, Code Analyzer, ApexGuru scans, LWC and accessibility checks, and hooks that run automatically. Review uses a separate, read-only adversarial reviewer agent whose findings humans judge. Release has the agent validate and promote changes through deterministic gates, with a human owning the production step. Observe has the agent read debug logs and traces to find production issues and start the next loop.

The post closes with a principle: each repeated mistake should become a constraint. Advisory instructions and skills reduce errors, but deterministic tests, Code Analyzer rules, hooks and quality gates catch them regardless of who wrote the code, and the author recommends choosing the strongest option available and cleaning up existing code that the agent might copy. The author presents this as one approach to adapt rather than the only way, and suggests installing the skills and starting with the stages that suit the team.

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

Worth reading?

RecommendedArchitecture

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?

Agentforce and AI

Salesforce Catalog gives AI assistants a live index of your org's metadata (opens in a new tab)

You will learn what Salesforce Catalog indexes, how it grounds AI answers and code generation in your org's real object and field names, and how an admin enables it and connects an AI assistant or the Data 360 MCP server.

Without Catalog

  • Agent guesses field names
  • Deploy fails on unused field
  • Engineer or Setup review needed

With Catalog

  • Agent searches the live index
  • Returns closest real matches
  • Answers only what user may see
Catalog lets an agent check the org's real names before it answers or writes code

Salesforce Catalog is an index of how an org is built, covering Objects, Fields, Flows, Apex, Permission Sets, users, and Data 360 components such as data streams, calculated insights and segments. It updates as teams deploy changes, so no separate documentation has to be written or maintained. An AI assistant or agent consults the Catalog before answering, and every question runs as the signed-in user, so answers are limited to what that user may see.

The article gives examples from a service operations manager tracing a CSAT figure back to its source, a data owner checking what depends on a field before changing it, and a developer who avoids using an unused field name. Catalog matches questions by meaning as well as by name, returns a short ranked list of candidates, and lets the agent read details only for those, which the article says keeps responses fast in large orgs and reduces failed deploys.

An admin enables Catalog in Data Cloud Setup and turns on the MCP Server, then connects an AI assistant such as Claude, ChatGPT or Cursor, or Agentforce Vibes, which comes preconfigured. Teams building their own agents can use the Data 360 MCP Server, and Agent Context Engine uses Catalog to supply context. The article notes that Catalog is available in every edition that supports Data 360 and points to a setup guide for steps and permissions.

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

Worth reading?

Releases

AgentExchange now lets partners sell apps and services in one private offer (opens in a new tab)

You will learn what AgentExchange Commerce now allows partners to bundle into a single private offer, and what changed for multi-year terms and renewals.

Why read this

It is most useful to ISV partners and the architects who advise them.

Before

  • Managed package sold alone
  • Services bought separately
  • Separate invoices

Now

  • Package, SaaS and services in one offer
  • Mixed one-time and recurring charges
  • One consolidated invoice
A private offer can now bundle the app, services and subscriptions that used to be bought separately

Partners can now bring a Managed Package, partner-hosted SaaS products and professional services together in one private offer on AgentExchange. The offer can combine one-time service charges with recurring software or support subscriptions in a single order. Licenses for the Managed Package are provisioned automatically and kept in sync with the order, and the buyer receives one consolidated invoice.

Two further capabilities are added. Eligible partners can offer 24- or 36-month agreements with annual invoicing, though multi-year terms need account-level enablement from a Salesforce Partner Account Manager. Renewals can start from a pre-populated offer based on an existing order, with automated billing and license reconciliation at the contract anniversary and advance renewal notifications whose cadence is configured through Flow Builder.

Buyers must opt in to private offers in their Salesforce org before they can receive and accept them. The post points to release notes and a partner marketing hub for further detail.

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

Worth reading?

In brief