{"version":"2.1.285","anchor":"login-failure-now-distinguishes-provider-not-allowed-from-or","canonical_anchor":"login-failure-now-distinguishes-provider-not-allowed-from-or","heading":"Login refused by sign-in provider now recorded apart from organization refusals","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/login-failure-now-distinguishes-provider-not-allowed-from-or","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Login refused by sign-in provider now recorded apart from organization refusals\n\nWhen login is refused because the sign-in provider is not allowed, Claude Code records that separately from refusals by the organization\n\n**Unclear.** It is not clear what causes a login to be refused with `provider_not_allowed`.\n\n**What**\n\nWhen a login is rejected, Claude Code records an analytics event. If the reason given is `provider_not_allowed`, it now records a separate event for that case. Every other refusal is still recorded as the organization not being allowed, as before. Before this change, every refusal was recorded as an organization refusal.\n\n**Why**\n\nA login blocked because of the sign-in provider is now counted separately from one blocked by organization rules.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}