Skip to main content

User roles by company

Project description

Beta License: AGPL-3 OCA/server-backend 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

WeSolved

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-backend project on GitHub.

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

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

File details

Details for the file odoo_addon_base_user_role_company-17.0.1.2.0-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_base_user_role_company-17.0.1.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 2a3584d9196b1538a66525a795b50a0ba84f06cf5e60511b4e1be4dbfa5e0767
MD5 1b0e51bbf14e7f6b08d869cae7661781
BLAKE2b-256 74727bf69cf7226217b3ec8707266df0c07e5ea2134799aea7b20317c33010b5

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page