The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

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?

Recommended

How to invoke a Salesforce Screen Flow directly from a Slack workspace (opens in a new tab)

Readers will learn the exact steps to configure the Sales Cloud for Slack integration and route a Screen Flow into a Slack channel or direct message without leaving their messaging app.

The article outlines a method for running a Salesforce Screen Flow inside Slack by leveraging the Sales Cloud for Slack application. It begins with the prerequisite one-time connection between the Salesforce org and a Slack workspace, followed by assigning a Permission Set that includes system permissions for managing Slack app organization connections and user mappings.

Administrators must enable the Sales Cloud for Slack feature in Setup and install the corresponding app in their Slack directory. Once connected, creators can design a standard Screen Flow in Flow Builder and activate a hidden advanced setting labeled Make available in Slack during the save process.

To actually trigger the flow, a second autolaunched or Record-Triggered Flow acts as an invoker. This parent flow uses an action element to call the enabled Screen Flow, passing a Slack conversation identifier to determine whether the interactive button appears in a public channel or a private direct message. The piece concludes by noting that Salesforce automatically generates a background action for each enabled flow and advises clear button labeling for end users.

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

Worth reading?

Connecting Slack to Salesforce for record context and automated alerts (opens in a new tab)

Readers will learn how to use Guided Slack Setup to link a workspace, place the Slack component on record pages, and route Flow notifications to channels.

The article outlines the steps for linking a Slack workspace to a Salesforce org using the native Guided Slack Setup flow. Administrators verify the connection status, authenticate with Slack, and mark each configuration step as complete to maintain a clear rollout trail.

Once the connection is active, the Slack component can be added to Lightning Record Pages through App Builder. This places conversation history directly on layouts for objects like Accounts, allowing team members to view messages and reply without leaving the CRM while preserving record context.

The guide also demonstrates how to send automated alerts to Slack channels by configuring Flow Builder processes that trigger on stage changes or escalations. Users gain the ability to search for records and update fields from within Slack, with modifications syncing back to Salesforce in real time.

Rollout recommendations stress validating permissions with standard profiles, launching with a single object, enforcing consistent channel naming, and tracking adoption rates to optimize component placement and workflow design.

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

Worth reading?