Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

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

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

Authors

  • Open Source Integrators

Contributors

Open Source Integrators

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.

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

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

Metadata

Release files for odoo10-addon-base-user-role-company 10.0.1.0.0.99.dev3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo10-addon-base-user-role-company 10.0.1.0.0.99.dev3
File Interpreter ABI Platform
odoo10_addon_base_user_role_company-10.0.1.0.0.99.dev3-py2-none-any.whl Python 2 none any Details

Release files / odoo10_addon_base_user_role_company-10.0.1.0.0.99.dev3-py2-none-any.whl

Download URL odoo10_addon_base_user_role_company-10.0.1.0.0.99.dev3-py2-none-any.whl
Size 28.0 kB
Tags Python 2
SHA-256 checksum
How to use checksums
08fa27745a6cfc02c2947a508ce1bf4ac4505d3a4dabeabf3c901205fd42c0fc
BLAKE2b-256 checksum
How to use checksums
046776b5eb77538d9a26b9771bd91ff665fc976ed8a940118e91107178c9523b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.8.5
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page