Approvals

Everything your team requests — absences, clock-in corrections, schedule changes — lands in a single approvals inbox, with the same flow for everything: you approve or reject in one or two levels, and everyone involved gets an email notification.

What goes through approval

Which absence types require approval is configured in Absence types (side menu, Administration section).

Choose 1 or 2 levels

In Company settings you decide how many approval levels you want:

• 1 level: the request can be resolved by either the person's department manager or HR or administration. Whoever decides first closes the request.
• 2 levels: the department manager approves first and, only if they give the go-ahead, the request moves to HR or administration for the final decision. If the manager rejects it, it closes right there and never reaches the second level.

With 2 levels enabled, if the person has no department or their department has no manager, the request goes straight to HR/administration. That way nothing gets stuck waiting for an approver who doesn't exist.

Who resolves whose requests. A manager only resolves those of the employees of their department. HR or the administrators resolve a manager's requests, and another administrator resolves those of HR or of an administrator; in both cases in a single step, even if they are in a department with a manager.

Nobody can approve or reject their own requests — not even administrators. If nobody else manages you (you are the only administrator, even if there is HR), your absences and clock-in issues are recorded with a reason, and it is stated that there was no other approver; you record your schedule in your profile, also with a reason (the schedule change form takes you there).

The approvals inbox

1. Go to Approvals (side menu, Team section). You'll see the pending requests that are yours to resolve at the current step: a manager only sees those of their department's employees; HR and administration see those of the people they manage that are on their turn.
2. Review the details: who's asking, what they're asking for and, in 2-level flows, what the first level already decided.
3. Approve or reject. To reject, the comment is mandatory: the person will always know why. For clock-in issues it is also required to approve (it stays in the record), and if the entry arrived with a doubtful time, enter the real time.
4. Below the pending ones you have your last 20 resolved requests, in case you need to review a decision.

Once approved, the change applies itself: the absence is confirmed (and deducts balance if the type does), the issue corrects the clock-in entry, and the schedule change is scheduled.

Minimum coverage warning

If you set a minimum coverage percentage per department in Company settings, the inbox warns you when approving an absence that would leave the department below the threshold on any day of the range (counting both already-approved absences and pending ones, and excluding weekends and public holidays).

It's a warning, not a block: you decide whether to approve it anyway.

Email notifications

• When someone submits a request, the competent approvers for that step receive an email (department managers at level 1; HR/administration when it's their turn).
• In 2-level flows, when the first level approves, the second is notified automatically.
• When the request is resolved — approved or rejected — the person who submitted it receives an email with the outcome.

Each email arrives in the language each user has configured in their profile.

Next steps

• Set up absence types and their balances
• Define the team's base schedules
• Just arrived? Go over getting started