Answer: By default the agent doesn't reply to people outside your workspace, such as Slack Connect guests; set `blockExternals: false` only if those people should be able to use the agent. To keep the conversation between the agent and the person who started it, set `respondTo: "author"`. Status: Confirmed Entry: tool/cursor/permissions-and-security/slack-control-who-can-message Revision: 1 Digest: sha256:ba297ac424680d83 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:08:39Z Last changed: 2026-11-13T03:08:39Z Last verified: 2026-11-20T12:33:15Z Next check: 2026-11-21T12:33:15Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Default external blocking | blockExternals | [1] | 2026-11-20 Allow externals setting | blockExternals: false | [1] | 2026-11-20 Restrict to thread author | respondTo: "author" | [1] | 2026-11-20 Policy example | policy: { blockExternals: false, respondTo: "author" } | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/agent-sdk/guides/slack.md". https://cursor.com/docs/agent-sdk/guides/slack.md Role: primary. Accessed: 2026-11-20T12:33:15Z Quote: "By default, the agent doesn't reply to people outside your workspace, such as Slack Connect guests. Set `blockExternals" (Supports: Default external blocking) Quote: "Set `blockExternals: false` only if those people should be able to use the agent." (Supports: Allow externals setting) Quote: "To keep the conversation between the agent and the person who started it, set `respondTo: "author"`." (Supports: Restrict to thread author) Quote: "policy: { blockExternals: false, respondTo: "author" }," (Supports: Policy example) Snapshot SHA-256: e41d022f06880bf0c38a9cfb12fa7ec0f43916a7aac309da62dcdfa6fe2d0245 (captured 2026-11-13T03:08:39Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:08:39Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:33:15Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:33:15Z Last attempt: 2026-11-20T12:33:15Z Notes and limitations: Extracted automatically from a single official source (section "Control who can message"). Related: https://latestn.com/tool/cursor/permissions-and-security/terminal-sandbox-blocks What does the Cursor terminal sandbox block? https://latestn.com/tool/cursor/permissions-and-security/verify-oidc-token How do I verify a Cursor Cloud Agent OIDC token? https://latestn.com/tool/cursor/permissions-and-security/verify-ssh-host-key How do I verify Cursor Origin's SSH host key fingerprints? https://latestn.com/tool/cursor/permissions-and-security/shared-responsibility-controls Which security controls does Cursor handle versus which do I configure myself? https://latestn.com/tool/cursor/permissions-and-security/shell-command-permissions How do I allow or deny shell commands in Cursor CLI using Shell permission tokens? https://latestn.com/tool/cursor/permissions-and-security/shell-mode-permissions-location Where are permissions configured for Cursor Shell Mode? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:08:39Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/permissions-and-security/slack-control-who-can-message/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/permissions-and-security/slack-control-who-can-message POST: https://latestn.com/dispute/tool/cursor/permissions-and-security/slack-control-who-can-message with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/permissions-and-security/slack-control-who-can-message?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I control which Slack users are allowed to message a Cursor Slack agent? Revision 1, last verified 2026-11-20T12:33:15Z. https://latestn.com/tool/cursor/permissions-and-security/slack-control-who-can-message (accessed 2026-11-21T10:07:23Z). @misc{LatestN_tool_cursor_permissions_and_security_slack_control_who_can_message_r1, title = {How do I control which Slack users are allowed to message a Cursor Slack agent?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/permissions-and-security/slack-control-who-can-message}}, note = {Revision 1; digest sha256:ba297ac424680d83; last verified 2026-11-20T12:33:15Z; accessed 2026-11-21T10:07:23Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/permissions-and-security/slack-control-who-can-message