Disable Developer Mode — Restrict & Audit Debug Access
by Cerevantix Technologies https://cerevantix.com$ 39.00
Developer mode, restricted at the source, not just hidden
Give only the right people access to Odoo developer/debug mode. Close the classic ?debug=1 URL bypass on the server, warn everyone else clearly, and keep a full audit trail of every attempt.
Every other developer-mode restriction on the market hides the debug icon or toggles a per-user flag in the UI — but leaves the ?debug=1 URL parameter wide open. Any user who knows or guesses the URL bypasses the restriction entirely, silently undermining change control and leaving administrators with no record of who tried, when, or whether it worked.
This module closes the bypass at its source by overriding Odoo's own debug-mode entry point on the server, not just in the browser. Only users in an authorized group can activate developer mode — via menu, bookmark, or URL parameter. Everyone else sees a clear warning instead, and every attempt, allowed or denied, is written to a permanent audit log.
Everything you need to lock down debug access
Every capability below is implemented in the module.
Closes the URL Bypass
Overrides Odoo's server-side debug handler directly, so ?debug=1 in the address bar, bookmarks, and the Settings link are all blocked the same way — not just hidden in the interface.
Group-Based Authorization
Grant developer/debug access to a dedicated security group. Anyone outside that group is denied, regardless of their other permissions.
Clear Warning for Restricted Users
Unauthorized users see a clear, editable warning message instead of a confusing failure, so they understand why debug mode did not activate and who to contact.
Full Access Audit Log
Every developer-mode attempt, allowed or denied, is written to a permanent log with the user, timestamp, and outcome — the compliance trail no competitor provides.
One-Toggle Enforcement
Turn the restriction on or off from Settings, see the current count of authorized users at a glance, and jump straight to the audit log from the same screen.
Administrators Always Retain Access
Break-glass access is built in: system administrators are never locked out of developer mode, even if the authorized-group configuration changes.
Hides the Native Debug Widget
The stock Odoo "Activate developer mode" control in Settings is hidden from unauthorized users, so there is no dangling shortcut left behind in the interface.
How it works
Assign the access group
Add trusted users to the developer-mode access group from Settings.
Enable enforcement
Turn on the restriction and customize the warning message shown to everyone else.
Users work as normal
Authorized users activate debug mode as usual; everyone else is stopped with a clear message, including on ?debug=1 links.
Review the audit trail
Open the access log anytime to see every allowed and denied attempt, by user and by date.
See it in action
From the audit log to the settings screen, every part of the restriction is visible and reviewable.
Every developer-mode attempt is logged, with denied and allowed rows clearly decorated for fast scanning.
Drill into any log entry to see the user, timestamp, and outcome of a specific developer-mode attempt.
Toggle enforcement, edit the warning message, see the authorized-user count, and open the access log — all from Settings.
A restricted user hitting ?debug=1 gets a clear warning toast instead of silent failure or unrestricted access.
Frequently asked
Does this stop the ?debug=1 URL trick that other apps miss?
Yes. The restriction is enforced on the server by overriding Odoo's own debug-mode handler, so the URL parameter, bookmarks, and the Settings link are all blocked identically — not just hidden with CSS or JavaScript.
Can administrators get locked out?
No. System administrators always retain developer-mode access as a built-in break-glass safeguard, independent of the authorized-user group configuration.
Where can I see who tried to access developer mode?
Every attempt, whether allowed or denied, is recorded in a dedicated audit log with the user, date, and outcome, accessible directly from the Settings screen.
Will restricted users understand why they were blocked?
Yes. They see a clear, editable warning message explaining that developer mode is restricted, instead of a confusing error or silent failure.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Restrict developer/debug mode to an authorized group, close the ?debug=1 URL bypass, and keep a full audit trail of every attempt.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 294 |
| Technical Name |
cerevantix_disable_developer_mode |
| License | OPL-1 |
| Website | https://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