In a growing finance team, everyone with accounting rights can see and post to every journal. A junior AR clerk can raise vendor bills against the bank journal; a purchasing user can open sensitive payroll or intercompany entries; a branch bookkeeper can reconcile a bank they should never touch. Odoo's out-of-the-box accounting security is coarse — the account.group_account_user and account.group_account_manager groups grant near-blanket access to account.move and account.journal, and there is no native "this person may only work in these journals" control per user. Once entry volume and headcount grow, that gap becomes an audit finding and a fraud surface, not just an inconvenience.

We build a dedicated journal-restriction layer on top of Odoo's own security model rather than bolting on a fragile UI filter. The core is a many-to-many link between res.users (or a configurable account.security.role you assign to users) and account.journal, enforced by ir.rule record rules on account.move, account.move.line, account.payment, and account.bank.statement. Because the restriction is evaluated by the ORM inside record rules, it holds everywhere — form and list views, the reconciliation widget, the invoicing dashboards, XML-RPC/JSON-RPC API calls, scheduled/automated actions, and QWeb reports alike — not just on the screens we happened to patch. A restricted user simply never sees a document in a journal they aren't entitled to, and cannot post one there either.

Technically, the module ships as a proper Odoo addon: a versioned __manifest__.py declaring dependencies on account, security defined in ir.model.access.csv plus data-file ir.rule records, a small model layer (models.Model with the journal-access fields and a compute/@api.depends helper that resolves a user's effective journal set from their roles), and OWL/XML views to manage the mappings from Settings. We add a check_journal_access() guard invoked on create/write of account.move so a blocked write fails loudly with a clear AccessError rather than silently, and an optional automated action that alerts an administrator when access is denied. We honor mail.thread audit logging on the access-role model so every change to who-can-touch-what is tracked. Multi-company deployments get company-aware rules that intersect journal access with the user's allowed companies; Community and Enterprise are both supported, with Enterprise-only touches (like the accounting dashboard) handled when present.

Delivery is build-to-order: you request a quotation, we run a short scoping call to confirm your journals, roles, company structure, and edge cases (default journals on sales/purchase, POS and bank feeds, existing custom security), then we build, test on a staging copy, and install on your Odoo. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company intersection rules, deeper localization, integration with existing custom accounting security, and data migration of historical assignments increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise.