{"version":"2.1.300","anchor":"session-credential-and-managed-gateway-voucher-handling-chan","canonical_anchor":"session-credential-and-managed-gateway-voucher-handling-chan","heading":"Managed-settings gateway check now needs a voucher","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/session-credential-and-managed-gateway-voucher-handling-chan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Managed-settings gateway check now needs a voucher\n\nThe managed-settings gateway check now fails with a reason when no voucher comes back, and passes the voucher on when one does\n\n**What**\n\nWhen Claude Code verifies the gateway it gets managed settings through, it now looks for a voucher in the answer. Managed settings are settings your organization controls.\n\n- With no voucher, the check reports that it is not verified and gives a reason.\n\n- With a voucher, it passes the voucher on.\n\nBefore, any answer was accepted as it was. The error shown when an MCP server rejects a session credential now comes from a shared message source. MCP servers are outside tools connected to Claude Code.\n\n**Why**\n\nThis changes how Claude Code decides whether to trust the gateway that delivers managed settings.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}