Custom fields, no code required
Add real fields to any Odoo object in three clicks — guided type selection, group-level access control, reusable templates, and a full audit trail, built entirely on Odoo's own field mechanism.
Business teams constantly need one more field — a certification date, a buyer reference, a loyalty tier — but adding it means waiting on a developer, wrestling with a flat list of 15+ cryptic field types, or hand-building a throwaway module that nobody tracks afterward.
A guided builder that creates real, native Odoo fields on any object, locks down visibility by security group, and drops the field onto the form automatically — with every creation, change and deletion logged for compliance.
Everything a business user needs to extend Odoo
Every capability below is implemented in the module.
Add Fields to Any Object
Create a field on Contacts, Users, or any other Odoo model in three steps: pick the object, enter the name and type, confirm. No XML, no developer.
Guided Field-Type Selector
Choose from text, rich text, number, checkbox, date, date & time, selection dropdown, link to one record, and link to many records — described by what they do, not by cryptic technical names.
One-Step Access Control
Restrict any field to specific security groups right on the creation screen — Finance, HR, or a custom group — so access is locked in from the first save.
Reusable Field Templates
Apply ready-made presets — Contact Extended Details, Compliance & Certification, People Data — to any object in one click, then customize each field as needed.
Field Property Toggles
Mark any field Required, Readonly, or Copied to duplicated records directly on the creation screen — the Odoo fundamentals several competitors leave out.
Conditional Visibility
Show or hide a custom field based on other field values with a visibility domain, so forms stay relevant instead of cluttered.
Automatic Form Placement
New fields are dropped onto the object's form view in a dedicated Custom Fields group automatically — no view XML to write or maintain.
Full Audit Trail
Every field created, modified, or deleted is logged with who, what and when — the log survives even after the field itself is removed, for audits and compliance reviews.
Native Behavior, Full Reporting
Fields are built on Odoo's own manual-field mechanism, so they behave exactly like native fields — searchable, filterable, groupable and reportable, everywhere.
How it works
Pick the Object
Choose which Odoo model — Contacts, Users, or any other — needs a new field.
Configure & Restrict
Set the name, type, properties, visibility domain, and the groups allowed to see it.
Create the Field
Confirm and the field goes live — on the model and on the form — in one click.
Track & Reuse
Every change is logged automatically; save the setup as a template to reuse elsewhere.
See it in action
Real screens from the module, captured on Odoo 17.
Every custom field definition in one list, across objects, with state badges for Draft and Created.
A selection field ("Loyalty Tier") in the Created state, showing its options, properties, and access groups.
A draft text field before creation, with the Create Field button and visibility-domain editor.
Ready-made templates: Contact — Extended Details, Compliance & Certification, and People Data.
The Contact — Extended Details template with its three field lines, ready to apply.
Apply a template to any object in one step through a guided wizard.
The audit log, mixing Created and Modified entries across Contacts and Users.
A Contact form showing custom fields automatically placed in their own group, populated with real values.
Frequently asked
Do the fields it creates behave like real Odoo fields?
Yes. Every field is created through Odoo's own manual-field mechanism, so it is searchable, filterable, groupable and reportable exactly like a native field.
Can I control who sees a field?
Yes. Each field can be restricted to one or more security groups on the same screen where you create it, so visibility is locked in from the start.
What happens to the audit log if I delete a field?
The log entries stay. Each entry records the model and field name at the time of the action, so the history survives even after the underlying field is removed.
Can I reuse the same set of fields on multiple objects?
Yes. Save a set of fields as a template and apply it to any object in one step through the Apply Template wizard, instead of recreating fields from scratch each time.
Get in Touch
Have questions or need help configuring a field or template? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Explore our other apps
A growing suite of Odoo apps.
Empowering growth through technology.
Add real, native custom fields to any Odoo object — guided, access-controlled, template-driven, and fully audited.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 745 |
| Technical Name |
cerevantix_custom_fields |
| License | OPL-1 |
| Website | https://www.cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module