-
Predefined fine-granular permissions to view and process data.
-
Can be compiled to individual roles.
-
For some tasks users need individual permissions or assignments additional to privileges.
-
Are deprecated after the migration of RPA Manager to Anypoint Access Management
User Roles and Permissions
Automating a process takes an interdisciplinary team. Knowledge, skills, and responsibilities are distributed over several different persons. Not everyone can do anything or should know anything for security reasons. These restrictions are implemented as user roles and permissions in RPA Manager.
User Permission Scopes
Permissions determine what users of the RPA products can see and do:
-
See and open
-
a module
-
a view
-
an object and its data
-
-
Perform an action in a view
-
Create objects
-
Edit data
-
Transition objects
-
Take decisions
-
Use products
-
Analyze data
-
Monitor
-
usage
-
performance
-
-
Report results
User Permissions Types
Permissions have different scopes and purposes. They can be combined.
Permission Type | Scope | Example |
---|---|---|
Privileges / RPA (Deprecated) Permissions |
You can guess the purpose of these example privileges from their name:
|
|
RPA Permissions |
|
You can guess the purpose of these example privileges from their name:
|
Roles |
|
The role |
Assignments |
|
|
Individual Permission |
|
Credentials can only be used by users selected on creation. |
Transferred Permission |
|
API Keys are needed when an RPA Manager Invocable Configuration is included into a Composer Flow. |