I want to use Cursor to search through slack channels for things, do some analysis etc, but my IT/security folks are not going to give the ok to enable the Cursor Slack app. They say that with the permissions as-is today, Cursor would have access to DMs. Can anyone confirm if that is or is not the case today?
Hi Andrew — yes, the DM-related scopes (im:*, mpim:*) are part of the standard scope set our Slack app requests, and they’re required for normal functioning: that’s how Cursor DMs you status updates on your agent runs, sends the welcome/intro message, and lets you message @Cursor directly. They aren’t configurable today.
It’s worth noting that with a Slack bot token, those scopes only cover DMs the bot itself is part of (when you DM @Cursor or add it to a group DM). They don’t grant access to DMs between other users. This is standard Slack policy.
Hi Kevin, so just to confirm Cursor would not be able to read group DMs or DMs between other users, correct?
Hi @Andrew_Moyse Yes that’s correct! The permission is for Cursor to DM you with welcome messages, status updates, and periodic reminders, that type of thing. You might get a DM like “Hey, here are some cool ways to use Cursor” type of message. But Cursor does not have access to your DMs