{"version":"2.1.261","anchor":"clearer-managed-settings-error-when-org-requires-cloud-gatew","canonical_anchor":"clearer-managed-settings-error-when-org-requires-cloud-gatew","heading":"Clearer managed-settings error when org requires Cloud gateway sign-in","tier":"notice","area":"Cloud Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/clearer-managed-settings-error-when-org-requires-cloud-gatew","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Clearer managed-settings error when org requires Cloud gateway sign-in\n\nA clearer error now tells you exactly how to fix a mismatched credential under gateway-mode org policy.\n\nWhen managed settings require first-party login but a non-OAuth credential is configured under an org policy specifically set to \"gateway\" mode, the validation error message is now more specific. It tells the user to remove the Anthropic-issued credential and sign in with `\/login`, or, if the provider is managed via `CLAUDE_CODE_USE_*`, notes that no sign-in is needed.\n\n- Area: Cloud Gateway\n- Names: `\/login`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}