Roles
There are standard Roles that grant access to the Request to Work feature. Additional custom roles can be created, or replicated and modified, which give access to this feature. For more information, see the Configuration section>System card>Roles screen.
Roles can be assigned to all Primary Home employees in an organization unit through the Organization Unit>Roles screen or to individual employees through the Employee Record>Roles screen.
Standard roles cannot be modified, however, additional custom roles can be created (User Defined) or copied (Replicated) from existing standard roles and modified to grant access to this feature. For more information on creating new roles, or replicating and modifying existing roles, see the Configuration section>System card>Roles screen>Steps for Replicating a Role or Steps for Adding a New Role.
Note: Since the custom roles may be the ones preferred by your corporation, the roles are not listed in this document. To locate existing roles that grant access to a specific policy, a report can be run. This report is found in the Reports section>System card>Authorization Roles Assigned to a Policy.
Request to Work Authorization Policy
Roles that are able to access this feature have the Request to Work authorization policy included in the role.
The following screen print shows the location of the access to the employee Request to Work screen. The Maximum Severity Level field indicates the level of validation exception message that employees can override, if any. 
More About Overriding Schedule Validations
Depending on Roles assigned to users, they may be able to override validation messages and continue to add, edit, or approve a schedule. If users do not have the authorization to override the exception, there is no option to continue and save the transaction.
Override access is determined by:
- The Maximum Severity Level override allowed by the user's role
- The Severity Level of the exception message
Maximum Severity Level Override Allowed by the User's Role
Depending on the role assigned to users, they may be able to override the exception message generated when a scheduling rule is violated by adding, editing, or approving a request for a schedule.
The roles are found in the Configuration section>System card>Roles screen.
In the Maximum Severity Level field, indicate the severity level of the validation exception that can be overridden. Severity levels (in order of severity) are Critical, Warning, and Informational. All exceptions with that severity level or below can be overridden for assigned users. For example, if this value is set to Warning, this user can override validation exceptions of Warning and Informational, but cannot override exceptions with a severity level of Critical. If no value is entered in this field, the user cannot override ANY level of exception message.
Severity Level of the Exception
Severity levels for a validation rule are set up on the Configuration section>System card>Exception Value screen, in the Severity Level field. Severity levels (in order of severity) are Critical, Warning, Informational, or None.
Note: The severity level displayed in the warning message may not match the value set up on this screen. If the user is able to override the error, then the level is displayed as Warning regardless of the actual exception definition severity level. If the user is not able to override the error then the level is displayed as Critical regardless of the exception definition.
The following screen print shows the location of the access to the supervisor approval screen for the Request to Work feature. The Maximum Severity Level field indicates the level of validation exception message that users can override, if any. More About Overriding Schedule Validations
Depending on Roles assigned to users, they may be able to override validation messages and continue to add, edit, or approve a schedule. If users do not have the authorization to override the exception, there is no option to continue and save the transaction.
Override access is determined by:
- The Maximum Severity Level override allowed by the user's role
- The Severity Level of the exception message
Maximum Severity Level Override Allowed by the User's Role
Depending on the role assigned to users, they may be able to override the exception message generated when a scheduling rule is violated by adding, editing, or approving a request for a schedule.
The roles are found in the Configuration section>System card>Roles screen.
In the Maximum Severity Level field, indicate the severity level of the validation exception that can be overridden. Severity levels (in order of severity) are Critical, Warning, and Informational. All exceptions with that severity level or below can be overridden for assigned users. For example, if this value is set to Warning, this user can override validation exceptions of Warning and Informational, but cannot override exceptions with a severity level of Critical. If no value is entered in this field, the user cannot override ANY level of exception message.
Severity Level of the Exception
Severity levels for a validation rule are set up on the Configuration section>System card>Exception Value screen, in the Severity Level field. Severity levels (in order of severity) are Critical, Warning, Informational, or None.
Note: The severity level displayed in the warning message may not match the value set up on this screen. If the user is able to override the error, then the level is displayed as Warning regardless of the actual exception definition severity level. If the user is not able to override the error then the level is displayed as Critical regardless of the exception definition.
