Who this is for: Tenant administrators and organization owners who set product behavior for the people they manage.The Config page is where you set product behavior, such as session limits, which products members get, and telemetry, for the people you manage. To open it, go to Settings > Config in the admin portal. The same page appears at both the tenant and the organization level, with the same list of settings. For the settings themselves, see Available settings.
Video: Config essentials (2 min 23 s). Narrated with an AI-generated voice, with on-screen captions.
How settings are applied
Each setting is resolved through a chain of levels, and a value set at any level becomes the starting point for the levels below it:- The Anthropic default
- Your tenant
- Tenant-wide group settings
- The organization
- Organization group settings
Setting kinds
Each setting has a fixed kind, which decides how its values combine across the chain:- A simple value is replaced at each level, and the most specific level that set it wins. Most settings work this way, including lists of values such as network hosts, where a lower level’s list replaces the one above it.
- A restriction is a limit that each level below the tenant can tighten but not loosen from what the levels above it set. The tightest of those values takes effect, except that values set below a lock don’t apply. For example, if the tenant sets a session idle timeout of 30 minutes, an organization can set 15, but a value of 60 has no effect.
- A collection accumulates entries from each level. Connectors and plugins work this way.
- A product switch, such as Claude Desktop, turns a whole product on or off. Once an administrator turns the product off at any level that applies to a person, turning it on at a lower level has no effect.
Locks
A lock prevents levels below from changing a setting. To lock a setting on the tenant Config page or at either group level, expand it, choose Must use this value, and save. Levels below then see it marked Locked by your level and can’t change it. Any value a lower level had previously set is ignored while your lock is in place, and it comes back into effect if you later remove the lock. How far a lock reaches depends on where you set it:- On the tenant Config page, the lock reaches everyone in the tenant. The setting becomes read-only for every organization and at both group levels.
- On a tenant-wide group setting, the lock reaches the people that group’s settings apply to. They get the locked value even if their organization has set a different one, and organizations cannot set their own value for that group while the lock is in place. Other people in those organizations are not affected.
Group-specific settings
In addition to setting values for your whole tenant or organization, you can set values for the members of a directory group. A directory group is a group that your identity provider has pushed to Claude for Government over SCIM, as described on the Identity and access page. A group’s settings can be tenant-wide or scoped to one organization:- Tenant-wide group settings sit between the tenant and the organization in the chain. Tenant administrators manage these.
- Organization group settings apply only to people who are members of both the group and the organization. Organization owners manage these for their own organization.
The Organization instructions, Organization Analytics connector, and Analytics API settings can be set at the tenant and organization levels, but not at either group level. Settings that only a tenant administrator can set can’t be set for a group.
Turn a feature on for one group
How you give a feature to one group and nobody else depends on the setting:- A simple value, such as Code in Claude Desktop: turn the feature off on the organization’s Config page, then choose the group in the scope bar on that page and turn it on.
- A product switch that is off until a level turns it on, such as Claude Code: leave it unset for the tenant and the organization, and turn it on for the group. An off saved at the tenant or the organization takes priority over the group’s on, so reset it there first.
When someone belongs to more than one group
Only one group’s settings apply to any given person. When someone is a member of more than one group, the settings from their highest-priority group that has any configuration are used, and the other groups are ignored for that person. A group has configuration for a person once any setting is set or locked for it, either as a tenant-wide group setting or as an organization group setting in that person’s organization. When a higher-priority group gains configuration for someone, it takes the place of the lower-priority group that applied to them before, and the lower-priority group’s settings, including locked ones, stop applying to them. Removing a group’s last setting, changing the priority order, or changing someone’s group memberships in your identity provider can change which group applies to a person in the same way. A tenant administrator sets the priority order on the Identity and access page. It cannot be reordered at the organization level.What differs between the tenant and organization levels
Almost all settings can be set at either level, with these differences:- Some settings can be set only by a tenant administrator. Let organizations manage their own seat tiers and Compliance API appear on both pages, but are always read-only at the organization level.
- Tenant administrators can open any organization’s Config page and act on that organization’s behalf, as described under Config at the tenant level. Organization owners see only their own organization.
When changes take effect
Settings that govern the admin portal apply immediately. Settings that govern the Claude applications themselves are delivered to each member’s application the next time it refreshes its configuration. You do not need to push anything. Most changes take effect when the member restarts the application. Claude Desktop prompts for that restart, and requires it once the Restart deadline for configuration changes has passed. On Claude Desktop 2.2553.0 and later, a few settings take effect in a running application without a restart, such as the Claude Desktop banner. The Claude Code command-line tool applies its settings at startup and on an hourly poll. Changes to the session limits reach members as follows:- Session idle timeout: A shorter session idle timeout applies to new sign-ins immediately. Members who are already signed in move to it within the timeout period their session already had.
- Maximum session length: Raising or removing the maximum session length applies to new sign-ins only. Lowering the maximum session length, or setting one for the first time, also reaches members who are already signed in, taking up to one idle timeout period to do so.