Subscribe

UiPath Automation Ops

The UiPath Automation Ops Guide

About Policy Deployment

You can deploy policies at tenant, group, and user level for each product. Policies deployed at tenant level are applied to all the users in that tenant. For more granularity, you can apply different policies to specific groups or specific users. Deployments defined at user level override deployments at group level, which in turn override those at tenant level.

In addition to the custom policies you define in Automation Ops, two default deployment options are available for each product:

  • No Policy - Disables the enforcement of a governance policy from Automation Ops at the user, group, or tenant level.
  • Inherit - Inherits the governance policy from the higher level (user inherits from group and group inherits from tenant).

The policy that is applied for a product to a user is determined in the following order:

  1. When a policy is deployed at user level, the policy is applied to the user.
    • If a policy created in Automation Ops is selected, the policy overrides any policy deployed at group or tenant level.
    • If the No Policy option is selected, the product is not governed by Automation Ops for the user, overriding any policy deployed at group or tenant level.
    • If the Inherit option is selected, the policy defined at group level is applied. If one does not exist, the tenant-level policy is applied.
  2. When no policy deployment is defined at user level:
    • If the user is part of a group and a policy is deployed at group level, the group policy is applied to the user.
      • If a policy created in Automation Ops is selected, the policy overrides any policy deployed at tenant level.
      • If the No Policy option is selected, the product is not governed by Automation Ops for the user, overriding any policy deployed at tenant level.
      • If the Inherit option is selected, the policy defined at tenant level is applied.
    • If the user is part of multiple groups where a policy is deployed, the policy with the highest priority is applied to the user. When one or more custom policies are deployed, the policy with the lowest priority value takes precedence. When no custom policies are deployed at group level, any No Policy group deployment takes precedence over Inherit.
  3. When no policy deployment is defined at user or group level, the policy deployed at tenant level for the product is applied to the user.
    • If the No Policy option is selected, the product is not governed by Automation Ops for the user.
  4. For StudioX, Studio, and Studio Pro, when the product is not governed by Automation Ops (the No Policy option is applied to the user), the policy enforced using the file-based governance model is applied, if applicable.

📘

Note:

The policies deployed from Automation Ops are applied when the user signs in to their account from Studio or the Assistant, If the user is already signed in, the policies are applied when the user restarts the application.

When Studio is governed using Automation Ops, the policy name is displayed in the Help tab in Studio Backstage View. When hovering over the policy name, a tooltip is displayed that indicates Config source: Modern Governance.

Messages displayed in Studio windows that contain settings that are governed inform the user that functionality may be restricted by the company policy. For example, such a message appears in the Manage Sources tab in Studio Backstage View and in the Workflow Analyzer tab in the Project Settings window.

Updated 2 months ago


About Policy Deployment


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.