Attendance settings have two levels: a general level for the whole company, and an individual level for each person. This article covers when to use the individual level — details on each option are in article B2-15.
Two levels
| Level | Where | Applies to |
|---|---|---|
| General | Time & Attendance › Settings › General | The whole company |
| Individual | Employee profile › Time & Attendance tab | One person |
Four situations where you should use individual settings
| Situation | What to turn on | Why |
|---|---|---|
| Field sales staff | Clock in from anywhere | Not tied to a fixed GPS point |
| Leadership, contract freelancers | No attendance tracking | Not recorded on the timesheet |
| Shift managers at sites where workers don't have smartphones | Allow clocking in on behalf of others + Require a face photo when clocking in on behalf of others | Solves a real problem, but must come with a verification layer |
| Positions with flexible hours | Allow late clock-in · Allow early clock-in | Working enough hours is what matters, not being tied to a shift window |
Allow clocking in on behalf of others is the option that requires the most careful consideration in the entire system. It exists for real situations, but enabling it for the wrong person opens the door to attendance fraud — exactly what the AI Camera was created to prevent. If you enable it, always enable Require a face photo when clocking in on behalf of others as well, and record the reason.
When a whole group needs the same settings
Don't edit each profile. Use Update attendance settings by file in HR › Create ▾ › Import file — see article B2-04. It's much faster and less error-prone than manually editing thirty profiles.
Principles
- Individual settings are the exception, not the default. The more exceptions there are, the harder it is to know why one person's timesheet differs from another's.
- Record the reason each time you set an exception. The profile's History tab records who changed what, but not why.
- Review periodically. When an employee changes position and an old exception remains, it becomes a silent loophole.
