Set AI controls for a project

Last updated: October 26, 2026

Set what work in one project may use, for everyone who works in it, such as a stricter content tolerance or a model the project must not touch.

Before you start

  • Project AI controls are an Enterprise feature.

  • You need Edit content policy, which the Admin role has. Only a project's own workspace can set its controls.

Steps

  1. Open the project, select the settings gear beside its name, and scroll to the AI controls card.

  2. Under Models, type the name of the model the project must not use in Filter models.

  3. Set it to Off and select the lock at the end of its row, so no group or member in the project can turn it back on.

  4. Under Content tolerance, pick a level at or below the workspace's. Levels above it are unavailable in a project.

  5. Select Save.

Result

Every generation and agent run in the project uses the project's controls, whoever starts it. A value you leave on Inherit follows the workspace. A value you lock holds for every group and member working in the project; one you leave unlocked can still be changed for a group or a member.

What a project can set

  • Layer agent and Spend confirmation: whether the agent and its subagents run in the project, and when it asks before spending.

  • Models: which kinds of generation and models the project can use, and their default settings.

  • Content tolerance: stricter than the workspace's, never more permissive. Levels above the workspace's are unavailable (A project can only be stricter than its workspace).

Sharing is set per workspace, not per project. A project's input guardrails and output scoring rules are in the Content policy card of the same settings page; see Input guardrails and Set up scoring rules for a workspace or project.

Production tips

  • Use projects for client or title rules. A client's approved model list or a game's age rating belongs on its project, so it holds for everyone who joins, and nobody has to remember to apply it.

  • Lock what a client signed off on. Without a lock, a group or a member's own controls can turn a model back on inside the project.

  • Check from the workspace too. If the workspace locks a value, the project shows it read-only and cannot change it.

If something goes wrong

  • There is no AI controls card in the project's settings. Your role does not include Edit content policy, or the project belongs to another workspace.

  • The card asks you to upgrade. Project AI controls need Enterprise. The workspace's own controls work on every plan.

  • A content tolerance level cannot be selected. It is above the workspace's level. Lower the workspace's level, or keep the project at or below it.

  • A control is greyed out with "Locked by the ... workspace". The workspace or a parent workspace locked it.

Related