This release is a pre-release and may not be stable for production use.
User profiles
Extending the base_user_role module, this one adds the notion of profiles. Effectively profiles act as an additional filter to how the roles are used. Through the new widget, much in the same way that a user can switch companies when they are part of the multi company group, users have the possibility to change profiles when they are part of the multi profiles group.
- This allows users to switch their permission groups dynamically. This can be useful for example to:
finer grain control on menu and model permissions (with record rules this becomes very flexible)
break down complicated menus into simpler ones
easily restrict users accidentally editing or creating records in O2M fields and in general misusing the interface, instead of excessively explaining things to them
- When you define a role, you have the possibility to link it to a profile. Roles are applied to users in the following way:
Apply user’s roles without profiles in any case
Apply user’s roles that are linked to the currently selected profile
Note that this module assumes a multicompany environment
Table of contents
Configuration
Go to Configuration / Users / Profiles and create a profile. Go to Configuration / Users / Roles and define some role lines with profiles. Be careful when defining role lines that company ids and profiles are correctly configured.
Usage
Once you have set up at least one profile for a user, use the widget in the top bar to switch user profiles. Note that it is possible to use no profile; in this case, the user will only get the roles that always apply (i.e the ones with no profile_id).
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
Kevin Khao <kevin.khao@akretion.com>
Sébastien Beau <sebastien.beau@akretion.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.
This module is part of the OCA/server-backend project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo12-addon-base-user-role-profile 12.0.1.0.0.99.dev8
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 |
|---|---|---|---|---|
| odoo12_addon_base_user_role_profile-12.0.1.0.0.99.dev8-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_base_user_role_profile-12.0.1.0.0.99.dev8-py3-none-any.whl |
Release files / odoo12_addon_base_user_role_profile-12.0.1.0.0.99.dev8-py3-none-any.whl
| Download URL | odoo12_addon_base_user_role_profile-12.0.1.0.0.99.dev8-py3-none-any.whl |
|---|---|
| Size | 43.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e211afce52be8a9420c719fb9d657e09cdd229bd6ece4eae3b7e3e3ca93aca60
|
|
BLAKE2b-256 checksum How to use checksums |
2b84c392c21cb8dd44ceabf3c8f7cfeee803ac1908b5bfc374beda5ec0e29d71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo12-addon-base-user-role-profile 12.0.1.0.0.99.dev8
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.