|The RWM application was deprecated with Appian 24.1. The application will no longer be updated or pre-installed for new Appian Cloud sites with Appian RPA enabled.
RWM will be removed in a future release and we encourage customers to use the Operations Console to manage robots instead.
Robotic Workforce Manager (RWM) comes with a number of groups provided by default. Add users to these groups to grant access to different parts of the application. To help control who sees what in RWM, you can also configure groups to grant users access based on their roles in the application.
This page lists the RWM business groups and what access is given to the members of each group by default.
The following table describes the application's various user roles and their access to different modules and views.
|The members of this group can initiate new automation requests from Appian
|Control Center Executives
|Members of this group can access the RPA Metrics tab
|Control Center Admins
|These group members can access the Control Center functionality
|These group members can work on exceptions
|This group contains members who triage exceptions from robotic processes
|Business COE Reviewer
|This group contains Business COE who accepts the business decisions of all the onboarding automations
|Technical COE Reviewer
|This group contains Technical COE who accepts the technical logistics of all the onboarding automations
|AI Specialist Reviewer
|This group contains the AI Specialist, who accepts the AI review task of all onboarding automations
|The group contains the Owner of the onboarding automation request.
|This group users can view and manage Business Exceptions
If you want groups other than RWM Admins and Control Center Admins to start or schedule an RPA process, add the group to the
|Group contains all the admin members who can access all the modules
|RWM All Viewers
|This group contains all the viewers of the application, by default all the Business Roles are added to it.
|The members of this group receive alert messages of the process models in Appian
|RWM Process Initiators
|The members of this group can initiate the process model
|All Process Models
Robotic processes can deal with sensitive data, so security and access control are top concerns. Certain business units may also be interested in only some of the data RWM has to offer. For example, the marketing and accounting departments may not need to see the same information. Further, groups within a department can each have a different focus, such as marketers supporting a certain line of business or product offering.
You don't need to assign each user a specific role in RWM if you only want to grant them access to parts of the application. If RWM's default user groups don't provide you with enough configuration options, you can create a new group and choose the groups that have access to certain areas of the application.
Create groups to mirror your organization's structure. For example, if there are three lines of business within a business unit, you can create a group for each line of business within the business unit group.
This way, you can still configure RWM access for each of the smaller groups and streamline options where the whole group should be given access. For more common areas of the application, you can grant access to the business unit group so everyone within the parent and child groups has access.
To create a new group so it has access to the Control Center and Automation Planner:
Learn best practices for onboarding new users to RWM and how to add them to the appropriate groups.
Now you're ready to configure which roles have access to actions in RWM. The actions are grouped by the different components of an automation, such as Process, Resource, Queue, or Automation.
Configure the group's access:
Roles and Security