Ir Actions Report Multi Company
Make Report Actions multi-company Aware.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Lets you assign report actions to a specific company, so each company only sees its own reports (plus shared ones).
This module makes report actions company-aware. On the report action form (the screen where a PDF or paper report is configured), a new Company field appears right after the report name, so you can link a report to one company or leave it empty to share it with all companies.
A global record rule is added on report actions: a user only sees reports whose company is empty or belongs to the companies currently selected in the company switcher. This keeps reports from one company out of the way when working in another.
When Odoo builds the list of reports available on a document (for example the print menu on a sales order or invoice), it now filters them by the active companies. It also keeps the existing checks: reports restricted to user groups are only shown to members of those groups, and reports are hidden if the user has no read access to the underlying model.
The module touches the report action model ir.actions.report and the generic actions model ir.actions.actions, and adds a security rule on report actions. No new menus are created; the change is visible directly in the report configuration form and in the print/report menus of documents.
Depends on
Models and fields (2)
- ir.actions.report · extends an existing modelcompany_id
- ir.actions.actions · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/multi-company.
terminal Installation and usage
OCA documentation · Odoo 16.0Usage
Source · Odoo 16.0The usual multi-company record rule is installed automatically.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.