{"version":"2.1.312","anchor":"claude-in-slackteams-sessions-are-excluded-from-server-mana","canonical_anchor":"claude-in-slackteams-sessions-are-excluded-from-server-mana","heading":"Claude in Slack and Teams sessions skip server-managed settings","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/claude-in-slackteams-sessions-are-excluded-from-server-mana","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Claude in Slack and Teams sessions skip server-managed settings\n\nSessions run by Claude in Slack or Teams now skip server-managed settings, marked by a new `claude_tag` reason; policy limits are decided separately\n\n**What**\n\nServer-managed settings are settings an organisation sets centrally and Claude Code downloads from the server. A new `claude_tag` reason now marks sessions that do not use them. Claude Code's own message says: 'Claude in Slack and Claude in Teams sessions don't apply server-managed settings; organization policy limits are decided separately'.\n\n- When Claude Code decides whether to fetch these settings, it now answers no with reason `claude_tag` when three things hold: a surface check passes, a second check fails, and no stored claude.ai login is found. The login helper warns 'could not read the claude.ai login' when it cannot read the login.\n\n- The same `claude_tag` case was added to the list of reasons a session cannot use these settings and to the handling of login attempts, next to `sandboxed_entrypoint`.\n\n**Why**\n\nOrganisation admins should know that sessions run by Claude in Slack or Claude in Teams will not apply server-managed settings. Organisation policy limits for those sessions are decided separately.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no"}