7.2.3 RPAM Policies - Role Definition

RPAM policies are implemented by defining roles in the Resource Reservation system. These roles are created by combining default system permissions into groups.

This modular approach ensures each role has the precise permissions needed for its designated responsibilities. For example, some roles might focus on initiating reservation requests, while others are designed for administrative tasks like managing, approving, and scheduling reservations. This customization ensures roles are equipped to effectively carry out their functions throughout the entire reservation lifecycle.

To create roles that meet your organization's needs, combine various permissions such as 'Requires Authorization,' 'Can Authorize,' or 'Can Self Book.' Once defined, roles can be assigned to multiple users or user groups, seamlessly integrating with your workflow.

Roles are defined from the Permissions tab of a profile Settings menu by clicking the Permissions button to access the Managing Permissions Groups dialog window.

Below is a list of available permissions:

Permission	Description
Immediate access	Enables immediate access to the profile.
Requires Authorization	Indicates that the user request requires an approval.
Can Authorize	Can authorize / approve reservation request
Can Self Book	Can create reservations for oneself.
Can Get Booked	Can be added by others for the use of a resource.
Can Book Others	Can create reservations for others.
Allow Recurrency	Can create recurring reservations.

Important

The first time a new role is created in the system, an additional default role - "Access" - is added by default. As the name suggests, this role only grants permission to access an Access Profile and no other permission.