Access all OUs’ Purchase Orders
This module allow a user to have Access all OUs’ purchase orders, without having to add OUs in user setting.
Example use case, a shared procurement team under an OU but need to work on purchase orders of all OUs.
Table of contents
Configuration
To configure a user to have access to all OUs’ purchase orders (without all OUs access):
Go to Settings / Users & Companies / Users
For a user, select checkbox “Access all OUs’ purchase orders”
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
Kitti U. <kittiu@ecosoft.co.th>
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/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-purchase-operating-unit-access-all 15.0.1.0.0.4
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_purchase_operating_unit_access_all-15.0.1.0.0.4-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_purchase_operating_unit_access_all-15.0.1.0.0.4-py3-none-any.whl |
Release files / odoo_addon_purchase_operating_unit_access_all-15.0.1.0.0.4-py3-none-any.whl
| Download URL | odoo_addon_purchase_operating_unit_access_all-15.0.1.0.0.4-py3-none-any.whl |
|---|---|
| Size | 22.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34b758d9fcd284af0c4c809cb0862280cf6e63371a4a60cb4fabdbaba2e59f88
|
|
BLAKE2b-256 checksum How to use checksums |
7c7abb557b7c1a646071996337b5fe00159673489eb0ac14b333412907608ef7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo-addon-purchase-operating-unit-access-all 15.0.1.0.0.4
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.
