This release is a pre-release and may not be stable for production use.
This module allows defining groups whose membership is a condition expressed as python code. For every user, it is evaluated during login if she belongs to the group or not.
Table of contents
Configuration
Check Dynamic on a group you want to be dynamic. Now fill in the condition, using user which is a browse record of the user in question that evaluates truthy if the user is supposed to be a member of the group and falsy if not.
There is a constraint on the field to check for validity if this expression. When you’re satisfied, click the button Evaluate to prefill the group’s members. The condition will be checked now for every user who logs in.
Usage
We have a group called Amsterdam and want it to contain all users from city of Amsterdam. So we use the membership condition
user.partner_id.city == 'Amsterdam'Now we can be sure every user living in this city is in the right group, and we can start assigning local menus to it, adjust permissions, etc. Keep in mind that view overrides can also be restricted by a group id, this gives a lot of possibilities to dynamically adapt views based on arbitrary properties reachable via the user record.
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
Holger Brunn <hbrunn@therp.nl>
Ronald Portier <ronald@therp.nl>
Other credits
Odoo Community Association: Icon.
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.
This module is part of the OCA/server-auth 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 odoo11-addon-auth-dynamic-groups 11.0.1.0.0.99.dev9
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 |
|---|---|---|---|---|
| odoo11_addon_auth_dynamic_groups-11.0.1.0.0.99.dev9-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for odoo11_addon_auth_dynamic_groups-11.0.1.0.0.99.dev9-py2.py3-none-any.whl |
Release files / odoo11_addon_auth_dynamic_groups-11.0.1.0.0.99.dev9-py2.py3-none-any.whl
| Download URL | odoo11_addon_auth_dynamic_groups-11.0.1.0.0.99.dev9-py2.py3-none-any.whl |
|---|---|
| Size | 47.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
c06dc3d370e726712012a75d0fe610a2a2b396f60adf083344c7f5aa1e3009d9
|
|
BLAKE2b-256 checksum How to use checksums |
a879fff69d18b97abab041e6678bdb39719858155995ca29bf9fd430387af76b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo11-addon-auth-dynamic-groups 11.0.1.0.0.99.dev9
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.
