Today4 stories · 1 brief

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 15The independent daily for Salesforce admins, developers and architects4 stories · 1 brief

Must-readReleases

Salesforce moves Trailblazer Community forums to Slack in November 2026 (opens in a new tab)

You will learn the exact timeline for the Trailblazer Community migration to Slack, how historical forum data will be preserved and indexed, and practical steps to prepare your account before the switch.

Existing Forums

  • Asynchronous replies taking time
  • Full forum threads remaining indexed
  • Structured questions and answers

New Slack Community

  • Real-time conversations and quicker interactions
  • Summarized accepted answers syncing back
  • Conversational discussions in channels
Comparison of the current Trailblazer Community forums versus the upcoming Slack workspace

Salesforce has announced that the online Trailblazer Community forums are moving to Slack, with the new experience becoming generally available in November 2026. The forums become read-only on October 30, 2026, so members can still browse and search existing posts but cannot publish new ones, and there is a gap before the Slack community opens during which new questions cannot be asked. The move is presented as a response to member requests for real-time conversation, easier peer connection and quicker access to trusted answers. The Slack version will be built around channels chosen during onboarding based on location, role, industry and products, a Slackbot to help find channels and Trailhead resources, and an Answers Agent AI that draws on trusted community knowledge. Joining is free, requires no paid Slack license, and uses an existing Trailblazer ID.

The historical forum archive is to remain accessible and searchable after October 30, so members need not export their saved threads. New answers in Slack will not be immediately visible to web searches. Accepted answers from product channels are to be anonymized, summarized and synced back to the website starting in early 2027. The author flags several gaps: answers posted before that rollout may not be indexed, only accepted product-channel answers will sync, full conversations will not be preserved, and contributors will receive less public credit. Local and specialist Trailblazer groups will not get their own Slack spaces by default. Instead, they will sit within regional hubs and global channels, group pages will stay on the separate group site, and new public channel requests will be reviewed by Salesforce.

The article gives practical advice for preparing: check which email address is linked to your Trailblazer ID and consider using a personal address, find out whether your employer blocks Slack and, if so, plan to use a personal device, and learn the basics via the Get Started in Slack trail on Trailhead. The author is cautious about whether the AI agent could reduce human participation and reputation-building, and notes that the FAQ leaves open questions such as whether the agent will use the forum archive, how reputation carries over, and what happens to the Forum Ambassador program. The author concludes that the success of the move depends on balancing Slack’s immediacy with the lasting, searchable value of forums, and encourages members to post outstanding questions before October 30 and to keep helping others once the new community launches.

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

Worth reading?

RecommendedAgentforce and AI

Six checks to vet agents and MCP tools before installing from AgentExchange (opens in a new tab)

Readers will learn a structured six-point checklist for evaluating the security, permissions and costs of agents and MCP tools before they reach production.

Why read this

The guide explains how to test these integrations safely and establish ongoing monitoring.

The article outlines the transition of AppExchange to AgentExchange, noting that the marketplace now hosts agents, subagents and MCP servers alongside traditional managed packages. It emphasizes that these newer components operate at runtime rather than just adding static metadata, which changes how administrators must assess their impact.

Authors provide a six-step verification process covering security review status, profile access limits, data flow mapping, agent user permissions, pricing structures using Flex Credits, and publisher reputation. They stress that passed security reviews set a baseline but do not guarantee safe runtime behavior.

The piece recommends a Sandbox evaluation workflow that includes testing under different user states, allowing only necessary MCP tools, enabling logging, and modeling costs at projected volumes. It concludes with operational rules such as enforcing least privilege, requiring weekly transcript reviews during pilots, and defining offboarding procedures before deployment.

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

Worth reading?

DevOps

Build a Claude Code mod to display Salesforce CLI org context (opens in a new tab)

You will learn how to create a Claude Code mod that reads Salesforce CLI configuration files to show your default org, its type, and Scratch Org expiry directly above the command prompt.

Why read this

The guide covers the required plugin structure, event hooks, and testing steps.

The article walks through creating a custom plugin for Claude Code that surfaces Salesforce CLI context directly in the terminal interface. It explains how to set up the plugin manifest, define reactive state types, and structure the directory for hooks and tests.

Instead of running slow CLI commands, the mod reads internal Salesforce authentication and configuration files to determine the target org alias, My Domain, org type, and Scratch Org expiration date. It also tracks which organizations are connected to configured Salesforce MCP servers.

The tutorial details several event hooks that trigger when sessions start, directories change, or tool calls execute. A render hook draws a colored status band above the prompt, using theme-aware colors to distinguish production, sandbox, and Scratch environments. The author includes validation and testing procedures, plus instructions for making the plugin load automatically across sessions.

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

Worth reading?

Agentforce and AI

Security researchers identify unauthenticated prompt injection paths in Agentforce (opens in a new tab)

Readers will understand how external inputs can bypass controls to reach Agentforce internal instructions, and why current governance models struggle to monitor these paths.

Researchers have identified a security vulnerability in Salesforce Agentforce where automated flows create unauthenticated pathways from external customer messages directly into internal program instructions. This occurs when services convert emails or web submissions into support records and pass them through chained integrations.

The primary challenge highlighted is a lack of visibility into these execution environments. External monitoring tools cannot easily inspect what happens inside the program boundaries, making it difficult to track risk profiles or detect unauthorized access attempts.

The article notes that similar exploitation tactics are part of the City-Forum data theft operation targeting enterprise platforms since March 2025. It also emphasizes that relying on written security policies without operational proof exposes organizations to significant regulatory fines under European Union artificial intelligence regulations.

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

Worth reading?

In brief