Automation Ops policy settings that govern agents, covering tenant access, guardrails, model availability, and the design limits enforced at publish time.

This section explains how you can manage UiPath Agents in your organization using Automation Ops™ policies.

Two Automation Ops™ policies govern agents:

A policy takes effect in the tenants where it is deployed. For the full field-level reference, see Settings for AI Trust Layer Policies and Settings for Studio Web Policies in the Automation Ops user guide.

Access to Agents is controlled by the Enable Agents product toggle in the AI Trust Layer policy. The toggle is set to Yes by default.

Guardrails are configured at two levels: centrally for every agent in a tenant, or individually per agent in Studio Web. For the difference between the two levels, see Guardrails.

The Centralized guardrails tab of the AI Trust Layer policy defines the guardrails that apply to every agent of a covered type in the tenant. Detection settings are configured once per guardrail type and applied uniformly to every agent. For the configuration options of each type, see Centralized guardrails.

The Models tab of the AI Trust Layer policy controls which UiPath-managed models agents can call. Agents and coded agents each have their own product-level model controls. For example, a policy can restrict agents to Bring Your Own Model configurations, turn off a model provider, or lock agents to the currently selected model versions so that newly released models are not allowed automatically. For the full list of controls, see Models.

These controls apply to UiPath-managed models only. Models configured through a custom LLM configuration remain available regardless of how the Models tab is set.

The Model Regions tab restricts the geographic regions that LLM traffic is routed to, including the calls agents make. Routing follows the default region configuration unless it is set to Custom, in which case only the selected regions are used.

Beyond Enable Agents, the Product Toggles tab carries other toggles that change what agents can do. For example, disabling calls to third-party AI models blocks those calls for every product that uses them, including agents, and disabling Context Grounding causes agents that depend on it to fail. For the full list of toggles and their defaults, see Product Toggles.

The Design tab of the Studio Web policy sets limits that an agent must meet before it can be published. The limits are enforced in the agent builder in Studio Web. For example, a policy can require a minimum agent score, cap the temperature an agent can be configured with, or require the agent to define at least one Human In the Loop escalation.

These limits apply to new agents and to new versions of existing agents. An agent that is already published continues to run unchanged, but an updated version of it must meet the limits before it can be published again.

For the configuration options of each setting, see Design in the Automation Ops user guide.