Guide

For managers

Use Approvals to review assigned requests, read the supporting information and record decisions within your scope.

A manager has two outcomes to protect: decisions have enough evidence and team work does not remain stuck at their step. Open notifications for new signals and Open approvals for items waiting on you.

Each day: decide pending work

Open Approvals and prioritise items near their deadline or affecting attendance, payroll, or payment.
Open the source record and read its details, evidence, history, and current approval step.
Compare it with the work schedule, team scope, or relevant policy.
Use an action offered by the screen. When rejecting an item, write a reason that tells the requester what must change.
Read the new state and next owner before leaving.

Before deciding, answer five questions:

Is this the correct person and within my team scope?
Is the date, period, or date range correct?
Is there enough data and evidence?
How does the decision affect shifts, attendance, payroll, or budget?
Is there a conflict of interest or a need for an independent approver?

Read the right list and current step

Pending my approval contains requests you can act on at the current step. Related to me tracks requests you submitted or participated in; appearing in this list does not by itself grant permission to approve.

Filter by request type, status or group to narrow the list. Open an item and read the requester, business details, current step and history. When following a notification or a direct link, confirm the request before acting. If its details fail to load, select Retry; do not submit a replacement request merely because the original has not loaded.

After selecting Approve or Reject, read the confirmation and confirm once. Rejection needs a specific reason, such as an incorrect date or missing evidence. One approval can leave the request waiting for another person or step. Treat the whole process as complete only when both its status and the source business record confirm completion.

After you agree at the current step, the screen shows You have approved this step and prevents another decision at that step. Waiting for lists the people who have not yet agreed. Continue tracking the request in Related to me.

If a message says the request has changed, refresh and read the new step before deciding again. If you are assigned to consecutive steps, each step still needs a separate decision based on its current information.

Your permission must still be effective when you decide. If the screen reports missing permission in the applicable scope, ask an administrator to check the role and data groups. A previous assignment or continued access to history does not guarantee approval access. Expense claims and advances use the subject employee’s primary group.

For advances and expense claims, check the request code, title and Amount before confirming. Older requests may not include a code or title in the inbox snapshot. If required details or evidence are missing, review the source record with someone who has access before deciding.

Delegate or act on several requests

Select Delegate when the step allows it and a suitable recipient is available. Read the dialog’s explanation: a general workflow adds a co-approver, while Payroll and KPI approvals managed by those modules transfer the assignment. The recipient needs the appropriate permission and scope. Delegation does not extend the deadline.

For multiple requests, review the count in the confirmation and use a shared reason only when it applies to every item. A batch can partly succeed if a request has changed or your permission has changed. Read the successful and failed counts. The result keeps each failed item and its reason; select an item to open that request and check its latest state. Retry only items that remain eligible, rather than repeating the successful batch.

Cancel request depends on the requester and current status. Being an approver does not automatically allow you to cancel for the requester. If no suitable action remains, review the history and contact the person responsible for the business process.

On a phone, the list and details appear one at a time. Use Back to return to the list after reviewing or acting on an item.

When approving leave or overtime

Check the team’s schedule, available cover, applicable balance or limit, and the requested dates. After deciding, confirm the request changed to the intended state; reading a notification is not the same as approving its request.

Follow the complete leave and overtime workflow.

When reviewing team attendance

If you have access under Operations, filter to the group and period you own. Focus on missing check-in or checkout times, shift mismatches, and pending requests. Hand source-data corrections to HR before the period is closed.

Monthly attendance explains where manager confirmation ends and HR period closure begins.

Each week: review your team

Check the upcoming work schedule and gaps requiring coordination.
Finish requests that could affect the open attendance period.
If responsible for performance, select Open KPI overview and verify the period, subject, and source evidence before entering or approving a score.
Use the Open organization tree to confirm team scope, then follow proposed changes to position, salary, manager, or employment state that require your input.

Use these workflows when needed:

Before a hand-off deadline

Before HR closes attendance

No team leave or overtime request remains forgotten.
Every abnormal shift or attendance entry has an owner.
Important corrections have a reason or supporting evidence.

Before approving payroll or payment

Open the source record instead of deciding from a notification title.
Check the total, applicable period, exceptions, and preparer.
Keep duties separate when company policy requires an independent approver.

When you need help

Do not ask an employee to submit repeatedly when a request already exists. Note its name or reference, current state, current owner, and action time, then follow Support.