The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Building Custom Objects and Permission Sets with the Salesforce Development Plugin for Claude Code (opens in a new tab)

You will learn how to set up the Salesforce Development Plugin in Claude Code, prepare an org with the metadata-experts and salesforce-api-context MCP Servers, and generate a Custom Object, Permission Sets and a Lightning page as metadata.

Why read this

You will also see why the older Salesforce DX MCP Server is being retired and why deployments should stay with humans.

  1. Create the DX project
  2. Build the Custom Object and fields
  3. Build the Permission Sets
  4. Build the Lightning page
  5. Package the metadata for a human to deploy
The main stages of building metadata with the plugin in the worked example

The article explains how the Salesforce Development Plugin for Claude Code differs from other tools with similar names. It groups Skills, the Salesforce CLI and hosted metadata servers into one toolset, while the Salesforce DX MCP Server reaches end-of-life on November 2, 2026, and Salesforce in Claude is aimed at end users rather than builders. The author lists the prerequisites: Node.js, Python, the Salesforce CLI and Claude Code, with a Claude plan that includes Claude Code. The org must have the MCP Servers page under Integrations and API Catalog used to enable the metadata-experts and salesforce-api-context MCP Servers.

The walkthrough then installs the plugin with the claude plugin install command and runs the setup command to check the org connection. The author builds a worked example, The General Store, using prompts that create a DX project, an Equipment Loan Custom Object with picklists, a lookup and a long text field, two Permission Sets, and a Lightning Record Page. He reviews the generated XML to confirm the read, create and edit permissions match the requirements.

The piece closes with advice on safety. It recommends building in a sandbox, Developer Edition org or Scratch Org, keeping deployments in human hands, and giving the agent specific field names and permissions because the model is trained on generic data.

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

Worth reading?

Builder Central turns a requirements prompt into a working Salesforce app (opens in a new tab)

You will learn how Builder Central plans and builds a Custom Object, List View and Permission Set from a plain-language prompt, what it leaves for the Admin to finish, and how it fits beside Lightning App Builder and Flow Builder.

  1. Describe the app in a prompt
  2. Review the project plan
  3. Build in a separate workspace
  4. Publish to the org
  5. Assign the Permission Set
The order in which Builder Central moved the Bulk Delivery Management app from prompt to live use

The author tested Builder Central, a beta conversational workspace for planning, building, previewing and deploying Salesforce apps and agents from plain language. He described a spreadsheet replacement app in one prompt, naming a Custom Object and its fields, and Builder Central first produced a project plan for review before building anything in its own separate workspace.

After the initial build it suggested extra customization, such as a List View, which he accepted. He published the app, asked Builder Central to assign the Permission Set to his user, and then opened the app from the App Launcher. The build took about 12 minutes in real time, though he sped up parts of the video.

The result was not complete: the record page did not show all fields, so he adjusted it in Lightning App Builder. He argues the change matters less for saving time than for shortening the loop between requirements meetings and a working prototype, while Admins still own permissions, automation, user experience and testing. He recommends trying it in a sandbox, recreating an existing app conversationally, and checking the beta limitations.

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

Worth reading?

How to enable and assign the Slackbot UI permission in Salesforce (opens in a new tab)

You will learn how to connect your Salesforce org to Slack and configure the Slackbot UI system permission so users can access the agent directly in Lightning Experience.

  1. Connect Salesforce org to Slack workspace
  2. Create a Permission Set for Slackbot
  3. Enable the Slackbot UI system permission
  4. Assign the Permission Set to users
The setup sequence for giving users access to Slackbot in Salesforce Lightning

The article outlines the configuration steps required to make Slackbot available inside Salesforce Lightning Experience. Before any user-facing features can be enabled, administrators must link their Salesforce org to a Slack workspace through the Manage Slack Connection setting and accept the pending request.

Access is controlled via a dedicated system permission called Slackbot UI. Administrators create a Custom Permission Set, navigate to System Permissions, check the box for the Slackbot UI capability, and save the changes. The Permission Set is then assigned to individual users or groups who require access.

Best practices emphasize validating the connection in a Sandbox first, using a dedicated Permission Set for easier auditing, and setting assignment expiration dates for pilot phases. The guide also notes that using Slackbot may require Flex Credits approval from a Salesforce administrator, and recommends verifying that the agent respects existing object and field-level security before full deployment.

Read the original at InfallibleTechie (opens in a new tab)

Worth reading?

Must-read

Salesforce delivers long-awaited Flow actions, List View permissions, and User history tracking (opens in a new tab)

Readers will learn how to configure mass Screen Flow actions in List View layouts, restrict List View sharing without granting broad permissions, and enable Field History Tracking on the User object.

Delivered IdeaExchange Features

  • Flow Quick Actions in List Views
  • Manage Shared List Views Permission
  • Inline Editing on List Views
  • Field History Tracking for Users
  • Restart Superbadge Progress
Five long-requested IdeaExchange ideas finally shipped in recent releases

The latest IdeaExchange updates highlight several features delivered in Winter ’27 and Summer ’26 that resolve long-standing administrative limitations. Administrators can now execute Screen Flow actions against multiple records selected in List View layouts or Related Lists by passing record identifiers into a text collection variable, eliminating the need for custom components or workarounds.

A new Manage Shared List Views permission replaces the broad Manage Public List Views requirement, allowing targeted sharing without exposing all public views across the organization. Winter ’27 also removes the restriction preventing inline editing in List Views containing multiple record types, though administrators must manually activate the setting in User Interface Settings and test it carefully due to varying Validation Rules and picklist values.

Field History Tracking is now available for the User object, monitoring up to twenty fields such as profile, role, and manager changes for eighteen months. The article also notes that Trailhead Superbadges can now be restarted after completion, supporting skill reinforcement rather than single-use certification, while additional roadmap items like dark mode and Opportunity restriction rules remain in development.

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

Worth reading?

Must-read

Automate temporary access management with Permission Set expiration dates (opens in a new tab)

You will learn how to configure automatic expiration dates on Permission Set assignments and manage them individually or in bulk.

Why read this

The piece outlines best practices for temporary access scenarios and highlights important considerations for compliance and user communication.

Old Method

  • Manually remove permissions later
  • Trust memory or calendar reminders
  • Use deprecated session-based activation

New Automation

  • Set expiration on Permission Set assignments
  • Choose fixed dates or relative day counts
  • Automatically lapse access for clean audits
Contrasting manual permission revocation with automatic expiration dates

Salesforce now allows administrators to set expiration dates directly on Permission Set assignments, eliminating the need for manual revocation of temporary access.

Administrators can configure expirations when adding individual assignments or use the Manage Assignment Expiration action in Setup for bulk updates. The system supports both fixed calendar dates and relative day counts for recurring temporary needs.

The feature benefits contractors, project teams, and compliance audits by ensuring access lapses automatically. The author warns that expiration happens silently, recommends automating recurring assignments with Flow, and notes that this model replaces the deprecated session-based activation approach.

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

Worth reading?