The treasurer's dilemma: when total visibility becomes a risk
Imagine Carlos, finance manager at a manufacturing company with several branches. Each branch manages its own bank accounts in Odoo, but Carlos noticed something worrying: his main treasurer could see all movements in all accounts, including those of branches he did not supervise. This was not about distrust, but a basic security principle: why should a team member access information they do not need for their work? This unnecessary exposure created operational risks and vulnerabilities. Carlos needed a solution that would let him precisely define which accounting journals each user could see, without complicating daily processes. This situation is more common than you think, and today we will show you how to solve it.
The missing security layer: advanced permissions per journal
Accounting journals in Odoo group critical financial movements: sales, purchases, banks, cash. By default, users with basic accounting permissions can see all journals, but this is not always appropriate. The advanced Journal Access Control feature adds an extra layer of permissions on top of the base permissions, letting you restrict access to specific journals per user or per group. This means you can keep your company's general permissions structure while adding granular restrictions where they matter most.
Applied example: At Carlos's company, they decided that branch supervisors would only see the bank journals of their own branch. They created a "North Branch Supervisor" group and assigned that group only to the corresponding bank journal. When a new supervisor joined that branch, they simply added her to the existing group. She automatically could see her branch's journal without any extra configuration on each journal. Carlos, working with Ganemo, implemented this solution in one afternoon, taking advantage of the fact that the Journal Access Control module is included for free in their maintenance plan.
Step-by-step setup: from administrator to end user
The crucial first step is making sure the administrator user can manage these permissions. Under Advanced Settings > Security, enable the "Has access to all journals" option for the user who will configure the restrictions. Only then can you edit the "Assigned Users" and "Allowed Groups" fields on each journal. The interface is clear: if the fields are empty, any user with base accounting permissions can see that journal. When you add users or groups, access is automatically restricted to them only.
Applied example: Laura, systems administrator at a services firm, needed her accounting assistant, Marco, to see only sales and operating expense journals, but not investment or loan journals. She enabled his administration permission, went to the investments journal and, under "Assigned Users", added only the CFO. Then, on the sales journal, she added Marco. When Marco logged in, he only saw the journals he was allowed to see. Laura highlighted how intuitive the process was: Ganemo not only provided the tool, but its design prevents common security configuration mistakes.
The cascade effect: beyond the dashboard
The real power of this setup is not only in filtering which journals appear on the dashboard, but in limiting which records can be seen across the entire platform. When a user does not have access to a journal, they also cannot see the invoices, payments, entries or journal items associated with it. The only logical exception is payments linked to invoices they do have access to, maintaining consistency in processes. This creates a secure environment where sensitive information is naturally isolated.
Applied example: A hotel chain implemented this feature to separate the operations of its different properties. Each hotel manager only had access to the journals of their property. When the Hotel Costa manager opened the vouchers register, they did not see the invoices of Hotel Montaña, even though they technically had general accounting permissions. This let them delegate responsibilities without exposing information between properties. The implementation was guided by Ganemo, who adapted the solution to their multi-company structure in Odoo.
From theory to your company: how to access this feature
This granular control capability is not a standard feature in every Odoo implementation, but it is available through the Journal Access Control module. If you are already a Ganemo client with active maintenance, this module is included at no extra cost. You just need to install it from Apps and start configuring. The interface is the same as we showed: intuitive, with clear help messages that prevent confusion. For companies that are not clients, the module is available in the Odoo app store, with special discounts for members of the Ganemo communities.
Applied example: A fast-growing tech startup expanded its finance department. The founder, concerned about keeping control while delegating, contacted Ganemo to implement Journal Access Control. In two days, they had differentiated permissions configured for: general accountants (full access), cost analysts (expense journals only) and collections assistants (sales and bank journals only). The founder commented: "It was like installing secure doors in a building that used to be open. Our team has what it needs to work, without unnecessary risks."
Turn visibility into controlled security
Access control over accounting journals goes beyond a technical setting; it is a proactive security strategy. By implementing these restrictions, you not only protect sensitive information, but also clarify responsibilities and reduce operational risks. The solution is flexible enough to suit everything from SMEs to large corporations, and implementing it with Ganemo ensures it works in harmony with the rest of your Odoo ecosystem. Ready to transform how your users interact with financial information?