Claude Code ignores admin SCIM plugin policies
An enterprise user highlighted a critical gap where marketplace plugin selection policies configured in the Claude Admin panel and mapped to SCIM groups do not sync or apply to Claude Code. This limitation breaks the centralized context administration model for organizations attempting broad, secure deployments of Claude across developer environments, as the CLI continues to rely on localized configuration controls instead of real-time organization policies.
Centralized enterprise security fails when local CLI clients operate as administrative silos. Without automatic SCIM group mapping to local terminal instances, developers are forced to rely on manual setups or MDM workarounds, which directly compromises policy compliance.
* Policy Sync Deficit: Claude Code uses local settings files (~/.claude/settings.json) and does not regularly check in with cloud-based SCIM admin policies.
* Workaround Overhead: Organizations must use MDM tools (like Jamf or Intune) to push managed-settings.json locally to developer machines or configure repo-level setups to control plugin access.
* Deployment Friction: The lack of automatic enforcement slows down enterprise-wide adoption as compliance teams cannot guarantee security bounds on plugins.
DISCOVERED
3h ago
2026-07-13
PUBLISHED
3h ago
2026-07-13
RELEVANCE
AUTHOR
dani_avila7