Is Salesforce Data Secure in Slack? Permissions, Risks and What to Check
Is Salesforce data secure in Slack?
Yes, as long as your Salesforce permissions are set up correctly. Slack only shows information according to each user's existing Salesforce permissions, and Slackbot, Slack's AI assistant, works the same way. The main exception is shared record previews: when someone shares a record in a conversation, everyone there sees the details the sharer has access to.
Most of the risk sits in your own Salesforce setup, not in Slack or the AI. That means the fixes are in your hands, and most of them should happen before launch.
How do Salesforce permissions work in Slack?
When Slack is connected to Salesforce, permissions carry over. Each person's Slack account is matched to their Salesforce account, and Slack only shows information according to that person's permissions.
In practice:
- Records follow Salesforce access. A rep who can't see another region's accounts in Salesforce can't see them in Slack either.
- Shared record previews are the exception. When someone shares a record in a channel or direct message, everyone in that conversation sees the details the sharer has access to, as they were when it was shared. Admins can limit how much detail previews show.
- Changes are recorded in Salesforce. An update a person makes from Slack, including through Slackbot, is recorded under their name. Automated workflows may record changes under the account that set them up.
- Approvals are recorded on the record. When a manager approves a discount in Slack, the decision is saved on the Salesforce record.
- People without a Salesforce licence see conversations, not records. They can take part in channels but won't see Salesforce data through Slack.
What are the security risks of connecting Slack to Salesforce?
Each of the main risks has a clear fix.
People seeing records they shouldn't
Slack and Slackbot show whatever Salesforce allows. A record someone could technically open, but would never have gone looking for, is now one question away. Shared record previews also show everyone in the conversation the details the sharer has access to. Review Salesforce permissions before turning on the AI, especially sharing rules that were set up loosely years ago, and set how much detail record previews show.
Confident wrong answers from the AI
Slackbot treats Salesforce as correct, so stale contacts and duplicate accounts produce wrong answers delivered with confidence. In Validity's 2026 State of CRM Data report, 68% of respondents said a pipeline or performance number had been challenged because the data behind it was wrong. Clean up contacts and duplicates first, then keep records current with updates made from Slack.
Customer details reaching people outside the company
Slack lets you share channels with other companies, like a customer or a supplier. Salesforce record previews don't appear in those channels, and Salesforce channels can't include people from outside your company. Anything people type, paste or upload into a shared channel is still visible to everyone in it. Set rules on what goes into shared channels, and watch who's in any internal channel where reports are posted.
Knowing who changed what
Slackbot acts as the person asking, and approvals are saved on the record, so those changes have a clear owner in Salesforce's record history. Automated workflows may record changes under the account that set them up. Check which account each automation runs under, and turn on field history tracking for the fields that matter most.
Your data and the AI vendor
Slack says customer data isn't used to train its AI models. Your IT and privacy teams should still review Slack's terms before launch, along with any data residency requirements your company has.
What security features need a paid Slack plan?
Based on Slack's pricing page:
- Free: Salesforce permissions carry over, and messages with outside companies are limited to one-on-one.
- Pro: shared channels with up to 250 outside organizations.
- Business+: single sign-on (SAML) and automatic user setup (SCIM), so people are added and removed from Slack through your identity system.
- Enterprise+: data loss prevention, audit logs and enterprise search.
For most companies, single sign-on is the feature IT will ask about first, which makes Business+ the usual starting point for a company-wide rollout.
What should you check before connecting Slack to Salesforce?
- Salesforce permissions. Review who can see which accounts, opportunities and fields.
- Data quality. Merge duplicate accounts and update or remove stale contacts.
- Shared channel rules. Decide what can be posted in channels with outside companies.
- Record previews. Decide how much detail shared records show.
- Report rules. Decide which channels can have Salesforce reports posted in them.
- Slack's terms. Have IT and privacy review how Slack handles customer data.
- Sign-in. Decide whether you need single sign-on before rolling out beyond a pilot team.
Frequently asked questions
Can Slack users see Salesforce records they don't have access to?
No, with one exception. Slack only shows information according to each user's existing Salesforce permissions, but a shared record preview shows everyone in the conversation the details the sharer has access to.
Does Slack use customer data to train its AI?
Slack says customer data isn't used to train its AI models.
Who is recorded when a Salesforce record is changed from Slack?
The person who made the change. Slackbot acts as the person who asked, so its changes are recorded under that person's name. Automated workflows may record changes under the account that set them up.
Can people outside the company see Salesforce data in a shared channel?
Salesforce record previews don't appear in channels shared with other companies. Anything people type, paste or upload there is visible to everyone in the channel, so set rules on what goes into those channels.
Does a Slack user need a Salesforce licence?
Only to work with Salesforce records in Slack. People without one can still take part in conversations.
Get the full guide to Slack and Salesforce
This is the fourth post in our five-part series on Slack and Salesforce. Our free guide, 14 Things Slack Can Do for You Once It's Connected to Your Salesforce, covers 14 things Slack can do with Salesforce, how security and costs work, and what it takes to roll it out.
Download the free guide, or talk to our team about a Salesforce permissions review before you connect Slack.
Sources
- Salesforce, "Slack is the AI work platform for every Salesforce customer, ready on day one": https://www.salesforce.com/news/linked-content/slack-is-the-ai-work-platform-for-every-salesforce-customer-ready-on-day-one/
- Slack, "Pricing and plans": https://slack.com/pricing
- Slack, "Implementation guide: Salesforce in Slack": https://d34u8crftukxnk.cloudfront.net/slackpress/prod/sites/6/Implementation-Guide-Salesforce-in-Slack_V1.pdf
- Validity, "State of CRM Data Report 2026": https://www.validity.com/resource-center/state-of-crm-data-report-2026/
- Slack Help Center, "Security for Salesforce channels": https://slack.com/help/articles/32675871067283-Security-for-Salesforce-channels
What Copilotforce Means If Your Company Runs Salesforce and Microsoft 365
On November 17 at Microsoft Ignite, Salesforce and Microsoft announced a partnership called Copilotforce. It puts Salesforce data and sales tools inside Microsoft Copilot and Teams, and it connects Salesforce's data platform with Microsoft Fabric.
Read article →What Can Slack's AI Do With Your Salesforce Data?
Slack's AI can prepare account briefs, answer questions about your customers, build reports on request and update Salesforce records once you approve the change, all from inside Slack.
Read article →How to Roll Out Slack With Salesforce: Owners, Ground Rules and a Phased Plan
Start with one sales team. Connect the free Slack workspace to Salesforce, review your Salesforce permissions, and move a pilot team's internal conversations into Slack with the basics turned on. Add automation once you're on a paid plan, turn on Slackbot after the permissions review, and expand to the rest of the company based on what worked.
Read article →