# Please align Slack integration docs with Marketplace scope list (User + Bot)

**URL:** <https://forum.cursor.com/t/please-align-slack-integration-docs-with-marketplace-scope-list-user-bot/173288>\
**Category:** Help\
**Tags:** docs, slack, security\
**Created:** [September 29, 2026, 7:17am UTC](https://forum.cursor.com/t/please-align-slack-integration-docs-with-marketplace-scope-list-user-bot/173288 "2026-09-29T07:17:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![T.H](https://avatars.discourse-cdn.com/v4/letter/t/b5e925/32.png) [@T.H](https://forum.cursor.com/u/T.H)\
**Post date:** [September 29, 2026, 7:17am UTC](https://forum.cursor.com/t/please-align-slack-integration-docs-with-marketplace-scope-list-user-bot/173288/1 "2026-09-29T07:17:56Z")

</div>

### Summary

Our security team uses the [Slack integration permissions docs](https://cursor.com/en-US/docs/integrations/slack#permissions) when approving the Cursor Slack app. That page only lists **18 bot scopes**. On the [Slack Marketplace](https://slack.com/marketplace/A08SKDT6QUW-cursor) → **Security & Compliance** tab, I also see **30 User Token Scopes** and **22 Bot Token Scopes** (including scopes not on the docs, e.g. `links:read` / `links:write` on the bot side).

Screenshot attached.

 ![file-8d0f95cadb2c64f256a799c45d8faa71](https://us1.discourse-cdn.com/cursor1/original/3X/e/0/e0859223c380d525046686da4f5772e19eb75c4a.png)

### Questions

1. **Documentation:** Could you update the Slack integration permissions section to include **both User and Bot token scopes** , with short descriptions (like the current bot table), so it matches what admins see on Marketplace?

2. **Sensitive scopes:** For scopes such as `search:read.private`, `app_configurations:read` / `write`, and `managed_apps:install` — what product features require them, and can any of them be disabled or limited per workspace?

Thanks.

---

<div class="post-metadata">

**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:** [September 29, 2026, 9:05am UTC](https://forum.cursor.com/t/please-align-slack-integration-docs-with-marketplace-scope-list-user-bot/173288/6 "2026-09-29T09:05:29Z")

</div>

Hey @T.H, the standard workspace install is bot-token only, and the user token scopes are only ever issued if an individual opts in (connecting the Slack MCP or setting up a custom bot). For the full per-scope purposes and exactly what can be limited for your workspace, since this is feeding a formal security review, the best path is to email [hi@cursor.com](mailto:hi@cursor.com). We’ll walk it through with you and point you to the right artifacts (SOC 2 and more) via the [Trust Center](https://trust.cursor.com/).

---

<div class="post-metadata">

**Author:** ![T.H](https://avatars.discourse-cdn.com/v4/letter/t/b5e925/32.png) [@T.H](https://forum.cursor.com/u/T.H)\
**Post date:** [September 29, 2026, 9:23am UTC](https://forum.cursor.com/t/please-align-slack-integration-docs-with-marketplace-scope-list-user-bot/173288/7 "2026-09-29T09:23:33Z")

</div>

Thanks @mohitjain — that helped.

I’d mixed this up with my own setup: I’m using Slack’s [slack-skills-plugin](https://github.com/slackapi/slack-skills-plugin) (Slack MCP) on my machine. The scope list I was worried about was from that personal plugin/MCP connection, not from our workspace’s standard Cursor Slack integration. Sorry for the noise.