[DOCS] Managed settings docs omit `requiredMinimumVersion` and `requiredMaximumVersion`

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

minimumVersion in the available settings table, plus the managed-settings/admin guidance for version enforcement

Current Documentation

The settings page currently documents only a lower-bound version key:

| minimumVersion | Floor that prevents background auto-updates and claude update from installing a version below this one. Switching from the "latest" channel to "stable" via /config prompts you to stay on the current version or allow the downgrade. Choosing to stay sets this value. Also useful in managed settings to pin an organization-wide minimum | "2.1.100" |

The setup guide expands only that same floor behavior:

### Pin a minimum version The minimumVersion setting establishes a floor. Background auto-updates and claude update refuse to install any version below this value, so moving to the "stable" channel does not downgrade you if you are already on a newer "latest" build. In managed settings, this enforces an organization-wide minimum that user and project settings cannot override.

The admin setup matrix also exposes only that one version policy:

| Version floor | Prevent auto-update from installing below an org-wide minimum | minimumVersion |

No code.claude.com page currently documents requiredMinimumVersion or requiredMaximumVersion.

What's Wrong or Missing?

The v2.1.163 release adds requiredMinimumVersion and requiredMaximumVersion managed settings, but the live docs still describe only minimumVersion, which is an update floor rather than a startup gate.

A. The new managed-settings keys are undocumented

There is no settings reference entry describing the new keys, their accepted values, or which settings scopes honor them.

B. The startup-enforcement behavior is undocumented

The docs do not explain that Claude Code refuses to start when the installed version is outside the allowed range, or that the user is directed to an approved version. Without that distinction, admins only see minimumVersion and cannot tell when they should use an update floor versus a required version range.

Suggested Improvement

Add requiredMinimumVersion and requiredMaximumVersion to the settings reference with managed-settings scope, accepted version format, and a short behavior note.

Also update the setup/admin guidance to distinguish the two controls clearly:

• minimumVersion: blocks updates or downgrades below a floor
• requiredMinimumVersion / requiredMaximumVersion: block Claude Code from starting outside an approved version range

Include a managed-settings example such as:

{
"requiredMinimumVersion": "2.1.150",
"requiredMaximumVersion": "2.1.199"
}

Add one note describing the failure mode: when the installed version is outside the allowed range, Claude Code exits at startup and tells the user which approved version to install.

Impact

High - Prevents users from using a feature

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/settings | 226 | minimumVersion is documented, but no required-version keys are listed |
| https://code.claude.com/docs/en/setup | 222-237 | Setup explains only the version floor and managed minimum |
| https://code.claude.com/docs/en/admin-setup | 81 | Admin setup exposes only minimumVersion as the version policy control |
| https://code.claude.com/docs/en/server-managed-settings | 119-120 | This page sends admins to the settings reference for the full key list |

Total scope: 4 pages affected

Relevant release context: v2.1.163 adds managed version-range enforcement via requiredMinimumVersion and requiredMaximumVersion.