<a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg"> </a> <a name="security-rules-for-sales-teams"></a> <h2>Security rules for sales teams</h2> <p>This module sets different permissions levels for accessing sales and CRM records based on the sales team: customers, sales orders, leads, opportunities, phone calls and sales teams.</p> <p>It also handles the propagation of the sales team from commercial partners to the contacts, which standard doesn't make.</p> <a name="installation"></a> <h3>Installation</h3> <p>At installation time, this module sets in all the contacts that have the sales team empty the sales team of the parent. If you have a lot of contacts, this operation can take a while.</p> <a name="configuration"></a> <h3>Configuration</h3> <p>On the user configuration (Configuration &gt; Users &gt; Users), select in the <em>Sales Team</em> section the option &quot;See only own team&quot;. Then, the documents mentioned before will be filtered out to have only those belonging to the teams the user belongs to.</p> <p>This is complementary to the &quot;Sales&quot; level access, but sometimes can be incoherent depending on the combination chosen. If you chose &quot;See Own Leads&quot; on <em>Sales</em> section, marking or unmarking the sales team check will be irrelevant, because the most restricting level, which is the sales one, will prevail.</p> <a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/167/8.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a> <a name="bug-tracker"></a> <h3>Bug Tracker</h3> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/sale-workflow/issues">GitHub Issues</a>. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.</p> <a name="known-issues-roadmap"></a> <h3>Known issues/Roadmap</h3> <ul class="simple"> <li>This module is designed for supporting only sales part, so someone that has access to other Odoo parts (for example, an accountant), shouldn't have this new permission, or some access errors will be found when seeing invoices and other documents. A <em>sales_team_security_account</em> bridge module can be done for fixing this case, but not in the case of for example warehouse.</li> </ul> <a name="credits"></a> <h3>Credits</h3> <a name="contributors"></a> <h4>Contributors</h4> <ul class="simple"> <li>Pedro M. Baeza &lt;<a class="reference external" href="mailto:pedro.baeza&#64;serviciosbaeza.com">pedro.baeza&#64;serviciosbaeza.com</a>&gt;</li> </ul> <a name="maintainer"></a> <h4>Maintainer</h4> <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="http://odoo-community.org/logo.png" /></a> <p>This module is maintained by the OCA.</p> <p>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.</p> <p>To contribute to this module, please visit <a class="reference external" href="https://odoo-community.org">https://odoo-community.org</a>.</p>