Answer: Discord's control-plane surface is deny-by-default, even for the bot's owner; to interact with the bot from a Discord DM, the user must be in the allowlist, which is managed via config or the dashboard. Every allowlist add is SEL-audited, and the allowlist forces a per-user opt-in. Status: Confirmed Entry: tool/kiro/permissions-and-security/discord-allowlist Revision: 2 Digest: sha256:ca5cf12eccea63dd (changes whenever the content changes) Timeline: Created: 2026-11-13T03:39:11Z Last changed: 2026-11-20T13:23:59Z (Management method: config or the dashboard → Managed via config or the dashboard) Last verified: 2026-11-20T13:23:59Z Next check: 2026-11-21T13:23:59Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Default policy | deny-by-default | [1] | 2026-11-20 Requirement for DM interaction | the user must be in the allowlist | [1] | 2026-11-20 Management method | Managed via config or the dashboard | [1] | 2026-11-20 Audit | Every allowlist add is SEL-audited. | [1] | 2026-11-20 Rationale | The allowlist forces a per-user opt-in. | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Discord - Interfaces - Crew - Docs - Kiro". https://kiro.dev/docs/crew/interfaces/discord/ Role: primary. Accessed: 2026-11-20T13:23:59Z Quote: "Discord's control-plane surface is deny-by-default, even for the bot's owner." (Supports: Default policy) Quote: "To interact with the bot from a Discord DM, the user must be in the allowlist." (Supports: Requirement for DM interaction) Quote: "Managed via config or the dashboard" (Supports: Management method) Quote: "Every allowlist add is SEL-audited." (Supports: Audit) Quote: "The allowlist forces a per-user opt-in." (Supports: Rationale) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 4478bdb0f2d5216abc2d290eb93dc1974c56a474575c4fed1a8472fb3fbb55c9 (captured 2026-11-20T13:23:58Z) 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]. Cross-check: not-available at 2026-11-20T13:23:59Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:23:59Z Last attempt: 2026-11-20T13:23:59Z Notes and limitations: Extracted automatically from a single official source (section "Deny-by-default allowlist"). Related: https://latestn.com/tool/kiro/permissions-and-security/discord-tool-approval How do I approve tool use when Kiro Crew runs in Discord? https://latestn.com/tool/kiro/permissions-and-security/enable-and-use-sandbox How do I enable and configure the Kiro local command sandbox? https://latestn.com/tool/kiro/permissions-and-security/gateway-api-authentication How do I authenticate to the Kiro Crew Gateway API? https://latestn.com/tool/kiro/permissions-and-security/custom-agent-allowed-tools How do I restrict which tools a Kiro custom agent can use? https://latestn.com/tool/kiro/permissions-and-security/define-permission-rules How do I define permission rules in Kiro? https://latestn.com/tool/kiro/permissions-and-security/delegate-agent-approval How does the agent approval flow work in Kiro CLI delegate? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:23:59Z | changed | Management method: config or the dashboard → Managed via config or the dashboard | [1] 2026-11-13T03:39:11Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/discord-allowlist/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/kiro/permissions-and-security/discord-allowlist POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/discord-allowlist with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/discord-allowlist?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does the deny-by-default allowlist work for Kiro Crew on Discord? Revision 2, last verified 2026-11-20T13:23:59Z. https://latestn.com/tool/kiro/permissions-and-security/discord-allowlist (accessed 2026-11-21T10:07:29Z). @misc{LatestN_tool_kiro_permissions_and_security_discord_allowlist_r2, title = {How does the deny-by-default allowlist work for Kiro Crew on Discord?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/discord-allowlist}}, note = {Revision 2; digest sha256:ca5cf12eccea63dd; last verified 2026-11-20T13:23:59Z; accessed 2026-11-21T10:07:29Z} } 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/kiro/permissions-and-security/discord-allowlist