Answer: Permission rules are defined in YAML files, with two scopes: workspace-scoped at ~/.kiro/workspace-roots//permissions.yaml (use deny to block dangerous operations) and user-scoped at ~/.kiro/settings/permissions.yaml (use allow to pre-approve trusted operations). Status: Confirmed Entry: tool/kiro/permissions-and-security/define-permission-rules Revision: 1 Digest: sha256:01f29460ca78d8e8 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:43:13Z Last changed: 2026-11-13T03:43:13Z Last verified: 2026-11-20T13:30:11Z Next check: 2026-11-21T13:30:11Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of format | YAML files | [1] | 2026-11-20 workspace-scoped path | ~/.kiro/workspace-roots//permissions.yaml | [1] | 2026-11-20 workspace-scoped effect | deny | [1] | 2026-11-20 user-scoped path | ~/.kiro/settings/permissions.yaml | [1] | 2026-11-20 user-scoped effect | allow | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Capability-based permissions - What's new in 1.0 - IDE 1.x - Docs - Kiro". https://kiro.dev/docs/ide/whats-new-v1/permissions/ Role: primary. Accessed: 2026-11-20T13:30:11Z Quote: "Permissions are defined in YAML files." (Supports: format) Quote: "Workspace-scoped ( ~/.kiro/workspace-roots//permissions.yaml , stored per-user outside the repository)" (Supports: workspace-scoped path) Quote: "use deny to block dangerous operations in a specific project" (Supports: workspace-scoped effect) Quote: "User-scoped ( ~/.kiro/settings/permissions.yaml )" (Supports: user-scoped path) Quote: "use allow to pre-approve trusted operations across all workspaces" (Supports: user-scoped effect) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 2580cad86f9cb63981b32faab107d2716fbb9997429f8383b97fb55dd7c06828 (captured 2026-11-20T13:30:11Z) 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:30:11Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:30:11Z Last attempt: 2026-11-20T13:30:11Z Notes and limitations: Extracted automatically from a single official source (section "Defining rules"). Related: 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/kiro/permissions-and-security/discord-allowlist How does the deny-by-default allowlist work for Kiro Crew on Discord? 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/configure-tool-access How do I configure which built-in tools Kiro can access? https://latestn.com/tool/kiro/permissions-and-security/create-trust-policy-iam-role How do I create a trust policy for an IAM role in Kiro? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:43:13Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/define-permission-rules/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/define-permission-rules POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/define-permission-rules with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/define-permission-rules?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I define permission rules in Kiro? Revision 1, last verified 2026-11-20T13:30:11Z. https://latestn.com/tool/kiro/permissions-and-security/define-permission-rules (accessed 2026-11-21T10:06:31Z). @misc{LatestN_tool_kiro_permissions_and_security_define_permission_rules_r1, title = {How do I define permission rules in Kiro?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/define-permission-rules}}, note = {Revision 1; digest sha256:01f29460ca78d8e8; last verified 2026-11-20T13:30:11Z; accessed 2026-11-21T10:06:31Z} } 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/define-permission-rules