Operating Unit in CRM
This module introduces the following features:
Adds the Operating Unit (OU) to the Lead.
The user’s default Operating Unit (OU) is proposed at the time of creating the Lead / Opportunity.
Security rules are defined to ensure that users can only see the Opportunity / Lead of that Operating Units in which they are allowed access to.
Table of contents
Usage
To use this module, you need to:
Go to CRM > Sales > Leads or CRM > Sales > Opportunities
When creating a new lead or opportunity, the operating unit will be automatically set based on:
The operating unit of your default sales team, or
Your default operating unit if the sales team doesn’t have an operating unit
You can filter leads and opportunities by operating unit using the search filter
You can only see leads and opportunities from operating units you have access to
The operating unit field is only visible if you belong to the “Multi Operating Unit” group
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
ForgeFlow S.L. <contact@forgeflow.com>
Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>
Jarsa Sistemas, S.A. de C.V. <info@jarsa.com.mx>
Tran Thanh Trai <traitt@trobz.com>
Heliconia Solutions Pvt. Ltd. <https://www.heliconia.io>_
Julien Coux <julien.coux@camptocamp.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/operating-unit 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 odoo-addon-crm-operating-unit 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 | Actions Reset |
|---|---|---|---|---|
| odoo_addon_crm_operating_unit-19.0.1.0.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_crm_operating_unit-19.0.1.0.0.2-py3-none-any.whl |
Release files / odoo_addon_crm_operating_unit-19.0.1.0.0.2-py3-none-any.whl
| Download URL | odoo_addon_crm_operating_unit-19.0.1.0.0.2-py3-none-any.whl |
|---|---|
| Size | 28.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dbcca96c3eb808542c22c5c5b1e00885d2701f01b239b7c09bbb310418d2bf83
|
|
BLAKE2b-256 checksum How to use checksums |
6cb0a640d2781fbe1e77d47358e5ccfc2f5de16a5eecccbbf25d1c3e2c430079
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-crm-operating-unit 19.0.1.0.0.2
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.
