Document autoTier enterprise managed setting (#63411)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 0d308d88-df22-408e-9530-2ca5bdd91c62
Copilot-Session: 32650de5-7439-4c9e-96fa-82e814f92f09

Author: Strombon

content/copilot/how-tos/administer-copilot/manage-for-enterprise/use-managed-settings/override-settings-for-teams.md

@@ -14,11 +14,11 @@ category:
 
 With a server-managed deployment, you can configure your enterprise's `{% data variables.copilot.managed_setting_file %}` file to apply different governance settings to groups of users based on their enterprise team membership. The enterprise defines all settings in a central place, and team membership determines which users receive a given set of values. **If you haven't created the `{% data variables.copilot.managed_setting_file %}` file yet, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/use-managed-settings/get-started).**
 
-To make a key eligible for team overrides, you will mark it as `overridable` in `{% data variables.copilot.managed_setting_file %}`. An overridable key uses the team's value when set, or falls back to your enterprise default when the team leaves it unset.
+To let teams replace an enterprise default, mark the key as `overridable` in `{% data variables.copilot.managed_setting_file %}`. An overridable key uses the team's value when set, or falls back to your enterprise default when the team leaves it unset.
 
 ## Supported keys
 
-The `{ "overridable": <VALUE> }` syntax applies to the `model`, `permissions.disableBypassPermissionsMode`, `permissions.deny`, `permissions.ask`, `permissions.allow`, `allowedMcpServers`, `deniedMcpServers`, `extraKnownMarketplaces`, `strictKnownMarketplaces`, and `sandbox` keys.
+The `{ "overridable": <VALUE> }` syntax applies to the `model`, `autoTier`, `permissions.disableBypassPermissionsMode`, `permissions.deny`, `permissions.ask`, `permissions.allow`, `allowedMcpServers`, `deniedMcpServers`, `extraKnownMarketplaces`, `strictKnownMarketplaces`, and `sandbox` keys.
 
 `enabledPlugins` works additively. The enterprise `{% data variables.copilot.managed_setting_file %}` sets a baseline, and an enterprise team file can add more plugins on top of it.
 
@@ -64,7 +64,7 @@ You will use `copilot/{% data variables.copilot.team_mappings_file %}` and the `
     }
     ```
 
-1. Create the team settings file under `copilot/{% data variables.copilot.team_settings_directory %}`. You can include any keys you marked as overridable, plus the additive key `enabledPlugins`. Every other key stays governed by your enterprise default.
+1. Create the team settings file under `copilot/{% data variables.copilot.team_settings_directory %}`. You can include any keys you marked as overridable, more restrictive values for `autoTier`, plus the additive key `enabledPlugins`. Every other key stays governed by your enterprise default.
 
    ```json
    {

content/copilot/reference/enterprise-administrators/enterprise-managed-settings.md

@@ -25,6 +25,7 @@ For instructions on creating the file, see [AUTOTITLE](/copilot/how-tos/administ
 | `permissions.ask` | Requires a fresh human approval before specific operations can proceed | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} |
 | `permissions.allow` | Permits specific operations to proceed without a prompt | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} |
 | `model` | Sets your preferred model as the default for new conversations | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} |
+| `autoTier` | Sets the default Auto routing tier for new conversations | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} |
 | `enabledPlugins` | Enables or disables specific plugins by key | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
 | `extraKnownMarketplaces` | Adds plugin marketplaces that users can access | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
 | `strictKnownMarketplaces` | Restricts plugin installation to explicitly listed marketplaces | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} |
@@ -44,6 +45,7 @@ The following example shows these keys in one managed settings file.
 ```json
 {
   "model": "auto",
+  "autoTier": "intelligence",
   "permissions": {
     "disableBypassPermissionsMode": "disable",
     "deny": [
@@ -201,6 +203,23 @@ This key is overridable by enterprise team mapping. In your `{% data variables.c
 > [!NOTE]
 > `model` was originally documented as `permissions.model`. Clients still read the nested `permissions.model` value when the top-level `model` key is absent, but you should use the top-level `model` key in new configurations.
 
+## autoTier
+
+Sets the default routing tier for new conversations when the selected model is `"auto"`. Accepted values, from most restrictive to least restrictive, are `"efficiency"`, `"balance"`, `"intelligence"`, and `"unmanaged"`. This setting does not select the model itself.
+
+In {% data variables.copilot.copilot_cli_short %}, this setting requires version 1.0.87-0 or later. In {% data variables.product.prodname_vscode_shortname %}, it requires version 1.140.0 or later.
+
+Set `autoTier` to a string other than `"unmanaged"` to lock the tier against user and repository overrides. To provide a default that users, repositories, and enterprise teams can override, use `overridable`:
+
+```json
+{
+  "model": "auto",
+  "autoTier": { "overridable": "balance" }
+}
+```
+
+For example, a team settings file can set `"autoTier": "intelligence"`. If the team does not set `autoTier`, the enterprise default applies.
+
 ## permissions
 
 ### deny, ask, allow