Intercompany shared contact
This module automatically shares all the contacts originating from companies (res.company object).
For example, suppose we have a multi-company environment with two companies (res.company) A and B in Odoo. We have users uA, uB (belonging to their respective companies).
Normally, uA cannot access the contact B. With this module, uA can see B (and inversely uB can see A). uA still can’t see all the other (supplier/reseller) contacts of company B.
Table of contents
Known issues / Roadmap
Instead of sharing all company contacts by default, it should be possible to selectively do so for example with a flag on res.company.
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
Sébastien Beau <sebastien.beau@akretion.com>
Kevin Khao <kevin.khao@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.
Current maintainer:
This module is part of the OCA/multi-company 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 odoo14-addon-intercompany-shared-contact 14.0.1.1.3
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 |
|---|---|---|---|---|
| odoo14_addon_intercompany_shared_contact-14.0.1.1.3-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_intercompany_shared_contact-14.0.1.1.3-py3-none-any.whl |
Security for odoo14-addon-intercompany-shared-contact 14.0.1.1.3
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.
