README.rst 2.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879
  1. .. image:: https://img.shields.io/badge/licence-AGPL--3-blue.svg
  2. :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
  3. :alt: License: AGPL-3
  4. ==============================
  5. Security rules for sales teams
  6. ==============================
  7. This module sets different permissions levels for accessing sales and CRM
  8. records based on the sales team: customers, sales orders, leads, opportunities,
  9. phone calls and sales teams.
  10. It also handles the propagation of the sales team from commercial partners to
  11. the contacts, which standard doesn't make.
  12. Installation
  13. ============
  14. At installation time, this module sets in all the contacts that have the sales
  15. team empty the sales team of the parent. If you have a lot of contacts, this
  16. operation can take a while.
  17. Configuration
  18. =============
  19. On the user configuration (Configuration > Users > Users), select in the
  20. *Sales Team* section the option "See only own team". Then, the documents
  21. mentioned before will be filtered out to have only those belonging to the
  22. teams the user belongs to.
  23. This is complementary to the "Sales" level access, but sometimes can be
  24. incoherent depending on the combination chosen. If you chose "See Own Leads"
  25. on *Sales* section, marking or unmarking the sales team check will be
  26. irrelevant, because the most restricting level, which is the sales one, will
  27. prevail.
  28. .. image:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas
  29. :alt: Try me on Runbot
  30. :target: https://runbot.odoo-community.org/runbot/167/8.0
  31. Bug Tracker
  32. ===========
  33. Bugs are tracked on `GitHub Issues
  34. <https://github.com/OCA/sale-workflow/issues>`_. In case of trouble, please
  35. check there if your issue has already been reported. If you spotted it first,
  36. help us smashing it by providing a detailed and welcomed feedback.
  37. Known issues/Roadmap
  38. ====================
  39. * This module is designed for supporting only sales part, so someone that has
  40. access to other Odoo parts (for example, an accountant), shouldn't have
  41. this new permission, or some access errors will be found when seeing invoices
  42. and other documents. A *sales_team_security_account* bridge module can be
  43. done for fixing this case, but not in the case of for example warehouse.
  44. Credits
  45. =======
  46. Contributors
  47. ------------
  48. * Pedro M. Baeza <pedro.baeza@serviciosbaeza.com>
  49. Maintainer
  50. ----------
  51. .. image:: http://odoo-community.org/logo.png
  52. :alt: Odoo Community Association
  53. :target: https://odoo-community.org
  54. This module is maintained by the OCA.
  55. OCA, or the Odoo Community Association, is a nonprofit organization whose
  56. mission is to support the collaborative development of Odoo features and
  57. promote its widespread use.
  58. To contribute to this module, please visit https://odoo-community.org.