# Cannot connect to Slack **URL:** \ **Category:** Bug Reports\ **Tags:** slack, cloud-agents\ **Created:** [August 26, 2026, 4:10am UTC](https://forum.cursor.com/t/cannot-connect-to-slack/169504 "2026-08-26T04:10:02Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![hfjallemark](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/hfjallemark/32/116616_2.png) [@hfjallemark](https://forum.cursor.com/u/hfjallemark)\ **Post date:** [August 26, 2026, 4:10am UTC](https://forum.cursor.com/t/cannot-connect-to-slack/169504/1 "2026-08-26T04:10:02Z")
### Where does the bug appear (feature/product)? Cloud Agent (GitHub, Slack, Web, Linear) ### Describe the Bug Getting an error when trying to connect Cursor to Slack: > ### Cursor could not be installed. > > It looks like something has gone awry. Don’t worry it’s not your fault, but you won’t be able to install Cursor at the moment. > > **Error details** > > ```auto > Unapproved permissions requested > links:read, links:write > > ``` ### Steps to Reproduce Go to [https://cursor.com/dashboard/integrations](https://cursor.com/dashboard/integrations) and click **Connect** on Slack or go to your Slack admin portal [Cursor & Slack Integration | Slack Marketplace](https://YOUR-WORKSPACE.slack.com/marketplace/A08SKDT6QUW-cursor) and click **Add to Slack** ### Expected Behavior It should install Cursor Slack app. ### Screenshots / Screen Recordings ![Screenshot 2026-08-26 at 11.09.14.png](https://us1.discourse-cdn.com/cursor1/original/3X/4/a/4a9f891606e3f550e5bfa6ce2af10180f9078b97.png) ### Operating System MacOS ### Version Information Cursor Cloud ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![Iwark](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/iwark/32/118729_2.png) [@Iwark](https://forum.cursor.com/u/Iwark)\ **Post date:** [August 26, 2026, 4:54am UTC](https://forum.cursor.com/t/cannot-connect-to-slack/169504/5 "2026-08-26T04:54:05Z")
Same error here. Reproduced from [cursor.com/dashboard/integrations](https://cursor.com/dashboard/integrations) → Slack Connect. Slack rejects the install with: > Unapproved permissions requested: `links:read`, `links:write` This also blocks **new Slack MCP / Slack plugin auth** in the Cursor IDE. Existing Cursor Slack installs keep working (old token / old scope set). A workspace admin cannot add those two scopes from Slack — they are not on the installed Cursor app, there is no app-request to approve, and Marketplace only shows **Open in Slack** (no **Add to Slack** ). Looks like the same class of issue as [this May 2026 unapproved-scopes thread](https://forum.cursor.com/t/slack-mcp-oauth-requests-may-2026-scopes-but-slack-marks-them-unapproved-so-cursor-only-exposes-old-14-tools/165743): Cursor’s OAuth request includes scopes that are not yet approved on the published Cursor Slack app. Please add `links:read` and `links:write` to the published Cursor Slack app (A08SKDT6QUW) so new installs / reconnects can complete. - Cursor 3.17.19 (stable, macOS 26.5) - Slack workspace already has Cursor installed (Cloud Agents / `@cursor` still works) ---
**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\ **Post date:** [August 26, 2026, 7:22am UTC](https://forum.cursor.com/t/cannot-connect-to-slack/169504/8 "2026-08-26T07:22:38Z")
Hey @hfjallemark and thanks @Iwark for the extra detail. A recent change had the Cursor Slack app request two permissions that aren’t approved on our Slack Marketplace listing yet, so Slack blocks the install. We’ve let the team know and this is an issue we’re tracking. In the meantime: existing Slack connections keep working, so hold off on disconnecting or clearing your Slack tokens - reconnecting is the part that’s currently blocked. A Slack-admin approval won’t fix it either. I’ll post here as soon as new installs work again. ---
**Author:** ![ajkommit](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@ajkommit](https://forum.cursor.com/u/ajkommit)\ **Post date:** [August 26, 2026, 10:21am UTC](https://forum.cursor.com/t/cannot-connect-to-slack/169504/9 "2026-08-26T10:21:42Z")
so this is known issue, even from my side. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [August 26, 2026, 1:07pm UTC](https://forum.cursor.com/t/cannot-connect-to-slack/169504/14 "2026-08-26T13:07:54Z")
Quick update: new Slack installs are working again! If you were hitting the “Unapproved permissions requested” error, please retry — clicking **Connect** on the [cursor.com](http://cursor.com/) integrations page or **Add to Slack** from the Slack Marketplace should now complete normally. This also unblocks new Slack connections from the IDE. Thanks for the reports, and sorry for the disruption! ---
**Author:** ![chibadai](https://avatars.discourse-cdn.com/v4/letter/c/c5a1d2/32.png) [@chibadai](https://forum.cursor.com/u/chibadai)\ **Post date:** [September 13, 2026, 3:26am UTC](https://forum.cursor.com/t/cannot-connect-to-slack/169504/15 "2026-09-13T03:26:53Z")
Hi — I’m hitting a Slack connection failure that looks different from the “Unapproved permissions requested” issue in this thread. It may also be a broader web/dashboard problem, not Slack-specific. **What I’m trying to do** On a Cursor Automation, **Send to Slack** shows **Requires connection**. I click **Connect**. **What happens** I’m redirected to `https://cursor.com/dashboard/integrations`, and the page fails with a generic error (Japanese UI): > 何らかの問題が発生しました > 予期せぬエラーが発生しました。もう一度お試しください。 > (“Something went wrong / An unexpected error occurred. Please try again.”) I never reach Slack’s OAuth / permission consent screen, so this does not appear to be the `links:read, links:write` install rejection. **Additional context** Logging into **Cursor in the browser** (not only Integrations) shows the **same generic error page**. So Connect → Integrations may be failing because the web app / dashboard itself is erroring, rather than because Slack OAuth is rejecting scopes. **Notes** - Other tools on the same automation can connect; only **Send to Slack** stays on “Requires connection”. - The warning “One or more tools require additional authentication to be used” remains. - Retrying still shows the same crash. - I’m not attaching screenshots because the automation screen contains private workspace details. **Ask** Could you check whether the browser dashboard / integrations page is failing for some accounts, which would also block new Slack connections? Thanks. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 13, 2026, 7:49am UTC](https://forum.cursor.com/t/cannot-connect-to-slack/169504/16 "2026-09-13T07:49:20Z")
@chibadai Feel free to start a new thread.