attendance_add
Write one attendance record, a clock-in or clock-out, at the moment it actually happened.
| Namespace | attendance |
|---|---|
| Effect | workspace_write |
| Approval | not required |
| Presence | not required |
| Privacy | workspace_attendance |
| Version | v4 |
What the model reads
Write one attendance record, a clock-in or clock-out, at the moment it actually happened. Omit date and time for right now, which is what somebody clocking in as they arrive means. A person writes their own record from the last three days and it goes in at once, with status added and its eventID. A press right now that reverses the one before it within a minute, clocking back in at the same place or clocking straight out again, takes that earlier record back instead of adding one: status removed, eventID names the record taken back, and that is a finished answer too. A clock-in right now while a shift is still open clocks that shift out at the same moment before the new one starts, so moving to another place ends one shift where the next begins. Reaching further back is an administrator's to write, for anybody. Asked by anybody else it comes back with status asked and no eventID, and the administrators have already been told what was asked for: that is a finished answer and the task is done. Say an administrator was asked and leave it there; do not call this again. A moment in the future is refused. location names a work location this company has registered and clock_out does not use it. reason says why a record is being written by hand, and is kept when given, never demanded.