Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Organizational structure and hierarchy

Creating and maintaining an organizational structure in Pega Robot Manager™ streamlines the assignment and deployment of packages and run-time configuration settings to users. This structure eliminates the need to directly access the users' desktops for attended robots. The organizational structure also helps to identify necessary updates to users' desktops for new versions of packages and corresponding run-time environments. Pega Robot Manager communicates with a synchronization engine, which ensures the correct package and run-time version is downloaded to the users' desktop, based on the organizational structure package assignment and user membership.

Organizational structure creation

Package and run-time configuration settings can be assigned directly to users if required. However, assigning these settings using the organizational structure offers a more scalable approach. Multiple users can belong to a single department. The assignments can only be applied to a parent-level department. The assignments automatically apply to the parents' child-level sub-departments. For example, an assignment made at a top-level department automatically applies to all sub-departments unless a different assignment is made at a lower level.

Note: The organizational structure does not apply to unattended robots because the robots inherit packages and settings directly from the assigned work group.

The organizational structure is made up of departments and sub-departments. The hierarchical structure requires a minimum of three levels but supports additional levels to offer more granular alignment between users and assigned packages. Each user belongs directly to one department. Packages are assigned to a department. This user-package relationship determines the packages to which users have access. Because the departments are hierarchical, users can access packages based on inheritance from a package assigned to a parent department.

The following image depicts a sample of the Robotic Banking Corporation's organization. The hierarchy includes three department levels and the number of users mapped to each department. Notice that users belong directly to a department at the lowest level, with the parent levels showing the number of users based on inheritance.

A table of departments in Robot Manager, showing the organizational hierarchy of the Robotic Banking Corporation.

You can create or maintain the organizational structure in Robot Manager or Dev Studio. It is a best practice to create and maintain the structure in one tool. For example, if you create an organizational hierarchy in Robot Manager, maintain or edit the structure through Robot Manager, not Dev Studio.

Note: In Dev Studio, the organizational structure uses the Org>Div>Unit terminology, while Pega Robot Manager refers to the org structure as departments and sub-departments.
Tip: As a Pega best practice, align your organizational structure with your company's HR structure.

Check your knowledge with the following interaction:

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice