Configure Approval Hierarchy and Notifications

When you configure approvals, the predefined approval chain includes the manager of the worker being evaluated.

However, you can add additional levels of approvers and other roles, such as HR specialist. Other roles must have the correct privilege for approvals and a data security profile that lets that includes access to the worker whose performance document they're asked to approve.

To add the HR specialist as an approver, you must also add an area of responsibility for the HR specialist using the Areas of Responsibility task in My Client Groups > Quick Actions > Show More > Areas of Responsibility.

Approval Rules

HR specialists can configure an approval rule for performance documents to use the current assignment hierarchy instead of the primary assignment in a hierarchy. So, if they submit a performance document on an employee's nonprimary assignment for approval, it's routed using the nonprimary assignment hierarchy.

You can set up multiple level approvals for performance documents using the manager's current or primary assignments. If a performance document has multiple levels of approvals and the approvers have multiple assignments, then you can route approvals using the assignment hierarchy of the employee, or route them using the manager's primary assignments.

If multiple approval rules exist, HR specialists can use parallel approvals in an approval rule to send approval requests to multiple participants at the same time. Only the first person to respond needs to process the approval.

Notifications

When you activate notifications, each approver receives worklist and email notification that a document was submitted for approval. The notification contains a link to the performance document so the approver can view it.

When all approvers have approved or rejected the document, the worker's manager receives notification whether the document was approved or rejected. The approval process is repeated if a manager resubmits a document after rejection, or a second approval task is configured in the process flow. If the performance document is approved, the next task in the process flow becomes available or if the approval is the last task, the performance document is completed. If the approval is rejected, then the previous task in the process flow becomes the current task so any requested changes can be made before the approval task is resubmitted.