e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
48 lines
1.4 KiB
ReStructuredText
48 lines
1.4 KiB
ReStructuredText
===========================
|
|
Manage multiple sales teams
|
|
===========================
|
|
|
|
In Odoo, you can manage several sales teams, departments or channels
|
|
with specific sales processes. To do so, we use the concept of *Sales
|
|
Channel*.
|
|
|
|
Create a new sales channel
|
|
==========================
|
|
|
|
To create a new *Sales Channel*, go to :menuselection:`Configuration --> Sales Channels`.
|
|
|
|
There you can set an email alias to it. Every message sent to that email
|
|
address will create a lead/opportunity.
|
|
|
|
.. image:: media/multi_sales_team01.png
|
|
:align: center
|
|
|
|
Add members to your sales channel
|
|
---------------------------------
|
|
|
|
You can add members to any channel; that way those members will see the
|
|
pipeline structure of the sales channel when opening it. Any
|
|
lead/opportunity assigned to them will link to the sales channel.
|
|
Therefore, you can only be a member of one channel.
|
|
|
|
This will ease the process review of the team manager.
|
|
|
|
.. image:: media/multi_sales_team02.png
|
|
:align: center
|
|
|
|
If you now filter on this specific channel in your pipeline, you will
|
|
find all of its opportunities.
|
|
|
|
.. image:: media/multi_sales_team03.png
|
|
:align: center
|
|
|
|
Sales channel dashboard
|
|
=======================
|
|
|
|
To see the operations and results of any sales channel at a glance, the
|
|
sales manager also has access to the *Sales Channel Dashboard* under
|
|
*Reporting*.
|
|
|
|
It is shared with the whole ecosystem so every revenue stream is
|
|
included in it: Sales, eCommerce, PoS, etc.
|