Toggle navigation
Inizia qui

Base Action Visibility Restriction Domain

Beta License: AGPL-3 OCA/server-ux Translate me on Weblate Try me on Runboat

Using restriction records you can create domains for different groups. Domain will allow/deny action run on specific target model records.

If all restrictions of an action are without domain - action is hidden based on group (base_action_visibility_restriction behaviour).

If at least one restriction with domain - action is shown. Access will be defined once user run action.

If restriction record without domain - user can’t run action. If with domain - domain defines for which records user (users group) can run action.

Table of contents

Usage

Restrict access to a Window Action.

Window actions normally have a wizard - window that opens after you run action.

Window actions have as Destination Model a model of the wizard. Not a target model.

Lets say you want to limit access to the window action Create Invoices for Sale Order.

  1. Enable debug mode.
  2. Select multiple records in the Sale Orders list view.
  3. Action -> Create Invoices.
  4. Click bug symbol. Click Edit Action.
  5. Go to Security tab.
  6. Create restrictions lines and save.

Restrict access to a Server Action.

Server actions dont have a wizard. They are linked directly to a target model. They are performed right away after you click action.

Lets say you want to limit access to the server action Mark Quotation as Sent for Sale Order.

  1. Enable debug mode.
  2. Go to Settings -> Technical -> Server Actions.
  3. Search for Mark Quotation as Sent. You can see in the Model field it is Sale Order.
  4. Go to Security tab.
  5. Create restrictions lines and save.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Ilyas
  • Ooops404

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainer:

ilyasprogrammer

This module is part of the OCA/server-ux project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.