Slack

A Slack connection saves new messages from selected channels as Threads in your Team workspace on Nowledge Cloud, so your team can find the original discussion later. Start with one channel that is safe to share, bind it to a shared Space, and send a new, non-sensitive message to check the result.

Before you connect

• Open your Team workspace on Nowledge Cloud in a browser. Sign in with your Nowledge account or email and password, with permission to manage that workspace's settings. Access-key sign-in cannot install Slack.
• Be allowed to install apps in the target Slack workspace. Ask a Slack administrator if your organization requires approval.
• Choose a channel whose content may be saved to Mem and a shared Space to receive it. Review both audiences: channel membership and Space membership can differ.

You do not need to configure MCP, run a bot yourself, or send Slack tokens to an AI.

Connect one channel and check the result

The App manages the connection. These are the outcomes to check; labels may vary by version.

1. Start the connection in Mem under Connectors → Chat Apps → Slack. On Slack's consent page, check the app, target workspace, and permissions below before allowing access.
2. Return to Mem to check the connection status, then invite the app into your chosen Slack channel. Installing the app alone does not synchronize every channel.
3. Send @Mem bind in the channel, then open Set up in Mem in the reply. A Mem administrator checks the workspace and channel, then selects an existing shared Space or creates one and binds it. Channels cannot bind to Personal, and new channels have no default binding.
4. Send a new, non-sensitive channel message and a test reply. In Mem, open Threads in the destination Space and check the channel source, original text, and sender. Top-level messages may be grouped by UTC day, while replies use the Slack thread anchor; they are not guaranteed to appear in the same imported Thread.

Connected does not prove synchronization. Finding the new message in the correct Space's Thread verifies that capture. You do not need to import the channel's entire history first.

To ask Mem a question, @ the app in the channel. The person asking may need to confirm their Slack-to-Mem identity through a private link and must have the required Space Read access. The installer's identity cannot authorize another person. Ordinary channel messages do not automatically trigger AI answers.

Why Slack asks for these permissions

The consent page is the authority for what this installation actually requests. The table describes the current hosted OAuth implementation. If the page differs, check the app and version with your administrator before approving.

See Slack's scope reference for permission definitions. Capture is restricted to joined, explicitly bound channels. OAuth permissions are broader than this product capture boundary and do not replace binding or Space access checks.

Update an existing installation

New permissions are not automatically granted to existing installations. An administrator should choose Reconnect Slack on the Slack connection page in Mem, review the original workspace and added permissions in Slack, and complete consent. Do not disconnect first: disconnecting clears channel bindings. If the expected permissions are absent, ask your administrator to confirm the app's permissions were updated rather than retrying repeatedly.

Even after consent, email display depends on server-side activation and the profile Slack returns. Missing scopes, unavailable profiles, and lookup failures preserve the Slack ID; the interface may show an available name, otherwise the stable ID. Existing messages are not automatically rewritten, and a new reply does not upgrade an older root message's attribution.

Sender details record who spoke; they do not enroll a Mem member or grant Space access. An email does not need a matching Mem account to be recorded as source information.

What is saved and who can read it

New human messages are captured only while the connection is active, the app is in the channel, and an administrator has explicitly bound that channel. Do not rely on bulk history backfill, bot-message import, edit or deletion propagation, or 📌 reaction saving as delivered hosted features.

Saved Threads follow the destination Space's permissions, not a copy of Slack's channel member list. Members who can read a shared Space may be outside the original private Slack channel. Removing someone from Slack does not revoke their Mem access. Administrators must manage access in both places. For Slack Connect channels, review the external-sharing warning and permission to retain content from other organizations before binding.

Direct messages are separate from channel bindings and do not enter that shared Space just because a channel is bound. Supported direct-message saving uses the linked member's Personal. This connection is not a backup of the entire Slack workspace.

Disconnect and troubleshoot

Disconnecting Slack in Mem clears that connection's credentials and channel bindings and stops future synchronization. Review bindings again after reconnecting. It does not delete previously saved Threads; manage those separately in Mem. Disconnecting in Mem does not mean the app was uninstalled from Slack. Remove the Slack app under your organization's policy to revoke that installation. Do not assume deleting a Slack message deletes its Mem copy.

When reporting an error, share only a redacted timestamp, error text, and failing stage. Never share tokens, authorization codes, or complete links containing credentials.

Next step

Review Space access before connecting more channels, so the people who can read captured content match your team's intent.