| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 2134 |
| Technical Name |
simplified_access_management |
| License | OPL-1 |
| Website | https://www.subisoft.in |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 2134 |
| Technical Name |
simplified_access_management |
| License | OPL-1 |
| Website | https://www.subisoft.in |
Simplified Access Management Studio
Complete user access control for Odoo 18. Hide menus, fields, buttons, reports and restrict model operations — all managed from one dedicated app.
01. Menu / Sub-menu Rules
Hide any top-level or sub-level menu for specific users or groups. Applied server-side — hidden menus are never sent to the browser at all.
- Hide Sales, Purchase, Inventory, HR or any app menu
- Hide sub-menus within any application
- Apply by Specific Users or User Groups
- Server-side via
load_menus()override - Changes take effect immediately on next page load
02. Field Access Rules
Control field visibility and editability at the server level. Works in form views, list views, kanban views, and even quick-create popups.
- Hide Field — completely removed from view arch
- Read-Only — visible but not editable
- Make Required — field becomes mandatory
- Select fields from dropdown (no technical names)
- Server-side via
postprocess_and_fields() - Works inside view cache — cannot be bypassed
03. Model Access Rules
Restrict what users can do with records. From disabling a single action to making an entire model read-only with one toggle.
- Disable Create — removes New button
- Disable Edit / Write — form becomes read-only
- Disable Delete — records cannot be removed
- Disable Archive / Unarchive
- Disable Duplicate
- Disable Export
- Make Model Read-Only — all of the above at once
- Domain Filter — restrict which records are visible
04. Global Access Rules
Apply restrictions that span the entire Odoo interface — not model-specific. One rule controls the user's entire session.
- Read-Only User — full interface lockdown
- Disable Developer Mode access
- Disable Login — lock user out completely
- Hide Import button in all list views
- Hide Export button in all list views
- Hide Duplicate / Archive from cog menu
- Hide Filters and Group-By in search bars
- Restrict Script / XMLRPC Access
- Restrict Module Install / Uninstall / Upgrade
05. Report Access Rules
Remove specific reports from the Print menu in the cog dropdown. Hidden at the server level before the menu is built.
- Select reports from a dropdown — no technical names
- Hidden reports never appear in Print submenu
- Server-side via
get_bindings()override - Option to hide the entire Reporting menu
- Apply per user or user group
Button / Tab Rules
Hide or make read-only any button or tab in a form view. Buttons are auto-discovered from the model's form view — just pick from a dropdown.
Chatter Access Rules
Control chatter visibility per user. Hide Send Message, Log Note, Schedule Activity, entire Chatter section, or Followers widget.
Company-Wise Scoping
Every rule supports company-wise restrictions. Perfect for multi-branch or multi-company Odoo deployments.
User Groups Support
Target restrictions by Specific Users or User Groups. Changes to a group automatically apply to all its members.
Instant Cache Invalidation
Saving a rule automatically clears all relevant caches. No restart required — restrictions apply on the very next page load.
Login Lock
Disable a user's ability to log in entirely — without deleting the account. Useful for seasonal or contract staff.
Field Hiding — postprocess_and_fields()
Overrides the lowest-level view processing method. Runs inside the view cache — patches are stored and served with the arch. Works in form, list, quick-create, and dialog views.
Menu Hiding — load_menus()
Overrides the server method that builds the navigation tree. Hidden menus are never included in the JSON response — not just CSS-hidden. Handles both dict and list formats (Odoo 18).
Report Hiding — get_bindings()
Overrides the method that populates the Print submenu in the cog dropdown. Filtered at the SQL level before the response is built.
DB-Level Rule Filtering
Rules are filtered using SQL joins on user_ids and group_ids — not Python loops. Scales to hundreds of rules and thousands of users without performance degradation.
Session Context Injection
TAM context is injected into session_info and also available via /tefugen/access/context RPC. Fetched fresh on every navigation — always up to date.
MutationObserver JS
Catches dynamically rendered buttons, dropdowns, and cog menu items. Handles Odoo's OWL component lifecycle — elements hidden as soon as they appear in the DOM.
Ready to Control Your Odoo Access?
Install once. Configure rules from the dedicated Access Management app. No code changes needed.
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