Roles
- Updated: 2024/07/25
Roles
The Control Room enforces role-based access control (RBAC). There are two types of roles: System-created and User-created.
RBAC enables users to access specific features based on the assigned roles and the
accessibility provided to the user. The benefits of creating roles include:
- Increased security by controlling users access according to their specified roles.
- Ability to create user roles based on your organization's requirements.
- Ability to create user roles with all possible permissions that are supported in the Control Room.
- Ability to customize roles based on your needs without any permissions being disabled. You can select all the required permissions.
- Ability to assign permissions to a role based on your organization's requirements.
- System-created roles
- These roles are preconfigured with the permissions necessary to perform the tasks
within the scope of a system-created role. You can view and modify a
system-created role. If a role is assigned to more than one user, you will not be
able to disable a system-created role.Note: It is optional to use system-created roles.
- User-created roles
- These roles are created by authorized users. You can create a user-created role
with all possible or available permissions.
Note: Before you create and assign roles that are similar to system-created roles, you should consider any potential security risks. For example, if you create a role with permissions similar to AAE_Admin, such users will be able to make changes to the Control Room settings.
Before removing a user role from an active RPA, administrators need to verify that all unfinished bot development is checked-in.