docs: organization rollout guide for Claude Code managed settings#161
Draft
GuyMoses wants to merge 3 commits into
Draft
docs: organization rollout guide for Claude Code managed settings#161GuyMoses wants to merge 3 commits into
GuyMoses wants to merge 3 commits into
Conversation
Document how Team/Enterprise admins distribute and configure the plugin org-wide: auto-install via the Organization plugins page, push non-secret config through server-managed settings (or MDM/on-disk managed-settings.json), and keep the auth token in the per-user OS keychain rather than inlining it in plaintext policy. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
All contributors have signed the CLA ✍️ ✅ |
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds an Organization rollout (Team / Enterprise admins) section to the Claude Code plugin README covering how to distribute and configure the plugin org-wide with minimal per-developer work.
Why
Today the plugin requires manual per-user install + configuration. Claude Code's managed-settings mechanisms let admins automate both. This documents the paths.
Contents
enabledPluginsalone only enables).Admin Settings → Claude Code → Managed settings, withenabledPlugins+pluginConfigsexample. Notes plan/role requirements, hourly refresh, in-memory cache.managed-settings.jsonpaths per OS, plus the server-vs-endpoint non-merge precedence caveat./plugin → Configure), sincesensitivevalues are keychain-encrypted and never written tosettings.json. Advises against inlining the token into managedpluginConfigs.options/ theenvblock, which are plaintext at rest./status, session banner, data in Dash0.Status / open item
Draft. One behavior is not yet verified: whether Claude Code honors a
sensitivevalue delivered via managed settings, and if so how it's stored. An internal test plan exists to validate this before we ever recommend a centralized-token path; the README currently steers admins to the keychain regardless.