Odoo attendance without a button.

How work start and stop become attendance

The desktop tracker records when real activity begins and ends; your Odoo turns the first and last genuine work into the day's attendance pair. Because the record comes from observed work rather than a pressed button, a six-hour day made of twelve fragments does not read the same as one long morning — the shape is in your own day, and the mechanism is in how Odoo automatic time tracking works. Attendance is one output of the same record that also writes automatic timesheets.

Limitations, stated plainly

Attendance is only as complete as the tracked work behind it. If someone never starts the tracker, no record is invented — the gap stays visible instead of being silently filled, which is the honest failure mode. Meetings, phone calls and AI-assisted spells with little keyboard input are handled as low-input work rather than absence (see the mechanism), but a day entirely away from the machine is a day with no derived attendance. That is by design: derived attendance describes work at the machine, and anything else belongs in Odoo as leave or a manual entry.

Corrections and administrator controls

Records are Odoo's own attendance entries, so managers correct them exactly like any attendance — no separate console, no export-and-fix loop. Administrators control the inputs that shape derivation: what counts as work via classification rules and work profiles, how long samples and diagnostics are kept via retention and privacy settings, and whether screenshots exist at all. Manual edits leave an audit trail in the reports.