- Release Notes
- Getting Started
- Access Control
- Installation and upgrade
- Activities
- Designing long-running workflows
- Start Job And Get Reference
- Wait for Job and Resume
- Add Queue Item And Get Reference
- Wait For Queue Item And Resume
- Create Form Task
- Wait for Form Task and Resume
- Resume After Delay
- Assign Tasks
- Create External Task
- Wait For External Task and Resume
- Complete Task
- Forward Task
- Get Form Tasks
- Get Task Data
- Add Task Comment
- Update Task Labels
- Actions
- Processes
Access Control
In order for a user to be able to use Action Center services and the desired level of access, they require the corresponding permissions on Actions,Action Assignment and Action Catalogs in Orchestrator.
Learn About Roles in Orchestrator.
The validation admin sees all the generated document validation actions and handles having them assigned to users on the Administer page. Can also validate an action themselves. Should be granted the following permissions:
- View,Edit on Actions
- View,Edit,Create,Delete on Storage Files
- View on Storage Buckets
- View,Edit,Create on Action Assignments
- View,Edit,Create on Action Catalogs.
The validation user sees all the form and document validation actions assigned to themselves such that they are able to validate them on the My Actions page. Should be granted the following permissions:
- View,Edit on Actions
- View,Edit , Create on Storage Files
- View on Storage Buckets
- View,Edit on Action Assignments
The classification admin sees all the generated document classification actions and handles having them assigned to users on the Administer page. Can also validate an action themselves. Should be granted the following permissions:
- View,Edit on Actions
- View,Edit,Create,Delete on Storage Files
- View on Storage Buckets
- View,Edit,Create on Action Assignments
- View,Edit,Create on Action Catalogs.
The classification user sees all the form and document classification actions assigned to themselves such that he is able to validate them on the My Actions page. Should be granted the following permissions:
- View,Edit on Actions
- View,Edit on Storage Files
- View on Storage Buckets
- View,Edit on Action Assignments
The action admin sees all the generated form actions and handles having them assigned to users on the Administer page. Can also validate an action themselves. Should be granted the following permissions:
- View,Create on Action Assignment.
- View,Edit,Create on Action Catalogs.
- View,Edit,Create on Actions.
In order for the Robot to generate an action, upload, download and delete data from a storage bucket, it needs the appropriate permissions. Make sure the Robot role has been granted the following:
To create an action:
- View,Edit,Create on Actions
To upload document data:
- View,Edit,Create on Storage Files
- View on Storage Buckets
To delete document data after downloading:
- View,Edit,Delete on Storage Files
- View on Storage Buckets
- When the Azure AD integration is enabled,
you cannot assign tasks to users in Action Center if they haven't signed in using
their AD account. The same behavior occurs for local user groups , when the
users haven't signed in using their local user account.
Workaround: Consider asking your users to sign in after their accounts have been created, using either their AD or local user account. Alternatively, you can continue to assign tasks to the user's UiPath account. But then organization administrators should delay the task of discontinuing UiPath account use until the issue is resolved.
- In the case of folders that have permissions set for DirectoryGroup, all Azure AD users appear in the Assign To User drop-down list, even if they don't have permissions for the specified folder. Even if users without the appropriate permissions show up in the Assign To User drop-down list, you can't assign Actions to them. This behavior is a user interface issue only, caused by an API that returns all Azure AD users, regardless of their folder permissions.
