Agents governance

Automation Ops policy settings that govern agents, covering tenant access, AI Trust Layer product toggles, 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:

• AI Trust Layer policy — Controls tenant-level access to Agents and the AI Trust Layer product toggles that affect agents.
• Studio Web policy — Controls the limits an agent must meet before it can be published.

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.

Enabling or disabling access to Agents

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.

1. Navigate to Automation Ops™ in your Automation Suite™ organization.
2. Create or edit a product policy for AI Trust Layer. For details, refer to Creating a governance policy.
3. On the Product Toggles tab, activate the Enable Agents option.
4. Save the policy.
5. Deploy the policy to any tenant where you want to build or run agents.

Important:

If you disable agents using the AI Trust Layer policy, users in the tenant where the policy is deployed are not able to access the Agents page in Automation Suite.

Beyond Enable Agents, the Product Toggles tab carries other toggles that change what agents can do. For example, disabling calls to AI models through AI Trust Layer blocks those calls for every product that uses them, including agents. For the full list of toggles and their defaults, see Product Toggles.

Agent design settings in the Studio Web policy

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.

Note:

If the policy sets a maximum number of tokens per agent response, the effective value can vary by model. The value shown in the agent builder follows either this policy or the model's maximum token limit.

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