Set AI controls for a group
Last updated: October 26, 2026
Give one team different AI controls from the rest of the workspace, such as a model only the cinematics team may use.
Before you start
Groups and their AI controls are an Enterprise feature.
You need Manage workspace settings, which the Admin role has.
The group needs to exist. See Set a usage limit for a group to create one.
Steps
Open Settings, select Groups under People, and open the team's group.
Open the Model controls tab. It shows the models the group's members may use, and what each one inherits.
Type the model's name in Filter models. A model the workspace leaves off reads Inherits Off from the ... workspace.
Set it to On. The note changes to Replaces Off inherited from the ... workspace.
Select Save.
Result
Every member of the group gets the group's controls in every project, except where the workspace or a project locked a value. Anything left on Inherit follows the project and the workspace.
When a member is in several groups
Where a member's groups disagree, the more permissive setting wins: On beats Off, and a higher spend confirmation amount beats a lower one. A member in one group that turns a model off and another that turns it on can use it. For a model's default settings, groups that disagree cancel out and the project's or workspace's default applies.
A member's own controls take precedence over all their groups. See Set AI controls for one member.
What a group can set
A group's page splits its AI controls over two tabs:
Model controls: the kinds of generation and the models the group's members may use, whether models nobody has turned on by name can run, and where each model's generations start.
Agent controls: the Layer agent, its subagents and Spend confirmation. Set them the same way as models, then select Save on that tab. See Control the Layer agent and its spending.
Each tab saves on its own. Content tolerance and sharing belong to workspaces and projects, and groups cannot lock values.
Production tips
Grant with groups, restrict at the workspace. Because the most permissive group wins, groups work best for giving a team more than the workspace's baseline. To take something away from everyone, set it at the workspace, and lock it if no group may give it back.
Keep one group per team. The same group carries the team's role, its usage limit and its model and agent controls, on separate tabs of the group's page.
Check the result. Use Preview as a member on the Models or Agents page with someone from the group.
If something goes wrong
A control is greyed out with "Locked by the ... workspace". The workspace or a parent workspace locked it, and no group can change it.
A member of the group still cannot use a model. A project they work in locks it off, or the model's kind of generation is off. Check with Preview as a member.
A member has a model the group turns off. Another of their groups, or their own controls, turn it on.