Roles and permissions

The roles and permissions for Actions are set from Orchestrator.

Robot role

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 assign an action:

• Create on Actions Assignments

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

Personal workspace administrator role

To generate actions in the context of a personal workspace folder and have them displayed in the Action Center inbox, the following permissions have been added as default:

• Create,View,Edit,Delete on Actions.
• Create,View,Edit,Delete on Action Catalogs.

Custom roles - actions

Note: The Create permission on Action Assignments enables the Manage Actions view on the actions panel, which facilitates the management of all actions in the corresponding Orchestrator folder. To view and manage only the actions assigned to yourself, switch to the My Actions view.

We recommend defining the following roles for handling actions:

Action admin user

As an action admin, you see all the generated Form Actions and assign them to users in the Manage Actions view.

The following permissions are required:

• View,Create on Action Assignment.
• View,Edit,Create on Action Catalogs.

• View,Edit,Create,Delete on Actions.

  
  

  

  
  

To manage action labels, the following permissions are required:

• View,Create,Delete on Tags.

Action user

As an action user, you see all the Form Actions assigned to you, and edit them in the My Actions view.

The following permissions are required:

• View,Edit,Create on Actions.

  
  

  

  
  

To manage action labels, the following permissions are required:

• View,Create,Delete on Tags.

Technical user

As a technical user, you handle External Actions.

The following permissions are required:

• Edit on Actions.

To manage action labels, the following permissions are required:

• View,Create,Delete on Tags.

Custom roles - processes

We recommend defining the following roles for handling processes:

Queue process user

As a queue process user, you can generate forms to provide inputs to a queue.

The following permissions are required:

• View on Queues.

• View,Edit,Delete on Transactions.

  
  

  

  
  

Job process user

As a job process user, you can generate forms to provide inputs to a job.

The following permissions are required:

• View on Processes.

• View,Edit,Delete on Jobs.

  
  

  

  
  
  Note:

  To trigger a process through file upload, you need the following permissions:

  • View,Edit, Create on Storage Files.