This release is a pre-release and may not be stable for production use.
Base Action Visibility Restriction Domain
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.
Enable debug mode.
Select multiple records in the Sale Orders list view.
Action -> Create Invoices.
Click bug symbol. Click Edit Action.
Go to Security tab.
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.
Enable debug mode.
Go to Settings -> Technical -> Server Actions.
Search for Mark Quotation as Sent. You can see in the Model field it is Sale Order.
Go to Security tab.
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
Contributors
-
Ilyas <irazor147@gmail.com>
Maintainers
This module is maintained by the OCA.
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:
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo14-addon-base-action-visibility-restriction-domain 14.0.1.0.1.dev4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo14_addon_base_action_visibility_restriction_domain-14.0.1.0.1.dev4-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_base_action_visibility_restriction_domain-14.0.1.0.1.dev4-py3-none-any.whl |
Release files / odoo14_addon_base_action_visibility_restriction_domain-14.0.1.0.1.dev4-py3-none-any.whl
| Download URL | odoo14_addon_base_action_visibility_restriction_domain-14.0.1.0.1.dev4-py3-none-any.whl |
|---|---|
| Size | 25.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
15d871f84d73d8e5f1c587116bfc8e9cf8f4f2a6f0083aa9f0ac03a26dccf3a1
|
|
BLAKE2b-256 checksum How to use checksums |
d08f2afc9025a1a6640d50a74262909b6d59dfabae25790b291a2c474739c406
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo14-addon-base-action-visibility-restriction-domain 14.0.1.0.1.dev4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
