[ADD] odoo_sh: Mention Python dependency behavior in FAQ

Odoo.sh doesn't use the requirements.txt included in Odoo but Python
packages available in the Linux distribution instead. This is
non-obvious and can be confusing to users, especially in the cases where
the version available in the distribution and requirements.txt are
different.

Adding this section is intended to clarify that, and to provide a
reference for developers of custom modules on what to expect.

opw-2688205

.gitignore

@@ -4,7 +4,6 @@
 
 # Sphinx build files
 _build/
-extensions/odoo_theme/static/style.css
 
 # Dependencies
 odoo

.tx/config

@@ -47,6 +47,11 @@ file_filter = locale/<lang>/LC_MESSAGES/services.po
 source_file = locale/sources/services.pot
 source_lang = en
 
+[odoo-13-doc.theme]
+file_filter = locale/<lang>/LC_MESSAGES/sphinx.po
+source_file = locale/sources/sphinx.pot
+source_lang = en
+
 [odoo-13-doc.user_settings]
 file_filter = locale/<lang>/LC_MESSAGES/settings.po
 source_file = locale/sources/settings.pot
@@ -55,4 +60,4 @@ source_lang = en
 [odoo-13-doc.websites]
 file_filter = locale/<lang>/LC_MESSAGES/websites.po
 source_file = locale/sources/websites.pot
-source_lang = en
+source_lang = en

Makefile

@@ -5,6 +5,14 @@ ifndef WORKERS
   WORKERS = auto
 endif
 
+ifndef BUILD_DIR
+  BUILD_DIR    = _build
+endif
+
+ifndef CURRENT_LANG
+  CURRENT_LANG = en
+endif
+
 SPHINX_BUILD   = sphinx-build
 CONFIG_DIR     = .
 SPHINXOPTS     = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSION) \
@@ -13,7 +21,6 @@ SPHINXOPTS     = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSIO
                  -A google_analytics_key=$(GOOGLE_ANALYTICS_KEY) \
 				 -j $(WORKERS)
 SOURCE_DIR     = content
-BUILD_DIR      = _build
 
 HTML_BUILD_DIR = $(BUILD_DIR)/html
 ifdef VERSIONS
@@ -37,10 +44,9 @@ help:
 clean:
 	@echo "Cleaning build files..."
 	rm -rf $(BUILD_DIR)/*
-	rm extensions/odoo_theme/static/style.css
 	@echo "Cleaning finished."
 
-html: extensions/odoo_theme/static/style.css
+html: $(HTML_BUILD_DIR)/_static/style.css
 	@echo "Starting build..."
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b html $(SPHINXOPTS) $(SOURCE_DIR) $(HTML_BUILD_DIR)
 	@echo "Build finished."
@@ -60,9 +66,10 @@ gettext:
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b gettext $(SOURCE_DIR) locale/sources
 	@echo "Generation finished."
 
-extensions/odoo_theme/static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
+$(HTML_BUILD_DIR)/_static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
 	@echo "Compiling stylesheets..."
-	pysassc $(subst .css,.scss,$@) $@
+	mkdir -p $(HTML_BUILD_DIR)/_static
+	pysassc extensions/odoo_theme/static/style.scss $(HTML_BUILD_DIR)/_static/style.css
 	@echo "Compilation finished."
 
 #=== Development and debugging rules ===#
@@ -70,6 +77,6 @@ extensions/odoo_theme/static/style.css: extensions/odoo_theme/static/style.scss
 fast: SPHINXOPTS += -A collapse_menu=True
 fast: html
 
-static: extensions/odoo_theme/static/style.css
-	cp -r extensions/odoo_theme/static/* _build/html/_static/
-	cp -r static/* _build/html/_static/
+static: $(HTML_BUILD_DIR)/static/style.css
+	cp -r extensions/odoo_theme/static/* $(HTML_BUILD_DIR)/_static/
+	cp -r static/* $(HTML_BUILD_DIR)/_static/

conf.py

@@ -60,6 +60,11 @@ sys.path.insert(0, str(extension_dir.absolute()))
 # Search for the directory of odoo sources to know whether autodoc should be used on the dev doc
 odoo_dir = Path('odoo')
 odoo_dir_in_path = False
+if not odoo_dir.is_dir():
+    parent_odoo_dir = Path('../odoo')
+    if parent_odoo_dir.is_dir():
+        _logger.info('Using parent dir to find odoo sources')
+        odoo_dir = parent_odoo_dir
 if not odoo_dir.is_dir():
     _logger.warning(
         f"Could not find Odoo sources directory at {odoo_dir.absolute()}.\n"
@@ -130,6 +135,7 @@ github_user = 'odoo'
 github_project = 'documentation'
 
 locale_dirs = ['../locale/']
+templates_path = ['../extensions']
 
 # custom docname_to_domain to divide the translations of applications in subdirectories
 sphinx.transforms.i18n.docname_to_domain = (
@@ -284,7 +290,7 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
             for _alternate_version in sorted(_alternate_versions, reverse=True)
             if _alternate_version != version and (
                 _alternate_version != 'master' or pagename.startswith('developer')
-            )
+            ) and not _alternate_version.startswith('saas')
         ]
 
     def _localize():

content/administration.rst

@@ -1,14 +1,22 @@
-==============
-Administration
-==============
+:nosearch:
+:show-content:
+:hide-page-toc:
+:show-toc:
+
+====================
+Install and Maintain
+====================
+
+These guides provide instructions on how to install, maintain and upgrade Odoo databases.
+
+.. seealso::
+    :doc:`History of Versions <administration/maintain/supported_versions>`
 
 
 .. toctree::
+    :titlesonly:
 
     administration/install
-    administration/deployment
-    administration/update
-    administration/db_upgrade
+    administration/maintain
+    administration/upgrade
     administration/odoo_sh
-    administration/db_management
-    administration/enterprise

content/administration/db_management.rst

@@ -1,10 +0,0 @@
-===================
-Database Management
-===================
-
-
-.. toctree::
-
-    db_management/db_online
-    db_management/db_premise
-    db_management/hosting_changes

content/administration/db_management/db_online.rst

@@ -1,233 +0,0 @@
-
-.. _db_online:
-
-==========================
-Online Database management
-==========================
-
-To manage your databases, access the `database management page
-<https://www.odoo.com/my/databases>`__ (you will have to sign in). Then click
-on the `Manage Your Databases <https://www.odoo.com/my/databases/manage>`__
-button.
-
-.. image:: media/databases.png
-    :align: center
-
-Make sure you are connected as the administrator of the database you
-want to manage - many operations depends on identifying you remotely to that
-database.
-
-Several actions are available:
-
-.. image:: media/db_buttons.png
-    :align: center
-
-* :ref:`Upgrade <upgrade_button>`
-    Upgrade your database to the latest Odoo version to enjoy cutting-edge
-    features
-* :ref:`Duplicate <duplicate_online>`
-    Make an exact copy of your database, if you want
-    to try out new apps or new flows without compromising
-    your daily operations
-* :ref:`Rename <rename_online_database>`
-    Rename your database (and its URL)
-* **Backup**
-    Download an instant backup of your database; note that we
-    back up databases daily according to our Odoo Cloud SLA
-* :ref:`Domains <custom_domain>`
-    Configure custom domains to access your
-    database via another URL
-* :ref:`Delete <delete_online_database>`
-    Delete a database instantly
-* Contact Support
-    Access our `support page <https://www.odoo.com/help>`__
-    with the correct database already selected
-
-.. _upgrade_button:
-
-Upgrade
-=======
-
-.. warning:: Upgrading your database to a newer version of Odoo is a complex operation
-    that require time and caution. It is extremely important that you
-    fully test the process before upgrading your production database.
-
-Odoo releases new versions regularly (at least once a year), and upgrading your
-database to enjoy new Odoo features is part of the Odoo Online experience.
-
-The upgrade process can take some time, especially if you use multiple apps or
-apps that manage sensitive data (e.g. Accounting, Inventory, etc.). In general,
-the 'smaller' the database, the quickest the upgrade. A single-user
-database that uses only CRM will be processed faster than a multi-company,
-multi-user database that uses Accounting, Sales, Purchase and Manufacturing.
-
-Unfortunately, it is impossible to give time estimates for every upgrade request,
-since Odoo.com will test manually every database upgrade at least once and will
-need to correct/adapt changes made to the standard Odoo Apps (e.g. through Studio
-or through a Success Pack) on a case-by-case basis. This can make the process
-slower, since requests are treated in the order they arrive. This is especially
-true in the months following the release of a new major version, which can lengthen
-the upgrade delay significantly.
-
-The upgrade process is quite simple from your point of view:
-
-1. You request a test upgrade
-2. Once all tests have been validated **by you**, you upgrade your actual database
-
-The process to request a test or a production (*actual*) upgrade is the same.
-
-First, make sure to be connected to the database you want to upgrade and access the
-`database management page <https://www.odoo.com/my/databases>`__.
-
-.. note:: You have to have an active session with access to the Settings app
-    in the database you want to upgrade for the button to be visible.
-
-On the line of the database you want to upgrade, click
-on the "Cog" menu. If an newer version of Odoo is available, you will see an 'Upgrade'
-button.
-
-.. image:: media/upgrade1.png
-    :align: center
-
-You have the possibility to choose the target version of the upgrade. By default,
-we select the highest available version available for your database; if you were
-already in the process of testing an upgrade, we will automatically select the
-version you were already testing (even if we released a more recent version during
-your tests).
-
-.. image:: media/upgrade_test.png
-    :align: center
-
-By clicking on the "Test upgrade" button, an upgrade request will be generated.
-Only one request can be made at time for each database; if a request has already
-been made, you will see an 'Upgrade Queued' note instead and asking another
-request will not be possible.
-
-A test upgrade will create a copy of your database, upgrade it and make it
-available to you automatically once successful. If this is the first test you
-request for this particular database, a manual testing phase will be done by
-Odoo.com - this could take time (up to several weeks). Subsequent requests
-will not go through that manual testing step and will usually be made
-available in a few hours. Once the test database is available, you should
-receive an e-mail with the URL of the test database.
-
-**Testing your database is the most important step of the upgrade process!**
-Even though we test all upgrades manually, we do not know your work processes.
-A change in standard workflows of Odoo in new versions might require you to
-change internal processes, or some of the customizations you made through Odoo
-Studio might not work properly. *It is up to you to make sure that everything
-works as it should!* You can report issues with your test database through our
-`Support page <https://www.odoo.com/help>`__.
-
-Make sure to do one last test of your upgrade right before the final upgrade
-(e.g. the day before) to ensure everything will run smoothly. Downgrading is
-not possible and post-poning an upgrade is always easier than being prevented
-to work by an upgrade issue after the fact!
-
-Once you are ready and you have validated all your tests, you can click
-again on the Upgrade button and confirm by clicking on Upgrade (the button
-with the little rocket!) to switch your production database to the new version.
-Your database will then be taken offline within the next 10 minutes and will be
-upgraded automatically; you receive a confirmation
-e-mail once the process is completed.
-
-.. image:: media/upgrade_prod.png
-    :align: center
-
-.. warning::
-   Your database will be taken offline during the upgrade (usually between 30min up to several hours
-   for big databases), so make sure to plan your migration during non-business hours.
-
-.. _duplicate_online:
-
-Duplicating a database
-======================
-
-.. note:: Database duplication, renaming, custom DNS, etc. is not available
-    for trial databases on our Online platform. Paid Databases and "One App
-    Free" database can duplicate without problem.
-
-
-In the line of the database you want to duplicate, you will have a few
-buttons. To duplicate your database, just click **Duplicate**. You will
-have to give a name to your duplicate, then click **Duplicate Database**.
-
-.. image:: media/db_duplicate.png
-    :align: center
-
-.. danger:: If you do not check the "For testing purposes" checkbox when
-  duplicating a database, all external communication will remain active:
-
-  * Emails are sent
-
-  * Payments are processed (in the e-commerce or Subscriptions apps, for
-    example)
-
-  * Delivery orders (shipping providers) are sent
-
-  * Etc.
-
-  Make sure to check the checkbox "For testing purposes" if you want these
-  behaviours to be disabled.
-
-After a few seconds, you will be logged in your duplicated database.
-Notice that the url uses the name you chose for your duplicated
-database.
-
-.. note::
-   Duplicate databases expire automatically after 15 days.
-
-   .. image:: media/dup_expires.png
-      :align: center
-
-.. _rename_online_database:
-
-Rename a Database
-===================
-
-To rename your database, make sure you are connected to the database you want
-to rename, access the `database management page <https://www.odoo.com/my/databases>`__
-and click **Rename**. You will have to give a new name to your database,
-then click **Rename Database**.
-
-.. image:: media/rename.png
-    :align: center
-
-.. _delete_online_database:
-
-Deleting a Database
-===================
-
-You can only delete databases of which you are the administrator.
-
-.. danger:: When you delete your database all the data will be permanently lost.
-    The deletion is instant and for all the Users. We advise you to do an
-    instant backup of your database before deleting it, since the last automated
-    daily backup may be several hours old at that point.
-
-
-From the `database management page <https://www.odoo.com/my/databases>`__,
-on the line of the database you want to delete, click on the "Delete" button.
-
-.. image:: media/delete_button.png
-    :align: center
-
-
-Read carefully the warning message that will appear and proceed only if you
-fully understand the implications of deleting a database:
-
-.. image:: media/delete_warning.png
-    :align: center
-
-After a few seconds, the database will be deleted and the page will
-reload automatically.
-
-.. note::
-    * If you need to re-use this database name, it will be immediately available.
-
-    * It is not possible to delete a database if it is expired or linked
-      to a Subscription. In these cases contact
-      `Odoo Support <https://www.odoo.com/help>`__
-
-    * If you want to delete your Account, please contact
-      `Odoo Support <https://www.odoo.com/help>`__

content/administration/db_upgrade.rst

@@ -1,415 +0,0 @@
-
-.. |assistance-contact| replace::
-   If you need Odoo assistance on this matter, please contact your Odoo Account Manager or contact
-   our `Sales department`_.
-.. _Sales department: mailto:sales@odoo.com
-
-.. _db-upgrade:
-
-=======
-Upgrade
-=======
-
-.. _db-upgrade/overview:
-
-Overview
-========
-
-.. _db-upgrade/process:
-
-The upgrade process
--------------------
-
-This documentation is for our *On-Premise* (self-hosted) and *Odoo.sh* customers. If you are hosted
-Online, please check our :ref:`instruction page for our Online (SaaS) customers <upgrade_button>`.
-
-.. _db-upgrade/definition:
-
-Definition
-~~~~~~~~~~
-
-An upgrade is switching to a newer version of Odoo (e.g., Odoo 13.0 to Odoo 14.0)
-
-An upgrade does not cover:
-
-* changing :ref:`Editions <db-upgrade/faq/editions-change>` (i.e., Community to Enterprise edition)
-* switching :ref:`hosting type <db-upgrade/faq/hosting-types-switch>` (i.e., On-Premise to Online or
-  Odoo.sh)
-* migration from another ERP to Odoo
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/process-workflow:
-
-Process workflow
-~~~~~~~~~~~~~~~~
-
-The upgrade process in a nutshell:
-
-#. You create a test upgrade request.
-#. | The request is processed by Odoo:
-   | This happens via an automated process that runs the database through an upgrade script and
-     takes between 20 and 120 minutes. Only if an issue(s) arises will we have to intervene
-     manually and adjust the script specifically to your database until the upgrade succeeds.
-#. Odoo delivers a test database.
-#. You test your database for possible discrepancies (see :ref:`db-upgrade/test-guidance`)
-#. If there are any discrepancies, you report them to the Upgrade support team via the
-   :ref:`Help portal <db-upgrade/test-assistance>`.
-#. We will fix the issues and send you a new test database.
-#. Once you completed the testing and are happy with the result, you decide on a date and time when
-   you stop users from accessing Odoo, freeze all data entries and create an upgrade request for the
-   production upgrade.
-#. Odoo delivers the production database through the automated process.
-#. You restore it in your Production environment a few short hours later and continue working on the
-   newly upgraded database.
-
-.. _db-upgrade/service-level:
-
-Service Level Agreement
------------------------
-
-What is covered by the Enterprise Licence?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the
-following service at all times.
-
-The upgrade of:
-
-* standard applications
-* Studio customization (as long as the Studio app is still active)
-* customizations done by our consulting and developer services *if* they are covered by a
-  ‘Maintenance of Customisations’ subscription
-
-The Upgrade Service is limited to the technical conversion and adaptation of your database (standard
-modules and data) to make it compatible with the targeted version.
-
-What upgrading does NOT cover
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-* The cleaning of pre-existing data & configuration while upgrading
-* Any new developments and/or upgrade of your own :ref:`custom modules
-  <db-upgrade/faq/custom-modules>`
-* `Training <https://www.odoo.com/learn>`_ on the new version
-
-You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription
-Agreement <upgrade>` page.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/get-started:
-
-Get started
-===========
-
-The upgrade process varies depending on where your database is hosted.
-
-.. _db-upgrade/online:
-
-Online (SaaS)
--------------
-
-If you are hosted Online, please check our :ref:`instruction page for our Online (SaaS) customers
-<upgrade_button>`.
-
-.. _db-upgrade/odoo-sh:
-
-Odoo.sh
--------
-
-If you are Odoo.sh hosted, check our :doc:`specific instructions to be able to upgrade
-<odoo_sh/advanced/upgrade_your_database>`.
-
-.. _db-upgrade/on-premise:
-
-On-Premise
-----------
-
-There are two possibilities:
-
-#. Via the interface of our `website form <https://upgrade.odoo.com>`_
-#. | For technically-advanced users and partners, via the following command line (to be used on the
-     machine where your database is hosted):
-   | ``python <(curl -s beta.upgrade.odoo.com/upgrade) test -d <your db name> -t 14.0``
-
-What does it do?
-~~~~~~~~~~~~~~~~
-
-The above command will dump your database to a file, then send it to the upgrade platform for
-upgrade, displaying you the live logs, then restore the upgraded database back on your server as a
-duplicate test database.
-
-.. _db-upgrade/steps:
-
-Steps
-=====
-
-.. _db-upgrade/steps-test:
-
-The testing phase
------------------
-
-.. _db-upgrade/test-process:
-
-Test process
-~~~~~~~~~~~~
-
-Also referred to as the pre-production phase, the test phase allows you to review an upgraded
-version of your database without affecting your production database in any way.
-
-We suggest that you run the test upgrade process at least once, but you can do it as often as you
-want (one at a time).
-
-Once you receive your upgraded test database, you should check that all data, processes and
-functionality are still correct and working as expected.
-
-If you do find discrepancies, you'll be able to:
-
-* | :ref:`Report your issues <db-upgrade/test-assistance>`
-  | and/or
-* Ask for a new :ref:`test request <db-upgrade/test-db-request>` after the reported issues have
-  been fixed in the upgrade script.
-
-When you do not find any discrepancies, you'll be able to:
-
-* Move on to the upgrade of your :ref:`production database <db-upgrade/production-live>`.
-
-.. _db-upgrade/test-db-request:
-
-Request a test database
-~~~~~~~~~~~~~~~~~~~~~~~
-
-When filling the `website form <https://upgrade.odoo.com>`_, select *Testing* purpose.
-
-.. image:: media/db-upgrade-test-purpose.png
-   :align: center
-   :alt: Selection of the "Testing" purpose in the upgrade form on Odoo
-
-.. _db-upgrade/test-guidance:
-
-Test guidance
-~~~~~~~~~~~~~
-
-Every business and organization has its own operational needs and will have to test its specific
-Odoo instance respectively. However, we recommend you look at `the test scenario
-<https://drive.google.com/open?id=1Lm4JqbsHBirB1wMi14UChoz_YHLjx5ec>`_ we created, a high-level idea
-of what you should test and look out for.
-
-.. todo:: change link "test scenario" once the related doc is published
-
-.. _db-upgrade/test-assistance:
-
-Assistance
-~~~~~~~~~~
-
-If you encounter issues or problems in the **test database**, please contact the Odoo Upgrade
-Support:
-
-#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
-#. Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type.
-
-   .. image:: media/db-upgrade-test-assistance.png
-      :align: center
-      :alt: Selection of "An issue related to my upgrade" as Ticket Type in the support form on Odoo
-
-   .. warning::
-      If you choose another *Ticket Description* type, the request will be redirected to another
-      team than the upgrade one and will slow down the processing and response time.
-
-#. Please provide as much detail as you can. Where applicable, illustrate the current and previous
-   flows with videos and/or screenshots. This will avoid clarifying questions and speed up the
-   resolution process significantly.
-
-   .. image:: media/db-upgrade-test-assistance-details.png
-      :align: center
-      :alt: "Detailed Description" field in the support form on Odoo
-
-.. note::
-   * The purpose of the test phase is not to correct existing data or configurations in your
-     database.
-   * |assistance-contact|
-
-.. _db-upgrade/steps-production:
-
-The production launch
----------------------
-
-.. _db-upgrade/production-live:
-
-Production goes live
-~~~~~~~~~~~~~~~~~~~~
-
-The production upgrade request is when you decide to upgrade your current database with all your
-production data (invoices, VAT returns, inventories, current orders) to a new version of your choice.
-
-After your :ref:`tests <db-upgrade/steps-test>` are completed to your satisfaction, submit the
-request to upgrade your production database via our `website form <https://upgrade.odoo.com>`_.
-Select *Production* purpose.
-
-.. image:: media/db-upgrade-production-purpose.png
-   :align: center
-   :alt: Selection of the "Production" purpose in the upgrade form on Odoo
-
-.. danger::
-   Going into production without first testing may lead to:
-
-   - business interruptions (e.g. no longer having the possibility to validate an action)
-   - poor customer experiences (e.g. an eCommerce website that does not work correctly)
-
-.. _db-upgrade/production-assistance:
-
-Assistance
-~~~~~~~~~~
-
-If you encounter issues or problems in the **production database**, please contact the **Odoo
-Support**:
-
-#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
-#. Under the *Ticket Description* section, select the appropriate type related to your issue but
-   **do not select** the option *An issue related to my upgrade*.
-
-   .. note::
-      After upgrading to production, the support will be provided by the Support team instead of the
-      Upgrade team.
-
-#. Please provide as much detail as you can. Where applicable, illustrate the current and previous
-   flows with videos and/or screenshots. This will avoid clarifying questions and speed up the
-   resolution process significantly.
-
-   .. image:: media/db-upgrade-production-assistance-details.png
-      :align: center
-      :alt: "Detailed Description" field in the support form on Odoo
-
-   .. warning::
-      If you choose *An issue related to my upgrade* as ticket type, the request will be redirected
-      to another team than the support one and will slow down the processing and response time.
-
-.. _db-upgrade/faq:
-
-FAQ
-===
-
-.. _db-upgrade/faq/why:
-
-Why upgrade?
-------------
-
-* You benefit from the latest features of the :ref:`new major version
-  <db-upgrade/faq/release-notes>` released by Odoo.
-* If you are in an :ref:`unsupported version <db-upgrade/supported-versions>`, you get a new version
-  with support.
-
-.. _db-upgrade/faq/when:
-
-When to upgrade?
-----------------
-
-Whenever you want. You can make your upgrade request as soon as a new version is released on our
-`website form <https://upgrade.odoo.com>`_.
-
-.. _db-upgrade/faq/availability:
-
-Availability of the new version
--------------------------------
-
-Please kindly note that as soon as we announce the release of a new major version (usually at the
-end of year), the Upgrade Service team needs to adapt the upgrade scripts to it, which is why the
-new version is not immediately available for existing databases.
-
-.. _db-upgrade/faq/finalization:
-
-Finalization of the upgrade (:abbr:`ETA (Estimated Time of Arrival)`)
----------------------------------------------------------------------
-
-Unfortunately, it is impossible to give time estimates for every upgrade request. Odoo offers so
-many possibilities (e.g. branding, workflows, customization, etc) that it can get tricky to upgrade,
-and translate to the new structure. If you use multiple apps managing sensitive data (e.g.,
-Accounting, Inventory, etc.), some cases may still require a human intervention, making the process
-slower.
-
-This is especially true during the first months following the release of a new major version, which
-can significantly lengthen the upgrade delay.
-
-In general, the ‘smaller’ the database, the quickest the upgrade. A single-user database that uses
-only CRM will be processed faster than a multi-company, multi-user database that uses Accounting,
-Sales, Purchase, and Manufacturing.
-
-So, in a nutshell, what can impact your upgrade lead time?
-
-* Source & targeted versions
-* Installed apps
-* Volume of data
-* Amount of customization (models, fields, methods, workflows, reports, website, etc.)
-* Installation of new apps or configuration changes after the start of the test phase
-
-Usually, the delays experienced during the first request (waiting time between the time you
-submitted your first request for a test upgrade) can generally give you an idea of the time to wait
-for the production request.
-
-.. _db-upgrade/faq/custom-modules:
-
-Upgrade of the custom modules
------------------------------
-
-As stated in our :doc:`../legal/terms/enterprise`, section :ref:`charges_standard`, this optional
-service is subject to additional fees.
-
-If you have a custom code, you can choose to have it upgraded by our services, by one of our
-`partners <https://www.odoo.com/partners>`_ or you can do it yourself.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/editions-change:
-
-Editions change (from Community to Enterprise)
-----------------------------------------------
-
-An upgrade does not cover a change of `Editions <https://www.odoo.com/page/editions>`_
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/hosting-types-switch:
-
-Switching the hosting types (Self-hosted vs Online vs Odoo.sh)
---------------------------------------------------------------
-
-An upgrade does not cover a change of `Hosting types <https://www.odoo.com/page/hosting-types>`_.
-
-Open the following link to get :doc:`more information about how to change your hosting type
-<db_management/hosting_changes>`.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/release-notes:
-
-Release Notes by version
-------------------------
-
-Open our `Release Note <https://www.odoo.com/page/release-notes>`_ page to get a summary of the new
-features and improvements made in each version.
-
-.. _db-upgrade/assistance:
-
-Assistance
-==========
-
-.. _db-upgrade/contact:
-
-Contact our Upgrade service support
------------------------------------
-
-Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo
-Upgrade Team <mailto:upgrade@odoo.com>`_. We will be very pleased to answer it as soon as possible.
-
-.. _db-upgrade/supported-versions:
-
-Supported versions
-------------------
-
-Please note that Odoo provides support and bug fixing only for the three last major versions of Odoo.
-
-This is a factor to take into consideration before upgrading. If you are on an older version, we
-suggest you to prefer the most recent version to benefit from a longer support (before having to
-upgrade again).
-
-You can get more information about our :doc:`supported versions <../services/support/supported_versions>`.

content/administration/deployment.rst

@@ -1,10 +0,0 @@
-==========
-Deployment
-==========
-
-
-.. toctree::
-
-    deployment/deploy
-    deployment/cdn
-    deployment/email_gateway

content/administration/install.rst

@@ -1,782 +1,12 @@
+:nosearch:
 
-.. _setup/install:
+=======
+Install
+=======
 
-===============
-Installing Odoo
-===============
+.. toctree::
 
-There are multiple ways to install Odoo, or not install it at all, depending
-on the intended use case.
-
-This documents attempts to describe most of the installation options.
-
-:ref:`setup/install/online`
-    The easiest way to use Odoo in production or to try it.
-
-:ref:`setup/install/packaged`
-    Suitable for testing Odoo, developing modules and can be used for
-    long-term production use with additional deployment and maintenance work.
-
-:ref:`setup/install/source`
-    Provides greater flexibility:  e.g. allow multiple running Odoo versions on
-    the same system. Good for developing modules, can be used as base for
-    production deployment.
-
-:ref:`setup/install/docker`
-    If you usually use docker_ for development or deployment, an official
-    docker_ base image is available.
-
-
-.. _setup/install/editions:
-
-Editions
-========
-
-There are two different Editions_ of Odoo: the Community and Enterprise versions.
-Using the Enterprise version is possible on our SaaS_ and accessing the code is
-restricted to Enterprise customers and partners. The Community version is freely
-available to anyone.
-
-If you already use the Community version and wish to upgrade to Enterprise, please
-refer to :ref:`setup/enterprise` (except for :ref:`setup/install/source`).
-
-
-.. _setup/install/online:
-
-Online
-======
-
-Demo
-----
-
-To simply get a quick idea of Odoo, demo_ instances are available. They are
-shared instances which only live for a few hours, and can be used to browse
-around and try things out with no commitment.
-
-Demo_ instances require no local installation, just a web browser.
-
-SaaS
-----
-
-Trivial to start with, fully managed and migrated by Odoo S.A., Odoo's SaaS_
-provides private instances and starts out free. It can be used to discover and
-test Odoo and do non-code customizations (i.e. incompatible with custom modules
-or the Odoo Apps Store) without having to install it locally.
-
-Can be used for both testing Odoo and long-term production use.
-
-Like demo_ instances, SaaS_ instances require no local installation, a web
-browser is sufficient.
-
-
-.. _setup/install/packaged:
-
-Packaged installers
-===================
-
-Odoo provides packaged installers for Windows, deb-based distributions
-(Debian, Ubuntu, …) and RPM-based distributions (Fedora, CentOS, RHEL, …) for
-both the Community and Enterprise versions.
-
-These packages automatically set up all dependencies (for the Community version),
-but may be difficult to keep up-to-date.
-
-Official Community packages with all relevant dependency requirements are
-available on our nightly_ server. Both Communtiy and Enterprise packages can
-be downloaded from our download_ page (you must to be logged in as a paying
-customer or partner to download the Enterprise packages).
-
-Windows
--------
-
-#. Download the installer from our nightly_ server (Community only) or the Windows installer from
-   the download_ page (any edition).
-#. Execute the downloaded file.
-
-   .. warning:: | On Windows 8 and later you may see a warning titled "Windows protected your PC".
-                | Click on **More Info** and then on **Run anyway**.
-
-#. Accept the UAC_ prompt.
-#. Go through the various installation steps.
-
-Odoo will automatically be started at the end of the installation.
-
-Linux
------
-
-Debian/Ubuntu
-'''''''''''''
-
-Odoo 13.0 'deb' package currently supports `Debian Buster`_, `Ubuntu 18.04`_ or above.
-
-Prepare
-^^^^^^^
-
-Odoo needs a `PostgreSQL`_ server to run properly. The default configuration for
-the Odoo 'deb' package is to use the PostgreSQL server on the same host as your
-Odoo instance. Execute the following command in order to install the PostgreSQL server:
-
-.. code-block:: console
-
-  $ sudo apt install postgresql -y
-
-.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
-             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
-             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
-             details on the various versions.
-
-Repository
-^^^^^^^^^^
-
-Odoo S.A. provides a repository that can be used with  Debian and Ubuntu distributions. It can be
-used to install *Odoo Community Edition* by executing the following commands **as root**:
-
-.. code-block:: console
-
-    # wget -O - https://nightly.odoo.com/odoo.key | apt-key add -
-    # echo "deb http://nightly.odoo.com/13.0/nightly/deb/ ./" >> /etc/apt/sources.list.d/odoo.list
-    # apt-get update && apt-get install odoo
-
-You can then use the usual `apt-get upgrade` command to keep your installation up-to-date.
-
-At this moment, there is no nightly repository for the Enterprise Edition.
-
-Deb Package
-^^^^^^^^^^^
-
-Instead of using the repository as described above, the 'deb' packages for both the *Community* and
-*Enterprise* editions can be downloaded from the `official download page <download_>`_.
-
-Next, execute the following commands **as root**:
-
-.. code-block:: console
-
-    # dpkg -i <path_to_installation_package> # this probably fails with missing dependencies
-    # apt-get install -f # should install the missing dependencies
-    # dpkg -i <path_to_installation_package>
-
-This will install Odoo as a service, create the necessary PostgreSQL_ user
-and automatically start the server.
-
-.. warning:: The `python3-xlwt` Debian package does not exists in Debian Buster nor Ubuntu 18.04.
-             This python module is needed to export into xls format.
-
-             If you need the feature, you can install it manually with:
-
-             .. code-block:: console
-
-                $ sudo pip3 install xlwt
-
-.. warning:: The `num2words` python package does not exists in Debian Buster nor Ubuntu 18.04.
-             Textual amounts will not be rendered by Odoo and this could cause problems with the
-             `l10n_mx_edi` module.
-
-             If you need this feature, you can install manually with:
-
-             .. code-block:: console
-
-                $ sudo pip3 install num2words
-
-Fedora
-''''''
-
-Odoo 13.0 'rpm' package supports Fedora 30.
-
-Prepare
-^^^^^^^
-Odoo needs a `PostgreSQL`_ server to run properly. Make sure that the `sudo` command is available
-and well configured and, only then, execute the following command in order to install the PostgreSQL
-server:
-
-.. code-block:: console
-
-    $ sudo dnf install -y postgresql-server
-    $ sudo postgresql-setup --initdb --unit postgresql
-    $ sudo systemctl enable postgresql
-    $ sudo systemctl start postgresql
-
-.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
-             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
-             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
-             details on the various versions.
-
-Repository
-^^^^^^^^^^
-
-Odoo S.A. provides a repository that can be used with the Fedora distributions.
-It can be used to install *Odoo Community Edition* by executing the following
-commands:
-
-.. code-block:: console
-
-    $ sudo dnf config-manager --add-repo=https://nightly.odoo.com/13.0/nightly/rpm/odoo.repo
-    $ sudo dnf install -y odoo
-    $ sudo systemctl enable odoo
-    $ sudo systemctl start odoo
-
-RPM package
-^^^^^^^^^^^
-
-Instead of using the repository as described above, the 'rpm' packages for both the *Community* and
-*Enterprise* editions can be downloaded from the `official download page <download_>`_.
-
-Once downloaded, the package can be installed using the 'dnf' package manager:
-
-.. code-block:: console
-
-    $ sudo dnf localinstall odoo_13.0.latest.noarch.rpm
-    $ sudo systemctl enable odoo
-    $ sudo systemctl start odoo
-
-
-.. _setup/install/source:
-
-Source Install
-==============
-
-The source "installation" is really about not installing Odoo, and running it directly from source
-instead.
-
-This can be more convenient for module developers as the Odoo source is more easily accessible
-than using packaged installation (for information or to build this documentation and have it
-available offline).
-
-It also makes starting and stopping Odoo more flexible and explicit than the services set up by the
-packaged installations, and allows overriding settings using
-:ref:`command-line parameters <reference/cmdline>` without needing to edit a configuration file.
-
-Finally it provides greater control over the system's set up, and allows to more easily keep
-(and run) multiple versions of Odoo side-by-side.
-
-Windows
--------
-
-Fetch the sources
-'''''''''''''''''
-
-There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**.
-
-Archive
-^^^^^^^
-
-Community Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <community-repository_>`_
-* `Nightly server <nightly_>`_
-
-Enterprise Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <enterprise-repository_>`_
-
-Git
-^^^
-
-The following requires git_ to be installed on your machine and that you have basic knowledge of
-git commands.
-
-Community Edition:
-
-.. code-block:: doscon
-
-    C:\> git clone https://github.com/odoo/odoo.git
-
-
-Enterprise Edition: (see :ref:`setup/install/editions` to get access)
-
-.. code-block:: doscon
-
-  C:\> git clone https://github.com/odoo/enterprise.git
-
-.. note:: **The Enterprise git repository does not contain the full Odoo source code**. It is only
-          a collection of extra add-ons. The main server code is in the Community version. Running
-          the Enterprise version actually means running the server from the Community version with
-          the addons-path option set to the folder with the Enterprise version. You need to clone
-          both the Community and Enterprise repository to have a working Odoo Enterprise
-          installation.
-
-Prepare
-'''''''
-
-Python
-^^^^^^
-
-Odoo requires Python 3.6 or later to run. Visit `Python's download page <https://www.python.org/downloads/windows/>`_
-to download and install the latest version of Python 3 on your machine.
-
-During installation, check **Add Python 3 to PATH**, then click **Customize Installation** and make
-sure that **pip** is checked.
-
-.. note:: If Python 3 is already installed, make sure that the version is 3.6 or above, as previous
-          versions are not compatible with Odoo.
-
-          .. code-block:: doscon
-
-              C:\> python --version
-
-          Verify also that pip_ is installed for this version.
-
-          .. code-block:: doscon
-
-              C:\> pip --version
-
-PostgreSQL
-^^^^^^^^^^
-
-Odoo uses PostgreSQL as database management system. `Download and install PostgreSQL <https://www.postgresql.org/download/windows/>`_
-(supported version: 10.0 and later).
-
-By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to
-create a new PostgreSQL user:
-
-#. Add PostgreSQL's `bin` directory (by default: `C:\\Program Files\\PostgreSQL\\<version>\\bin`) to
-   your `PATH`.
-#. Create a postgres user with a password using the pg admin gui:
-
-   1. Open **pgAdmin**.
-   2. Double-click the server to create a connection.
-   3. Select :menuselection:`Object --> Create --> Login/Group Role`.
-   4. Enter the username in the **Role Name** field (e.g. `odoo`).
-   5. Open the **Definition** tab and enter the password (e.g. ``odoo``), then click **Save**.
-   6. Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?** to
-      `Yes`.
-
-Dependencies
-^^^^^^^^^^^^
-
-Before installing the dependencies, you must download and install the
-`Build Tools for Visual Studio <https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019>`_.
-When prompted, select **C++ build tools** in the **Workloads** tab and install them.
-
-Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
-community directory.
-
-.. tip:: It can be preferable to not mix python modules packages between different instances of Odoo
-         or with your system. You can use virtualenv_ to create isolated Python environments.
-
-Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip**
-on the requirements file in a terminal **with Administrator privileges**:
-
-.. code-block:: doscon
-
-    C:\> cd \CommunityPath
-    C:\> pip install setuptools wheel
-    C:\> pip install -r requirements.txt
-
-.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
-             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
-             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
-             details on the various versions.
-
-For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
-needed:
-
-#. Download and install `nodejs <https://nodejs.org/en/download/>`_.
-#. Install `rtlcss`:
-
-   .. code-block:: doscon
-
-       C:\> npm install -g rtlcss
-
-#. Edit the System Environment's variable `PATH` to add the folder where `rtlcss.cmd` is located
-   (typically: `C:\\Users\\<user>\\AppData\\Roaming\\npm\\`).
-
-Running Odoo
-''''''''''''
-
-Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the
-command-line interface of the server. It is located at the root of the Odoo Community directory.
-
-To configure the server, you can either specify :ref:`command-line arguments <reference/cmdline/server>` or a
-:ref:`configuration file <reference/cmdline/config>`.
-
-.. tip:: For the Enterprise edition, you must add the path to the `enterprise` addons to the
-         `addons-path` argument. Note that it must come before the other paths in `addons-path` for
-         addons to be loaded correctly.
-
-Common necessary configurations are:
-
-* PostgreSQL user and password.
-* Custom addon paths beyond the defaults, to load your own modules.
-
-A typical way to run the server would be:
-
-.. code-block:: doscon
-
-    C:\> cd CommunityPath/
-    C:\> python odoo-bin -r dbuser -w dbpassword --addons-path=addons -d mydb
-
-Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the
-PostgreSQL login, `dbpassword` is the PostgreSQL password
-and `mydb` is the default database to serve on `localhost:8069`. You can add other
-directory paths separated by a comma to ``addons`` at the end of the addons-path option.
-
-Linux
------
-
-Fetch the sources
-'''''''''''''''''
-
-There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**.
-
-Archive
-^^^^^^^
-
-Community Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <community-repository_>`_
-* `Nightly server <nightly_>`_
-
-Enterprise Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <enterprise-repository_>`_
-
-Git
-^^^
-
-The following requires git_ to be installed on your machine and that you have basic knowledge of
-git commands.
-
-Community Edition:
-
-.. code-block:: console
-
-    $ git clone https://github.com/odoo/odoo.git
-
-
-Enterprise Edition: (see :ref:`setup/install/editions` to get access)
-
-.. code-block:: console
-
-  $ git clone https://github.com/odoo/enterprise.git
-
-.. note:: **The Enterprise git repository does not contain the full Odoo source code**. It is only
-          a collection of extra add-ons. The main server code is in the Community version. Running
-          the Enterprise version actually means running the server from the Community version with
-          the addons-path option set to the folder with the Enterprise version. You need to clone
-          both the Community and Enterprise repository to have a working Odoo Enterprise
-          installation.
-
-Prepare
-'''''''
-
-Python
-^^^^^^
-
-Odoo requires Python 3.6 or later to run. Use your package manager to download and install Python 3
-on your machine if it is not already done.
-
-.. note:: If Python 3 is already installed, make sure that the version is 3.6 or above, as previous
-          versions are not compatible with Odoo.
-
-          .. code-block:: console
-
-              $ python3 --version
-
-          Verify also that pip_ is installed for this version.
-
-          .. code-block:: console
-
-              $ pip3 --version
-
-PostgreSQL
-^^^^^^^^^^
-
-Odoo uses PostgreSQL as database management system. Use your package manager to download and install
-PostgreSQL (supported version: 10.0 and later).
-
-On Debian/Unbuntu, it can be achieved by executing the following:
-
-.. code-block:: console
-
-    $ sudo apt install postgresql postgresql-client
-
-By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to
-create a new PostgreSQL user:
-
-.. code-block:: console
-
-  $ sudo -u postgres createuser -s $USER
-  $ createdb $USER
-
-.. note:: Because your PostgreSQL user has the same name as your Unix login, you will be able to
-          connect to the database without password.
-
-Dependencies
-^^^^^^^^^^^^
-
-For libraries using native code, it is necessary to install development tools and native
-dependencies before the Python dependencies of Odoo. They are available in `-dev` or `-devel`
-packages for Python, PostgreSQL, libxml2, libxslt1, libevent, libsasl2 and libldap2.
-
-On Debian/Unbuntu, the following command should install all the required libraries:
-
-.. code-block:: console
-
-    $ sudo apt install python3-dev libxml2-dev libxslt1-dev libldap2-dev libsasl2-dev \
-        libtiff5-dev libjpeg8-dev libopenjp2-7-dev zlib1g-dev libfreetype6-dev \
-        liblcms2-dev libwebp-dev libharfbuzz-dev libfribidi-dev libxcb1-dev libpq-dev
-
-Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
-community directory.
-
-.. tip:: It can be preferable to not mix python modules packages between different instances of Odoo
-         or with your system. You can use virtualenv_ to create isolated Python environments.
-
-Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip**
-on the requirements file:
-
-.. code-block:: console
-
-    $ cd /CommunityPath
-    $ pip3 install setuptools wheel
-    $ pip3 install -r requirements.txt
-
-.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
-             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
-             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
-             details on the various versions.
-
-For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
-needed:
-
-#. Download and install **nodejs** and **npm** with your package manager.
-#. Install `rtlcss`:
-
-   .. code-block:: console
-
-       $ sudo npm install -g rtlcss
-
-Running Odoo
-''''''''''''
-
-Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the
-command-line interface of the server. It is located at the root of the Odoo Community directory.
-
-To configure the server, you can either specify :ref:`command-line arguments <reference/cmdline/server>` or a
-:ref:`configuration file <reference/cmdline/config>`.
-
-.. tip:: For the Enterprise edition, you must add the path to the `enterprise` addons to the
-         `addons-path` argument. Note that it must come before the other paths in `addons-path` for
-         addons to be loaded correctly.
-
-Common necessary configurations are:
-
-* PostgreSQL user and password. Odoo has no defaults beyond
-  `psycopg2's defaults <http://initd.org/psycopg/docs/module.html>`_: connects over a UNIX socket on
-  port `5432` with the current user and no password.
-* Custom addon paths beyond the defaults, to load your own modules.
-
-A typical way to run the server would be:
-
-.. code-block:: console
-
-    $ cd /CommunityPath
-    $ python3 odoo-bin --addons-path=addons -d mydb
-
-Where `CommunityPath` is the path of the Odoo Community installation
-and `mydb` is the default database to serve on `localhost:8069`. You can add other
-directory paths separated by a comma to ``addons`` at the end of the addons-path option.
-
-Mac OS
-------
-
-Fetch the sources
-'''''''''''''''''
-
-There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**.
-
-Archive
-^^^^^^^
-
-Community Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <community-repository_>`_
-* `Nightly server <nightly_>`_
-
-Enterprise Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <enterprise-repository_>`_
-
-Git
-^^^
-
-The following requires git_ to be installed on your machine and that you have basic knowledge of
-git commands.
-
-Community Edition:
-
-.. code-block:: console
-
-    $ git clone https://github.com/odoo/odoo.git
-
-
-Enterprise Edition: (see :ref:`setup/install/editions` to get access)
-
-.. code-block:: console
-
-  $ git clone https://github.com/odoo/enterprise.git
-
-.. note:: **The Enterprise git repository does not contain the full Odoo source code**. It is only
-          a collection of extra add-ons. The main server code is in the Community version. Running
-          the Enterprise version actually means running the server from the Community version with
-          the addons-path option set to the folder with the Enterprise version. You need to clone
-          both the Community and Enterprise repository to have a working Odoo Enterprise
-          installation.
-
-Prepare
-'''''''
-
-Python
-^^^^^^
-
-Odoo requires Python 3.6 or later to run. Use your preferred package manager (homebrew_, macports_)
-to download and install Python 3 on your machine if it is not already done.
-
-.. note:: If Python 3 is already installed, make sure that the version is 3.6 or above, as previous
-          versions are not compatible with Odoo.
-
-          .. code-block:: console
-
-              $ python3 --version
-
-          Verify also that pip_ is installed for this version.
-
-          .. code-block:: console
-
-              $ pip3 --version
-
-PostgreSQL
-^^^^^^^^^^
-
-Odoo uses PostgreSQL as database management system. Use `postgres.app <https://postgresapp.com>`_
-to download and install PostgreSQL (supported version: 10.0 and later).
-
-By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to
-create a new PostgreSQL user:
-
-.. code-block:: console
-
-  $ sudo -u postgres createuser -s $USER
-  $ createdb $USER
-
-.. note:: Because your PostgreSQL user has the same name as your Unix login, you will be able to
-          connect to the database without password.
-
-Dependencies
-^^^^^^^^^^^^
-
-Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
-community directory.
-
-.. tip:: It can be preferable to not mix python modules packages between different instances of Odoo
-         or with your system. You can use virtualenv_ to create isolated Python environments.
-
-Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip**
-on the requirements file:
-
-.. code-block:: console
-
-   $ cd /CommunityPath
-   $ pip3 install setuptools wheel
-   $ pip3 install -r requirements.txt
-
-.. warning:: Non-Python dependencies need to be installed with a package manager:
-
-             #. Download and install the **Command Line Tools**:
-
-                .. code-block:: console
-
-                   $ xcode-select --install
-
-             #. Download and install the package manager of your choice (homebrew_, macports_).
-             #. Install non-python dependencies.
-
-.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
-             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
-             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
-             details on the various versions.
-
-For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
-needed:
-
-#. Download and install **nodejs** with your preferred package manager (homebrew_, macports_).
-#. Install `rtlcss`:
-
-   .. code-block:: console
-
-       $ sudo npm install -g rtlcss
-
-Running Odoo
-''''''''''''
-
-Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the
-command-line interface of the server. It is located at the root of the Odoo Community directory.
-
-To configure the server, you can either specify :ref:`command-line arguments <reference/cmdline/server>` or a
-:ref:`configuration file <reference/cmdline/config>`.
-
-.. tip:: For the Enterprise edition, you must add the path to the `enterprise` addons to the
-         `addons-path` argument. Note that it must come before the other paths in `addons-path` for
-         addons to be loaded correctly.
-
-Common necessary configurations are:
-
-* PostgreSQL user and password. Odoo has no defaults beyond
-  `psycopg2's defaults <http://initd.org/psycopg/docs/module.html>`_: connects over a UNIX socket on
-  port `5432` with the current user and no password.
-* Custom addon paths beyond the defaults, to load your own modules.
-
-A typical way to run the server would be:
-
-.. code-block:: console
-
-    $ cd /CommunityPath
-    $ python3 odoo-bin --addons-path=addons -d mydb
-
-Where `CommunityPath` is the path of the Odoo Community installation
-and `mydb` is the default database to serve on `localhost:8069`. You can add other
-directory paths separated by a comma to ``addons`` at the end of the addons-path option.
-
-
-.. _setup/install/docker:
-
-Docker
-======
-
-The full documentation on how to use Odoo with Docker can be found on the
-official Odoo `docker image <https://registry.hub.docker.com/_/odoo/>`_ page.
-
-.. _Debian Buster: https://www.debian.org/releases/buster/
-.. _demo: https://demo.odoo.com
-.. _docker: https://www.docker.com
-.. _download: https://www.odoo.com/page/download
-.. _Ubuntu 18.04: http://releases.ubuntu.com/18.04/
-.. _EPEL: https://fedoraproject.org/wiki/EPEL
-.. _PostgreSQL: http://www.postgresql.org
-.. _the official installer:
-.. _install pip:
-    https://pip.pypa.io/en/latest/installing.html#install-pip
-.. _Quilt: http://en.wikipedia.org/wiki/Quilt_(software)
-.. _saas: https://www.odoo.com/page/start
-.. _the wkhtmltopdf download page: https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.5
-.. _UAC: http://en.wikipedia.org/wiki/User_Account_Control
-.. _wkhtmltopdf: http://wkhtmltopdf.org
-.. _pip: https://pip.pypa.io
-.. _macports: https://www.macports.org
-.. _homebrew: http://brew.sh
-.. _wheels: https://wheel.readthedocs.org/en/latest/
-.. _virtualenv: https://pypi.python.org/pypi/virtualenv
-.. _virtualenvwrapper: https://virtualenvwrapper.readthedocs.io/en/latest/
-.. _pywin32: http://sourceforge.net/projects/pywin32/files/pywin32/
-.. _community-repository: https://github.com/odoo/odoo
-.. _enterprise-repository: https://github.com/odoo/enterprise
-.. _git: https://git-scm.com/
-.. _Editions: https://www.odoo.com/pricing#pricing_table_features
-.. _nightly: https://nightly.odoo.com/
-.. _extra: https://nightly.odoo.com/extra/
+    install/install
+    install/deploy
+    install/cdn
+    install/email_gateway

content/administration/install/cdn.rst

@@ -1,7 +1,6 @@
-
-========================================
-Deploying with Content Delivery Networks
-========================================
+===========================================
+Setting up a Content Delivery Network (CDN)
+===========================================
 
 .. _reference/cdn/keycdn:
 

content/administration/install/deploy.rst

@@ -1,7 +1,6 @@
-
-==============
-Deploying Odoo
-==============
+====================
+System configuration
+====================
 
 This document describes basic steps to set up Odoo in production or on an
 internet-facing server. It follows :ref:`installation <setup/install>`, and is

content/administration/install/email_gateway.rst

@@ -1,7 +1,6 @@
-
-==================
-Odoo email gateway
-==================
+=============
+Email gateway
+=============
 
 The Odoo mail gateway allows you to inject directly all the received emails in Odoo.
 

content/administration/install/install.rst

@@ -0,0 +1,782 @@
+
+.. _setup/install:
+
+===============
+Installing Odoo
+===============
+
+There are multiple ways to install Odoo, or not install it at all, depending
+on the intended use case.
+
+This documents attempts to describe most of the installation options.
+
+:ref:`setup/install/online`
+    The easiest way to use Odoo in production or to try it.
+
+:ref:`setup/install/packaged`
+    Suitable for testing Odoo, developing modules and can be used for
+    long-term production use with additional deployment and maintenance work.
+
+:ref:`setup/install/source`
+    Provides greater flexibility:  e.g. allow multiple running Odoo versions on
+    the same system. Good for developing modules, can be used as base for
+    production deployment.
+
+:ref:`setup/install/docker`
+    If you usually use docker_ for development or deployment, an official
+    docker_ base image is available.
+
+
+.. _setup/install/editions:
+
+Editions
+========
+
+There are two different Editions_ of Odoo: the Community and Enterprise versions.
+Using the Enterprise version is possible on our SaaS_ and accessing the code is
+restricted to Enterprise customers and partners. The Community version is freely
+available to anyone.
+
+If you already use the Community version and wish to upgrade to Enterprise, please
+refer to :ref:`setup/enterprise` (except for :ref:`setup/install/source`).
+
+
+.. _setup/install/online:
+
+Online
+======
+
+Demo
+----
+
+To simply get a quick idea of Odoo, demo_ instances are available. They are
+shared instances which only live for a few hours, and can be used to browse
+around and try things out with no commitment.
+
+Demo_ instances require no local installation, just a web browser.
+
+SaaS
+----
+
+Trivial to start with, fully managed and migrated by Odoo S.A., Odoo's SaaS_
+provides private instances and starts out free. It can be used to discover and
+test Odoo and do non-code customizations (i.e. incompatible with custom modules
+or the Odoo Apps Store) without having to install it locally.
+
+Can be used for both testing Odoo and long-term production use.
+
+Like demo_ instances, SaaS_ instances require no local installation, a web
+browser is sufficient.
+
+
+.. _setup/install/packaged:
+
+Packaged installers
+===================
+
+Odoo provides packaged installers for Windows, deb-based distributions
+(Debian, Ubuntu, …) and RPM-based distributions (Fedora, CentOS, RHEL, …) for
+both the Community and Enterprise versions.
+
+These packages automatically set up all dependencies (for the Community version),
+but may be difficult to keep up-to-date.
+
+Official Community packages with all relevant dependency requirements are
+available on our nightly_ server. Both Communtiy and Enterprise packages can
+be downloaded from our download_ page (you must to be logged in as a paying
+customer or partner to download the Enterprise packages).
+
+Windows
+-------
+
+#. Download the installer from our nightly_ server (Community only) or the Windows installer from
+   the download_ page (any edition).
+#. Execute the downloaded file.
+
+   .. warning:: | On Windows 8 and later you may see a warning titled "Windows protected your PC".
+                | Click on **More Info** and then on **Run anyway**.
+
+#. Accept the UAC_ prompt.
+#. Go through the various installation steps.
+
+Odoo will automatically be started at the end of the installation.
+
+Linux
+-----
+
+Debian/Ubuntu
+'''''''''''''
+
+Odoo 13.0 'deb' package currently supports `Debian Buster`_, `Ubuntu 18.04`_ or above.
+
+Prepare
+^^^^^^^
+
+Odoo needs a `PostgreSQL`_ server to run properly. The default configuration for
+the Odoo 'deb' package is to use the PostgreSQL server on the same host as your
+Odoo instance. Execute the following command in order to install the PostgreSQL server:
+
+.. code-block:: console
+
+  $ sudo apt install postgresql -y
+
+.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
+             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
+             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
+             details on the various versions.
+
+Repository
+^^^^^^^^^^
+
+Odoo S.A. provides a repository that can be used with  Debian and Ubuntu distributions. It can be
+used to install *Odoo Community Edition* by executing the following commands **as root**:
+
+.. code-block:: console
+
+    # wget -O - https://nightly.odoo.com/odoo.key | apt-key add -
+    # echo "deb http://nightly.odoo.com/13.0/nightly/deb/ ./" >> /etc/apt/sources.list.d/odoo.list
+    # apt-get update && apt-get install odoo
+
+You can then use the usual `apt-get upgrade` command to keep your installation up-to-date.
+
+At this moment, there is no nightly repository for the Enterprise Edition.
+
+Deb Package
+^^^^^^^^^^^
+
+Instead of using the repository as described above, the 'deb' packages for both the *Community* and
+*Enterprise* editions can be downloaded from the `official download page <download_>`_.
+
+Next, execute the following commands **as root**:
+
+.. code-block:: console
+
+    # dpkg -i <path_to_installation_package> # this probably fails with missing dependencies
+    # apt-get install -f # should install the missing dependencies
+    # dpkg -i <path_to_installation_package>
+
+This will install Odoo as a service, create the necessary PostgreSQL_ user
+and automatically start the server.
+
+.. warning:: The `python3-xlwt` Debian package does not exists in Debian Buster nor Ubuntu 18.04.
+             This python module is needed to export into xls format.
+
+             If you need the feature, you can install it manually with:
+
+             .. code-block:: console
+
+                $ sudo pip3 install xlwt
+
+.. warning:: The `num2words` python package does not exists in Debian Buster nor Ubuntu 18.04.
+             Textual amounts will not be rendered by Odoo and this could cause problems with the
+             `l10n_mx_edi` module.
+
+             If you need this feature, you can install manually with:
+
+             .. code-block:: console
+
+                $ sudo pip3 install num2words
+
+Fedora
+''''''
+
+Odoo 13.0 'rpm' package supports Fedora 30.
+
+Prepare
+^^^^^^^
+Odoo needs a `PostgreSQL`_ server to run properly. Make sure that the `sudo` command is available
+and well configured and, only then, execute the following command in order to install the PostgreSQL
+server:
+
+.. code-block:: console
+
+    $ sudo dnf install -y postgresql-server
+    $ sudo postgresql-setup --initdb --unit postgresql
+    $ sudo systemctl enable postgresql
+    $ sudo systemctl start postgresql
+
+.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
+             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
+             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
+             details on the various versions.
+
+Repository
+^^^^^^^^^^
+
+Odoo S.A. provides a repository that can be used with the Fedora distributions.
+It can be used to install *Odoo Community Edition* by executing the following
+commands:
+
+.. code-block:: console
+
+    $ sudo dnf config-manager --add-repo=https://nightly.odoo.com/13.0/nightly/rpm/odoo.repo
+    $ sudo dnf install -y odoo
+    $ sudo systemctl enable odoo
+    $ sudo systemctl start odoo
+
+RPM package
+^^^^^^^^^^^
+
+Instead of using the repository as described above, the 'rpm' packages for both the *Community* and
+*Enterprise* editions can be downloaded from the `official download page <download_>`_.
+
+Once downloaded, the package can be installed using the 'dnf' package manager:
+
+.. code-block:: console
+
+    $ sudo dnf localinstall odoo_13.0.latest.noarch.rpm
+    $ sudo systemctl enable odoo
+    $ sudo systemctl start odoo
+
+
+.. _setup/install/source:
+
+Source Install
+==============
+
+The source "installation" is really about not installing Odoo, and running it directly from source
+instead.
+
+This can be more convenient for module developers as the Odoo source is more easily accessible
+than using packaged installation (for information or to build this documentation and have it
+available offline).
+
+It also makes starting and stopping Odoo more flexible and explicit than the services set up by the
+packaged installations, and allows overriding settings using
+:ref:`command-line parameters <reference/cmdline>` without needing to edit a configuration file.
+
+Finally it provides greater control over the system's set up, and allows to more easily keep
+(and run) multiple versions of Odoo side-by-side.
+
+Windows
+-------
+
+Fetch the sources
+'''''''''''''''''
+
+There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**.
+
+Archive
+^^^^^^^
+
+Community Edition:
+
+* `Official download page <download_>`_
+* `GitHub repository <community-repository_>`_
+* `Nightly server <nightly_>`_
+
+Enterprise Edition:
+
+* `Official download page <download_>`_
+* `GitHub repository <enterprise-repository_>`_
+
+Git
+^^^
+
+The following requires git_ to be installed on your machine and that you have basic knowledge of
+git commands.
+
+Community Edition:
+
+.. code-block:: doscon
+
+    C:\> git clone https://github.com/odoo/odoo.git
+
+
+Enterprise Edition: (see :ref:`setup/install/editions` to get access)
+
+.. code-block:: doscon
+
+  C:\> git clone https://github.com/odoo/enterprise.git
+
+.. note:: **The Enterprise git repository does not contain the full Odoo source code**. It is only
+          a collection of extra add-ons. The main server code is in the Community version. Running
+          the Enterprise version actually means running the server from the Community version with
+          the addons-path option set to the folder with the Enterprise version. You need to clone
+          both the Community and Enterprise repository to have a working Odoo Enterprise
+          installation.
+
+Prepare
+'''''''
+
+Python
+^^^^^^
+
+Odoo requires Python 3.6 or later to run. Visit `Python's download page <https://www.python.org/downloads/windows/>`_
+to download and install the latest version of Python 3 on your machine.
+
+During installation, check **Add Python 3 to PATH**, then click **Customize Installation** and make
+sure that **pip** is checked.
+
+.. note:: If Python 3 is already installed, make sure that the version is 3.6 or above, as previous
+          versions are not compatible with Odoo.
+
+          .. code-block:: doscon
+
+              C:\> python --version
+
+          Verify also that pip_ is installed for this version.
+
+          .. code-block:: doscon
+
+              C:\> pip --version
+
+PostgreSQL
+^^^^^^^^^^
+
+Odoo uses PostgreSQL as database management system. `Download and install PostgreSQL <https://www.postgresql.org/download/windows/>`_
+(supported version: 10.0 and later).
+
+By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to
+create a new PostgreSQL user:
+
+#. Add PostgreSQL's `bin` directory (by default: `C:\\Program Files\\PostgreSQL\\<version>\\bin`) to
+   your `PATH`.
+#. Create a postgres user with a password using the pg admin gui:
+
+   1. Open **pgAdmin**.
+   2. Double-click the server to create a connection.
+   3. Select :menuselection:`Object --> Create --> Login/Group Role`.
+   4. Enter the username in the **Role Name** field (e.g. `odoo`).
+   5. Open the **Definition** tab and enter the password (e.g. ``odoo``), then click **Save**.
+   6. Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?** to
+      `Yes`.
+
+Dependencies
+^^^^^^^^^^^^
+
+Before installing the dependencies, you must download and install the
+`Build Tools for Visual Studio <https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019>`_.
+When prompted, select **C++ build tools** in the **Workloads** tab and install them.
+
+Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
+community directory.
+
+.. tip:: It can be preferable to not mix python modules packages between different instances of Odoo
+         or with your system. You can use virtualenv_ to create isolated Python environments.
+
+Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip**
+on the requirements file in a terminal **with Administrator privileges**:
+
+.. code-block:: doscon
+
+    C:\> cd \CommunityPath
+    C:\> pip install setuptools wheel
+    C:\> pip install -r requirements.txt
+
+.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
+             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
+             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
+             details on the various versions.
+
+For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
+needed:
+
+#. Download and install `nodejs <https://nodejs.org/en/download/>`_.
+#. Install `rtlcss`:
+
+   .. code-block:: doscon
+
+       C:\> npm install -g rtlcss
+
+#. Edit the System Environment's variable `PATH` to add the folder where `rtlcss.cmd` is located
+   (typically: `C:\\Users\\<user>\\AppData\\Roaming\\npm\\`).
+
+Running Odoo
+''''''''''''
+
+Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the
+command-line interface of the server. It is located at the root of the Odoo Community directory.
+
+To configure the server, you can either specify :ref:`command-line arguments <reference/cmdline/server>` or a
+:ref:`configuration file <reference/cmdline/config>`.
+
+.. tip:: For the Enterprise edition, you must add the path to the `enterprise` addons to the
+         `addons-path` argument. Note that it must come before the other paths in `addons-path` for
+         addons to be loaded correctly.
+
+Common necessary configurations are:
+
+* PostgreSQL user and password.
+* Custom addon paths beyond the defaults, to load your own modules.
+
+A typical way to run the server would be:
+
+.. code-block:: doscon
+
+    C:\> cd CommunityPath/
+    C:\> python odoo-bin -r dbuser -w dbpassword --addons-path=addons -d mydb
+
+Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the
+PostgreSQL login, `dbpassword` is the PostgreSQL password
+and `mydb` is the default database to serve on `localhost:8069`. You can add other
+directory paths separated by a comma to ``addons`` at the end of the addons-path option.
+
+Linux
+-----
+
+Fetch the sources
+'''''''''''''''''
+
+There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**.
+
+Archive
+^^^^^^^
+
+Community Edition:
+
+* `Official download page <download_>`_
+* `GitHub repository <community-repository_>`_
+* `Nightly server <nightly_>`_
+
+Enterprise Edition:
+
+* `Official download page <download_>`_
+* `GitHub repository <enterprise-repository_>`_
+
+Git
+^^^
+
+The following requires git_ to be installed on your machine and that you have basic knowledge of
+git commands.
+
+Community Edition:
+
+.. code-block:: console
+
+    $ git clone https://github.com/odoo/odoo.git
+
+
+Enterprise Edition: (see :ref:`setup/install/editions` to get access)
+
+.. code-block:: console
+
+  $ git clone https://github.com/odoo/enterprise.git
+
+.. note:: **The Enterprise git repository does not contain the full Odoo source code**. It is only
+          a collection of extra add-ons. The main server code is in the Community version. Running
+          the Enterprise version actually means running the server from the Community version with
+          the addons-path option set to the folder with the Enterprise version. You need to clone
+          both the Community and Enterprise repository to have a working Odoo Enterprise
+          installation.
+
+Prepare
+'''''''
+
+Python
+^^^^^^
+
+Odoo requires Python 3.6 or later to run. Use your package manager to download and install Python 3
+on your machine if it is not already done.
+
+.. note:: If Python 3 is already installed, make sure that the version is 3.6 or above, as previous
+          versions are not compatible with Odoo.
+
+          .. code-block:: console
+
+              $ python3 --version
+
+          Verify also that pip_ is installed for this version.
+
+          .. code-block:: console
+
+              $ pip3 --version
+
+PostgreSQL
+^^^^^^^^^^
+
+Odoo uses PostgreSQL as database management system. Use your package manager to download and install
+PostgreSQL (supported version: 10.0 and later).
+
+On Debian/Unbuntu, it can be achieved by executing the following:
+
+.. code-block:: console
+
+    $ sudo apt install postgresql postgresql-client
+
+By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to
+create a new PostgreSQL user:
+
+.. code-block:: console
+
+  $ sudo -u postgres createuser -s $USER
+  $ createdb $USER
+
+.. note:: Because your PostgreSQL user has the same name as your Unix login, you will be able to
+          connect to the database without password.
+
+Dependencies
+^^^^^^^^^^^^
+
+For libraries using native code, it is necessary to install development tools and native
+dependencies before the Python dependencies of Odoo. They are available in `-dev` or `-devel`
+packages for Python, PostgreSQL, libxml2, libxslt1, libevent, libsasl2 and libldap2.
+
+On Debian/Unbuntu, the following command should install all the required libraries:
+
+.. code-block:: console
+
+    $ sudo apt install python3-dev libxml2-dev libxslt1-dev libldap2-dev libsasl2-dev \
+        libtiff5-dev libjpeg8-dev libopenjp2-7-dev zlib1g-dev libfreetype6-dev \
+        liblcms2-dev libwebp-dev libharfbuzz-dev libfribidi-dev libxcb1-dev libpq-dev
+
+Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
+community directory.
+
+.. tip:: It can be preferable to not mix python modules packages between different instances of Odoo
+         or with your system. You can use virtualenv_ to create isolated Python environments.
+
+Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip**
+on the requirements file:
+
+.. code-block:: console
+
+    $ cd /CommunityPath
+    $ pip3 install setuptools wheel
+    $ pip3 install -r requirements.txt
+
+.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
+             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
+             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
+             details on the various versions.
+
+For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
+needed:
+
+#. Download and install **nodejs** and **npm** with your package manager.
+#. Install `rtlcss`:
+
+   .. code-block:: console
+
+       $ sudo npm install -g rtlcss
+
+Running Odoo
+''''''''''''
+
+Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the
+command-line interface of the server. It is located at the root of the Odoo Community directory.
+
+To configure the server, you can either specify :ref:`command-line arguments <reference/cmdline/server>` or a
+:ref:`configuration file <reference/cmdline/config>`.
+
+.. tip:: For the Enterprise edition, you must add the path to the `enterprise` addons to the
+         `addons-path` argument. Note that it must come before the other paths in `addons-path` for
+         addons to be loaded correctly.
+
+Common necessary configurations are:
+
+* PostgreSQL user and password. Odoo has no defaults beyond
+  `psycopg2's defaults <http://initd.org/psycopg/docs/module.html>`_: connects over a UNIX socket on
+  port `5432` with the current user and no password.
+* Custom addon paths beyond the defaults, to load your own modules.
+
+A typical way to run the server would be:
+
+.. code-block:: console
+
+    $ cd /CommunityPath
+    $ python3 odoo-bin --addons-path=addons -d mydb
+
+Where `CommunityPath` is the path of the Odoo Community installation
+and `mydb` is the default database to serve on `localhost:8069`. You can add other
+directory paths separated by a comma to ``addons`` at the end of the addons-path option.
+
+Mac OS
+------
+
+Fetch the sources
+'''''''''''''''''
+
+There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**.
+
+Archive
+^^^^^^^
+
+Community Edition:
+
+* `Official download page <download_>`_
+* `GitHub repository <community-repository_>`_
+* `Nightly server <nightly_>`_
+
+Enterprise Edition:
+
+* `Official download page <download_>`_
+* `GitHub repository <enterprise-repository_>`_
+
+Git
+^^^
+
+The following requires git_ to be installed on your machine and that you have basic knowledge of
+git commands.
+
+Community Edition:
+
+.. code-block:: console
+
+    $ git clone https://github.com/odoo/odoo.git
+
+
+Enterprise Edition: (see :ref:`setup/install/editions` to get access)
+
+.. code-block:: console
+
+  $ git clone https://github.com/odoo/enterprise.git
+
+.. note:: **The Enterprise git repository does not contain the full Odoo source code**. It is only
+          a collection of extra add-ons. The main server code is in the Community version. Running
+          the Enterprise version actually means running the server from the Community version with
+          the addons-path option set to the folder with the Enterprise version. You need to clone
+          both the Community and Enterprise repository to have a working Odoo Enterprise
+          installation.
+
+Prepare
+'''''''
+
+Python
+^^^^^^
+
+Odoo requires Python 3.6 or later to run. Use your preferred package manager (homebrew_, macports_)
+to download and install Python 3 on your machine if it is not already done.
+
+.. note:: If Python 3 is already installed, make sure that the version is 3.6 or above, as previous
+          versions are not compatible with Odoo.
+
+          .. code-block:: console
+
+              $ python3 --version
+
+          Verify also that pip_ is installed for this version.
+
+          .. code-block:: console
+
+              $ pip3 --version
+
+PostgreSQL
+^^^^^^^^^^
+
+Odoo uses PostgreSQL as database management system. Use `postgres.app <https://postgresapp.com>`_
+to download and install PostgreSQL (supported version: 10.0 and later).
+
+By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to
+create a new PostgreSQL user:
+
+.. code-block:: console
+
+  $ sudo -u postgres createuser -s $USER
+  $ createdb $USER
+
+.. note:: Because your PostgreSQL user has the same name as your Unix login, you will be able to
+          connect to the database without password.
+
+Dependencies
+^^^^^^^^^^^^
+
+Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
+community directory.
+
+.. tip:: It can be preferable to not mix python modules packages between different instances of Odoo
+         or with your system. You can use virtualenv_ to create isolated Python environments.
+
+Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip**
+on the requirements file:
+
+.. code-block:: console
+
+   $ cd /CommunityPath
+   $ pip3 install setuptools wheel
+   $ pip3 install -r requirements.txt
+
+.. warning:: Non-Python dependencies need to be installed with a package manager:
+
+             #. Download and install the **Command Line Tools**:
+
+                .. code-block:: console
+
+                   $ xcode-select --install
+
+             #. Download and install the package manager of your choice (homebrew_, macports_).
+             #. Install non-python dependencies.
+
+.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
+             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
+             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
+             details on the various versions.
+
+For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
+needed:
+
+#. Download and install **nodejs** with your preferred package manager (homebrew_, macports_).
+#. Install `rtlcss`:
+
+   .. code-block:: console
+
+       $ sudo npm install -g rtlcss
+
+Running Odoo
+''''''''''''
+
+Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the
+command-line interface of the server. It is located at the root of the Odoo Community directory.
+
+To configure the server, you can either specify :ref:`command-line arguments <reference/cmdline/server>` or a
+:ref:`configuration file <reference/cmdline/config>`.
+
+.. tip:: For the Enterprise edition, you must add the path to the `enterprise` addons to the
+         `addons-path` argument. Note that it must come before the other paths in `addons-path` for
+         addons to be loaded correctly.
+
+Common necessary configurations are:
+
+* PostgreSQL user and password. Odoo has no defaults beyond
+  `psycopg2's defaults <http://initd.org/psycopg/docs/module.html>`_: connects over a UNIX socket on
+  port `5432` with the current user and no password.
+* Custom addon paths beyond the defaults, to load your own modules.
+
+A typical way to run the server would be:
+
+.. code-block:: console
+
+    $ cd /CommunityPath
+    $ python3 odoo-bin --addons-path=addons -d mydb
+
+Where `CommunityPath` is the path of the Odoo Community installation
+and `mydb` is the default database to serve on `localhost:8069`. You can add other
+directory paths separated by a comma to ``addons`` at the end of the addons-path option.
+
+
+.. _setup/install/docker:
+
+Docker
+======
+
+The full documentation on how to use Odoo with Docker can be found on the
+official Odoo `docker image <https://registry.hub.docker.com/_/odoo/>`_ page.
+
+.. _Debian Buster: https://www.debian.org/releases/buster/
+.. _demo: https://demo.odoo.com
+.. _docker: https://www.docker.com
+.. _download: https://www.odoo.com/page/download
+.. _Ubuntu 18.04: http://releases.ubuntu.com/18.04/
+.. _EPEL: https://fedoraproject.org/wiki/EPEL
+.. _PostgreSQL: http://www.postgresql.org
+.. _the official installer:
+.. _install pip:
+    https://pip.pypa.io/en/latest/installing.html#install-pip
+.. _Quilt: http://en.wikipedia.org/wiki/Quilt_(software)
+.. _saas: https://www.odoo.com/page/start
+.. _the wkhtmltopdf download page: https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.5
+.. _UAC: http://en.wikipedia.org/wiki/User_Account_Control
+.. _wkhtmltopdf: http://wkhtmltopdf.org
+.. _pip: https://pip.pypa.io
+.. _macports: https://www.macports.org
+.. _homebrew: http://brew.sh
+.. _wheels: https://wheel.readthedocs.org/en/latest/
+.. _virtualenv: https://pypi.python.org/pypi/virtualenv
+.. _virtualenvwrapper: https://virtualenvwrapper.readthedocs.io/en/latest/
+.. _pywin32: http://sourceforge.net/projects/pywin32/files/pywin32/
+.. _community-repository: https://github.com/odoo/odoo
+.. _enterprise-repository: https://github.com/odoo/enterprise
+.. _git: https://git-scm.com/
+.. _Editions: https://www.odoo.com/pricing#pricing_table_features
+.. _nightly: https://nightly.odoo.com/
+.. _extra: https://nightly.odoo.com/extra/

content/administration/maintain.rst

@@ -0,0 +1,14 @@
+:nosearch:
+
+========
+Maintain
+========
+
+.. toctree::
+
+    maintain/update
+    maintain/enterprise
+    maintain/hosting_changes
+    maintain/online
+    maintain/on_premise
+    maintain/supported_versions

content/administration/maintain/enterprise.rst

@@ -1,9 +1,9 @@
 
 .. _setup/enterprise:
 
-============================
-From Community to Enterprise
-============================
+===============================
+Upgrade Community to Enterprise
+===============================
 
 Depending on your current installation, there are multiple ways to upgrade
 your community version.

content/administration/maintain/hosting_changes.rst

@@ -1,9 +1,9 @@
 
 .. _db_management/hosting_changes:
 
-===============
-Hosting Changes
-===============
+=======================
+Change hosting solution
+=======================
 
 You may want to move your Odoo database from one hosting solution to another.
 Depending on the platforms, you have to do it by yourself or contact our support team first.
@@ -59,4 +59,3 @@ From Odoo.sh to on-premises
 1.  Grab a :ref:`backup of your Odoo.sh production database <odoo_sh_branches_backups>`.
 2.  Restore it from the database manager on your local server.
 
-

content/administration/maintain/on_premise.rst

@@ -1,9 +1,6 @@
-
-.. _db_premise:
-
-===============================
-On-premises Database management
-===============================
+==============================
+On-premise database management
+==============================
 
 Register a database
 ===================
@@ -21,7 +18,7 @@ Registration Error Message
 If you are unable to register your database, you will likely encounter this
 message:
 
-.. image:: media/error_message_sub_code.png
+.. image:: on_premise/error_message_sub_code.png
     :align: center
     :alt: Something went wrong while registering your database,
           you can try again or contact Odoo Help
@@ -44,14 +41,14 @@ Solutions
   * You can unlink the old database yourself on your `Odoo Contract
     <https://accounts.odoo.com/my/subscription>`__ with the button "Unlink database"
 
-    .. image:: media/unlink_single_db.png
+    .. image:: on_premise/unlink_single_db.png
         :align: center
 
 
     A confirmation message will appear; make sure this is the correct database as
     it will be deactivated shortly:
 
-    .. image:: media/unlink_confirm_enterprise_edition.png
+    .. image:: on_premise/unlink_confirm_enterprise_edition.png
         :align: center
 
 
@@ -65,7 +62,7 @@ Solutions
     <https://accounts.odoo.com/my/subscription>`__, a short message will appear
     specifying which database is problematic:
 
-    .. image:: media/unlink_db_name_collision.png
+    .. image:: on_premise/unlink_db_name_collision.png
         :align: center
 
 
@@ -96,7 +93,7 @@ Error message due to too many users
 If you have more users in your local database than provisionned in your
 Odoo Enterprise subscription, you may encounter this message:
 
-.. image:: media/add_more_users.png
+.. image:: on_premise/add_more_users.png
     :align: center
     :alt: This database will expire in X days, you
           have more users than your subscription allows
@@ -125,7 +122,7 @@ Database expired error message
 If your database reaches its expiration date before your renew your subscription,
 you will encounter this message:
 
-.. image:: media/database_expired.png
+.. image:: on_premise/database_expired.png
     :align: center
     :alt: This database has expired.
 
@@ -157,7 +154,7 @@ You can duplicate your database by accessing the database manager on your
 server (<odoo-server>/web/database/manager). In this page, you can easily
 duplicate your database (among other things).
 
-.. image:: media/db_manager.gif
+.. image:: on_premise/db_manager.gif
     :align: center
 
 
@@ -175,5 +172,5 @@ System Parameters`, we advise you to use a `uuid generator <https://www.uuidtool
 use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any
 other record by clicking on it and using the edit button.
 
-.. image:: media/db_uuid.png
+.. image:: on_premise/db_uuid.png
     :align: center

content/administration/maintain/online.rst

@@ -0,0 +1,143 @@
+=================================
+Online (SaaS) database management
+=================================
+
+To manage a database, sign in to https://www.odoo.com and access the `database management page
+<https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on *My Databases*.
+
+.. image:: online/my-databases.png
+   :align: center
+   :alt: Clicking on the user icon opens a drop-down menu. "My databases" button is highlighted.
+
+.. note::
+   Make sure you are connected as the administrator of the database you want to manage.
+
+.. image:: online/dropdown-menu.png
+   :align: right
+   :alt: Clicking on the gear icon opens the drop-down menu.
+
+Open the drop-down menu next to the database you want to manage by clicking on the gear icon.
+
+Several actions are available:
+
+- :ref:`online/upgrade`
+- :ref:`online/duplicate`
+- :ref:`online/rename`
+- :ref:`online/download`
+- :ref:`online/domains`
+- :ref:`online/tags`
+- :ref:`online/delete`
+- :ref:`online/contact-support`
+- :ref:`online/users`
+
+.. _online/upgrade:
+
+Upgrade
+=======
+
+Upgrade the database to the latest Odoo version.
+
+.. warning::
+   Upgrading a database to a newer version of Odoo is a complex operation that requires time and
+   caution. It is essential to test the upgrade before upgrading the production database.
+
+.. seealso::
+   - :doc:`../upgrade/process`
+
+.. _online/duplicate:
+
+Duplicate
+=========
+
+Make an exact copy of the database to be able to perform testing without compromising the daily
+operations.
+
+.. important::
+   - By checking *For testing purposes*, all external communication (emails, payments, delivery
+     orders, etc.) are disabled by default on the duplicated database.
+   - Duplicate databases expire automatically after 15 days.
+
+.. _online/rename:
+
+Rename
+======
+
+Rename the database and its URL.
+
+.. _online/download:
+
+Download
+========
+
+Download instantly a ZIP file with a backup of the database.
+
+.. note::
+   Databases are backed up daily according to the `Odoo Cloud SLA
+   <https://www.odoo.com/cloud-sla>`_.
+
+.. _online/domains:
+
+Domains
+=======
+
+Configure custom domains to access the database via another URL.
+
+.. seealso::
+   - :doc:`/applications/websites/website/publish/domain_name`
+
+.. _online/tags:
+
+Tags
+====
+
+Add tags to sort your databases out. You can search the tags in the search bar.
+
+.. _online/delete:
+
+Delete
+======
+
+Delete a database instantly.
+
+.. danger::
+   Deleting a database means that all data is permanently lost. The deletion is instant and for all
+   users. It is recommended to create a backup of the database before deleting it.
+
+Read carefully the warning message that pops up and proceed only if you fully understand the
+implications of deleting a database:
+
+.. image:: online/delete.png
+   :align: center
+   :alt: A warning message is prompted before deleting a database.
+
+.. note::
+   - Only an administrator can delete a database.
+   - The database name is immediately available for a new database.
+   - It is not possible to delete a database if it is expired or linked to a subscription. If
+     needed, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
+   - To delete your account, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
+
+.. _online/contact-support:
+
+Contact Support
+===============
+
+Access the Odoo `support page <https://www.odoo.com/help>`_ with your database's details already
+pre-filled.
+
+.. _online/users:
+
+Invite / Remove Users
+=====================
+
+To invite users, fill out the email address of the new user and click on *Invite*. To add multiple
+users, click on *Add more users*.
+
+.. image:: online/invite-users.png
+   :align: center
+   :alt: Clicking on "Add more users" adds additional email fields.
+
+To remove users, select the users to remove and click on *Remove*.
+
+.. seealso::
+   - :doc:`/applications/general/users/manage_users`

content/administration/maintain/supported_versions.rst

@@ -0,0 +1,88 @@
+
+.. _supported_versions:
+
+==================
+Supported versions
+==================
+
+
+Odoo provides support and bug fixing **for the 3 last major versions** of Odoo.
+
+Users hosted on **Odoo Online** may use intermediary versions (sometimes called *SaaS versions*) that are
+supported as well. These versions are not published for Odoo.sh or On-Premise
+installations.
+
+
+What's the support status of my Odoo?
+=====================================
+
+This matrix shows the support status of every version.
+
+**Major releases are in bold type.**
+
++-----------------+-------------+----------+-------------+----------------+------------------------+
+|                 | Odoo Online | Odoo.sh  | On-Premise  | Release date   | End of support         |
++=================+=============+==========+=============+================+========================+
+| **Odoo 15.0**   | |green|     | |green|  | |green|     | October 2021   | October 2024 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 14.0**   | |green|     | |green|  | |green|     | October 2020   | October 2023 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 13.0**   | |green|     | |green|  | |green|     | October 2019   | October 2022 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 12.saas~3  | |orange|    | N/A      | N/A         | August 2019    |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 12.0**   | |orange|    | |orange| | |red|       | October 2018   | October 2021           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 11.saas~3  | |orange|    | N/A      | N/A         | April 2018     |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 11.0**   | |orange|    | |orange| | |red|       | October 2017   | October 2020           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 10.saas~15 | |orange|    | N/A      | N/A         | March 2017     |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 10.saas~14 | |orange|    | N/A      | N/A         | January 2017   |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 10.0**   | |orange|    | |orange| | |red|       | October 2016   | October 2019           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 9.saas~11  | |orange|    | N/A      | N/A         | May 2016       |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 9.0**    | |orange|    | N/A      | |red|       | October 2015   | October 2018           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 8.saas~6   | |orange|    | N/A      | N/A         | February 2015  |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 8.0**    | |orange|    | N/A      | |red|       | September 2014 | October 2017           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+
+
+.. note::
+
+    |green| Supported version
+
+    |red| End-of-support
+
+    N/A Never released for this platform
+
+    |orange| Some of our older customers may still run this version on our Odoo Online servers, we provide help only on blocking issues and advise you to upgrade.
+
+    🏁 Future version, not released yet
+
+
+.. This is an awful way to display colored circles but "Large Green Circle Emoji" was only released
+   in 2019 (see https://unicode-table.com/en/1F7E2/). Let's wait a few more years...
+
+.. |green| image:: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyMzIuMTkgMjMyLjE5Ij48Y2lyY2xlIGN4PSIxMTYuMDkiIGN5PSIxMTYuMDkiIHI9IjExNi4wOSIgc3R5bGU9ImZpbGw6IzAwYTcwMCIvPjwvc3ZnPg==
+   :width: 15
+
+.. |red| image:: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyMzIuMTkgMjMyLjE5Ij48Y2lyY2xlIGN4PSIxMTYuMDkiIGN5PSIxMTYuMDkiIHI9IjExNi4wOSIgc3R5bGU9ImZpbGw6I2QwMDAwMCIvPjwvc3ZnPg==
+   :width: 15
+
+.. |orange| image:: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyMzIuMTkgMjMyLjE5Ij48Y2lyY2xlIGN4PSIxMTYuMDkiIGN5PSIxMTYuMDkiIHI9IjExNi4wOSIgc3R5bGU9ImZpbGw6I2ZmYTcwMCIvPjwvc3ZnPg==
+   :width: 15
+
+I run an older version of Odoo/OpenERP/TinyERP
+==============================================
+
+OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform.
+
+TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform.
+
+Even though we don't support older versions, you can always `upgrade from any version <https://upgrade.odoo.com/>`_.

content/administration/maintain/update.rst

@@ -1,9 +1,9 @@
 
 .. _setup/update:
 
-=============================
-Updating an Odoo installation
-=============================
+==============
+Bugfix updates
+==============
 
 Introduction
 ============
@@ -147,4 +147,4 @@ Docker
 ------
 
 Please refer to our `Docker image documentation <https://hub.docker.com/_/odoo/>`_ for
-specific update instructions.
+specific update instructions.

content/administration/odoo_sh.rst

@@ -1,5 +1,7 @@
+:nosearch:
+
 =======
-Odoo sh
+Odoo.sh
 =======
 
 

content/administration/odoo_sh/advanced.rst

@@ -1,3 +1,4 @@
+:nosearch:
 
 =================
 Advanced
@@ -8,5 +9,4 @@ Advanced
 
    advanced/containers
    advanced/submodules
-   advanced/upgrade_your_database
    advanced/frequent_technical_questions

content/administration/odoo_sh/advanced/containers.rst

@@ -167,7 +167,7 @@ In the above commands, the argument:
 * ``--stop-after-init`` will immediately shutdown the server instance after it completed the operations you asked.
 
 More options are available and detailed in the
-:doc:`CLI documentation </developer/reference/cmdline>`.
+:doc:`CLI documentation </developer/misc/other/cmdline>`.
 
 You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh to run your server.
 Look for "*odoo: addons paths*":

content/administration/odoo_sh/advanced/frequent_technical_questions.rst

@@ -30,3 +30,26 @@ We advise that:
   `idempotent <https://stackoverflow.com/a/1077421/3332416>`_: they must not
   cause side-effects if they are started more often than expected.
 
+Why are the installed Python libraries different from Odoo's own requirements.txt?
+----------------------------------------------------------------------------------
+
+On Odoo.sh, Odoo uses the Python libraries available in the Linux distribution
+to fulfill its dependencies. Odoo is compatible with the packages in Debian
+stable and Ubuntu LTS releases. The `requirements.txt <https://github.com/odoo/odoo/blob/master/requirements.txt>`_
+included with Odoo is intended for use on different distributions where the
+same library versions might not be available. As a result, Odoo.sh does not use
+Odoo's own requirements.txt file and there might be occasional differences
+between them.
+
+For example, reportlab 3.5.34 is the version available on Ubuntu 20.04 as a
+distribution package. That distribution uses Python 3.8, in which case
+requirements.txt in `Odoo 14.0 <https://github.com/odoo/odoo/blob/2097c75dc38b310c4d9ddecd79e2218448a51a4c/requirements.txt#L46>`_
+specifies reportlab 3.5.55. Normally speaking the pin in requirements.txt
+should reflect that and be 3.5.34, but it turns out that this version only
+works if Ubuntu's patches are applied to it. Ubuntu LTS releases have
+backporting of bug fixes, which means that the behavior of a Python package in
+the distribution might not be the same as that same version when installed with
+pip. This is the case with reportlab, which is why the pin is different.
+
+If a custom module requires a more recent version of a package than is
+installed on Odoo.sh, you can specify it in your own requirements.txt file.

content/administration/odoo_sh/getting_started.rst

@@ -1,3 +1,4 @@
+:nosearch:
 
 =================
 Get started

content/administration/odoo_sh/getting_started/branches.rst

@@ -42,7 +42,7 @@ instance will be held temporarily unavailable for maintenance reason.
 
 This method is equivalent to perform an upgrade of the module through the Apps menu,
 or through the :code:`-u` switch of
-:doc:`the command line </developer/reference/cmdline>`.
+:doc:`the command line </developer/misc/other/cmdline>`.
 
 In the case the changes in the commit prevent the server to restart,
 or if the modules update fails,

content/administration/odoo_sh/getting_started/create.rst

@@ -78,7 +78,8 @@ You can start using Odoo.sh. Your first build is about to be created. You will s
 Import your database
 ====================
 
-You can import your database in your Odoo.sh project as long as this is an Odoo 10.0, 11.0 or above database.
+You can import your database in your Odoo.sh project as long as it is in a :doc:`supported version
+</administration/maintain/supported_versions>` of Odoo.
 
 Push your modules in production
 -------------------------------
@@ -183,4 +184,4 @@ as you can only have one database linked per subscription.
 
 If you plan to make it your production,
 unlink your former database from the subscription, and register the newly imported database.
-Read the :ref:`database registration documentation <db_premise>` for instructions.
+Read the :doc:`database registration documentation <../../maintain/on_premise>` for instructions.

content/administration/odoo_sh/overview.rst

@@ -1,3 +1,4 @@
+:nosearch:
 
 =================
 Overview

content/administration/upgrade.rst

@@ -0,0 +1,12 @@
+:nosearch:
+
+=======
+Upgrade
+=======
+
+.. toctree::
+
+    upgrade/process
+    upgrade/odoo_sh
+    upgrade/service_level
+    upgrade/faq

content/administration/upgrade/faq.rst

@@ -0,0 +1,171 @@
+.. |assistance-contact| replace::
+   If you need Odoo assistance on this matter, please get in touch with your Odoo Account Manager or
+   our `Sales department`_.
+.. _Sales department: mailto:sales@odoo.com
+
+===
+FAQ
+===
+
+.. _upgrade-faq/why:
+
+Why upgrade
+===========
+
+* You benefit from the latest features of the :ref:`new major version
+  <upgrade-faq/release-notes>` released by Odoo.
+* If you are in an :ref:`unsupported version <upgrade/supported-versions>`, you get a new version
+  with support.
+
+.. _upgrade-faq/when:
+
+When to upgrade
+===============
+
+Whenever you want. You can make your upgrade request as soon as a new version is released or when
+your version turns unsupported, and you still wish to enjoy support.
+
+.. _upgrade-faq/availability:
+
+Availability of the new version
+===============================
+
+As soon as Odoo announces the release of a new major version, you can create a test upgrade request
+to try the latest version. Please note that at this point, the upgrade scripts will only have been
+tested with demo data. Please report any issue you might encounter while testing via the `Odoo
+Support page <https://www.odoo.com/help>`_ and make sure to be happy with your test version before
+requesting the upgrade of your database in production.
+
+.. _upgrade-faq/duration:
+
+Duration of the upgrade
+=======================
+
+It is impossible to give time estimates for every upgrade request.
+
+In general, the "smaller" the database, the quickest the upgrade request is completed. A single-user
+database that uses only CRM will be processed faster than a multi-company, multi-user database that
+uses Accounting, Sales, Purchase, and Manufacturing.
+
+You can expect the time it takes for the platform to upgrade the test database will be similar to
+the production upgrade.
+
+.. _upgrade-faq/project:
+
+The upgrade project
+===================
+
+It depends on the user involvement (the time spent on testing, reporting problems, etc.) and the
+issues encountered that might need to be addressed by our technical team.
+
+So, in a nutshell, what can impact your upgrade lead time?
+
+* Source & targeted versions
+* Installed apps
+* Volume of data
+* Amount of customization (models, fields, methods, workflows, reports, website, etc.)
+* Installation of new apps or configuration changes after the start of the test phase
+* User commitment
+
+.. _upgrade-faq/custom-modules:
+
+Upgrade of the custom modules
+=============================
+
+As stated in our :doc:`/legal/terms/enterprise`, section :ref:`charges_standard`, this optional
+service is subject to additional fees.
+
+Depending on your situation, the custom code could be upgraded by our services, by one of our
+partners, or you can do it yourself.
+
+.. note:: |assistance-contact|
+
+.. _upgrade-faq/editions-change:
+
+Editions change (from Community to Enterprise)
+==============================================
+
+The upgrade always returns an Enterprise edition of Odoo, whether the database you sent was a
+community or enterprise edition. It is required to have an enterprise subscription to upgrade.
+
+.. note:: |assistance-contact|
+
+.. seealso::
+   - `Editions <https://www.odoo.com/page/editions>`_
+
+.. _upgrade-faq/hosting-types-switch:
+
+Switching the hosting types (Self-Hosting vs. Online Hosting - SaaS vs. Cloud Platform - Odoo.sh)
+=================================================================================================
+
+An upgrade does not cover a change of `Hosting types <https://www.odoo.com/page/hosting-types>`_.
+
+Open the following link to get :doc:`more information about how to change your hosting type
+<../maintain/hosting_changes>`.
+
+.. note:: |assistance-contact|
+
+.. _upgrade-faq/release-notes:
+
+Release Notes by version
+========================
+
+Open our `Release Note <https://www.odoo.com/page/release-notes>`_ page to get a summary of the new
+features and improvements made in each version.
+
+How long is my test available for
+---------------------------------
+
+An Odoo Online (SaaS) test database is available for one month by default. We can extend this trial
+period upon request. For Odoo.sh or on-premise, there is no restriction.
+
+How many tests to perform before upgrading to production?
+---------------------------------------------------------
+
+As many as needed. When you are comfortable with the database, run a last test upgrade 48 hours
+before requesting your production upgrade and test your workflows one last time.
+
+How to/Where to report upgrade issues?
+--------------------------------------
+
+If you encounter issues during the upgrade process, please contact the Odoo Support through the
+`Odoo Support page <https://www.odoo.com/help>`_
+
+- To report an issue discovered during the testing phase, please select **An issue related to my
+  upgrade (test phase)**.
+- To report an issue discovered post-upgrade, please select **An issue related to my upgrade
+  (production)**
+
+Upgrading to production
+-----------------------
+
+Once you have completed testing and are happy with the result, you decide on a date and time when
+you stop users from accessing Odoo, freeze all data entries, and create an upgrade request for the
+production upgrade.
+
+
+How is my data handled in the Upgrade Platform?
+-----------------------------------------------
+
+The Odoo Upgrade platform uses the same Privacy Policy as the rest of Odoo.com services.
+
+Your data is hosted on servers that follow our security guidelines, namely:
+
+- SSL - All web connections to client instances are protected with 256-bit SSL encryption
+  (HTTPS with a 2048-bit modulus SSL certificate), and running behind Grade A SSL stacks. All our
+  certificate chains are using SHA-2 already.
+- Safe System - Our servers are running recent Linux distribution with up-to-date security patches,
+  with firewall and intrusion countermeasures (not disclosed for obvious reasons).
+
+Servers are located at the same locations as our Cloud providers with the following services:
+
+- Restricted perimeter, physically accessed by authorized data center employees only
+- Physical access control with security badges or biometrical security
+- Security cameras monitoring the data center locations 24/7
+- Security personnel on-site 24/7
+
+The uploaded and migrated databases uploaded to the Upgrade platform are kept for up to 3 months and
+are permanently deleted following that period.
+
+You can learn more about privacy and data handling at Odoo by visiting our `General Data Protection
+Regulation page <https://www.odoo.com/gdpr>`_.

content/administration/upgrade/odoo_sh.rst

@@ -1,9 +1,7 @@
 
-=====================
-Upgrade your database
-=====================
-
-.. _odoosh-advanced-upgrade_your_database:
+=======================
+Odoo.sh version upgrade
+=======================
 
 Download and Upload your database
 =================================

content/administration/upgrade/process.rst

@@ -0,0 +1,256 @@
+.. |assistance-contact| replace::
+   If you need Odoo assistance on this matter, please get in touch with your Odoo Account Manager or
+   our `Sales department`_.
+.. _Sales department: mailto:sales@odoo.com
+
+===============
+Upgrade process
+===============
+
+.. _upgrade/overview:
+
+Overview
+========
+
+An upgrade is switching to a newer version of Odoo (e.g., Odoo 14.0 to Odoo 15.0).
+
+An upgrade does not cover:
+
+* Changing :ref:`editions <upgrade-faq/editions-change>` (i.e., Community to Enterprise edition)
+* Switching :ref:`hosting type <upgrade-faq/hosting-types-switch>` (i.e., On-Premise to Online or
+  Odoo.sh)
+* Migration from another ERP to Odoo
+
+.. note:: |assistance-contact|
+
+.. _upgrade/process-workflow:
+
+Process workflow
+----------------
+
+The upgrade process in a nutshell:
+
+#. You create a test upgrade request.
+#. | Odoo processes the request:
+   | This happens via an automated process that runs the database through an upgrade script and
+     takes between 20 and 120 minutes. Only if an issue(s) arises will we have to intervene
+     manually and adjust the script specifically to your database until the upgrade succeeds.
+#. Odoo delivers a test database.
+#. You test your database for possible discrepancies (see :ref:`upgrade/test-guidance`)
+#. If there are any discrepancies, you report them to the Upgrade support team via the help portal
+   (see :ref:`upgrade/test-assistance`).
+#. We will fix the issues and send you a new test database.
+#. Once you have completed the testing and are happy with the result, you decide on a date and time
+   when you stop users from accessing Odoo, freeze all data entries, and create an upgrade request
+   for the production upgrade.
+#. Odoo delivers the production database through the automated process.
+#. You restore it in your Production environment a few short hours later and continue working on the
+   newly upgraded database (this is done automatically on SaaS).
+
+.. _upgrade/get-started:
+
+Get started
+===========
+
+The upgrade process varies depending on where your database is hosted.
+
+.. _upgrade/online:
+
+Online Hosting (SaaS)
+---------------------
+
+The upgrade request is made via your `database manager <https://www.odoo.com/my/databases>`_.
+
+.. image:: process/online-access-databases.png
+   :align: center
+   :alt: Click on the profile button then on "My Databases"
+
+.. image:: process/online-upgrade-button.png
+   :align: center
+   :alt: Click on the settings button next to your database, then on "Upgrade"
+
+.. _upgrade/odoo-sh:
+
+Cloud Platform (Odoo.sh)
+------------------------
+
+:doc:`odoo_sh`
+
+.. _upgrade/on-premise:
+
+Self-Hosting (On-Premise)
+-------------------------
+
+There are two possibilities:
+
+#. Via `Odoo Upgrade service <https://upgrade.odoo.com>`_
+#. | For technically advanced users and partners, via the following command line on the machine
+     where your database is hosted:
+   | ``python <(curl -s https://upgrade.odoo.com/upgrade) test -d <your db name> -t <target
+     version>``
+
+The above command will dump your database to a file, send it to the upgrade platform for an upgrade,
+display you the live logs, and restore the upgraded database back on your server as a duplicate test
+database.
+
+.. _upgrade/testing-phase:
+
+Testing Phase (pre-production phase)
+====================================
+
+This phase allows you to review an upgraded version of your database without affecting your
+production database in any way.
+
+We suggest that you run the test upgrade process at least once, but you can do it as many times as
+you need (one at a time).
+
+Once you receive your upgraded test database, check that all data, processes, and functionality are
+still correct and working as expected.
+
+If you do find discrepancies, report your issues (see :ref:`upgrade/test-assistance`) and request
+a new test database (see :ref:`upgrade/test-db-request`) when the reported issues are fixed in
+the upgrade script.
+
+If you do not find any discrepancies, you'll be able to move on to the upgrade of your
+:ref:`production database <upgrade/production-live>`.
+
+.. _upgrade/test-db-request:
+
+Request a test database
+-----------------------
+
+When filling the `website form <https://upgrade.odoo.com>`_, select *Testing* purpose.
+
+.. image:: process/test-purpose.png
+   :align: center
+   :alt: Selection of the "Testing" purpose in the upgrade form on Odoo
+
+.. _upgrade/test-guidance:
+
+Test guidance
+-------------
+
+Every business and organization has its own operational needs and has to test its specific Odoo
+instance respectively. We recommend you look at `the test scenario
+<https://docs.google.com/document/d/1ypNs7JKPOsjNbKpdiKFH7Al6g6whZ9jr7f7duAQ5E1w/>` for further
+information.
+
+.. todo:: change link "test scenario" once the related doc is published
+
+.. _upgrade/test-assistance:
+
+Assistance
+----------
+
+If you encounter an issue in the **test database**, please get in touch with Odoo Upgrade Support
+via the `Odoo Support page <https://www.odoo.com/help>`_.
+
+Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type.
+
+   .. image:: process/test-assistance.png
+      :align: center
+      :alt: Selection of "An issue related to my upgrade" as Ticket Type in the support form on Odoo
+
+   .. warning::
+      If you choose another *Ticket Description* type, the request will be redirected to another
+      team. This will slow down the processing and response time.
+
+Please provide as much detail as you can (i.e., videos and screenshots to illustrate your issue).
+This will avoid clarifying questions and speed up the resolution process significantly.
+
+   .. image:: process/test-assistance-details.png
+      :align: center
+      :alt: "Detailed Description" field in the support form on Odoo
+
+.. note::
+   * The purpose of the test phase is not to correct existing data or configurations in your
+     database.
+   * |assistance-contact|
+
+.. _upgrade/steps-production:
+
+The production launch
+---------------------
+
+.. _upgrade/production-live:
+
+Production goes live
+~~~~~~~~~~~~~~~~~~~~
+
+The production upgrade request is when you decide to upgrade your current database with all your
+production data (invoices, VAT returns, inventories, current orders) to a new version of your
+choice.
+
+After your :ref:`tests <upgrade/testing-phase>` are completed to your satisfaction, submit the
+request to upgrade your production database via our `website form <https://upgrade.odoo.com>`_.
+Select *Production* purpose.
+
+.. image:: process/production-purpose.png
+   :align: center
+   :alt: Selection of the "Production" purpose in the upgrade form on Odoo
+
+.. danger::
+   Going into production without first testing may lead to:
+
+   - business interruptions (e.g., no longer having the possibility to validate an action)
+   - poor customer experiences (e.g., an eCommerce website that does not work correctly)
+
+.. _upgrade/production-assistance:
+
+Assistance
+~~~~~~~~~~
+
+If you encounter issues or problems in the **production database**, please get in touch with **Odoo
+Support**:
+
+#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
+#. Under the *Ticket Description* section, select the appropriate type related to your issue but
+   **do not select** the option *An issue related to my upgrade*.
+
+   .. note::
+      After upgrading to production, the support will be provided by the Support team instead of the
+      Upgrade team.
+
+#. Please provide as much detail as you can (i.e., videos and screenshots to illustrate your issue).
+   This will avoid clarifying questions and speed up the resolution process significantly.
+
+   .. image:: process/production-assistance-details.png
+      :align: center
+      :alt: "Detailed Description" field in the support form on Odoo
+
+   .. warning::
+      If you choose *An issue related to my upgrade* as ticket type, the request will be redirected
+      to another team than the support one and will slow down the processing and response time.
+
+.. _upgrade/assistance:
+
+Assistance
+==========
+
+.. _upgrade/contact:
+
+Contact our Upgrade service support
+-----------------------------------
+
+Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo
+Upgrade Team <mailto:upgrade@odoo.com>`_. We will be happy to answer it as soon as possible.
+
+.. _upgrade/supported-versions:
+
+Supported versions
+------------------
+
+Please note that Odoo provides support and bug fixing only for the three last major versions of
+Odoo.
+
+This is a factor to take into consideration before upgrading. If you are on an older version, we
+suggest you to prefer the most recent version to benefit from longer support (before having to
+upgrade again).
+
+You can get more information about our :doc:`supported versions <../maintain/supported_versions>`.
+
+.. seealso::
+   - :doc:`faq`
+   - :doc:`odoo_sh`
+   - :doc:`service_level`
+   - :doc:`../maintain/supported_versions`

content/administration/upgrade/service_level.rst

@@ -0,0 +1,37 @@
+.. |assistance-contact| replace::
+   If you need Odoo assistance on this matter, please get in touch with your Odoo Account Manager or
+   our `Sales department`_.
+.. _Sales department: mailto:sales@odoo.com
+
+=======================
+Service Level Agreement
+=======================
+
+What is covered by the Enterprise Licence?
+==========================================
+
+Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the
+following service at all times.
+
+The upgrade of:
+
+* standard applications
+* Studio customization (as long as the Studio app is still active)
+* customizations done by our consulting and developer services *if* they are covered by a
+  ‘Maintenance of Customisations’ subscription
+
+The Upgrade Service is limited to your database's technical conversion and adaptation (standard
+modules and data) to make it compatible with the targeted version.
+
+What upgrading does NOT cover
+=============================
+
+* The cleaning of pre-existing data & configuration while upgrading
+* Any new developments and/or upgrades of your own :ref:`custom modules
+  <upgrade-faq/custom-modules>`
+* `Training <https://www.odoo.com/learn>`_ on the latest version
+
+You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription
+Agreement <upgrade>` page.
+
+.. note:: |assistance-contact|

content/applications.rst

@@ -1,9 +1,18 @@
-============
-Applications
-============
+:nosearch:
+:show-content:
+:hide-page-toc:
+:show-toc:
+
+
+=========
+User Docs
+=========
+
+Discover our user guides and configuration tutorials per application.
 
 
 .. toctree::
+    :maxdepth: 2
 
     applications/finance
     applications/sales

content/applications/finance.rst

@@ -1,3 +1,5 @@
+:nosearch:
+
 =======
 Finance
 =======

content/applications/finance/accounting.rst

@@ -1,9 +1,25 @@
+:nosearch:
 :show-content:
+:hide-page-toc:
+:show-toc:
 
 ========================
 Accounting and Invoicing
 ========================
 
+**Odoo Invoicing** is a standalone invoicing app to create invoices, send them to your customers,
+and manage payments.
+
+**Odoo Accounting** is a full featured accounting app. Accountant productivity is at the core of its
+development with features such as AI-powered invoice recognition, synchronization with your bank
+accounts, smart matching suggestions, etc.
+
+.. seealso::
+   - `Odoo Tutorials: Invoicing <https://www.odoo.com/slides/invoicing-18>`_
+   - `Odoo Tutorials: Accounting <https://www.odoo.com/slides/accounting-19>`_
+   - :doc:`Accounting Cheat Sheet <accounting/getting_started/memento>`
+
+
 .. toctree::
    :titlesonly:
 
@@ -15,155 +31,3 @@ Accounting and Invoicing
    accounting/reporting
    accounting/others
    accounting/fiscal_localizations
-
-**Odoo Invoicing** is a standalone invoicing app that allows you to :doc:`issue invoices
-<accounting/receivables/customer_invoices/overview>`, send them to your customers, and manage
-payments, including :doc:`online payments
-<accounting/receivables/customer_payments/online_payment>`. It works as a "lighter" version of Odoo
-Accounting, and you can upgrade it to Odoo Accounting if you need more advanced accounting features.
-
-**Odoo Accounting** is a complete and strong accounting app. The automation of processes is at the
-core of its development with its perfect integration with all Odoo apps and with features such as
-:doc:`AI-powered invoice recognition <accounting/payables/supplier_bills/ocr>`,
-:doc:`synchronization with your bank accounts <accounting/bank/feeds/bank_synchronization>`, and
-:doc:`automatic suggestions for a simplified reconciliation process
-<accounting/bank/reconciliation/reconciliation_models>`.
-
-.. seealso::
-   - `Odoo Invoicing: product page <https://www.odoo.com/app/invoicing>`_
-   - `Odoo Accounting: product page <https://www.odoo.com/app/accounting>`_
-
-Double-entry bookkeeping
-========================
-
-Odoo automatically creates all the behind-the-scenes journal entries
-for each of your accounting transactions: customer invoices, point of
-sale order, expenses, inventory moves, etc.
-
-Odoo uses the rules of double-entry bookkeeping system: all journal
-entries are automatically balanced (sum of debits = sum of credits).
-
-.. seealso::
-   - :doc:`Understand Odoo's accounting transactions per document
-     <accounting/getting_started/memento>`
-
-Accrual and Cash Basis Methods
-==============================
-
-Odoo supports both accrual and cash basis reporting. This allows you to
-report income / expense at the time transactions occur (i.e., accrual basis), or when
-payment is made or received (i.e., cash basis).
-
-Multi-companies
-===============
-
-Odoo allows one to manage several companies within the same database. Each
-company has its own chart of accounts and rules. You can get
-consolidation reports following your consolidation rules.
-
-Users can access several companies but always work in one company at a
-time.
-
-Multi-currencies
-================
-
-Every transaction is recorded in the default currency of the
-company. For transactions occurring in another currency, Odoo stores
-both the value in the currency of the company and the value in the
-currency of the transaction. Odoo can generate currencies gains and
-losses after the reconciliation of the journal items.
-
-Currency rates are updated once a day using a yahoo.com online
-web-service.
-
-International Standards
-=======================
-
-Odoo accounting supports more than 50 countries. The Odoo core
-accounting implements accounting standards that are common to all
-countries. Specific modules exist per country for the
-specificities of the country like the chart of accounts, taxes, or
-bank interfaces.
-
-In particular, Odoo's core accounting engine supports:
-
-* Anglo-Saxon Accounting (U.S., U.K.,, and other English-speaking
-  countries including Ireland, Canada, Australia, and New Zealand)
-  where costs of good sold are reported when products are
-  sold/delivered.
-* European accounting where expenses are accounted at the supplier
-  bill.
-
-Odoo has modules to comply with IFRS rules.
-
-Accounts Receivable and Payable
-===============================
-
-By default, Odoo uses a single account for all account
-receivable entries and one for all accounts payable entries. You can
-create separate accounts per customers/suppliers, but you don't need
-to.
-
-As transactions are associated to customers or suppliers, you get
-reports to perform analysis per customer/supplier such as the customer
-statement, revenues per customers, aged receivable/payables, ...
-
-Wide range of financial reports
-===============================
-
-In Odoo, you can generate financial reports in real time. Odoo's
-reports range from basic accounting reports to advanced management
-reports. Odoo's reports include:
-
-* Performance reports (such as Profit and Loss, Budget Variance)
-* Position reports (such as Balance Sheet, Aged Payables, Aged
-  Receivables)
-* Cash reports (such as Bank Summary)
-* Detail reports (such as Trial Balance and General Ledger)
-* Management reports (such as Budgets, Executive Summary)
-
-Odoo's report engine allows you to customize your own report based on
-your own formulae.
-
-Import bank feeds automatically
-===============================
-
-Bank reconciliation is a process that matches your bank statement
-lines, as supplied by the bank, to your accounting transactions in the
-general ledger. Odoo makes bank reconciliation easy by frequently
-importing bank statement lines from your bank directly into your Odoo
-account. This means you can have a daily view of your cashflow without
-having to log into your online banking or wait for your paper bank
-statements.
-
-Odoo speeds up bank reconciliation by matching most of your imported
-bank statement lines to your accounting transactions. Odoo also
-remembers how you've treated other bank statement lines and provides
-suggested general ledger transactions.
-
-Calculate the tax you owe your tax authority
-============================================
-
-Odoo totals all your accounting transactions for your tax period and
-uses these totals to calculate your tax obligation. You can then check
-your sales tax by running Odoo's Tax Report.
-
-Inventory Valuation
-===================
-
-Odoo support both periodic (manual) and perpetual (automated)
-inventory valuations. The available methods are standard price,
-average price, LIFO (for countries allowing it) and FIFO.
-
-.. seealso::
-   - :doc:`View impact of the valuation method on your transactions
-     <../inventory_and_mrp/inventory/management/reporting/inventory_valuation_config>`
-
-Easy retained earnings
-======================
-
-Retained earnings are the portion of income retained by your
-business. Odoo automatically calculates your current year earnings in
-real time so no year-end journal or rollover is required.  This is
-calculated by reporting the profit and loss balance to your balance
-sheet report automatically.

content/applications/finance/accounting/bank.rst

@@ -1,3 +1,5 @@
+:nosearch:
+
 ===========
 Bank & Cash
 ===========

content/applications/finance/accounting/bank/feeds.rst

@@ -1,3 +1,5 @@
+:nosearch:
+
 ==========
 Bank Feeds
 ==========
@@ -8,4 +10,4 @@ Bank Feeds
    feeds/bank_statements
    feeds/bank_synchronization
    feeds/ponto
-   feeds/paypal
+   feeds/saltedge

content/applications/finance/accounting/bank/feeds/bank_synchronization.rst

@@ -2,102 +2,172 @@
 Bank Synchronization: Automatic Import
 ======================================
 
-Odoo can synchronize directly with your bank to get all bank statements imported automatically into
-your database.
+Odoo can synchronize directly with your bank institution to get all bank statements imported
+automatically into your database.
 
 To check if your bank is compatible with Odoo, go to `Odoo Accounting Features
-<https://www.odoo.com/page/accounting-features>`_, and search for your bank in the *Supported Banks*
-section.
+<https://www.odoo.com/page/accounting-features>`_, and click on *See list of supported institutions*.
 
-.. image:: media/bank_synchronization01.png
+.. image:: media/online-sync-doc.png
    :align: center
-   :alt: checking a bank's compatibility with Odoo
+   :alt: Checking a bank's compatibility with Odoo
 
-The countries which are fully supported include the United States, Canada, New Zealand, Austria, and
-Belgium.
-
-More than 30 countries are partially supported, including Colombia, India, France, and Spain.
+More than 20,000 institutions around the world are supported.
 
 To connect to the banks, Odoo uses multiple web-services:
 
-- **Plaid**: Mainly for the U.S
+- **Plaid**: United States of America and Canada
 - **Yodlee**: Worldwide
-- **Ponto**: For a growing number of European Banks. (:doc:`Click here for more information <ponto>`)
+- **Salt Edge**: Europe (:doc:`more information <saltedge>`)
+- **Ponto**: Europe (:doc:`more information <ponto>`)
 
 Configuration
 =============
 
-Odoo Online Users
------------------
+On-Premise users
+----------------
 
-Make sure the **Automatic Import** feature is activated by going to :menuselection:`Accounting
---> Configuration --> Settings` in the *Bank & Cash* section.
+To be able to use this service, you need to have a valid Odoo Enterprise subscription.
+So make sure that your database is registered with your Odoo Enterprise contract.
+We also use a proxy between your database and the third party provider so, in case of
+a connection error, please check that you don't have a firewall or a proxy blocking the
+following address:
 
-Odoo Enterprise Users
+- https://production.odoofin.com/
+
+First Synchronization
 ---------------------
 
-If you plan to use a bank interface with your Odoo Enterprise subscription, you don’t have to do
-anything special. Just make sure that your database is registered with your Odoo Enterprise contract.
+You can start synchronization either by going to :menuselection:`Accounting --> Configuration
+--> Add a Bank Account` or via the configuration bar on the accounting dashboard.
+
+Now you can search for your bank institution. Select it and follow the steps to synchronize with it.
 
 .. note::
-   you might want to check that you don't have a firewall/proxy blocking the following address:
+   If you have any issues during your first synchronization, please verify that your
+   web browser doesn't block pop-ups and that your adblocker is disabled.
 
-   - https://onlinesync.odoo.com/
+During your first synchronization, you will be asked for a phone number to secure your account.
+The reason we ask for such information is that we don't want your data falling into the wrong
+hands. Therefore, if we detect suspicious activity on your account, we block all requests coming
+from your account, and you need to reactivate it using that phone number.
+The third-party provider may request more information in order to connect with your bank institution.
+This information is not stored on Odoo's servers.
 
-Sync your bank feeds
-====================
+By default, transactions fetched from an online source are grouped inside the same statement, and
+one bank statement is created per month. You can change the bank statement creation periodicity
+in your journal settings.
 
-First, make sure that the **Automated Bank Synchronization** is activated in your journal.
+You can find all your synchronizations by going to :menuselection:`Accounting --> Configuration -->
+Online Synchronization`.
 
-To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, then open your *Bank
-Journal*, click on *Edit*, and select **Automated Bank Synchronization** in the *Bank Feed* field.
+Synchronize manually
+--------------------
 
-.. image:: media/bank_synchronization02.png
+After your first synchronization, the created journals are synchronized by default every 12 hours.
+If you wish, you can synchronize manually by clicking on the *Synchronize Now* button on the
+dashboard.
+
+.. image:: media/online-sync-sync-now-dashboard.png
    :align: center
-   :alt: Automated Bank Synchronization of a Bank Journal in Odoo
+   :alt: Synchronize Now Button
 
-You can then connect Odoo to your bank.
+Or you can go to :menuselection:`Accounting --> Configuration --> Online Synchronization`,
+select your institution and then click on the *Fetch Transactions* button.
 
-To do so, go to :menuselection:`Accounting --> Configuration --> Add a Bank Account`, and follow the
-steps.
-
-Once done, go back to your *Accounting dashboard*. You should now see a **Synchronize Now** button
-on your *Bank* card. Click on this button and enter your bank credentials.
-
-.. image:: media/bank_synchronization03.png
+.. image:: media/online-sync-form-view.png
    :align: center
-   :alt: Synchronize Now button in Odoo
+   :alt: Online Synchronization Form view
 
-After this, your bank feeds will be regularly synchronized.
+.. important::
+   Some institutions do not allow transactions to be fetched automatically. For such institutions,
+   during the automatic synchronization of the account, you receive an error message asking you to
+   disable the automatic synchronization. This message can be found in the chatter of your online
+   synchronizations. In this case, make sure to perform manual synchronizations.
 
-FAQ 
+Issues
+======
+
+Synchronization in error
+------------------------
+
+To report a connection error to the `Odoo support <https://www.odoo.com/help>`_, go to
+:menuselection:`Accounting --> Configuration --> Online Synchronization`, select the connection
+that failed, and copy the error description and the reference.
+
+Synchronization disconnected
+----------------------------
+
+If your connection with the proxy is disconnected, you can reconnect with the proxy using the
+*Reconnect* button.
+
+.. note::
+   This disconnection can be caused by the Odoo support. In this case, please contact the `support
+   <https://www.odoo.com/help>`_ directly with your client id or the reference of the error listed
+   in the chatter.
+
+.. _MigrationOnlineSync:
+
+Migration process for users having installed Odoo before December 2020
+======================================================================
+
+If you are on-premise, please first make sure that your source is up-to-date with the latest version
+of Odoo.
+
+Users who have created a database before December 2020 need to install the new module manually to
+use the new functionalities.
+
+To do so, go to :menuselection:`Apps --> Update Apps List`, remove the default filter in the search
+bar and type: **account_online_synchronization**. You can then click on the *Install* button to
+install the new module.
+
+.. image:: media/online-sync-module.png
+   :align: center
+   :alt: Installation button of the account_online_synchronization module
+
+Finally, make sure all your users refresh their Odoo page by pressing CTRL+F5.
+
+.. Note::
+
+   - All previous synchronizations are disconnected during the installation and won't work anymore.
+     You can find them directly in the synchronization menu (:menuselection:`Accounting -->
+     Configuration --> Online Synchronization`). It is not possible to resynchronize these
+     connections; you have to make new ones.
+   - Please do not uninstall *account_online_sync* which is the previous module for online
+     synchronization. The new one overrides it.
+   - By default *account_online_synchronization* is installed automatically with Accounting.
+
+FAQ
 ===
 
-The synchronization is not working in real-time, is that normal?
+The synchronization is not working in real-time. Is that normal?
 ----------------------------------------------------------------
 
 The process is not intended to work in real-time as third party providers synchronize your accounts
 at different intervals. To force the synchronization and fetch the statements, go to your
-*Accounting dashboard*, and click on the *Synchronize Now* button.
+*Accounting dashboard*, and click on the *Synchronize Now* button. You can also synchronize and
+fetch transactions through :menuselection:`Accounting --> Configuration --> Online Synchronization`.
+Some providers only allow one refresh per day, so it is possible that clicking on *Synchronize Now*
+does not get your latest transactions if you already performed such action earlier in the day.
 
-A transaction can be visible in your bank account, but not be fetched if it has the status
+A transaction can be visible on your bank account, but not be fetched if it has the status
 *Pending*. Only transactions with the *Posted* status will be retrieved. If it is not *Posted* yet,
 you will have to wait until the status changes.
 
-Is the Automatic Import feature included in my contract?
---------------------------------------------------------
+Is the Online Bank Synchronization feature included in my contract?
+-------------------------------------------------------------------
 
-- **Enterprise Version**: Yes, if you have a valid enterprise contract linked to your database.
 - **Community Version**: No, this feature is not included in the Community Version.
 - **Online Version**: Yes, even if you benefit from the One App Free contract.
+- **Enterprise Version**: Yes, if you have a valid enterprise contract linked to your database.
 
-Some banks have a status "Beta," what does this mean?
+Some banks have a status "Beta." What does this mean?
 -----------------------------------------------------
 
 This means that banking institutions are not yet fully supported by our Third Party Provider. Bugs
 or other problems may arise. Odoo does not support technical problems that occur with banks in the
-Beta phase, but the user may still choose to connect. Connecting with these banks can aid in the
-development process since the Provider will have real data & feedback from the connection.
+Beta phase, but the user may still choose to connect. Connecting with these banks contributes to the
+development process since the Provider will have real data and feedback from the connection.
 
 Why do my transactions only synchronize when I refresh manually?
 ----------------------------------------------------------------
@@ -109,22 +179,28 @@ until the security code is provided.
 Not all of my past transactions are in Odoo, why?
 -------------------------------------------------
 
-Transactions can only be fetched up to 3 months in the past.
+For some institutions, transactions can only be fetched up to 3 months in the past.
 
-Why don’t I see any transactions?
+Why don't I see any transactions?
 ---------------------------------
-When you first connect with your bank, you will be prompted to add each account to its own journal.
-If you skip this step, you will not be able to see your transactions in Odoo.
+
+During your first synchronization, you selected the bank accounts you decided to synchronize with
+Odoo. If you didn't synchronize any of your accounts, you can go to :menuselection:`Accounting -->
+Configuration --> Online Synchronization` to click on the *Fetch Accounts* button on the connection.
+
+There may also be no new transactions.
 
 If your bank account is properly linked to a journal and posted transactions are not visible in your
 database, please `submit a support ticket <https://www.odoo.com/help>`_.
 
 How can I update my bank credentials?
 -------------------------------------
-You can update your credentials in :ref:`developer mode <developer-mode>`.
 
-Then go to :menuselection:`Accounting --> Configuration --> Online Synchronization`, and open the
-Institution you want to edit, and click on *Update Credentials*.
+You can update your credentials by going to :menuselection:`Accounting --> Configuration --> Online
+Synchronization`, open the connection you want to update your credentials and click on the *Update
+Credentials* button.
 
 .. seealso::
    * :doc:`bank_statements`
+   * :doc:`ponto`
+   * :doc:`saltedge`