|This content applies solely to Robotic Workforce Manager, which must be purchased separately from the Appian base platform. This content was written for Appian 21.3 and may not reflect the interfaces or functionality of other Appian versions.|
As automations grow, you may find that more people are brought into the process, and by extension, the RWM environment. Each individual can support a key part of an automation lifecycle, from reviewing and approving requests to implementing and maintaining automations, or anywhere in between. You can set up new users for success as they get to know RWM.
This page describes guidance and steps to add new users to the RWM application and some tips on how to get them up to speed as part of your automation Center of Excellence.
RWM is pre-configured with user groups to help set security within the application and involve individuals based on their responsibilities. As you consider adding a new user to RWM, think about what they'll need to see and interact with.
Consider questions such as:
Answers to these questions can help narrow down which role group the user best fits into. The group a user belongs to greatly influences their experience in RWM. It's important to add them to the correct user group based on their role within the automation lifecycle so they have access to the tools they need to accomplish key goals.
The table below summarizes the ideal role for key responsibilities in RWM:
|Initiate automation requests, including inputting all relevant information||Automation Requestor|
|Review incoming automation requests to assess viability||AI Specialist Reviewer|
|Review and approve automations based on technical and business impact||Business COE Reviewer, Technical COE Reviewer|
|Resolve exceptions in an automation execution, assigned based on decision logic||Exception Assignee|
|Triages and assigns exceptions that aren't automatically assigned||Exception Manager|
|Add and manage user accounts for the RWM application||RWM Admin|
After you've determined the group the new user belongs in, follow these steps to add them:
You can also remove a group member if that user no longer needs to be a part of it.
Once the user has been added to RWM, they'll have access to the application. At this stage, it might be helpful to show them RWM's key components, as well as brief them on their role in the process. You can share parts of the user guide with the new user if their role has them working in the Automation Planner or Control Center.
After they're familiar with the user interface, provide context for the new user. Let them know specifically when and how they're involved in RWM's key processes. For example, if the user manages exceptions, let them know how they'll receive notifications and how quickly they're expected to intervene. If the user is part of the approval process, it might be helpful to show them who else reviews the requests or what information they'll need to provide when they input a decision.
On This Page