Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Access groups and roles in Pega Robot Manager

Updated on June 24, 2021

Pega Robot Manager provides a set of template access groups, each with a unique set of access roles that grant specific permissions to Robot Manager users.

Use the sample access groups for reference or a starting point for configuring your own Robot Manager-specific access groups that you tailor to your business needs and security best practices. For example, you can allow Robot Manager managers to view DevOps pipelines and initiate deployments to other environments.

Default access groups

The following out-of-the-box access groups provide a sample proposal for various job functions that you can fulfill in Robot Manager.

Default access groups in Pega Robot Manager

Access groupFunctionAccess roles
PegaRobotManager:AdministratorsEnables all types of actions in Dev Studio and the Robot Manager portal. This access group is the superuser account.PegaRULES:SecurityAdministratorPegaRULES:SysAdm4PegaRULES:PegaAPIAutomationPackageManagement:AdminPegaRobotManager:RobotRegistratorPegaRULES:RepositoryAdministrator
PegaRobotManager:ServicesGrants agents, job schedulers, and batch operations access to Robot Manager resources, without providing a direct access to the portal.AutomationPackageManagement:AdminPegaRobotManager:RobotRegistratorPegaRobotManager:ReportAdminPegaRULES:PegaAPIPegaRULES:SysAdm4PegaRULES:SecurityAdministrator
PegaRobotManager:DeveloperProvides access to Dev Studio in client applications that are built on top of Robot Manager, for example, to build cases.AutomationPackageManagement:DeveloperPegaRULES:User4
PegaRobotManager:RobotDevelopersProvides rights for publishing automation packages to Robot Manager.AutomationPackageManagement:DeveloperPegaRULES:User4PegaRULES:PegaAPI
PegaRobotManager:RuntimeUserProvides indirect access to Robot Manager to download automation packages and get assignments. Robot Runtime users are unattended robots that process assignments from robotic work queues.AutomationPackageManagement:RuntimeUserPegaRULES:PegaAPIPegaRULES:User4
PegaRobotManager:AssistantsProvides case workers (for example, CSRs) who are assisted by attended robots with permissions to fetch automation packages from Robot Manager.AutomationPackageManagement:DeveloperPegaRULES:PegaAPIPegaRULES:User4
PegaRobotManager:RPAServicesProvides access rights for granting unattended robots access to Robot Manager so that the robots can download automation packages and complete work assignments.PegaRobotManager:RobotRegistratorPegaRULES:PegaAPIPegaRULES:User4
PegaRobotManager:AuthorsProvides rights for creating and managing the following Robot Manager content types:
  • Reports on robot and user data
  • Spaces for user collaboration
PegaRobotManager:UsersEnables accessing Robot Manager content created by authors, such as reports, dashboards, and spaces.PegaRobotManager:ReportUserPegaRobotManager:SpaceUserPegaRULES:User4
PegaRobotManager:ManagersEnables the following actions:
  • Managing robots, for example, work group assignment, scheduling, auto-balancing settings
  • Managing users, for example, creating departments, adding or removing users
  • Managing automation packages and their assignment
  • Managing reports
  • Managing spaces
PegaRobotManager:UserAdminEnables managing users and departments.AutomationPackageManagement:UserAdminPegaRULES:User4
PegaRobotManager:DeploymentManagersEnables viewing deployment pipelines in the Robot Manager portal and triggering deployment of the Pega Robot Manager application with the associated artifacts to another environment.PegaRobotManager:DevOpsPegaRULES:User4

Access groups in the Pega Robot Manager portal

When you add users in the Pega Robot Manager portal, you associate users with a role that directly corresponds to an access group, as configured by the system administrator in Dev Studio. The following figure shows the relationship between the two entries:

Privilege management for Pega Robot Manager users
A diagram that shows how access groups in Dev Studio are recognized as user roles in the Pega Robot Manager portal

Default access roles

Pega Robot Manager contains a set of out-of-the-box access roles. By removing or adding access roles in an access group, you restrict or grant user access to various Robot Manager areas, based on their responsibilities.

Note: Each access role references a set of privileges that complement the security and access control features. For more information about access privileges in Robot Manager, download the list of Robot Manager access privileges.

Robot Manager has the following predefined access roles:

Administrators can perform all actions in Robot Manager. Only administrators can deploy packages to the Production deployment level.
Developers can publish and manage automation packages.
User admins can manage Robot Runtime users and the organizational hierarchy.
Robot Runtime users cannot log in to Robot Manager. Robot Runtime users are typically case workers who fetch their automation package assignment from Robot Manager.
Robot administrators can administer unattended robots.
Report administrators can view, create, edit, and delete custom reports. They can also view and delete the out-of-the-box reports or change their titles. Report administrators can also archive and remove operational data that is collected for reporting purposes.
Report writers can view, create, edit and delete custom reports. They can also view the out-of-the-box reports.
Report users can view custom and out-of-the-box reports.
DevOps users can view deployment pipelines in the Robot Manager portal and initiate deployment of the Robot Manager application with the associated artifacts to another environment.
Space managers can creating new spaces as well as view and collaborate in existing spaces.
Space users can view and collaborate in existing spaces.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us