Administrators can create workflows to define which attendance submissions need manual approval and which can be automatically approved. To create an approval workflow, add conditions to define which attendance violations should trigger an approval task. Then, add rules to specify who the approval applies to.
The system checks new attendance submissions against all active workflows. If a submission meets a workflow's conditions, it sends an approval task to the assigned approvers. Approvers can find and review these requests in their Inbox, where they can action multiple tasks at once.
If a submission doesn't match any workflow conditions, it's automatically approved.
Before you start
Permissions
Before you start, make sure the relevant users have the correct permissions:
- You need Administrator permissions to set up, edit, or monitor attendance approval workflows.
- To receive and action attendance requests, approvers must have View permissions for the relevant employee's attendance data.
- Only users with Propose permissions for attendance data trigger an approval process. Users with Edit permissions can adjust attendance data without approval.
Considerations
Keep the following in mind:
- When you activate a new approval workflow, it immediately applies to any new submissions, and new approvers get notified.
- Approvals only trigger when someone with Propose permissions submits changes to attendance data and their submission matches the conditions of an approval. Employees with Edit permissions don't trigger approvals.
- If you assign an employee role as the approver, all members of that role get the approval task. Once one of them approves it, the task disappears for all others.
- Approvers must have View permissions to attendance data.
- If multiple approvals match an employee's submission, the system applies the approval assigned the highest priority. For this reason, give the most general workflow the lowest priority, and the most specific the highest priority. See how to change the priority of workflows.
- Approvers can manage their email preferences for approval tasks by going to Personal Settings > Notifications. Enable the checkbox for Approvals to activate email notifications.
- If an approver’s employee status is Inactive or Leave, requests for them do not go to their delegate. Instead, they go directly to the last editor of the approval. If the approval process automatically migrated from our legacy system, this may be the longest-serving employee with Administrator permissions.
Set up an attendance approval workflow
Create an approval workflow for attendance submissions that violate the rules in the employees’ work schedule or time tracking policy.
Follow these steps:
- Go to Automations > Create workflow > Approvals.
- Choose the Approval for attendances with rule violations template.
- Click the trigger box to adjust the conditions. Without conditions, all attendance submissions will trigger the workflow.
- Optionally, add rules to define which employees this workflow applies to, using available preset or custom attributes. Add rules to include additional Supervisors in the approval process.
- Click Update to save the edits.
- To select the request approver, click the approval step. Select up to four approvers per step.
- Add multiple steps to create an approval chain. As soon as one of the approvers in a step actions the request, the workflow moves to the next step.
- If your organization has additional Supervisor capabilities, include them if required.
- If you add Affected person as an approver, employees will be able to approve their own attendances.
- Optional: Ensure requests aren't delayed by activating the Enable delegation option. Set how many days to wait before delegating and who should get the request. If that user is also unavailable, the workflow creator receives the task.
- Optional: add steps for approved or denied requests.
- Save and activate the workflow.
Note:
If a request is denied at any point in the approval chain, the workflow ends. It appears as complete in the Activity tab and the approval request is rejected. To inform users about the progress of the workflow in email, you must manually add a step to the workflow. This includes informing approvers about the task via email.
Conditions
When setting up an approval workflow, you can choose from the conditions in the table below. Keep in mind:
- Conditions only trigger if the corresponding section in the employee’s work schedule or time tracking policy is set up correctly.
- You can decide if a submission must match all or any of the conditions to trigger the workflow. Use the dropdown in the Condition drawer to switch between the two options.
- The time unit for all conditions is minutes.
| Condition | Relevant work schedule setting |
| Hours worked is shorter or longer than daily target hours |
This refers to the Work hours per day setting in work schedules. Example: An employee’s work schedule requires them to work 8 hours on a Monday, but they track 9 hours, which is 60 minutes too much. Your condition states that anything over 20 minutes triggers an approval. |
| Total break time exceeds working schedule |
This refers to the Break hours per day setting in work schedules. Example: An employee’s work schedule requires them to take a 30-minute break each day. However, they track a 45-minute break, which is 15 minutes too much. Your condition states that anything over 10 minutes triggers an approval. |
| Start time/end time is earlier or later than working schedule |
This refers to the Start and End times in work schedules. Example: An employee’s work schedule requires them to start work at 08:00. However, they clock in at 09:30, which is 90 minutes too late. Your condition states that anything later than 15 minutes triggers an approval. |
| Exact location was requested but is missing | This refers to the Location tracking settings in time tracking policies. Specifically, it relates to the option Capture exact location when people track time. |
| Person is outside of a workplace | This refers to the Location tracking settings in the relevant time tracking policy. Specifically, it relates to the option Capture location as inside or outside of workplaces. |
| Hours worked are longer than max hours |
This refers to the Maximum hours setting in time tracking policies. Example: An employee’s time tracking policy restricts them to a maximum of 7 working hours per day. However, they track 8 hours, which is 60 minutes too much. Your condition states that anything over 20 minutes triggers an approval. |
| Break is shorter than break rule |
This refers to the Break rules setting in time tracking policies. Specifically, it refers to the break duration you’ve defined for a particular break rule. Example: You create a break rule that requires employees to take a 30-minute break after 6 hours of work. An employee tracks a 10-minute break after 6 hours, which is 20 minutes too little. Your condition states that anything shorter by 5 minutes triggers an approval. |
| Break start is later than break rule |
This refers to the Break rules setting in time tracking policies. Specifically, it refers to the number of hours worked before a break is required. Example: You create a break rule that requires employees to take a break after 4 hours of work. An employee tracks a break after 5 hours, which is 60 minutes too late. Your condition states that anything later than 20 minutes triggers an approval. |
| No break taken | This condition triggers any time the employee doesn’t track a break, regardless of their work schedule or time tracking policy settings. |
Add additional supervisors to an approval
If your organization uses additional supervisors, you can include them in approval workflows. Follow these steps:
- Create an attendance approval workflow as outlined above.
- In the trigger box, add a rule.
- Select the relevant additional supervisor attribute, and whether the workflow applies to employees with or without this attribute. Update your changes.
- In the approval box, add an approval step.
- Click From this workflow and select the relevant additional Supervisor attribute. Update your changes.
- Complete the setup and save or activate the workflow.
How approval workflows apply to time entries
Personio doesn't distinguish between a clock-in made using a shared device and a time entry added manually through the desktop or mobile app. From a technical standpoint, Personio treats them the same. This means there's only one approval process for all time entries. You either auto-approve everything, or everything goes through manual approval.
If you want to automatically approve clock-ins from a shared device while flagging manually added entries for review, two approaches work well together:
Restrict retroactive time entries
In your time tracking policies, you can limit how far back employees can log time. You can set this to zero days (no retroactive entries at all) or a specific number of days. This means if someone forgets to clock in, they cannot fix it themselves. Someone with Edit permissions for their attendance data needs to make the correction for them. It's not automated, but it creates a manual approval step for any entries employees don't clock in on the day.
Set up conditional automations
In Automations, you can create rules that only trigger an approval request under certain conditions. For example, a rule can trigger when an entry exceeds or falls short of the expected working hours. This way, normal entries pass through without interruption, while Personio flags anything that looks unusual for review.
Next steps
To check pending approvals, Administrators can go to the Automations > Activity tab. Find more details in the Monitor and manage workflows article.