{"version":"2.1.311","anchor":"user-settings-permission-rules-read-with-warning-if-unloade","canonical_anchor":"user-settings-permission-rules-read-with-warning-if-unloade","heading":"Permission rules in your user settings are now included in another check","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/user-settings-permission-rules-read-with-warning-if-unloade","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Permission rules in your user settings are now included in another check\n\nA permission check that used only project and local settings now also reads your user settings, and warns if that file did not load\n\n**What**\n\nPermission rules are the allow and deny entries in your settings files that decide what Claude can do without asking you. One of the places in Claude Code that reads these rules used to look only at project settings and local settings. It now also reads your user settings, the settings that apply across all your projects.\n\nIf the user settings file fails to load, Claude Code logs a warning: \"The user settings file did not load, so none of its permission rules apply\".\n\n**Why**\n\nBefore, rules you had set in your user settings were ignored by this check. They now count, and if they cannot be loaded you get a warning instead of having them silently dropped.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}