- Get started
- Best practices
- Capabilities
- Skills
- CLI
- Examples
- Examples overview
- Recipe: build an agent
- Recipe: automate with RPA
- Recipe: enter data into a web app
- Recipe: extract data from a desktop app
- Recipe: refactor and test a workflow
- Recipe: a queue-based process with REFramework
- Recipe: build a Maestro Flow
- Recipe: build a Maestro Case
- Recipe: coded app and API workflow
- Recipe: build a coded function
- Recipe: verify a release with Test Manager
- Recipe: extract data from documents with IXP
- Advanced
- Help
Governance policies for authoring, deploying, and diagnosing product feature restrictions, tool-use permissions, and compliance posture across a UiPath tenant.
A coding agent can author and deploy governance policies across your UiPath tenant from a plain-language description of the rule you want enforced, then diagnose why a policy isn't taking effect.
What it does
Governance policies work on two layers, and the agent classifies your request into the right one before authoring anything:
- Product policies — block, restrict, or enforce specific features in Studio, StudioX, Assistant, Robot, AI Trust Layer, or Agent Builder. Deployed to a user, a group, or a whole tenant, with tenant-level settings overridden by group, and group by user.
- Access policies — allow or deny one workflow from invoking another as a tool, for example an agent calling a Maestro process, a Flow, an RPA workflow, an API workflow, or a case. Rules can be gated by tag, by caller, or by the acting user or group.
The agent can also check a tenant's compliance posture against a standard such as ISO 42001 or ISO 27001 and configure the recommended settings across products in one operation, always showing you the plan before applying anything.
Diagnosing policy behavior
Beyond authoring, the agent can investigate why a policy isn't taking effect, work through deployment precedence when user, group, and tenant settings conflict, and explain why a specific tool invocation was blocked.
The skill behind it
This work is powered by the uipath-governance skill, which authors, deploys, and diagnoses policies across both layers, and checks compliance posture against supported standards. You can see it in the Skills catalog.
A typical starting prompt
A first request might look like this:
"Block Agent Builder from using any model outside our approved list, for the whole tenant."
The agent classifies the request, shows you the policy it intends to create, and asks for confirmation before deploying it.
More prompts to try
- Deny any agent from invoking an RPA workflow tagged "finance-restricted" unless the caller is in the Finance Automation group.
- Why isn't the Studio policy I deployed to the Sales group taking effect for a specific user?
- Check our tenant's compliance posture against ISO 27001 and show me what's missing.
Go deeper
For the full picture of governance policies, see the Automation Ops governance documentation.