- Release Notes
- Introduction
- Governance
- Feeds Management
- Automation Ops™ User Roles
- Solutions Management
- Governance
- Source Control
- CI/CD Pipelines
- Feeds Management
- Logging
Automation Ops™ User Roles
By default, users in the Administrator group in your organization have full access to features in Automation Ops™.
- Assign Automation Ops™ roles to users.
- Perform the Pipelines Quick Setup (setting thePipelines environment and also deleting it).
- Access Manage Feeds.
- See the projects from UiPath® Cloud in Source Control.
When switching between Automation Ops roles or assigning a new role, there might be a 5 minutes or more delay until the new permissions are granted based on your new Automation Ops role.
The Automation Ops Administrator role grants you access to Automation Ops™ features, except accessing Manage Feeds and setting Pipelines environment (also deleting the Pipelines environment).
The following table describes the full list of permissions that you inherit when the Automation Ops Administrator role is assigned to you.
Automation Ops™ feature |
Permissions |
Governance |
Policy:
Policy Deployment:
Template Settings:
|
Pipelines |
Pipeline:
Runtime Environment:
|
Solutions |
Solutions:
|
Source Control |
Connection:
Project:
|
The Automation Ops Contributor grants you access to Automation Ops features, except Manage Feeds. It does not allow you to make Organization-level configurations such as: governance policy deployment, connecting to 3rd parties source control providers or setting Pipelines environment (also deleting the Pipelines environment).
The following table describes the full list of permissions that you inherit when the Automation Ops Contributor role is assigned to you.
Automation Ops™ feature |
Permissions |
Governance |
Policy:
|
Pipelines |
Pipeline:
Runtime Environment:
|
Solutions |
Solutions:
|
Source Control |
Connection:
Project:
|
For Solutions Management, the user needs the Solutions Contributor or Solutions Administrator roles granted in Orchestrator.
For Automation Ops™ - Pipelines, the user needs access to the Pipeline runtime folder, i.e., Automation Developer.
For more details about permissions in Orchestrator, refer to Assigning roles.