AARI web interface users
Various users are involved in AARI on the web interface and each user contributes in different ways to help the automate the business requirements.
AARI users are broadly categorized into two types, users who can access the Control Room and users who have access only to the web interface. Each user's role and responsibilities vary depending on the stage of the workflow.
Users and their roles
The following table illustrates the relationship between users, roles, and the permissions they have while using AARI on the web interface.
User | Role | Permissions |
---|---|---|
Control Room administrator | AAE_Admin | Create users with AARI license and assign roles. |
Bot Creator | AAE_Basic |
|
AARI admin | AAE_Robotic Interface Admin |
|
AARI manager | AAE_Robotic Interface Manager |
|
AARI user | AAE_Robotic Interface User |
|
Team roles and permissions
The following table explains the users, their roles and permissions within an AARI team.
Team Role | Control Room Role | Team Type | Permissions |
---|---|---|---|
Admin | AAE_Robotic Interface Manager | Shared |
|
Private |
|
||
Owner | AAE_Robotic Interface User | Shared |
|
Private |
|
||
Member | AAE_Robotic Interface User | Shared |
|
Private |
|
Example
Consider two teams, Finance and HR, and their team roles as given in the following table:
Finance (Private) | HR (Shared) | ||
---|---|---|---|
User | Role | User | Role |
User A | Owner | User X | Member |
User B | Member | User Y | Member |
User C | Member | User Z | Owner |
- User A can view and delete all the requests created inside the team Finance.
- Users B and C can view and delete only their requests inside the team Finance.
- Users X, Y, and Z can view all the requests but can delete only their request inside the team HR.
- User Z can view and delete all the requests created inside the team HR.