When an auditor or your CISO asks "who accessed the payroll records last quarter and what did they change?", most Odoo teams find there is no straight answer. Odoo core keeps create_date, write_date, and create_uid/write_uid on each record, and res.users.log notes the last connection — but there is no queryable login history, no failed-login trail, no record of reads, and no field-by-field before/after picture of a change. The mail.thread chatter only tracks fields you flagged with tracking=True, lives inside each record rather than in a security log, and can be edited by anyone with write access. It says nothing about who merely viewed a sensitive contract or salary. For regulated or sensitive data, that gap is exactly where compliance findings come from.

Access Audit & Login Monitor is a build-to-order Odoo application that closes the gap. We build a dedicated login-history model that captures every authentication attempt — user, source IP, device/user-agent, method (password, SSO/OAuth, or 2FA), and success/failure — by hooking the authentication and session lifecycle in base and web rather than scraping server logs after the fact. Failed attempts are counted against configurable thresholds, so brute-force patterns fire an admin alert email through an ir.cron sweep and Odoo's mail.mail / automated-action layer. On top of that we add field-level change auditing on the models you select: each monitored write records the old value, the new value, the author, and the timestamp, and per-model toggles for create/read/write/unlink let you log only the events compliance actually requires — read logging, the heaviest event, stays off until you switch it on for a truly sensitive model like payroll or contracts.

Technically, the module is a clean-room build: a small set of models.Model classes for the log entries, ORM overrides and a lightweight registry that intercept the audited operations, ir.model.access.csv plus record rules that make the audit records append-only (no write, no unlink — even admins cannot quietly rewrite history through the UI), and OWL/XML views plus QWeb templates for the dashboard, active-session viewer, and exportable reports. Suspicious-login flagging (new country/IP, impossible travel, off-hours access) is computed against a user's baseline and surfaced on the dashboard. The active-session viewer integrates with Odoo's session store so you can force-logout any single user or terminate all sessions with one click. A scheduled retention purge removes records older than your configured window, and every access event can be pushed to your SIEM or security mailbox via an optional webhook, daily email digest, or the standard XML-RPC/JSON-RPC API. Filterable CSV/PDF reports let auditors slice by user, model, or date range.

Because this is made to order, nothing ships until we agree the scope. After a short scoping call we confirm your target version and edition (17.0, 18.0, or 19.0, Community or Enterprise — SSO/MFA capture differs between editions), the exact models and events to audit, retention and alert policy, and any SIEM integration. We then build on a staging copy of your database, run UAT with you, and install to production with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); wider multi-company or multi-database coverage, additional audited models, deeper localization/regulatory mapping, and SIEM/webhook integration depth increase the quoted scope.