{"version":"2.1.285","anchor":"allowedproviders-policy-enforced-on-login-and-setup-token","canonical_anchor":"allowedproviders-policy-enforced-on-login-and-setup-token","heading":"Admins can restrict sign-in providers with a new allowedProviders setting","tier":"use","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/allowedproviders-policy-enforced-on-login-and-setup-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Admins can restrict sign-in providers with a new allowedProviders setting\n\nA new `allowedProviders` managed setting can block `claude auth login` and `setup-token` when the policy disallows Anthropic's own sign-in\n\n**What**\n\nManaged settings are settings an administrator puts in place on a machine. They gain an `allowedProviders` key. When it does not permit the first-party provider, meaning signing in directly with Anthropic, these commands refuse to run:\n\n- `claude auth login`\n\n- `setup-token`, which creates a long-lived Claude.ai subscription token\n\nIf the value of `allowedProviders` is invalid, the settings check reports it and asks you to fix it.\n\n**Why**\n\nAdministrators get control over which sign-in providers can be used on a machine. If sign-in is refused, this policy may be why.\n\n- Area: Managed Settings\n- Names: `allowedProviders`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}