When Notion AI reports that a Slack connection is missing, do not immediately disconnect the team’s connector. First determine whether the problem concerns workspace search, your own Slack sign-in, or approval for an action. The message alone does not prove that an OAuth token expired.
Record the exact message and what you asked Notion to do. A failed search and a refused request to post a message need different checks.
1. Identify the connection you actually need
The ordinary Slack integration handles features such as notifications and sending Slack messages into Notion. A working notification is not evidence that AI search has been connected.
Notion’s AI connector overview places connector management under Settings → Notion AI. Slack AI connectors require a Business or Enterprise workspace. The connector is installed for the workspace, not just for the person who originally installed it.
- Only you are affected: check your Notion workspace and Slack identity before touching shared settings.
- Several colleagues are affected: ask the workspace owner to inspect the shared connector and any recent app-policy changes.
- Search works, actions do not: check personal authorization and action approval separately.
Do not request a paid upgrade or a wider role solely from the wording of the error. Ask the owner to verify the existing arrangement first.
2. Restore personal authorization without removing the shared connector
Under the Slack-specific guide, Notion Agent can prompt you to connect your own Slack account. An administrator may also need to approve new permissions for actions. Complete the prompt with the intended Slack identity and workspace; keep Notion open during setup.
If the authorization screen names the wrong workspace, stop rather than grant access and fix it later. If the sign-in page fails to load, capture the error and try an approved browser session. Do not globally allow third-party cookies, disable security software or change organization sign-in policy as a blanket repair.
Slack’s app-request guide explains that updated scopes can require approval even when an app is already installed. Send the request to the responsible owner or app manager. They should inspect the proposed access and approve only an authorized use case, not weaken the workspace’s approval policy.
3. Reserve workspace reconnection for an owner-approved repair
Slack setup requires a Notion workspace owner and appropriate Slack-owner approval, in a Notion workspace with more than one member. Start a missing connector from Settings → Notion AI → + beside Slack, not from Slack.
Before replacing an existing connection, the owner should record the intended workspace and channel scope, notify affected users and check whether support recommends reconnection. A personal sign-in failure is not sufficient reason to remove everybody’s shared connection.
Disconnecting makes the connector’s Slack content unavailable to search. Initial indexing after setup can take up to 36 hours; new messages can take up to three hours, or longer with larger volumes. Do not repeatedly reconnect while waiting for indexing, or promise immediate restoration.
Keep the original approved scope. Connecting every channel or including future channels is a separate access decision, not a troubleshooting prerequisite. Do not lengthen token lifetimes to compensate for an unexplained failure.
4. Verify with a read-only request and inspect the source
In Notion AI chat, choose Slack under All sources. Ask about a known, permitted conversation and open the cited source. Agent actions can post as you, so do not use a message-sending request as a harmless connection test.
For example, ask it to find the decision in a specific thread that you can already open. Verify the answer against the original conversation. A plausible answer without the intended source is not a successful test, and one missing recent message is not proof of broken authorization.
If access still fails, send support the time, exact error, affected identities and workspaces, whether colleagues are affected, and whether search or actions fail. Include a non-sensitive example if possible. Never send access tokens, browser cookies or private channel exports as routine troubleshooting evidence.
Official documentation checked October 14, 2026. Actual permission approvals and reconnection must be handled by the authorized workspace administrators.