Answer: By default, only the email addresses on the allowed_emails list can reach the Kiro Crew Webex bot; an empty allowed_emails list rejects everyone. Group spaces are off by default and require both webex.allow_group_rooms set to true and space IDs listed in webex.allowed_room_ids, with the sender still on the email allowlist. Status: Confirmed Entry: tool/kiro/permissions-and-security/webex-who-can-reach Revision: 3 Digest: sha256:639624e65f5db2fa (changes whenever the content changes) Timeline: Created: 2026-11-13T03:39:21Z Last changed: 2026-11-20T13:24:15Z (Group space sender requirement: — → the sender must still be on the email allowlist) Last verified: 2026-11-20T13:24:15Z Next check: 2026-11-21T13:24:15Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Default access policy | Deny-by-default | [1] | 2026-11-20 Allowed senders | add only your own email(s) | [1] | 2026-11-20 Group spaces setting | webex.allow_group_rooms | [1] | 2026-11-20 Allowed room IDs setting | webex.allowed_room_ids | [1] | 2026-11-20 Group space sender requirement | the sender must still be on the email allowlist | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Webex - Interfaces - Crew - Docs - Kiro". https://kiro.dev/docs/crew/interfaces/webex/ Role: primary. Accessed: 2026-11-20T13:24:15Z Quote: "Deny-by-default — an empty allowed_emails list rejects everyone." (Supports: Default access policy) Quote: "Anyone in an org can message a Webex bot, so add only your own email(s)." (Supports: Allowed senders) Quote: "Set webex.allow_group_rooms to true and list the space IDs in webex.allowed_room_ids ." (Supports: Group spaces setting, Allowed room IDs setting) Quote: "Both are required: turning the switch on alone grants nothing, and the sender must still be on the email allowlist." (Supports: Group space sender requirement) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 800d3dc40f75a213cc20a58c2c7b66699246130e7a60e49a4231e85513bbde2c (captured 2026-11-20T13:24:12Z) 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:24:15Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:24:15Z Last attempt: 2026-11-20T13:24:15Z Notes and limitations: Extracted automatically from a single official source (section "Who can reach it"). Related: https://latestn.com/tool/kiro/permissions-and-security/wechat-access-policy How do I configure the access policy for the WeChat interface in Kiro Crew? https://latestn.com/tool/kiro/permissions-and-security/wechat-risks What are the risks of enabling the WeChat interface in Kiro Crew? https://latestn.com/tool/kiro/pricing-and-limits/cloud-sessions-limitations What are the current limitations of Kiro cloud sessions? https://latestn.com/tool/kiro/permissions-and-security/trusted-commands-denylist How do I configure trusted commands and the command denylist in Kiro 0.x? https://latestn.com/tool/kiro/permissions-and-security/validate-hook-inputs How do I validate inputs in Kiro hooks for security? https://latestn.com/tool/kiro/permissions-and-security/vpc-iam-roles What IAM roles does Kiro need to connect cloud sessions to a VPC? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:24:15Z | changed | Group space sender requirement: — → the sender must still be on the email allowlist | [1] 2026-11-20T13:24:15Z | changed | Allowed room IDs setting: — → webex.allowed_room_ids | [1] 2026-11-20T13:24:15Z | changed | Group spaces setting: — → webex.allow_group_rooms | [1] 2026-11-20T13:24:15Z | changed | Allowed senders: — → add only your own email(s) | [1] 2026-11-20T13:24:15Z | changed | Default access policy: — → Deny-by-default | [1] 2026-11-20T13:24:15Z | changed | sender requirement for spaces: the sender must still be on the email allowlist → — | [1] 2026-11-20T13:24:15Z | changed | allowed room IDs setting: webex.allowed_room_ids → — | [1] 2026-11-20T13:24:15Z | changed | group spaces switch: webex.allow_group_rooms → — | [1] 2026-11-20T13:24:15Z | changed | allowlist setting: allowed_emails → — | [1] 2026-11-20T13:24:15Z | changed | default access rule: Deny-by-default → — | [1] 2026-11-17T13:46:07Z | changed | sender requirement for spaces: — → the sender must still be on the email allowlist | [1] 2026-11-17T13:46:07Z | changed | allowed room IDs setting: — → webex.allowed_room_ids | [1] 2026-11-17T13:46:07Z | changed | group spaces switch: — → webex.allow_group_rooms | [1] 2026-11-17T13:46:07Z | changed | allowlist setting: — → allowed_emails | [1] 2026-11-17T13:46:07Z | changed | default access rule: — → Deny-by-default | [1] 2026-11-17T13:46:07Z | changed | Recommendation: add only your own email(s) → — | [1] 2026-11-17T13:46:07Z | changed | Group spaces: the bot ignores group spaces (even from allowed users) → — | [1] 2026-11-17T13:46:07Z | changed | Allowed message type: Direct messages only → — | [1] 2026-11-17T13:46:07Z | changed | Empty allowed_emails behavior: an empty allowed_emails list rejects everyone → — | [1] 2026-11-17T13:46:07Z | changed | Default access policy: Deny-by-default → — | [1] 2026-11-13T03:39:21Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/webex-who-can-reach/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/webex-who-can-reach POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/webex-who-can-reach with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/webex-who-can-reach?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Who can reach the Kiro Crew Webex bot? Revision 3, last verified 2026-11-20T13:24:15Z. https://latestn.com/tool/kiro/permissions-and-security/webex-who-can-reach (accessed 2026-11-21T10:05:28Z). @misc{LatestN_tool_kiro_permissions_and_security_webex_who_can_reach_r3, title = {Who can reach the Kiro Crew Webex bot?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/webex-who-can-reach}}, note = {Revision 3; digest sha256:639624e65f5db2fa; last verified 2026-11-20T13:24:15Z; accessed 2026-11-21T10:05:28Z} } 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/webex-who-can-reach