This module extends the export capability:
- It allows an admin to manage export profiles (ir.exports) that Odoo stores internally but does not show anywhere.
- It also adds a new column to access rights to enable/disable export and override the export method to check if the user is allowed to export. Export is enabled by default.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Lets administrators create and manage reusable export profiles for any Odoo model, and control per access-right whether users are allowed to export records.
This module makes the export profiles that Odoo stores internally visible and manageable. A new "Export Profiles" menu appears under the Settings area, where you can list, create and edit profiles for any database model.
On a profile you choose the model and then build the list of columns to export. Each line can go up to four levels deep through relational fields (for example customer/country/name), and the module automatically shows a friendly column label and the technical field path. It checks that fields exist, prevents the same field being added twice, and refuses more than four levels.
It also adds an "Export Access" checkbox to access rights. This checkbox appears in the model access list, the access-rights form, the model form and the group form. Export is allowed by default. When a user does not have export access on a model, the Export button is hidden in list views for that model (system administrators are not restricted).
The module touches ir.exports, ir.exports.line, ir.model.access, res.users, ir.model and ir.http, and includes a small list-view behaviour change so the export button respects these permissions.
Depends on
Menus it adds
Models and fields (5)
- ir.http · extends an existing model
- res.users · extends an existing model
- ir.exports · extends an existing modelname, model_id, resource
- ir.exports.line · extends an existing modelname, label, sequence, field1_id, field2_id, field3_id, field4_id, model1_id, model2_id, model3_id, model4_id
- ir.model.access · extends an existing modelperm_export (Export Access)
Text generated by AI (DeepSeek) from reading the Odoo 19.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: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/server-ux.
terminal Installation and usage
OCA documentation · Odoo 19.0Configuration
Source · Odoo 19.0- Activate the developer mode
- Go to Settings \> Users \> Groups to select a user group
- Edit the group and go to the Access Rights tab
- Uncheck the "Export Access" box on the object of your choice and save
You can also go to Settings \> Technical \> Security \> Access Rights.
Usage
Source · Odoo 19.0You can create the export profiles as you are used to:
- Go to any list view.
- Check some records.
- Click Action \> Export.
- Use the wizard to choose the columns to export.
- Click on the Template dropdown and select New template
- Give it a name.
- Click on the floppy disk icon to save it.
To manage export profiles, you need to:
- Go to Settings \> Technical \> User Interface \> Export Profiles.
- Create a new one.
- Choose a name.
- Choose a model (table in the database).
- Choose the fields to export.
- If you choose a related field, you can choose also up to 4 levels of subfields.
- You can drag & drop to reorder the fields.
To use one of those profiles, you need to:
- Go to any list view.
- Check some records.
- Click Action \> Export.
- Choose your saved export from Saved exports.
- Press Export to file.
Once you have configured groups who cannot export an object:
- Connect as a user of this group
- Go to the list view of the object you disabled the export
- Select records and open the Action menu. The "Export" is not there.
No verified information in OCA: Installation.
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.