Within Automation Hub each user can have one or more permissions and, depending on the specific needs of an automation, to each user, regardless of their assigned permission(s), different roles can be granted in order to allow them to contribute as collaborators to an automation idea.
Through the assigned permission level(s) the user can access different sections and functionalities from the platform. When an automation role is assigned, the user receives access and editing rights to specific sections from the automation profile page, still, this is not extended to all the automations from the platform.
The difference between permission and role is that the permission grants access to certain platform sections and functionalities while the role gives view/edit rights to the specific section(s) from the profile of certain automations.
User X and user Y are Business Analysts part of the CoE team. They are added to the Automation Hub tenant. By default, they are created as Standard Users if no other permission is granted.
Within the tenant, three automation ideas are submitted. We'll call them ideas A, B, and C.
User X's expertise is needed for the automation idea A. They need to be assigned the Business Analyst role and to be granted editing rights for the automation idea A. This gives them the right to edit the automation profile page of idea A. Still, user X does not have editing rights for the other automations, B, and C as they are not assigned a role for these ideas.
User Y's expertise is needed for the automation idea B. They need to be assigned the Business Analyses role and to be granted editing rights for the automation idea B. This gives them the right to edit the automation profile page of idea B. Still, user Y does not have editing rights for the other automations, A, and C as they are not assigned a role for these ideas.
The standard roles available in Automation Hub are based on best practices and comprise the various functions that could be involved in the Automation Journey still you can add other roles, customized as per your company's specific needs. This option allows you to define specific positions while maintaining the naming convention from within your organization and helping your team get more accustomed to using the platform.
Within the company, user W handles small or medium automation projects for department E. Their job title is Citizen Developer.
The Program Manager can create the Citizen Developer role in Automation Hub and assign it to user W only for the automations submitted by users from department E. This way user W can contribute with valuable input for the automations submitted by the department E since this is their area of expertise but does not have editing rights to automations submitted by users from other departments.
Updated 19 days ago