{"version":"2.1.221","anchor":"org-spend-cap-limits-get-their-own-wording","canonical_anchor":"org-spend-cap-limits-get-their-own-wording","heading":"Org spend-cap limits get their own wording","tier":"notice","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/org-spend-cap-limits-get-their-own-wording","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Org spend-cap limits get their own wording\n\nHitting an org spend cap now shows its own message with links matched to your account type.\n\n**What**\n\nHitting an organization spend cap now reads differently from hitting a monthly usage limit, with links matched to the account type.\n\n**Details**\n\n- `org_spend_cap_reached` is handled separately from the generic \"org's monthly usage limit\" message\n- team and enterprise accounts get a spend-limit message pointing at \/usage-credits or claude.ai\/admin-settings\/usage\n\n**Evidence**\n\n`org_spend_cap_reached`\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}