The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

A four-bucket Kit of 100 prompts for Admin work with Agentforce Vibes (opens in a new tab)

You will learn how the Admin Accelerator Kit's four prompt buckets (Understanding, Configuring, Troubleshooting, Documenting) are meant to be used, and which prompts to run first in a sandbox.

Why read this

You will also see how the buckets chain together on a real change, such as converting a text field to a picklist.

  1. Understanding: map what the org already does
  2. Configuring: plan, then build the change
  3. Troubleshooting: diagnose what breaks
  4. Documenting: record the change and the why
The four prompt buckets are meant to be used in sequence on a single change

The post introduces a set of 100 ready-made prompts for everyday admin tasks, presented at a Dreamforce 2026 session on Agentforce Vibes. The prompts are hosted as a markdown file in the Admin Accelerator Kit on GitHub, and readers can simply browser-copy them. They are organized into four buckets of five categories with five prompts each, and placeholders in angle brackets must be replaced with real API names. The authors note the prompts also work with other agents connected to a Salesforce org through MCP.

The author advises starting in a sandbox or Developer Edition org, especially for Configuring prompts, because Understanding and Documenting prompts mostly read metadata while Configuring prompts change it. Understanding prompts help map objects, Flows, permissions and business processes, and impact-analysis prompts help check what breaks before a field change. Configuring prompts range from “How do I” questions that yield click paths to “Create” and “Write” prompts that generate Flow or Validation Rule metadata for review before deployment.

Troubleshooting prompts cover Flow errors and permission problems, with the advice to paste the full fault email along with record IDs and the affected user. The kit also addresses conflicting automations that silently revert field values. Documenting prompts produce data dictionaries, release notes, deployment checklists and, most importantly, a record of why a rule was configured as it was.

The post closes by showing the buckets chained together on a Region picklist change, and invites feedback and contributions to the kit’s repository.

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

Worth reading?

Writing clearer prompts for agents when you administer Salesforce (opens in a new tab)

You will learn eight writing principles for prompting an agent on admin work, and see a weak prompt rewritten into a strong one for a Validation Rule.

Why read this

The advice applies to any agent request you make.

Joshua Birk argues that prompting an agent is a writing skill rather than a form of engineering, and that admins can apply the communication habits they already have. He notes that a good prompt is usually three to six plain-language sentences that name the exact objects, fields and Flows by API name, explain the business reason, and state the output wanted and the guardrails. A one-line prompt tends to cost several rounds of clarification, while a few extra sentences up front save them.

The article then sets out eight lessons: know your audience, lead with the goal, be specific, give context and explain why, define the output format, show examples, use plain language, and set constraints. Each comes with an admin example, such as naming the team size so the agent pitches its answer correctly, or pasting an existing Validation Rule so the agent follows its naming pattern. Constraints such as working only in a sandbox or not touching active Flows are written into the prompt from the start.

To show the lessons together, Birk rewrites a vague request to create a close-reason Validation Rule into a detailed prompt covering the object, field, error message, naming convention, length limit and a no-deploy instruction. He closes by saying that one prompt rarely produces a finished solution, so admins should plan follow-up prompts, and he points to Trailhead modules and a GitHub kit of 100 admin prompts.

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

Worth reading?

Recommended

Builder Central lets admins build and edit in a virtual layer before touching the sandbox (opens in a new tab)

You will learn how Builder Central keeps proposed metadata changes out of your sandbox until you approve them, how it edits existing flows and apps, and what its new project-plan review step does.

Why read this

The piece is a podcast transcript, so the specifics are mostly the speakers' claims and a demo.

  1. Describe the idea in Builder Central
  2. Review the project plan before building
  3. Explore changes in the virtual environment
  4. Publish to the sandbox on your approval
How a Builder Central change reaches the sandbox, as described in the episode

Builder Central, now in beta, is a Salesforce tool that lets admins go from a description of an idea to a working solution on the platform without writing code. The podcast hosts describe it as the result of about two and a half years of internal work, built on the team’s headless and MCP efforts, and aimed at low-code builders. Early customers reported that tasks which took seven to ten days for several people now take one person two to three hours.

The central design point is that Builder Central works in a virtual environment rather than changing sandbox metadata while you build. Changes stay out of the org until you explicitly publish the project to the sandbox with a button or by asking the agent to do it. Visualizers show flows and other output as they would look in the org before anything is deployed, and the speakers say the team keeps adding them.

The tool also covers the maintenance work that makes up most of an admin’s job. Because it can read all the metadata in an org, it can refactor or test existing flows, and the hosts say it generated flow tests that a product manager judged to be good. A feature due around TDX will let users pull an existing app into a project and restyle it with a brand kit. A new step, rolling out that week, has the agent build a project plan for the user to review and approve before it starts building, and inline editing lets users select a single component to change.

The episode is promotional in tone and mostly anecdotal, so treat the productivity figures and comparisons with Claude Code as the speakers’ own account. The practical takeaway is the publish-on-approval workflow and the plan review step, which are the parts most relevant to governance and sandbox risk.

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

Worth reading?

Must-read

Salesforce Multi-Framework now supports Angular, microfrontends, and Managed Packages (opens in a new tab)

Readers will learn how to build, embed, and distribute Angular applications directly on the Salesforce Platform using the new Multi-Framework runtime.

Why read this

The article also covers secure cross-app communication, localization, and enterprise authentication requirements.

Multi-Framework runtime capabilities

  • Angular framework support
  • Microfrontend embedding
  • Managed packages
  • Localization and internationalization
  • Multi-factor authentication
  • Multi-Framework Insights
The Winter '27 release introduces key enhancements to the Multi-Framework runtime

Salesforce Multi-Framework is a framework-agnostic runtime that lets developers run modern web apps directly on the Salesforce Platform, inheriting Salesforce authentication, security and governance without a separate hosting stack or manual token handling. After React reached general availability, the Winter ’27 release adds Angular as a second GA framework, with internal, external and basic templates, deployment as a UIBundle metadata type, and the same Data SDK and security model that React apps use. Internal apps run on the Salesforce.app domain, which isolates them from the Lightning runtime and from each other, while platform rules for object-level security, field-level security, sharing and validation continue to apply to data requests and saves.

Microfrontend is now generally available, allowing externally hosted React or Angular apps to be embedded in Lightning Experience, Experience Cloud, the Salesforce mobile app and Mobile Publisher apps without rebuilding them in Lightning Web Components. The lightning-ui-embedding component hosts the app in a sandboxed iframe and provides a two-way channel: hosts pass properties down and embedded apps send custom events back. Managed packages can now distribute non-site, employee-facing Multi-Framework apps together with their supporting metadata such as Permission Sets, Apex and Custom Objects, though site-based apps are not supported. The release also adds locale-aware formatting and localized labels through the Platform SDK and Data SDK, enterprise multi-factor authentication managed by Salesforce, and Multi-Framework Insights in Beta for performance and usage reporting.

The article also describes three ways to build these apps: Agentforce Vibes, now with Angular support and generally available, for code-first development; Builder Central in Beta for natural-language app creation by admins; and Quick Pages in Beta, where business users describe a page in plain language and get a data-driven page that respects the viewer’s security. Salesforce says Vue is the next UI framework planned, along with agentic experiences and Government Cloud support.

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

Worth reading?

Using Agentforce Vibes Skills to inspect and configure your Salesforce org (opens in a new tab)

Readers will learn how to access the prebuilt Skills library in Agentforce Vibes and use them to inspect, modify, and deploy metadata changes through a plan and verify workflow.

Why read this

The guide demonstrates practical administration tasks like creating reports and Record-Triggered Flows without writing code.

The article introduces Agentforce Vibes as a browser-hosted Visual Studio Code instance configured specifically for Salesforce development and administration. Although it functions as a developer environment, the piece emphasizes its value for administrators by focusing on the Skills feature, which bundles instructions for distinct configuration actions into reusable packages.

Administrators can browse the preinstalled Skills library through the Toolkit menu after launching Vibes from Setup. The system automatically detects verbs in user prompts and maps them to the appropriate Skills, allowing the agent to execute tasks efficiently without manual selection. Users can also manually add new Skills to expand the toolkit over time.

Changes made through Vibes follow a strict plan, verify, and deploy sequence. Modifications are initially written to the virtualized local filesystem rather than directly to the connected org. Administrators review the generated change plan, approve it, and then trigger deployment using built-in commands or conversational prompts, with the agent handling connection tokens and API calls behind the scenes.

The author strongly recommends testing these workflows in trial environments such as Scratch Orgs, Developer Edition, or sandboxes. Example use cases include creating Custom Objects, adding fields, generating Permission Sets, running SOQL queries, and building Record-Triggered Flows. While early deployments may encounter errors or require multiple attempts, the structured approach provides a safe way to explore AI-assisted platform configuration.

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

Worth reading?