Answer: The access policy maps to weixin.dm_policy, with the default being allowlist (only user IDs in weixin.allowed_user_ids). The default allowlist has an empty list, which authorizes nobody until you add an ID. Status: Confirmed Entry: tool/kiro/permissions-and-security/wechat-access-policy Revision: 3 Digest: sha256:a39eb5bcab72277f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:39:24Z Last changed: 2026-11-20T13:24:18Z (Allowed user IDs setting: — → weixin.allowed_user_ids) Last verified: 2026-11-20T13:24:18Z Next check: 2026-11-21T13:24:18Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Access policy setting | weixin.dm_policy | [1] | 2026-11-20 Default policy | allowlist (default) | [1] | 2026-11-20 Allowed user IDs setting | weixin.allowed_user_ids | [1] | 2026-11-20 Default state | allowlist with an empty list | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "WeChat (Weixin) - Interfaces - Crew - Docs - Kiro". https://kiro.dev/docs/crew/interfaces/wechat/ Role: primary. Accessed: 2026-11-20T13:24:18Z Quote: "Access policy Who can message the bot maps to weixin.dm_policy" (Supports: Access policy setting) Quote: "allowlist (default) Only user IDs in weixin.allowed_user_ids open" (Supports: Default policy) Quote: "Only user IDs in weixin.allowed_user_ids open" (Supports: Allowed user IDs setting) Quote: "The default is allowlist with an empty list, which authorizes nobody" (Supports: Default state) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: cdd0b17ea551c0c94e283df44a0bc5781c3e3cfed36ef37540dbbd75b1a6a78c (captured 2026-11-20T13:24:18Z) 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:18Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:24:18Z Last attempt: 2026-11-20T13:24:18Z Notes and limitations: Extracted automatically from a single official source (section "Access policy"). Related: 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/pricing-and-limits/compaction-limitations What are the limitations of compaction in Kiro? 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/kiro/permissions-and-security/webex-who-can-reach Who can reach the Kiro Crew Webex bot? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:24:18Z | changed | Allowed user IDs setting: — → weixin.allowed_user_ids | [1] 2026-11-20T13:24:18Z | changed | Access policy setting: — → weixin.dm_policy | [1] 2026-11-20T13:24:18Z | changed | Disabled policy: disabled → — | [1] 2026-11-20T13:24:18Z | changed | Open policy: open → — | [1] 2026-11-20T13:24:18Z | changed | Allowlist key: weixin.allowed_user_ids → — | [1] 2026-11-20T13:24:18Z | changed | Default policy: allowlist → allowlist (default) | [1] 2026-11-20T13:24:18Z | changed | Config key: weixin.dm_policy → — | [1] 2026-11-17T13:46:12Z | changed | Disabled policy: — → disabled | [1] 2026-11-17T13:46:12Z | changed | Open policy: — → open | [1] 2026-11-17T13:46:12Z | changed | Allowlist key: — → weixin.allowed_user_ids | [1] 2026-11-17T13:46:12Z | changed | Default policy: — → allowlist | [1] 2026-11-17T13:46:12Z | changed | Disabled behavior: All messages ignored → — | [1] 2026-11-17T13:46:12Z | changed | Open behavior: Anyone who messages the bot → — | [1] 2026-11-17T13:46:12Z | changed | Allowlist behavior: Only user IDs in weixin.allowed_user_ids → — | [1] 2026-11-17T13:46:12Z | changed | Default value: allowlist → — | [1] 2026-11-13T03:39:24Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/wechat-access-policy/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/wechat-access-policy POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/wechat-access-policy with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/wechat-access-policy?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure the access policy for the WeChat interface in Kiro Crew? Revision 3, last verified 2026-11-20T13:24:18Z. https://latestn.com/tool/kiro/permissions-and-security/wechat-access-policy (accessed 2026-11-21T10:06:49Z). @misc{LatestN_tool_kiro_permissions_and_security_wechat_access_policy_r3, title = {How do I configure the access policy for the WeChat interface in Kiro Crew?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/wechat-access-policy}}, note = {Revision 3; digest sha256:a39eb5bcab72277f; last verified 2026-11-20T13:24:18Z; accessed 2026-11-21T10:06:49Z} } 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/wechat-access-policy