Collaborator Roles are a sum of permissions that provide particular edit rights for an automation profile to the assigned user.
In order to create a team around an automation idea that collaborates on developing the idea and pushes it through the various phases, you need to add collaborators with one or more Collaborator Roles, from the Automation Profile > Collaborators > Manage Roles & Permissions screen.
Note:
Conditions to be able to select users and assign them as collaborators in an automation idea with Project Manager, Business Analyst, Solution Architect, RPA Developer, or any other custom Collaborator Role that you define:
- the Collaborator Role needs to be previously assigned in the user account.
- the user needs to be granted access to the idea's Categories.
To check or update the user account search for it in Admin Console > Manage Users > People screen and follow the steps from the Managing User Accounts page.
Details about each Collaborator Role and its designated permissions are available in the platform by accessing the Admin Console > Manage Users > User Roles > Collaborator Roles or below in this page.
By accessing the Collaborator Roles page from the platform you can also check out the two Help sections providing details about What are collaborator roles? and How do the tables work?. To dismiss them click the X icon on the top right corner. Once dismissed, the sections are not displayed anymore when the User Roles and Permissions page is accessed the next time. To see again the section click the Help icon.
Because some of the available default roles are uneditable as they are connected to the way the Automation Hub works, you have the option to add new, customized Collaborator Roles. Please check the Creating a New Collaborator Role page for more details.
Below you can check the default Collaborator Role matrix divided based on the availability of the option to Edit/Delete them:
Permanent Collaborator Roles
The following Collaborator Roles are permanent and cannot be deleted, edited, or disabled because they are connected to the way the Automation Hub works.
Employee Idea Submitter
Role automatically assigned to any user submitting an idea. Gives access to contribute with documentation.
- Edit the Documentation of an idea.
CoE Idea Submitter
Role automatically assigned to any user submitting a CoE idea.
- Edit the About page of an idea;
- Edit the Documentation of an idea.
Process Owner
As a Process Owner you are responsible for:
- Submitting the detailed assessment;
- Perform updates on the About page as needed;
- Provide complete and accurate documentation in relation to the process;
- Participate in UAT.
- Edit the About page of an idea;
- Update the Phase and Status of the idea during implementation;
- Edit the Documentation of an idea;
- Edit the Components of an idea;
- Manage the Collaborators in an idea.
Project Manager
As a Project Manager you are in charge of:
- Allocating collaborators to the automation initiative;
- Performing and updated the cost-benefit analysis;
- Keep track of the implementation progress;
- Keep stakeholders informed and manage their expectations.
- Edit the About page of an idea;
- Update the Phase and Status of the idea during implementation;
- View the Cost-Benefit Analysis of an idea;
- Edit the Cost-Benefit Analysis of an idea;
- Edit the Documentation of an idea;
- Edit the Components of an idea;
- Manage the Collaborators in an idea.
Editable Roles
The following Collaborator Roles are disposable and can be customized, disabled, or deleted as per each tenant's needs.
Business Analyst
As a Business Analyst you will gather the business requirements and understand the process AS IS, as well as document the TO BE process post automation. You will:
- Help business users/process owners complete the assessment for the process prior to automation;
- Perform in-depth analysis of the process once it is in implementation and capture all requirements and your recommendations for optimization in the Process Definition Document;
- Prepare test cases and conduct tests on the developed solution to make sure that it meets the acceptance criteria.
- Edit the About page of an idea;
- Edit the Documentation of an idea.
Solution Architect
As a Solution Architect you will design the technical architecture for the automation solution and document it in the Solution Design Document. Your focus when developing the architecture will be on:
- Robustness;
- Scalability;
- Efficiency;
- Replicability;
- Reusability of components.
- Edit the Documentation of an idea;
- Edit the Components of an idea.
RPA Developer
As an RPA Developer you will be coding the solution, testing as well as providing guidance on process design. You will:
- Document your code in the Development Specifications Document;
- Create and link reusable components to the automation initiative;
- Fix bugs and provide support during UAT and hypercare period;
- Create the Move to Production checklist.
- Edit the Documentation of an idea;
- Edit the Components of an idea.
Updated 6 days ago