Understanding Document Approval Delegation

A Benefits Administrator can delegate the authority to approve Life Events documents uploaded by employees to another user if required. The Life Events document approval workflow integrates with the HCM Delegation Framework, thus enabling the Benefits Administrator to delegate authority of Life Events document approval. The Benefits Administrator can create a delegation request to allow a proxy to approve Life Events documents on his/her behalf. The Benefits Administrator can set a date range for the proxy to complete the delegation request. The proxy can accept or reject the delegation request, and can approve, deny, or push back the Life Events document on behalf of the delegator. The delegator can revoke or withdraw the delegated authority when required.

Email notifications will be sent to the delegator when new delegation requests are made. The proxy will in turn be notified of any pending approval requests through email.

The following terms are important to understand the delegation feature:

• Delegation: The act of giving the authority to approve Life Events documents to another user.

• Delegator: A person who delegates authority to another user.

• Proxy: A person who is granted the authority to act on behalf of the delegator.

• Delegated Authority: The rights and privileges that are given from the delegator to the proxy.

• Delegation Request: A request from the delegator to the proxy to take on delegated authority.

• Delegation Period: The time range in which the delegated authority is in effect.

• Delegation Administrator: The system administrator who is responsible for configuring, managing, and maintaining delegated authorities.

• Revoke: When a delegator withdraws delegated authority.

Note:

To prevent situations of cascading or circular delegation chains, once the delegation framework passes delegated authority over an absence transaction to a proxy, the proxy cannot delegate authority over that transaction to another user. The delegation framework only passes authority over transactions from the initial delegator to the initial proxy.