# October 2026

> October 2026 release notes for Automation Ops in Automation Cloud and Test Cloud.

## October 6, 2026

### Studio and Studio Web governance policy toggle renamed to Allow Autopilot UI

The **Allow Autopilot** toggle in Studio and Studio Web governance policies is now **Allow Autopilot UI**. The new name clarifies that the toggle governs access to the Autopilot user interface specifically, to accurately reflect the permission it controls. For Studio policies, this affects the toggle available since the 24.10.0 policy template version, unchanged through 25.10.0.

For details, refer to [Settings for Studio policies](../user-guide/settings-for-studio-policies.md) and [Settings for Studio Web policies](../user-guide/settings-for-studio-web-policies.md).

**Correction:** This change was delivered on October 1, 2026.

## October 1, 2026

### Enforce your own guardrails organization-wide [Preview]

Your organization can now bring its own subscription to a supported safety vendor into the AI Trust Layer, and enforce that vendor's guardrails organization-wide through an AI Trust Layer policy, alongside the UiPath-managed guardrail types. Policies now list your own guardrails in the **Bring your own guardrails** section of the **Centralized guardrails** tab. Azure AI Language, Azure Content Safety, and Noma are the vendors supported during preview.

This means the safety checks your security team has already approved do not depend on each agent author remembering to add them. As a governance administrator, you decide centrally which of your own guardrails are mandatory, and whether each one covers every LLM call in the organization or only the products that need it.

For details, refer to [Settings for AI Trust Layer policies](../user-guide/settings-for-ai-trust-layer-policies.md#bring-your-own-guardrails).