Our Most Suggested Products
Hide/Show Action Button Specific Model
Hide/Show Action Button Specific Model allows administrators to control the visibility of the Action button for specific models on a user-by-user basis. Configure model restrictions with ease, and the module automatically hides or restores the Action button based on the assigned settings. This helps enforce role-based permissions, reduce access to unnecessary bulk actions, and maintain a secure, well-organized workflow across the system.
Features
User-Specific Action Button Restriction
Assign one or more models to individual users to control where the Action button is available. The application applies these restrictions only to the selected user, allowing administrators to customize action availability based on roles and operational requirements.
Automatic Action Button Visibility Management
The application automatically updates the visibility of the Action button according to the configured model restrictions. When a model is added to the restriction list, the Action button is hidden, and when it is removed, the button is restored automatically, ensuring permissions remain consistent without additional configuration.
Screenshot
1.)Configure Hidden Action Button Models
Select the models for which the Action button should be hidden for the selected user. Multiple models can be assigned, allowing administrators to apply action restrictions only where required. These settings provide better control over available operations while maintaining a user-specific configuration.
Navigation : Settings → Users & Companies → Users
2.)Action Button Hidden
When a user accesses a model configured with action restrictions, the Action button is automatically removed. Users can continue performing their regular tasks, but additional bulk actions are no longer available for the restricted model.
3.)Remove a Model from Restrictions
Remove a model from the restricted list to restore the Action button for that specific model. The change takes effect for the selected user while restrictions on other configured models remain unchanged.
Navigation : Settings → Users & Companies → Users
4.) Action Button Restored
After removing a model from the restriction list, the Action button becomes available again for that model. Users regain access to the supported bulk actions without affecting restrictions configured for other models.
User Guide
Teams
team@inkerp.com
Suggested Products
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 54 |
| Technical Name |
eg_hide_model_action_button |
| License | OPL-1 |
| Website | http://www.inkerp.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