Sales documents permissions by channels (teams)
This module adds a new “Sale” group called “User: Team Documents Only”, that includes the proper permissions for showing only the information related to that user sale team (having assigned that team/channel or no team at all, independently from the assigned salesman):
Contacts.
Quotations/Sales Orders (implemented in sales_team_security_sale)
Leads/Opportunities (implemented in sales_team_security_crm)
It also handles the sync (auto-creation and remove) of followers in company partners and childs of them according to salesmans. Any example about it: - Partner company > Salesman: Admin - Partner company, Contact 1 > Without salesman - Partner company, Contact 2 > Salesman: Demo All these partners have these followers: Admin + Demo
And finally, there are rules for partners to be restricted to the own ones for the group “User: Own Documents Only” for being coherent with the permission scheme. Someone with this permission will see:
Contacts without salesman assigned.
Contacts with them as salesman.
Contacts with them as follower.
For keeping consistent accesses, followers of the main and shipping/invoice contacts are synced according the salesman of the children contacts
Additionally, users with the “User: Team Documents Only” group can see contacts created by any salesman that belongs to the same sales team(s), allowing team members to view and access contacts managed by their teammates.
Table of contents
Installation
At installation time, this module syncs followers in parent contacts and invoice/shipping addresses. If you have a lot of contacts, this operation can take a while.
Configuration
Go to Configuration > Users & Companies > Users.
Open or create a user.
On the section “Sale”, select “User: Team Documents Only”.
Known issues / Roadmap
This module modifies the sales security groups hierarchy, so any other module doing something similar might conflict with this one.
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
-
Pedro M. Baeza
Víctor Martínez
César A. Sánchez
Carlos Lopez
-
Ramón Bajona
Iván Todorovich <ivan.todorovich@gmail.com>
-
Jonathan Oscategui Taza <info@pesol.es>
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 maintainers:
This module is part of the OCA/sale-workflow project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Release files for odoo-addon-sales-team-security 19.0.1.0.0.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 | Reset |
|---|---|---|---|---|
| odoo_addon_sales_team_security-19.0.1.0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_sales_team_security-19.0.1.0.0.3-py3-none-any.whl
| Download URL | odoo_addon_sales_team_security-19.0.1.0.0.3-py3-none-any.whl |
|---|---|
| Size | 35.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fbf129c5a6d3928d9a6d34b8196f28897dc52a4b015d073a6425af86123147df
|
|
BLAKE2b-256 checksum How to use checksums |
6f8a2c0d6bfbcab4b8fed483aed34ea9d79d16d33ab6f16d17903e70d3f38d62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
