{"version":"2.1.315","anchor":"policy-limits-attribution-to-the-signed-in-principal","canonical_anchor":"policy-limits-attribution-to-the-signed-in-principal","heading":"Organization limits are tied to the account that is signed in","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/policy-limits-attribution-to-the-signed-in-principal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Organization limits are tied to the account that is signed in\n\nClaude Code now records which account a policy limit decision belongs to and checks it again when the account changes\n\n**What**\n\nPolicy limits are restrictions an organization can place on Claude Code. When Claude Code works out whether a limit applies, it now records which signed-in account that decision belongs to. Before, it only recorded the token used.\n\nIf the signed-in account changes, Claude Code holds the old decision back or fetches a new one. It can also now see that a fixed sign-in credential has been replaced.\n\n**Why**\n\nThis stops a decision made for one account from being reused for a different account.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}