| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 111 |
| Technical Name |
ma_user_field_visibility |
| License | OPL-1 |
| Versions | 18.0 19.0 |
Your Odoo views show every field to every user, cluttering screens with data that is irrelevant or sensitive for certain roles.
User Field Visibility Control
What this module does
User Field Visibility Control lets administrators hide any field on any model for a specific user, across every view type including form, list, and kanban. Configuration takes seconds: open the user record, go to the Hidden Fields tab, pick a model, select one or more fields, and save.
Without this module, hiding fields for individual users requires writing custom view overrides per role or per user, which is fragile and hard to maintain. This module makes it a single admin action with no code and no module updates needed.
|
🔒
Per-User Field Control
Hide any field on any model for a specific user. Rules are independent per user and stack without conflict. |
👁
Works Across All Views
One rule hides the field in form, list, and kanban views. No separate configuration per view type needed. |
⚙
Admin-Only Interface
The Hidden Fields tab is visible only to System Administrators. End users never see the configuration. |
|
🏷 Multi-Field Selection
Pick multiple fields per model in one row using tag-style input. No need to add a separate row for each field. |
⚡ Instant Effect
Changes apply on the user's next page load. No server restart or cache clearing needed. |
|
📦 Base Only Dependency
Depends only on the base module. Works on Community and Enterprise with no extra installs. |
🛡 Safe Bootstrap
Built-in guard prevents any processing loop on meta-models during installation or upgrade. |
How it works
| 1 | Go to Settings > Users & Companies > Users and open any user record. |
| 2 | Click the Hidden Fields tab (visible to System Administrators only). |
| 3 | Click Add a line, select a Model, then pick one or more fields from that model using the tag input. |
| 4 | Save. That user will no longer see those fields in any view, across the entire Odoo instance. |
Screenshots
Hidden Fields Tab on User Form
Field Hidden in Form View
Column Hidden in List View
Technical information
| Technical Name | ma_user_field_visibility |
| Version | 19.0.1.0.0 |
| License | OPL-1 |
| Compatibility | Odoo 19 Community & Enterprise |
| Dependencies | base |
| Models Added | user.hidden.field |
| Models Extended | res.users, base (get_view) |
Need Help?
Questions, customization requests, or bug reports. We respond fast.
muneeb76834@gmail.com · Response within 1-2 business days
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