Slack Connect turns a Slack channel or DM into a shared space with people from other organisations, so every external connection is a trust decision about who can join, what they can see, which files and workflows cross the boundary, and whose retention rules apply. Slack's help centre describes channels that can host up to 250 organisations, each on a paid plan, plus one-to-one external DMs on any plan. This guide covers the customer-side controls Slack documents for Slack Connect: invitation and approval settings, per-organisation connection settings, file, canvas, list and workflow permissions, profile visibility and discoverability, data management, and the audit log actions that show what happened. It is for Slack owners and admins, security teams and data protection leads. Workspace-wide identity, admin roles and token hygiene are covered in the Slack Enterprise Security Guide; this page goes deeper on the external boundary only.
This is an independent guide from NHI Mgmt Group, based on Slack's public documentation as of November 2026. It is not sponsored or reviewed by Slack. Product features change, so confirm settings against Slack's current documentation.
Key takeaways
- Decide who can invite, and who approves: invitation types, approval rules and automatic acceptance are separate settings; set all three deliberately rather than leaving them to individual members.
- Tailor per partner: the Connections page lets you customise approvals, acceptance, file uploads, workflows and profile details for each external organisation.
- Retention is split by sender: your retention and editing rules cover only messages your members send; external content follows the other organisation's settings.
- Workflows and files cross the boundary: file uploads, canvases and lists are allowed for members by default, and workflow sharing has four separate permissions.
- The audit log tells the story: connect_dm_invite_* and external_shared_channel_* actions record every invitation, approval, connection and disconnection.
How Slack Connect works, and what your organisation controls
According to Slack's Slack Connect guide, your organisation owns any channel created in your workspace or Enterprise organisation. Only the owning organisation can invite or remove other organisations, manage posting permissions and keep using the channel after others are disconnected. Only the organisation that added an app can remove it from a channel. External conversations appear in the External Connections section of the sidebar with a banner, and external profile photos carry the other organisation's Slack icon.
| Element | Who controls it | Security implication |
|---|---|---|
| Channels your workspace created | Your organisation (owner) | You decide which organisations join and what permission they get |
| Channels another organisation owns | The other organisation, with your "Joining channels outside" setting deciding which of your members may accept | Your members can be in spaces governed by someone else's policies |
| Messages and files your members send | Your retention, editing, deletion and EKM settings | Your controls reach your content only |
| Messages and files external people send | Their organisation's settings | Their content may be kept longer or shorter than yours |
| Apps in a shared channel | The organisation that added the app | An app your members did not approve may read a shared channel; review channel membership including bots |
Slack offers two invitation types: Permission only to post and Permission to post, invite, and more. The narrower type keeps channel administration with your organisation and, per Slack's data management article, means only your organisation can set a custom retention policy for that channel.
Invitation, approval and acceptance settings
On Pro and Business+ these settings live under Admin > Workspace settings > Permissions > Slack Connect Channels. On Enterprise they live under Tools & settings > Organization settings > Slack Connect > Settings, with org-wide effect across workspaces. Slack's articles do not state defaults for these settings, so record the current value before you change anything.
| Setting (Slack's name) | What it controls | Recommended starting position |
|---|---|---|
| Sending channel invitations / Inviting people from outside | Each invitation type on or off, and which members may send it | Allow "Permission only to post" for a defined group; restrict "Permission to post, invite, and more" to channel managers |
| External people can invite | Who external people can invite, where the channel allows "post, invite, and more" | Limit to existing channel members or admins |
| Approvals | Who can approve, when approval is needed, where requests are sent | Require approval for new organisations; route to a named admin queue |
| Automatic acceptance | When invitations from other organisations are accepted automatically | Automatic only for established, customised partners |
| Joining channels outside [organisation] | Whether, and which, members may accept invitations to other organisations' channels | Enable for roles that work with partners, not everyone |
| Enabling Slack Connect in specific workspaces (Enterprise) | Which workspaces can use Slack Connect at all | Enable only in workspaces with a business need |
Invitation requests are reviewed under Tools & settings > Manage Slack Connect Invitations (Enterprise: Invitations), on the Open requests tab, with bulk approve or deny for up to 25 requests. On Pro and Business+ Workspace Owners and Admins approve; on Enterprise, Org Owners and Org Admins, who can delegate the task.
Per-organisation customisation
The Connections page (Directories > External > Manage connections on Pro and Business+, Slack Connect > Connections on Enterprise) lists connected and disconnected organisations with the number of shared channels and DMs. From the three dots beside an organisation you can choose Custom approval and acceptance settings, Customize for [organization name] for channel invitations, file uploads and profiles, or disconnect. Use this to build tiers:
- Core partners: long-term suppliers and customers under contract; automatic acceptance, file uploads on, standard profile details.
- Project partners: time-bound work; approval required, file uploads on, review at project end.
- Everyone else: approval required, post-only invitations, file uploads off, basic profile details.
Content controls: files, canvases, lists and workflows
Slack's file sharing article says members can upload files and share canvases and lists in Slack Connect channels and DMs by default, and owners and admins can change this. The settings are File uploads for Slack Connect, Canvases in Slack Connect and Lists in Slack Connect, set at workspace or org level; file uploads can also be set per external organisation under Connections, Universal, File uploads.
The setting Workflow usage for Slack Connect has four permissions, each worth deciding separately:
| Permission | Risk it manages | Typical choice |
|---|---|---|
| External people can use workflows created by your members | Partners triggering your automations | On for request intake workflows you designed for partners |
| External people can use workflows with third-party connector steps created by your members | Partner input flowing into connected SaaS systems under your credentials | Off unless each connector is reviewed |
| Your members can use workflows created by external people | Your members entering data into another organisation's automation | On with awareness training |
| Your members can use workflows with third-party connector steps created by external people | Your data reaching systems you do not control | Off by policy |
Slack documents fixed limits too: external people cannot start or continue workflows that need them to authenticate a third-party account, custom steps built by your members, keyword-triggered workflows, or workflows that create or archive channels or change user groups. External organisations must also be added to a workflow's "Who can find and use this workflow" setting.
Profiles, discoverability and Slack Connect DMs
- Member profiles: "Slack Connect Member Profiles" (Enterprise: "Member profiles") has two options. Basic details, the default, shows name and profile photo; Standard work details adds title, status, local time, pronouns and Do Not Disturb. Basic details limits what an outsider learns for pretexting. It can be set per organisation.
- Discoverability: "Slack Connect Discoverability" ("Anyone with their email address" or "No one"), or the Enterprise "External discoverability" toggle, controls whether people in other organisations can find your members by email address to start a DM. Members can also set their own preference.
- Unverified organisations: Slack notes admins can restrict unverified organisations from sending DM invitations to members. Turn this on to reduce unsolicited contact.
Slack Connect DMs are a phishing channel like email, with less filtering familiarity among staff. Teach members that the External Connections banner and organisation icon mark an outsider, that invitation links can be ignored, and how to report a suspicious DM. ATT&CK tracks this pattern as T1566.003 Spearphishing via Service. For the wider picture of chat-based phishing see the Collaboration Tool Security Guide.
Data management: retention, export, EKM and DLP
| Capability | How it applies in Slack Connect (per Slack's data management article) | What to do |
|---|---|---|
| Retention | Your settings apply to your members' messages and files; external content follows the other organisation's settings | Tell legal and records teams that shared channels hold mixed retention |
| Editing and deletion | Only the sending organisation can edit or delete a message | Plan takedown of mis-sent content through your own member or admin |
| Exports | Paid plans: public shared channels. Business+ and Enterprise: Workspace Owners and Org Owners can request private channels and external DMs. Exports omit a list of outside members and data from disconnected post-only channels | Keep your own record of partner membership |
| Enterprise Key Management | Applies to messages and files your members send | Include shared channels in key revocation runbooks |
| eDiscovery and DLP | On Enterprise plans, Org Owners can use eDiscovery and DLP tools on Slack Connect channel and DM content via the Discovery API; only your members' content can be edited or deleted through it | Point DLP rules at external conversations first |
Secrets pasted into a shared channel are disclosed to another organisation the moment they are sent. Scan shared channels for credentials and rotate anything found: the How to find secrets in chat messages guide covers the scanning approach.
Where identity fits: bots, tokens and external access
- Apps in shared channels: an app added by a partner sits in your shared channel under the partner's control. Review channel membership, including bots, when approving a connection.
- Your own bots: scope bot tokens to the channels they need and keep shared channels out of broad history scopes. See the Slack Tokens Security Guide and How to audit Slack apps, bots and tokens.
- Leavers on both sides: your SCIM deprovisioning removes your members; the partner's leavers depend on the partner. The external people dashboard (Business+ and Enterprise) lists every external person, their organisation and email, and lets you remove them from chosen channels or Disconnect them from everything your organisation hosts.
Detection and measurement
Stream the Audit Logs API (Enterprise) into your SIEM and alert on these actions:
| Audit log action | Why it matters |
|---|---|
| external_shared_channel_access_upgraded | An internal channel became a Slack Connect channel: check its history for sensitive content |
| external_shared_channel_invite_created / _approved / _accepted | New external access; match against an approved partner list |
| external_shared_channel_connected / _reconnected | A connection was made or restored after a disconnection |
| external_shared_channel_disconnected / _disconnect_and_archived | Offboarding evidence for a partner |
| connect_dm_invite_generated / _accepted | External DM contact, useful in phishing investigations |
| guest_created, guest_channel_join | Guest accounts, a separate route to external access, for completeness |
- Metric: percentage of connected organisations with customised per-partner settings.
- Metric: connected organisations with no shared channel activity in 90 days (candidates for disconnection).
- Metric: median time to approve or deny an invitation request.
- Metric: channels upgraded to Slack Connect per month, and the share reviewed for content before upgrade.
- Metric: secrets found in shared channels per quarter and time to rotate.
Rollout and review approach
- Baseline: export the Connections list and the external people dashboard; record current invitation, approval, file, workflow, profile and discoverability values.
- Policy: agree partner tiers with legal, procurement and data protection; map existing organisations to tiers.
- Pilot: apply the new approval and invitation settings in one workspace (Enterprise) or to a test group, and watch the invitation queue for a fortnight.
- Roll out: apply org-wide, then customise per organisation from the Connections page.
- Clean up: disconnect dormant organisations and remove external people who no longer need access.
- Monitor: turn on SIEM alerts for the actions above.
- Roll back: each setting is a toggle or menu choice; restore the recorded baseline value if business-critical partner work breaks, and fix it per organisation instead.
- Review: quarterly partner review alongside supplier reviews.
Small vs large organisations: a Pro or Business+ workspace has one Permissions tab and should concentrate on invitation types, approvals and file uploads. An Enterprise organisation should also restrict Slack Connect to specific workspaces, use per-organisation tiers, and feed audit logs and DLP.
Framework mapping
| Control area | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 | ISO/IEC 27001:2022 Annex A | ATT&CK |
|---|---|---|---|---|
| Approve and tier external organisations | GV.SC-07 | AC-20, AC-21 | A.5.19 | Not mapped |
| Limit who can invite and join | PR.AA-05 | AC-2 | A.5.15 | Not mapped |
| File, workflow and DLP controls | PR.DS-02 | AC-21 | A.5.14, A.8.12 | T1213.005 |
| Phishing via external DMs | DE.CM-03 | AU-6 | A.6.3 | T1566.003 |
Common failure patterns
- Upgrading an old internal channel: years of internal history become visible to the partner; create a new channel instead.
- Everyone can send "post, invite, and more": partners can then invite further outsiders into your channel.
- Assuming your retention covers partner messages: it covers only your members' content.
- Connector workflows left open: partner input runs through third-party steps under your organisation's authentication.
- No partner offboarding: contracts end but connections and external people remain.
- Standard profile details for every organisation: titles and status help a pretexting outsider.
Practitioner checklist
- Record current Slack Connect settings before changing them.
- Restrict "Permission to post, invite, and more" to channel managers.
- Require approval for new organisations and name the approvers.
- Limit "Joining channels outside" to roles that need it.
- Set file, canvas, list and workflow permissions, with connector workflows off by default.
- Use Basic details for profiles except trusted partners.
- Restrict DM invitations from unverified organisations.
- Scan shared channels for secrets and rotate findings.
- Alert on external_shared_channel_* and connect_dm_invite_* actions.
- Review connections and external people quarterly.
Standards and references
- Slack: Guide to managing Slack Connect in an Enterprise organization
- Slack: Manage Slack Connect channel invitation settings and permissions
- Slack: Manage Slack Connect channel approval settings and invitation requests
- Slack: How data management features apply to Slack Connect
- Slack: Manage file uploads, canvas sharing, and list sharing for Slack Connect
- Slack: Manage workflow usage in Slack Connect conversations
- Slack: Audit Logs API actions reference
- MITRE ATT&CK: Spearphishing via Service
Related NHI Mgmt Group resources: Slack Enterprise Security Guide · Slack Tokens Security Guide · How to audit Slack apps, bots and tokens · Collaboration Tool Security Guide