Slack Connector: Permissions and Data Handling
The Slack connector lets Enterpret Agent use connected Slack tools on your behalf, such as searching conversations, reading a thread, or sending a message when the tool and permissions allow it.
Each user authorizes their own Slack account. The connector uses that user's Slack token, subject to the granted scopes, Slack's access rules, your organization's controls, and the tools enabled for the session. A connection does not give Agent access to other users' private conversations.
This is separate from Slack feedback ingestion, asking Enterpret from Slack, and report delivery.
Connect your account
Use the Slack connector's connection flow in Enterpret and complete Slack authorization for the account and workspace you intend to use. Review the permissions shown on the actual consent screen. Your Slack administrator may need to approve the app or scopes.
Your teammates connect their own accounts independently. Authorizing your account does not authorize theirs. Slack access is also limited by the capabilities and scopes actually granted to your connection.
Permissions and their purpose
The current connector requests the user permissions below. Review the actual consent screen and connection status to confirm what your account has granted; a permission listed here does not mean every related action is available as a tool.
| Purpose | Scopes |
|---|---|
| Search public channels, private channels, direct messages, group direct messages, users, and files within your Slack access | search:read.public, search:read.private, search:read.im, search:read.mpim, search:read.users, search:read.files |
| Find conversations and read available history | channels:read, channels:history, groups:read, groups:history, im:read, im:history, mpim:read, mpim:history |
| Read files and canvases, and support file uploads | files:read, files:write, canvases:read |
| Resolve people, email addresses, and user groups | users:read, users:read.email, usergroups:read |
| Send messages, add or read reactions, and resolve emoji | chat:write, reactions:write, reactions:read, emoji:read |
Approvals before taking actions
Review the session's permission mode before asking Agent to act in Slack.
Ask: eligible connector calls can require approval, including reads as well as writes. You may be offered Approve once, Always allow, or Reject. A saved allowance can let a later matching call proceed without another prompt.
Auto: eligible calls can proceed without an individual approval prompt. Saved blocks and the connection's access restrictions still apply.
Do not assume every Slack message will pause for confirmation. Check the destination, proposed content, permission mode, and any saved allowances before delegating a posting task.
When Slack is accessed
Slack tools make requests using the connected account when they run. A configured automation may also use a connection when its tools and permissions allow it; connection and capability checks can run separately from an interactive conversation.
Connecting this connector does not configure continuous channel import into your feedback dataset. Use the inbound integration if you want to configure Slack channels as feedback sources.
Retrieved content and sharing
Slack content returned by tools can be included in the Agent session history and outputs. A personal connector does not make the resulting transcript private: people who can view a shared session can also see content retrieved into that session. Review the audience before sharing a session, copying an answer, or distributing an artifact.
Enterpret's published Privacy Policy states that Slack data is not used to train AI models. Refer to that policy and your organization's agreement for data-handling commitments, or contact Enterpret Support for questions about retention and deletion.
Disconnecting
Disconnect your personal Slack connection in Enterpret to stop Agent from using that connection. This is separate from disconnecting the organization-wide “Enterpret on Slack” workspace connection.
Disconnecting in Enterpret should not be treated as confirmation that Slack has immediately revoked the underlying authorization. If you need to revoke Slack-side access, use Slack's app-management controls or ask your Slack administrator. Disconnecting also does not remove Slack content already present in session history or shared outputs.