User roles by company
Enable User Roles depending on the Companies selected.
A company specific Role will only be enabled if it is set for all the currently selected companies.
For example, if a user is “Sales Manager” only for Company A, it will see that role enabled only if Company A is selected. If the user selects Company A and Company B, then the “Sales Manager” role won’t be enabled.
Table of contents
Configuration
Roles are set on the User form.
The “Company” additional column allows to set a Role as only valid for specific companies.
There is also a “Active Role” techincal field, only visible in developer mode. It shows what roles are active, after applying the company selection rules.
Usage
Select the active companies from the web client widget, near the top right corner. When doing so, the User’s security Groups are recomputed, based on the Roles.
When the user changes the company selection, only the groups available to all active companies will be activated.
For example:
A “SALES PERSON” and a “SALES MANAGER” roles are created.
A user is assigned to the roles:
“SALES PERSON”, with no specific company assigned (meaning all)
“SALES MANAGER” only to “My Company (Chicago)”
When selecting active companies from the UI widget:
If only “My Company (San Francisco)” is active, “SALES PERSON” will be active.
If only “My Company (Chicago)” is active, “SALES PERSON” and “SALES MANAGER” will be active.
If both “My Company (San Francisco)” and “My Company (Chicago)” is active, “SALES PERSON” will be active.
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
Daniel Reis <dreis@opensourceintegrators.com>
Chandresh Thakkar <cthakkr@opensourceintegrators.com>
Urvisha Desai <udesai@opensourceintegrators.com>
Robin Conjour <rconjour@wesolved.com>
Bert Van Groenendael <bert.vangroenendael@dynapps.eu>
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.
1 maintainer
Release files for odoo-addon-base-user-role-company 19.0.1.0.0.2
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 | Reset |
|---|---|---|---|---|
| odoo_addon_base_user_role_company-19.0.1.0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_base_user_role_company-19.0.1.0.0.2-py3-none-any.whl
| Download URL | odoo_addon_base_user_role_company-19.0.1.0.0.2-py3-none-any.whl |
|---|---|
| Size | 35.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94a4061d6128425ea8b4b7976c2f460e34ffccab840a1f0a567392cf1e0c8457
|
|
BLAKE2b-256 checksum How to use checksums |
fc98f2fa0afc100a36695ef45046fa59199fb38e9cd67bad1d5f6cac4f23a5a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
