Skip to Content

How to Block Buttons in Odoo Without Breaking Permissions? The Definitive Solution for Granular Control

Discover how to overcome the frustration of binary permissions in Odoo and gain precise control over every action your users can perform in the system
December 28, 2025 by
How to Block Buttons in Odoo Without Breaking Permissions? The Definitive Solution for Granular Control
Wilfredo Fernando Pastor Avila
| No comments yet

The Sales Manager's Frustration: When Permissions Are Too Generous

María, sales manager at a distribution company, faced a recurring dilemma. Her sales team needed full access to the sales module to create and manage orders, but she had discovered that several salespeople were cancelling confirmed orders by "mistake". The problem: in standard Odoo, if a user has permissions for sales, they automatically have access to the Cancel button. There was no way to let them work in sales while specifically blocking that dangerous action. Every cancellation meant hours of lost work and dissatisfied customers. This situation is common in companies that, like María's, find that Odoo's binary permissions can be too rigid for real business needs.

The Concept: Granular Permissions Beyond Standard Groups

The solution is not to modify Odoo's native permission groups, but to work on top of them with an additional layer of control. Imagine being able to define specific rules per user about which buttons they can see and which remain hidden, keeping the system's original security structure intact. This is especially valuable when, as with Ganemo, we implement solutions where each client has unique access control needs.

Practical Example: At María's company, we implemented a simple rule: for her sales team, hide the Cancel button on sales orders. The setup took less than 5 minutes. We selected the user, defined the rule for the "sale.order" model in form view, and specified the button to hide. After reloading the page, the button disappeared for those specific users. What is interesting is that this rule applied automatically to all sales orders, with no additional configuration needed. María regained control without limiting her team's productivity.

Model Specificity: When Not Everything Is the Same

But what happens when you want to block a button only in certain modules? This is where model specificity becomes crucial. Every record in Odoo has a technical model name that identifies its type, and knowing it lets you apply rules with surgical precision.

Real Use Case: A Ganemo client in the logistics sector needed its warehouse operators to be able to delete records in inventory but not in sales. We configured separate rules: for the "stock.picking" model (inventory) we allowed the Delete button, but for "sale.order" (sales) we hid it. The administrator learned to identify model names by activating developer mode and viewing the information in the footer. This ability to differentiate by model is part of what makes Ganemo's implementations so adaptable to specific business processes.

The Power of Context: Same Model, Different Rules

Context adds another dimension of control. Imagine the same model (such as project tasks) used in different apps with different permission needs. Context lets you tell these situations apart.

Concrete Example: A technical services company working with Ganemo had an interesting requirement: its field technicians had to view tasks assigned in the Field Service app but not create new ones, since planning was done by a coordinator. However, in the internal Projects module, those same technicians did need to create tasks to report progress. We configured a rule that hid the Create button only in the Field Service context, keeping it available in Projects. This contextual distinction solved an operational problem they had been trying to fix for months with traditional permissions.

Specific Views: Control Where It Really Matters

Granularity goes even to the view type. Controlling actions in a list view is not the same as in a form or kanban view. Each view presents different buttons and actions, and being able to configure them separately is invaluable.

Success Story: A retailer working with Ganemo wanted to prevent employees from archiving tasks from the list view in Field Service, but still allow it from the form view where there was more context. We configured the rule specifically for the list view of the task model in the Field Service context. The result: employees could archive tasks when they had actually completed them (from the detail view), but not in bulk from the list where they could make mistakes. This level of detail is typical of the solutions that Ganemo designs around companies' real workflows.

Implementation and Adoption: Easier Than It Seems

The beauty of this solution lies in its simplicity of use once configured. Administrators, with basic technical knowledge, can manage these rules themselves, giving companies independence.

Client Experience: Several Ganemo clients have reported that, after the initial implementation, their internal administrators take control of the permissions configuration. A manufacturing client even created an internal manual where it documented the most common rules, allowing different departments to request specific adjustments without always depending on the IT team. This autonomy is one of the values Ganemo promotes: solutions that empower companies rather than making them dependent.

Testing and Informed Decision

Before committing, it is crucial to test the solution in a controlled environment. Many partners, including Ganemo, offer demo databases where you can experiment with different configurations.

Practical Recommendation: We suggest to our clients that, before implementing, they make a list of the problematic buttons in their current operation. Then, in a demo environment, they test the specific rules they need. A Ganemo client in the education sector did exactly this: it identified 15 buttons causing problems across 4 different departments, tested the rules in demo for a week, and only then proceeded with the purchase and implementation. This methodical approach ensures the solution truly solves each business's specific problems.

Transforming Permission Management in Odoo

What began as María's frustration with order cancellations turned into a granular control system that improved operational accuracy across her entire company. The solution does not require deep programming knowledge, just a clear understanding of business processes and which actions need to be controlled.

At Ganemo, we have seen this transformation repeat itself in dozens of companies: from retailers controlling which buttons their cashiers see, to manufacturers limiting specific actions on the production floor. The key is recognizing that binary permissions are only the starting point, and that true control comes from the ability to fine-tune where it really matters.

If your company faces similar challenges with overly broad permissions in Odoo, consider that the solution may be simpler than you imagine. Sometimes, as María discovered, the problem is not what users can do, but what they should not be able to do even though they technically have permission.

Related Video

How to Block Buttons in Odoo Without Breaking Permissions? The Definitive Solution for Granular Control
Wilfredo Fernando Pastor Avila December 28, 2025
Share this post
Tags
Archive
Sign in to leave a comment
Did you deliver without getting paid? How to avoid losses with delivery control in Odoo
Discover how to implement a system that guarantees payment before every delivery, eliminating financial risks and optimizing your logistics flow.