Define Governance Policies

You can define one or more policies for each profile. You can then deploy them per tenant for each type of license, per group, or per user. For example, you can create and deploy separate StudioX policies for the users that have a Citizen Developer license and those with an RPA Developer Pro license.

Automation Ops™ is flexible and easy to use, enabling you to quickly govern large deployments:

Select the policy templates to use depending on the product versions installed in your organization (not applicable to Studio Web).
Create policies for the products you want to govern.

If your organization is already using the file-based governance model for Studio, you can migrate your policies by generating files from Studio and uploading them in Automation Ops™.
Deploy policies at tenant, group, or user level, and any combination thereof.

Select a Policy Template

Product settings can differ from one version to another and different policy templates are available for different versions. To ensure the settings in your policies match those available in the governed products, configure Automation Ops™ to use the policy template for the product version used in your organization. When a new product version is installed, check if a new policy template version is available and update to it to make sure the policies include all the product settings that can be governed in that version. Previous versions of Studio, though they will receive the policy containing the latest rules, will disregard these rules.

When no template exists in Automation Ops™ for a product version, use the highest available template up to that product version. For example, if Automation Ops™ includes the Studio template versions 20.10.3 and 21.10.0:

Use template version 20.10.3 to create policies for Studio 2020.10.10 or Studio 2021.4.3.
Use template version 21.10.0 to create policies for Studio 2021.10.0.

Note:

Before changing policy templates, you can download existing policies in a .json format to either use them as reference for future configurations or keep them as backup in case you need to revert to a previous template.