One button for time and activity
Start tracks both together, the way people work — not two switches nobody remembers to flip. A global shortcut (Ctrl+Alt+T) starts and stops it without hunting for the window.
Features
Everything it does. Not a shortlist.
Zeetavix WorkOS is Odoo employee time tracking that writes its own records: automatic Odoo timesheets, attendance automation, focus and activity reports, project budgets and evidence trails — all self-hosted on Odoo Community. No tiers gate any of this off — every plan gets every feature on this page, and the only thing price changes is how many people you are tracking. Where something is not built yet, it says so.
Before the list
This is what the list adds up to.
Three of the twenty-five screens, from a running install. The guide walks through all of them.
Automatic Odoo timesheets — time that records itself
The part people actually feel: nobody reconstructs their week from memory, and nobody has to remember to press anything. How Odoo automatic timesheets work, end to end.
Timesheet lines written for you
The moment a timer stops, a real Odoo timesheet line appears on the right project and task. Not an export, not a separate tool — Odoo’s own timesheets, filled in.
AI writes what the work was
Each line gets a description generated from the work behind it, on a background queue. Queued deliberately: nobody should wait on a model to finish before their timer stops.
Attendance without a punch clock
Clock-in and clock-out derived from when real work started and stopped, feeding Odoo’s own attendance records. No forgotten punches, no Monday-morning corrections.
Odoo employee activity tracking — understanding the work, not just counting it
Hours are a poor description of knowledge work. Four uninterrupted ninety-minute blocks and eight hours cut into forty fragments are the same number on a timesheet and completely different days.
Work episodes, not raw events
Thousands of window switches roll up into episodes — continuous stretches of one kind of work. It is the unit a person can read, and the only unit AI can reason about usefully.
Focus reports, judged by role
Deep blocks, longest stretch, switch rate, meeting load — measured against a threshold learned from that role’s own history. A support day of forty switches is the job being done well; an engineering day of forty is a conversation worth having.
Role-aware from the ground up
LinkedIn is the job in marketing and a distraction in engineering. Classification resolves per application, per role and per project, most specific first, and every answer carries the rule that produced it.
Meetings and AI work understood
A two-hour call is not idleness, and prompt-wait-read-accept is dense senior work that produces almost no keystrokes. Both are detected and reported separately rather than scored as absence.
Active, passive or away
Not a keystroke score. Reading a spec is passive — which every other tracker collapses into “idle” and every manager then reads as “gone”. Mouse movement earns nothing, so a jiggler scores zero.
Daily insights and anomaly flags
A productivity figure per person per day, days that look unlike that person’s own normal flagged for a look, and a plain-language summary of what happened.
Odoo team time tracking — the team, at a glance
One screen, instead of asking six people how their week went.
Team dashboard
Everyone’s hours today and this week, activity, who is online right now, and a breakdown by department — a real Odoo backend app, not a webpage bolted on beside one.
Leaderboard and daily achievements
Recognition built from real contribution rather than from who is loudest in standup. Quiet people who deliver stop being invisible.
Weekly limits and low activity
Who is over their weekly hours and who is under, surfaced early enough to act on — including spotting the person quietly working themselves into the ground.
A morning AI briefing
A few sentences on what changed: which projects are drifting, where the week went, what is worth a look. Generated by your own AI, on your own server.
Odoo project time tracking and budgets
Hours only matter once they are attached to something that costs money.
Attributed to real projects and tasks
Tracked work is resolved onto Odoo’s own Projects and Tasks as it arrives, so nothing needs re-filing later.
Budgets in real money
Time and cost budgets per project, moving as hours land. A project going over is something you notice in week two rather than at invoicing.
Timesheet evidence trails for Odoo — for the month you need it
Most months nobody opens any of this. The month a client disputes an invoice, it is the only thing that matters.
Screenshots at full detail — or blurred
Your choice, per deployment. Full detail is readable evidence; blurred keeps the application and layout recognisable while no text survives. Nothing in between, because a blur weak enough to leave text readable protects nobody while looking as though it does.
Retention you set, enforced automatically
Images are deleted on a schedule you choose — ninety days by default. The events themselves stay, so history and evidence trails stay intact. Only the pictures go.
Every line can produce its work
Open a timesheet line or an attendance record and see the episodes, activity and screenshots behind it. That is the difference between “our tracker says so” and an actual answer.
Self-hosted AI for Odoo time tracking — on your own terms
Every other tracker sends your team’s work to a model you did not choose, through a company you do not control.
Local, with Ollama
Run a model on your own hardware and nothing leaves the building at all. Not a promise about data handling — there is simply no outbound request.
Or your own key
OpenAI, Claude, Gemini or OpenRouter, called directly by your Odoo. We never see the key, the prompts or the answers, and we add no markup to the tokens.
Never in the way
All AI work runs on named background queues with their own retries and rate limits. A slow model makes a summary late; it never makes the product hang.
Odoo time tracker apps for Windows, macOS and Linux
A tracker that stops when the wifi does is not a tracker. This is built to be the boring, reliable part — the piece that puts time tracking on your Odoo Community server.
Works offline, indefinitely
Work is written locally and queued. When the network returns it drains on its own schedule with backoff. A day on a train loses nothing.
Encrypted on disk
The local database — observations and screenshots — is encrypted with a key held in the operating system’s own credential store. If that store is unreachable the agent refuses to start rather than quietly writing plaintext.
Sign in with Odoo
No second password and no embedded credentials. The agent sends the person to your own Odoo to approve the device, and waits for exactly one callback.
Windows today; macOS and Linux next
Window, activity and idle collection are Windows-only in this release. Screenshots and system information already work everywhere. Said here rather than discovered after buying.
Self-hosted Odoo time tracking — yours, not ours
The whole product runs inside the Odoo you already host. That is not a policy — it is the architecture. More on self-hosted employee time tracking.
Odoo Community is enough
No Enterprise licence required. If you already run Enterprise, this sits alongside it with nothing to migrate.
Nothing is sent to us. At all.
Not your data, and not a licence check either — that hourly call went when the subscription did. Your installation makes no request to Zeetavix of any kind, because there is no endpoint left to call.
Stop paying, keep everything
Tracking stops. Every timesheet, screenshot and report already in your Odoo stays exactly where it is. There is no export to request and no account to close.
See it running on your own Odoo.
$149 once, on the Odoo Apps Store. Unlimited users.
Get it on the Odoo Apps Store