What problem does it solve? Governance requests in UiPath span three distinct layers — AOps product policies, Access ToolUsePolicies, and compliance standards — and the same English sentence often maps to more than one of them. This Skill classifies each request to the correct layer first, then authors, deploys, and troubleshoots the right policy artifact without mixing branches. ## Core Features & Use Cases - AOps product policies: Block, restrict, or enforce features in Studio, StudioX, Assistant, Robot, AI Trust Layer, and Agent Builder, then deploy to users, groups, or tenants with correct precedence handling. - Access ToolUsePolicies: Control which Actor Processes and identities (User/Group) may invoke child resources such as Agents, Maestro flows, RPA workflows, and APIs, with tag-based scoping and a two-phase Spec-to-JSON authoring flow. - Compliance standards (ISO 42001): Run posture analysis, apply full or scoped recommended settings, restore drifted configurations, and handle the preview-feature 403 gate. - Diagnostics: Debug policies not taking effect, deployment precedence issues (user > group > tenant), and blocked tool invocations using deployed-policy and access-policy evaluate commands. - Use Case: A user asks to "block ChatGPT for my finance team using Studio." The Skill detects the ambiguity, asks which layer should govern the rule, then authors and deploys the correct policy with a single confirmation gate. ## Quick Start Ask the assistant to block a model, restrict a feature, or check ISO 42001 compliance posture for your UiPath tenant, and it will classify the request and guide you through authoring the policy.
