Studio Access Guard
by Odoo DevHouse https://apps.odoo.com/apps/modules/browse?author=Odoo%20DevHouse$ 24.99
In-App Purchases| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Studio (web_studio)
• Discuss (mail) |
| Lines of code | 48 |
| Technical Name |
hide_studio_button |
| License | OPL-1 |
| Website | https://apps.odoo.com/apps/modules/browse?author=Odoo%20DevHouse |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Studio (web_studio)
• Discuss (mail) |
| Lines of code | 48 |
| Technical Name |
hide_studio_button |
| License | OPL-1 |
| Website | https://apps.odoo.com/apps/modules/browse?author=Odoo%20DevHouse |
| Versions | 18.0 19.0 |
Hide Studio Button Access
This Odoo module provides administrators with the ability to restrict access to the Studio button in the top navigation bar, allowing better control over Odoo Studio customizations and preventing unauthorized users from modifying your system's interface and logic.
- Group-based Restriction: Easily control which user groups can see and access the Studio button
- Override Default Behavior: Restrict Studio access even from users with "Administration: Settings" rights
- Enterprise Compatible: Works seamlessly with Odoo Enterprise's Studio feature
- Non-Intrusive: Simply hides the button - no functionality is broken, just access control
- Easy to Configure: Simple group assignment through Odoo's standard user interface
Odoo Behavior
In Odoo, all users with the "Administration: Settings" configuration can see and access the Studio module by default. This includes the "Toggle Studio" button in the top navigation bar. While this is useful for administrators who need to customize the system, it can pose risks in production environments where accidental or unauthorized modifications could disrupt business processes.
This module offers enhanced control over Studio access by allowing administrators to restrict it even for users with the "Administration: Settings" right. By assigning users to the "Hide Studio Button" group, companies can ensure stricter governance over customizations and minimize the risk of unauthorized changes to views, reports, and business logic.
How to Use
Assign the Group
Under the "Access Rights" tab, check the "Hide Studio Button" option.
Unassign the Group
Under the "Access Rights" tab, uncheck the "Hide Studio Button" option
Before Module Installation
Studio button visible for users with Settings rights
After Module Installation
Studio button hidden for restricted users
Do You Need Assistance or Have a Feature Request?
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