{"version":"2.1.300","anchor":"trusted-client-data-check-now-returns-a-principal-or-a-refus","canonical_anchor":"trusted-client-data-check-now-returns-a-principal-or-a-refus","heading":"Signed client configuration is now checked against your organisation","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/trusted-client-data-check-now-returns-a-principal-or-a-refus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Signed client configuration is now checked against your organisation\n\nA signed configuration document is now matched to your logged-in organisation and refused if the signing organisation differs\n\n**Unclear.** Whether a refused document because of an organisation mismatch makes Claude Code exit is not settled.\n\n**What**\n\nClaude Code can load a signed configuration document from an address given with `--client-data-url` or `CLAUDE_CODE_CLIENT_DATA_URL`, and exits if it cannot load it. The check of that signature now also identifies who it belongs to, by organisation, account and workspace, or gives a reason for refusing.\n\nWhen the document does not name an organisation, Claude Code compares the organisation that signed it with the one you are logged in to, and refuses it if they differ.\n\n**Why**\n\nA signed configuration is now tied to your organisation and account, so one signed for a different organisation is not accepted.\n\n- Area: Managed Settings\n- Names: `CLAUDE_CODE_CLIENT_DATA_URL`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}