[IMP] web: update documentation of patch function

This commit updates the documentation of the patch function
with the changes done in https://github.com/odoo/odoo/pull/125716.

.tx/config

@@ -11,11 +11,6 @@ file_filter = locale/<lang>/LC_MESSAGES/applications.po
 source_file = locale/sources/applications.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:essentials]
-file_filter = locale/<lang>/LC_MESSAGES/essentials.po
-source_file = locale/sources/essentials.pot
-source_lang = en
-
 [o:odoo:p:odoo-16-doc:r:finance]
 file_filter = locale/<lang>/LC_MESSAGES/finance.po
 source_file = locale/sources/finance.pot
@@ -26,13 +21,6 @@ file_filter = locale/<lang>/LC_MESSAGES/general.po
 source_file = locale/sources/general.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:hr]
-file_filter   = locale/<lang>/LC_MESSAGES/hr.po
-source_file   = locale/sources/hr.pot
-type          = POT
-minimum_perc  = 0
-resource_name = hr
-
 [o:odoo:p:odoo-16-doc:r:index]
 file_filter = locale/<lang>/LC_MESSAGES/index.po
 source_file = locale/sources/index.pot
@@ -68,11 +56,6 @@ file_filter = locale/<lang>/LC_MESSAGES/settings.po
 source_file = locale/sources/settings.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:studio]
-file_filter = locale/<lang>/LC_MESSAGES/studio.po
-source_file = locale/sources/studio.pot
-source_lang = en
-
 [o:odoo:p:odoo-16-doc:r:websites]
 file_filter = locale/<lang>/LC_MESSAGES/websites.po
 source_file = locale/sources/websites.pot

COPYRIGHT

@@ -1,13 +0,0 @@
-Most of the files are
-
-  Copyright (c) 2004-2023 Odoo S.A.
-
-Some files may also contain contributions from third
-parties. In this case the original copyright of
-the contributions can be traced through the
-history of the source version control system.
-
-When that is not the case, the files contain a prominent
-notice stating the original copyright and applicable
-license, or come with their own dedicated COPYRIGHT
-and/or LICENSE file.

LICENSE

@@ -1,428 +0,0 @@
-Attribution-ShareAlike 4.0 International
-
-=======================================================================
-
-Creative Commons Corporation ("Creative Commons") is not a law firm and
-does not provide legal services or legal advice. Distribution of
-Creative Commons public licenses does not create a lawyer-client or
-other relationship. Creative Commons makes its licenses and related
-information available on an "as-is" basis. Creative Commons gives no
-warranties regarding its licenses, any material licensed under their
-terms and conditions, or any related information. Creative Commons
-disclaims all liability for damages resulting from their use to the
-fullest extent possible.
-
-Using Creative Commons Public Licenses
-
-Creative Commons public licenses provide a standard set of terms and
-conditions that creators and other rights holders may use to share
-original works of authorship and other material subject to copyright
-and certain other rights specified in the public license below. The
-following considerations are for informational purposes only, are not
-exhaustive, and do not form part of our licenses.
-
-     Considerations for licensors: Our public licenses are
-     intended for use by those authorized to give the public
-     permission to use material in ways otherwise restricted by
-     copyright and certain other rights. Our licenses are
-     irrevocable. Licensors should read and understand the terms
-     and conditions of the license they choose before applying it.
-     Licensors should also secure all rights necessary before
-     applying our licenses so that the public can reuse the
-     material as expected. Licensors should clearly mark any
-     material not subject to the license. This includes other CC-
-     licensed material, or material used under an exception or
-     limitation to copyright. More considerations for licensors:
-    wiki.creativecommons.org/Considerations_for_licensors
-
-     Considerations for the public: By using one of our public
-     licenses, a licensor grants the public permission to use the
-     licensed material under specified terms and conditions. If
-     the licensor's permission is not necessary for any reason--for
-     example, because of any applicable exception or limitation to
-     copyright--then that use is not regulated by the license. Our
-     licenses grant only permissions under copyright and certain
-     other rights that a licensor has authority to grant. Use of
-     the licensed material may still be restricted for other
-     reasons, including because others have copyright or other
-     rights in the material. A licensor may make special requests,
-     such as asking that all changes be marked or described.
-     Although not required by our licenses, you are encouraged to
-     respect those requests where reasonable. More considerations
-     for the public:
-    wiki.creativecommons.org/Considerations_for_licensees
-
-=======================================================================
-
-Creative Commons Attribution-ShareAlike 4.0 International Public
-License
-
-By exercising the Licensed Rights (defined below), You accept and agree
-to be bound by the terms and conditions of this Creative Commons
-Attribution-ShareAlike 4.0 International Public License ("Public
-License"). To the extent this Public License may be interpreted as a
-contract, You are granted the Licensed Rights in consideration of Your
-acceptance of these terms and conditions, and the Licensor grants You
-such rights in consideration of benefits the Licensor receives from
-making the Licensed Material available under these terms and
-conditions.
-
-
-Section 1 -- Definitions.
-
-  a. Adapted Material means material subject to Copyright and Similar
-     Rights that is derived from or based upon the Licensed Material
-     and in which the Licensed Material is translated, altered,
-     arranged, transformed, or otherwise modified in a manner requiring
-     permission under the Copyright and Similar Rights held by the
-     Licensor. For purposes of this Public License, where the Licensed
-     Material is a musical work, performance, or sound recording,
-     Adapted Material is always produced where the Licensed Material is
-     synched in timed relation with a moving image.
-
-  b. Adapter's License means the license You apply to Your Copyright
-     and Similar Rights in Your contributions to Adapted Material in
-     accordance with the terms and conditions of this Public License.
-
-  c. BY-SA Compatible License means a license listed at
-     creativecommons.org/compatiblelicenses, approved by Creative
-     Commons as essentially the equivalent of this Public License.
-
-  d. Copyright and Similar Rights means copyright and/or similar rights
-     closely related to copyright including, without limitation,
-     performance, broadcast, sound recording, and Sui Generis Database
-     Rights, without regard to how the rights are labeled or
-     categorized. For purposes of this Public License, the rights
-     specified in Section 2(b)(1)-(2) are not Copyright and Similar
-     Rights.
-
-  e. Effective Technological Measures means those measures that, in the
-     absence of proper authority, may not be circumvented under laws
-     fulfilling obligations under Article 11 of the WIPO Copyright
-     Treaty adopted on December 20, 1996, and/or similar international
-     agreements.
-
-  f. Exceptions and Limitations means fair use, fair dealing, and/or
-     any other exception or limitation to Copyright and Similar Rights
-     that applies to Your use of the Licensed Material.
-
-  g. License Elements means the license attributes listed in the name
-     of a Creative Commons Public License. The License Elements of this
-     Public License are Attribution and ShareAlike.
-
-  h. Licensed Material means the artistic or literary work, database,
-     or other material to which the Licensor applied this Public
-     License.
-
-  i. Licensed Rights means the rights granted to You subject to the
-     terms and conditions of this Public License, which are limited to
-     all Copyright and Similar Rights that apply to Your use of the
-     Licensed Material and that the Licensor has authority to license.
-
-  j. Licensor means the individual(s) or entity(ies) granting rights
-     under this Public License.
-
-  k. Share means to provide material to the public by any means or
-     process that requires permission under the Licensed Rights, such
-     as reproduction, public display, public performance, distribution,
-     dissemination, communication, or importation, and to make material
-     available to the public including in ways that members of the
-     public may access the material from a place and at a time
-     individually chosen by them.
-
-  l. Sui Generis Database Rights means rights other than copyright
-     resulting from Directive 96/9/EC of the European Parliament and of
-     the Council of 11 March 1996 on the legal protection of databases,
-     as amended and/or succeeded, as well as other essentially
-     equivalent rights anywhere in the world.
-
-  m. You means the individual or entity exercising the Licensed Rights
-     under this Public License. Your has a corresponding meaning.
-
-
-Section 2 -- Scope.
-
-  a. License grant.
-
-       1. Subject to the terms and conditions of this Public License,
-          the Licensor hereby grants You a worldwide, royalty-free,
-          non-sublicensable, non-exclusive, irrevocable license to
-          exercise the Licensed Rights in the Licensed Material to:
-
-            a. reproduce and Share the Licensed Material, in whole or
-               in part; and
-
-            b. produce, reproduce, and Share Adapted Material.
-
-       2. Exceptions and Limitations. For the avoidance of doubt, where
-          Exceptions and Limitations apply to Your use, this Public
-          License does not apply, and You do not need to comply with
-          its terms and conditions.
-
-       3. Term. The term of this Public License is specified in Section
-          6(a).
-
-       4. Media and formats; technical modifications allowed. The
-          Licensor authorizes You to exercise the Licensed Rights in
-          all media and formats whether now known or hereafter created,
-          and to make technical modifications necessary to do so. The
-          Licensor waives and/or agrees not to assert any right or
-          authority to forbid You from making technical modifications
-          necessary to exercise the Licensed Rights, including
-          technical modifications necessary to circumvent Effective
-          Technological Measures. For purposes of this Public License,
-          simply making modifications authorized by this Section 2(a)
-          (4) never produces Adapted Material.
-
-       5. Downstream recipients.
-
-            a. Offer from the Licensor -- Licensed Material. Every
-               recipient of the Licensed Material automatically
-               receives an offer from the Licensor to exercise the
-               Licensed Rights under the terms and conditions of this
-               Public License.
-
-            b. Additional offer from the Licensor -- Adapted Material.
-               Every recipient of Adapted Material from You
-               automatically receives an offer from the Licensor to
-               exercise the Licensed Rights in the Adapted Material
-               under the conditions of the Adapter's License You apply.
-
-            c. No downstream restrictions. You may not offer or impose
-               any additional or different terms or conditions on, or
-               apply any Effective Technological Measures to, the
-               Licensed Material if doing so restricts exercise of the
-               Licensed Rights by any recipient of the Licensed
-               Material.
-
-       6. No endorsement. Nothing in this Public License constitutes or
-          may be construed as permission to assert or imply that You
-          are, or that Your use of the Licensed Material is, connected
-          with, or sponsored, endorsed, or granted official status by,
-          the Licensor or others designated to receive attribution as
-          provided in Section 3(a)(1)(A)(i).
-
-  b. Other rights.
-
-       1. Moral rights, such as the right of integrity, are not
-          licensed under this Public License, nor are publicity,
-          privacy, and/or other similar personality rights; however, to
-          the extent possible, the Licensor waives and/or agrees not to
-          assert any such rights held by the Licensor to the limited
-          extent necessary to allow You to exercise the Licensed
-          Rights, but not otherwise.
-
-       2. Patent and trademark rights are not licensed under this
-          Public License.
-
-       3. To the extent possible, the Licensor waives any right to
-          collect royalties from You for the exercise of the Licensed
-          Rights, whether directly or through a collecting society
-          under any voluntary or waivable statutory or compulsory
-          licensing scheme. In all other cases the Licensor expressly
-          reserves any right to collect such royalties.
-
-
-Section 3 -- License Conditions.
-
-Your exercise of the Licensed Rights is expressly made subject to the
-following conditions.
-
-  a. Attribution.
-
-       1. If You Share the Licensed Material (including in modified
-          form), You must:
-
-            a. retain the following if it is supplied by the Licensor
-               with the Licensed Material:
-
-                 i. identification of the creator(s) of the Licensed
-                    Material and any others designated to receive
-                    attribution, in any reasonable manner requested by
-                    the Licensor (including by pseudonym if
-                    designated);
-
-                ii. a copyright notice;
-
-               iii. a notice that refers to this Public License;
-
-                iv. a notice that refers to the disclaimer of
-                    warranties;
-
-                 v. a URI or hyperlink to the Licensed Material to the
-                    extent reasonably practicable;
-
-            b. indicate if You modified the Licensed Material and
-               retain an indication of any previous modifications; and
-
-            c. indicate the Licensed Material is licensed under this
-               Public License, and include the text of, or the URI or
-               hyperlink to, this Public License.
-
-       2. You may satisfy the conditions in Section 3(a)(1) in any
-          reasonable manner based on the medium, means, and context in
-          which You Share the Licensed Material. For example, it may be
-          reasonable to satisfy the conditions by providing a URI or
-          hyperlink to a resource that includes the required
-          information.
-
-       3. If requested by the Licensor, You must remove any of the
-          information required by Section 3(a)(1)(A) to the extent
-          reasonably practicable.
-
-  b. ShareAlike.
-
-     In addition to the conditions in Section 3(a), if You Share
-     Adapted Material You produce, the following conditions also apply.
-
-       1. The Adapter's License You apply must be a Creative Commons
-          license with the same License Elements, this version or
-          later, or a BY-SA Compatible License.
-
-       2. You must include the text of, or the URI or hyperlink to, the
-          Adapter's License You apply. You may satisfy this condition
-          in any reasonable manner based on the medium, means, and
-          context in which You Share Adapted Material.
-
-       3. You may not offer or impose any additional or different terms
-          or conditions on, or apply any Effective Technological
-          Measures to, Adapted Material that restrict exercise of the
-          rights granted under the Adapter's License You apply.
-
-
-Section 4 -- Sui Generis Database Rights.
-
-Where the Licensed Rights include Sui Generis Database Rights that
-apply to Your use of the Licensed Material:
-
-  a. for the avoidance of doubt, Section 2(a)(1) grants You the right
-     to extract, reuse, reproduce, and Share all or a substantial
-     portion of the contents of the database;
-
-  b. if You include all or a substantial portion of the database
-     contents in a database in which You have Sui Generis Database
-     Rights, then the database in which You have Sui Generis Database
-     Rights (but not its individual contents) is Adapted Material,
-     including for purposes of Section 3(b); and
-
-  c. You must comply with the conditions in Section 3(a) if You Share
-     all or a substantial portion of the contents of the database.
-
-For the avoidance of doubt, this Section 4 supplements and does not
-replace Your obligations under this Public License where the Licensed
-Rights include other Copyright and Similar Rights.
-
-
-Section 5 -- Disclaimer of Warranties and Limitation of Liability.
-
-  a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
-     EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
-     AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
-     ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
-     IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
-     WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
-     PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
-     ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
-     KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
-     ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
-
-  b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
-     TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
-     NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
-     INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
-     COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
-     USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
-     ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
-     DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
-     IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
-
-  c. The disclaimer of warranties and limitation of liability provided
-     above shall be interpreted in a manner that, to the extent
-     possible, most closely approximates an absolute disclaimer and
-     waiver of all liability.
-
-
-Section 6 -- Term and Termination.
-
-  a. This Public License applies for the term of the Copyright and
-     Similar Rights licensed here. However, if You fail to comply with
-     this Public License, then Your rights under this Public License
-     terminate automatically.
-
-  b. Where Your right to use the Licensed Material has terminated under
-     Section 6(a), it reinstates:
-
-       1. automatically as of the date the violation is cured, provided
-          it is cured within 30 days of Your discovery of the
-          violation; or
-
-       2. upon express reinstatement by the Licensor.
-
-     For the avoidance of doubt, this Section 6(b) does not affect any
-     right the Licensor may have to seek remedies for Your violations
-     of this Public License.
-
-  c. For the avoidance of doubt, the Licensor may also offer the
-     Licensed Material under separate terms or conditions or stop
-     distributing the Licensed Material at any time; however, doing so
-     will not terminate this Public License.
-
-  d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
-     License.
-
-
-Section 7 -- Other Terms and Conditions.
-
-  a. The Licensor shall not be bound by any additional or different
-     terms or conditions communicated by You unless expressly agreed.
-
-  b. Any arrangements, understandings, or agreements regarding the
-     Licensed Material not stated herein are separate from and
-     independent of the terms and conditions of this Public License.
-
-
-Section 8 -- Interpretation.
-
-  a. For the avoidance of doubt, this Public License does not, and
-     shall not be interpreted to, reduce, limit, restrict, or impose
-     conditions on any use of the Licensed Material that could lawfully
-     be made without permission under this Public License.
-
-  b. To the extent possible, if any provision of this Public License is
-     deemed unenforceable, it shall be automatically reformed to the
-     minimum extent necessary to make it enforceable. If the provision
-     cannot be reformed, it shall be severed from this Public License
-     without affecting the enforceability of the remaining terms and
-     conditions.
-
-  c. No term or condition of this Public License will be waived and no
-     failure to comply consented to unless expressly agreed to by the
-     Licensor.
-
-  d. Nothing in this Public License constitutes or may be interpreted
-     as a limitation upon, or waiver of, any privileges and immunities
-     that apply to the Licensor or You, including from the legal
-     processes of any jurisdiction or authority.
-
-
-=======================================================================
-
-Creative Commons is not a party to its public
-licenses. Notwithstanding, Creative Commons may elect to apply one of
-its public licenses to material it publishes and in those instances
-will be considered the “Licensor.” The text of the Creative Commons
-public licenses is dedicated to the public domain under the CC0 Public
-Domain Dedication. Except for the limited purpose of indicating that
-material is shared under a Creative Commons public license or as
-otherwise permitted by the Creative Commons policies published at
-creativecommons.org/policies, Creative Commons does not authorize the
-use of the trademark "Creative Commons" or any other trademark or logo
-of Creative Commons without its prior written consent including,
-without limitation, in connection with any unauthorized modifications
-to any of its public licenses or any other arrangements,
-understandings, or agreements concerning use of licensed material. For
-the avoidance of doubt, this paragraph does not form part of the
-public licenses.
-
-Creative Commons may be contacted at creativecommons.org.
-

Makefile

@@ -18,7 +18,6 @@ CONFIG_DIR     = .
 SPHINXOPTS     = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSION) \
                  -D versions=$(VERSIONS) -D languages=$(LANGUAGES) -D language=$(CURRENT_LANG) \
                  -D is_remote_build=$(IS_REMOTE_BUILD) \
-                 -T \
                  -A google_analytics_key=$(GOOGLE_ANALYTICS_KEY) \
                  -A plausible_script=$(PLAUSIBLE_SCRIPT) \
                  -A plausible_domain=$(PLAUSIBLE_DOMAIN) \
@@ -27,7 +26,7 @@ SOURCE_DIR     = content
 
 HTML_BUILD_DIR = $(BUILD_DIR)/html
 ifdef VERSIONS
-  HTML_BUILD_DIR := $(HTML_BUILD_DIR)/16.0
+  HTML_BUILD_DIR := $(HTML_BUILD_DIR)/master
 endif
 ifneq ($(CURRENT_LANG),en)
   HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)
@@ -85,15 +84,5 @@ static: $(HTML_BUILD_DIR)/_static/style.css
 	cp -r extensions/odoo_theme/static/* $(HTML_BUILD_DIR)/_static/
 	cp -r static/* $(HTML_BUILD_DIR)/_static/
 
-# Called by runbot for the ci/documentation_guideline check.
 test:
-	@python tests/main.py $(SOURCE_DIR)/administration $(SOURCE_DIR)/applications $(SOURCE_DIR)/contributing $(SOURCE_DIR)/developer redirects
-
-# Similar as `test`, but called only manually by content reviewers to trigger extra checks.
-review:
-	@read -p "Enter relative content path: " path; read -p "Enter max line length (default: 100): " line_length; \
-	if [ -z "$$path" ]; then echo "Error: Path cannot be empty"; exit 1; fi; \
-	if echo $$path | grep -q 'content/'; then path=`echo $$path | sed 's|content/||'`; fi; \
-	if [ -z "$$line_length" ]; then line_length=100; fi; \
-	export REVIEW=1; \
-	python tests/main.py --max-line-length=$$line_length $(SOURCE_DIR)/$$path
+	@python tests/main.py $(SOURCE_DIR)/administration $(SOURCE_DIR)/applications $(SOURCE_DIR)/contributing $(SOURCE_DIR)/developer $(SOURCE_DIR)/services redirects

README.md

@@ -9,7 +9,6 @@
 - Python dependencies listed in the file `requirements.txt`.
 - Make
 - A local copy of the [odoo/odoo repository](https://github.com/odoo/odoo) (optional)
-- A local copy of the [odoo/upgrade-util repository](https://github.com/odoo/upgrade-util) (optional)
 
 ### Instructions
 
@@ -19,9 +18,8 @@
 3. See [this guide](https://www.odoo.com/documentation/latest/contributing/documentation.html)
    for more detailed instructions.
 
-Optional: place your local copy of the `odoo/odoo` and `odoo/upgrade-util` repositories in
-the parent directory or in the root directory of the documentation to build the latter
-with the documented Python docstrings.
+Optional: place your local copy of the `odoo/odoo` repository in the parent directory or in the root
+directory of the documentation to build the latter with the documented Python docstrings.
 
 ## Contribute to the documentation
 

conf.py

@@ -22,7 +22,7 @@ copyright = 'Odoo S.A.'
 # `version` is the version info for the project being documented, acts as replacement for |version|,
 # also used in various other places throughout the built documents.
 # `release` is the full version, including alpha/beta/rc tags. Acts as replacement for |release|.
-version = release = '16.0'
+version = release = 'master'
 
 # `current_branch` is the technical name of the current branch.
 # E.g., saas-15.4 -> saas-15.4; 12.0 -> 12.0, master -> master (*).
@@ -133,24 +133,6 @@ else:
         )
         odoo_dir_in_path = True
 
-if odoo_dir_in_path:
-    upgrade_util_dir = next(filter(Path.exists, [Path('upgrade-util'), Path('../upgrade-util')]), None)
-    if not upgrade_util_dir:
-        _logger.warning(
-            "Could not find Upgrade Utils sources directory in `upgrade_util`.\n"
-            "The developer documentation will be built but autodoc directives will be skipped.\n"
-            "In order to fully build the 'Developer' documentation, clone the repository with "
-            "`git clone https://github.com/odoo/upgrade-util` or create a symbolic link."
-        )
-        odoo_dir_in_path = False
-    else:
-        _logger.info(
-            "Found Upgrade Util sources in %(directory)s",
-            {'directory': upgrade_util_dir.resolve()},
-        )
-        from odoo import upgrade
-        upgrade.__path__.append(str((upgrade_util_dir / 'src').resolve()))
-
 # Mapping between odoo models related to master data and the declaration of the
 # data. This is used to point users to available xml_ids when giving values for
 # a field with the autodoc_field extension.
@@ -231,12 +213,14 @@ sphinx.transforms.i18n.docname_to_domain = (
 # is populated. If a version is passed to `versions` but is not listed here, it will not be shown.
 versions_names = {
     'master': "Master",
-    '18.0': "Odoo 18",
-    'saas-17.4': "Odoo Online",
-    'saas-17.2': "Odoo Online",
-    '17.0': "Odoo 17",
+    'saas-16.3': "Odoo Online",
+    'saas-16.2': "Odoo Online",
+    'saas-16.1': "Odoo Online",
     '16.0': "Odoo 16",
+    'saas-15.2': "Odoo Online",
     '15.0': "Odoo 15",
+    '14.0': "Odoo 14",
+    '13.0': "Odoo 13",
 }
 
 # The language names that should be shown in the language switcher, if the config option `languages`
@@ -245,14 +229,10 @@ languages_names = {
     'de': 'DE',
     'en': 'EN',
     'es': 'ES',
-    'es_419': 'ES (LATAM)',
     'fr': 'FR',
     'it': 'IT',
-    'ko': 'KR',
     'nl': 'NL',
     'pt_BR': 'PT',
-    'ro': 'RO',
-    'sv': 'SV',
     'uk': 'UA',
     'zh_CN': 'ZH (CN)',
     'zh_TW': 'ZH (TW)'
@@ -264,9 +244,6 @@ redirects_dir = 'redirects/'
 sphinx_tabs_disable_tab_closing = True
 sphinx_tabs_disable_css_loading = True
 
-# Autodoc ordering
-autodoc_member_order = 'bysource'
-
 #=== Options for HTML output ===#
 
 html_theme = 'odoo_theme'
@@ -336,15 +313,11 @@ latex_documents = [
 
     ('legal/terms/i18n/enterprise_tex_de', 'odoo_enterprise_agreement_de.tex',
      'Odoo Enterprise Subscription Agreement (DE)', '', 'howto'),
-    ('legal/terms/i18n/terms_of_sale_de', 'terms_of_sale_de.tex',
-     'Allgemeine Verkaufsbedingungen Odoo', '', 'howto'),
 
     ('legal/terms/i18n/enterprise_tex_es', 'odoo_enterprise_agreement_es.tex',
      'Odoo Enterprise Subscription Agreement (ES)', '', 'howto'),
     ('legal/terms/i18n/partnership_tex_es',
      'odoo_partnership_agreement_es.tex', 'Odoo Partnership Agreement (ES)', '', 'howto'),
-    ('legal/terms/i18n/terms_of_sale_es', 'terms_of_sale_es.tex',
-     'Términos Generales de Venta Odoo', '', 'howto'),
 
     ('legal/terms/i18n/enterprise_tex_pt_BR', 'odoo_enterprise_agreement_pt_BR.tex',
      'Odoo Enterprise Subscription Agreement (PT)', '', 'howto'),
@@ -466,7 +439,7 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
         """
         _current_lang = app.config.language or 'en'
         # Replace the context value by its upper-cased value ("FR" instead of "fr")
-        context['language'] = languages_names.get(_current_lang, _current_lang.upper())
+        context['language'] = languages_names.get(_current_lang)
         context['language_code'] = _current_lang
 
         # If the list of languages is not set, assume that the project has no alternate language
@@ -500,24 +473,8 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
         _version = _version or app.config.version
         _lang = _lang or app.config.language or 'en'
         _canonical_page = f'{pagename}.html'
-
-        # legal translations have different URLs schemes as they are not managed on transifex
-        # e.g. FR translation of /terms/enterprise => /fr/terms/enterprise_fr
-        if pagename.startswith('legal/terms/'):
-            if _lang in legal_translations and not pagename.endswith(f"_{_lang}"):
-                # remove language code for current translation, set target one
-                _page = re.sub("_[a-z]{2}$", "", pagename)
-                if 'terms/i18n' not in _page:
-                    _page = _page.replace("/terms/", "/terms/i18n/")
-                _canonical_page = f'{_page}_{_lang}.html'
-            elif _lang == 'en' and pagename.endswith(tuple(f"_{l}" for l in legal_translations)):
-                # remove language code for current translation, link to original EN one
-                _page = re.sub("_[a-z]{2}$", "", pagename)
-                _canonical_page = f'{_page.replace("/i18n/", "/")}.html'
-
         if app.config.is_remote_build:
             _canonical_page = _canonical_page.replace('index.html', '')
-
         return f'{_root}' \
                f'{f"/{_version}" if app.config.versions else ""}' \
                f'{f"/{_lang}" if _lang != "en" else ""}' \

content/administration.rst

@@ -3,63 +3,20 @@
 :hide-page-toc:
 :show-toc:
 
-===================
-Database management
-===================
+====================
+Install and Maintain
+====================
 
 These guides provide instructions on how to install, maintain and upgrade Odoo databases.
 
 .. seealso::
-    :doc:`History of Versions <administration/supported_versions>`
-
-Installation
-============
-
-Depending on the intended use case, there are multiple ways to install Odoo - or not install it at
-all.
-
-- :doc:`Online <administration/odoo_online>` is the easiest way to use Odoo in production or to try it.
-
-- :doc:`Packaged installers <administration/on_premise/packages>` are suitable for testing Odoo and
-  developing modules. They can be used for long-term production with additional deployment and
-  maintenance work.
-
-- :doc:`Source install <administration/on_premise/source>` provides greater flexibility, as it
-  allows, for example, running multiple Odoo versions on the same system. It is adequate to develop
-  modules and can be used as a base for production deployment.
-
-- A `Docker <https://hub.docker.com/_/odoo/>`_ base image is available for development or
-  deployment.
-
-.. _install/editions:
-
-Editions
-========
-
-There are two different editions.
-
-**Odoo Community** is the free and open-source version of the software, licensed under the `GNU
-LGPLv3 <https://github.com/odoo/odoo/blob/master/LICENSE>`_. It is the core upon which Odoo
-Enterprise is built.
-
-**Odoo Enterprise** is the shared source version of the software, giving access to more
-functionalities, including functional support, upgrades, and hosting. `Pricing
-<https://www.odoo.com/pricing-plan>`_ starts from one app free.
-
-.. tip::
-   :doc:`Switch from Community to Enterprise <administration/on_premise/community_to_enterprise>` at
-   any time (except for the source install).
+    :doc:`History of Versions <administration/maintain/supported_versions>`
 
 
 .. toctree::
     :titlesonly:
 
-    administration/hosting
-    administration/odoo_online
-    administration/odoo_sh
-    administration/on_premise
+    administration/install
+    administration/maintain
     administration/upgrade
-    administration/neutralized_database
-    administration/supported_versions
-    administration/mobile
-    administration/odoo_accounts
+    administration/odoo_sh

content/administration/hosting.rst

@@ -1,121 +0,0 @@
-=======
-Hosting
-=======
-
-.. _hosting/change-solution:
-
-Change hosting solution
-=======================
-
-The instructions to change the hosting type of a database depend on the current solution used and to
-which solution the database should be moved.
-
-Transferring an on-premise database
-===================================
-
-To Odoo Online
---------------
-
-.. important::
-   - Odoo Online is *not* compatible with **non-standard apps**.
-   - The database's current version must be :doc:`supported <supported_versions>`.
-
-#. Create a :ref:`duplicate of the database <on-premise/duplicate>`.
-#. In this duplicate, uninstall all **non-standard apps**.
-#. Use the database manager to grab a *dump with filestore*.
-#. `Submit a support ticket <https://www.odoo.com/help>`_ including the following:
-
-   - your **subscription number**,
-   - the **URL** you want to use for the database (e.g., `company.odoo.com`), and
-   - the **dump** as an attachment or as a link to the file (required for 60 MB+ files).
-
-#. Odoo then makes sure the database is compatible before putting it online. In case of technical
-   issues during the process, Odoo might contact you.
-
-.. note::
-   If you have time constraints, `submit a support ticket <https://www.odoo.com/help>`_ as soon as
-   possible to schedule the transfer.
-
-To Odoo.sh
-----------
-
-Follow the instructions found in :ref:`the Import your database section
-<odoo_sh_import_your_database>` of the Odoo.sh *Create your project* documentation.
-
-Transferring an Odoo Online database
-====================================
-
-.. important::
-   Odoo Online's :ref:`intermediary versions <supported_versions>` are not supported by Odoo.sh or
-   on-premise. Therefore, if the database to transfer is running an intermediary version, it must be
-   upgraded first to the next :ref:`major version <supported_versions>`, waiting for its release if
-   necessary.
-
-   .. example::
-      Transferring an online database running on Odoo 16.3 would require first upgrading it to Odoo
-      17.0.
-
-   .. tip::
-      Click the gear icon (:guilabel:`⚙`) next to the database name on the `Odoo Online database
-      manager <https://www.odoo.com/my/databases/>`_ to display its version number.
-
-   .. warning::
-      If there is an active Odoo subscription linked to the database being migrated, reach out to
-      the Customer Service Manager or `submit a support ticket <https://www.odoo.com/help>`_  to
-      complete the subscription transfer.
-
-To on-premise
--------------
-
-#. Sign in to `the Odoo Online database manager <https://www.odoo.com/my/databases/>`_ and click the
-   gear icon (:guilabel:`⚙`) next to the database name to :guilabel:`Download` a backup. If the
-   download fails due to the file being too large, `contact Odoo support
-   <https://www.odoo.com/help>`_.
-#. Restore the database from the database manager on your local server using the backup.
-
-To Odoo.sh
-----------
-
-#. Sign in to `the Odoo Online database manager <https://www.odoo.com/my/databases/>`_ and click the
-   gear icon (:guilabel:`⚙`) next to the database name to :guilabel:`Download` a backup. If the
-   download fails due to the file being too large, `contact Odoo support
-   <https://www.odoo.com/help>`_.
-#. Follow the instructions found in :ref:`the Import your database section
-   <odoo_sh_import_your_database>` of the Odoo.sh *Create your project* documentation.
-
-Transferring an Odoo.sh database
-================================
-
-To Odoo Online
---------------
-
-.. important::
-   Odoo Online is *not* compatible with **non-standard apps**.
-
-#. Uninstall all **non-standard apps** in a staging build before doing it in the production build.
-#. `Create a support ticket <https://www.odoo.com/help>`_ including the following:
-
-   - your **subscription number**,
-   - the **URL** you want to use for the database (e.g., `company.odoo.com`),
-   - which **branch** should be migrated,
-   - in which **region** you want the database to be hosted (Americas, Europe, or Asia),
-   - which user(s) will be the **administrator(s)**, and
-   - **when** (and in which timezone) you want the database to be up and running.
-
-#. Odoo then makes sure the database is compatible before putting it online. In case of technical
-   issues during the process, Odoo might contact you.
-
-.. note::
-   - If you have time constraints, `submit a support ticket <https://www.odoo.com/help>`_ as soon as
-     possible to schedule the transfer.
-   - Select the **region** closest to most of your users to reduce latency.
-   - Future **administrator(s)** must have an Odoo.com account.
-   - The **date and time** you want the database to be up and running are helpful to organize the
-     switch from the Odoo.sh server to the Odoo Online servers.
-   - Databases are **not reachable** during their migration.
-
-To on-premise
--------------
-
-#. Download a :ref:`backup of your Odoo.sh production database <odoo_sh_branches_backups>`.
-#. Restore the database from the database manager on your local server using the backup.

content/administration/install.rst

@@ -0,0 +1,14 @@
+:nosearch:
+
+=======
+Install
+=======
+
+.. If you add content on this page, remove the redirect rule 'install -> install/install'
+
+.. toctree::
+
+    install/install
+    install/deploy
+    install/cdn
+    install/email_gateway

content/administration/install/cdn.rst

@@ -57,7 +57,7 @@ Configure the Odoo instance with the new zone
 In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and then activate the
 :guilabel:`Content Delivery Network (CDN)` setting and copy/paste the :guilabel:`Zone URL` value
 from the earlier step into the :guilabel:`CDN Base URL` field. This field is only visible and
-configurable when the :ref:`developer mode <developer-mode>` is activated.
+configurable when :doc:`Developer Mode <../../applications/general/developer_mode>` is activated.
 
 .. note::
    Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN Base URL` and one

content/administration/install/deploy.rst

@@ -0,0 +1,742 @@
+====================
+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
+not generally necessary for a development systems that is not exposed on the
+internet.
+
+.. warning:: If you are setting up a public server, be sure to check our :ref:`security` recommendations!
+
+.. _db_filter:
+
+dbfilter
+========
+
+Odoo is a multi-tenant system: a single Odoo system may run and serve a number
+of database instances. It is also highly customizable, with customizations
+(starting from the modules being loaded) depending on the "current database".
+
+This is not an issue when working with the backend (web client) as a logged-in
+company user: the database can be selected when logging in, and customizations
+loaded afterwards.
+
+However it is an issue for non-logged users (portal, website) which aren't
+bound to a database: Odoo needs to know which database should be used to load
+the website page or perform the operation. If multi-tenancy is not used that is not an
+issue, there's only one database to use, but if there are multiple databases
+accessible Odoo needs a rule to know which one it should use.
+
+That is one of the purposes of :option:`--db-filter <odoo-bin --db-filter>`:
+it specifies how the database should be selected based on the hostname (domain)
+that is being requested. The value is a `regular expression`_, possibly
+including the dynamically injected hostname (``%h``) or the first subdomain
+(``%d``) through which the system is being accessed.
+
+For servers hosting multiple databases in production, especially if ``website``
+is used, dbfilter **must** be set, otherwise a number of features will not work
+correctly.
+
+Configuration samples
+---------------------
+
+* Show only databases with names beginning with 'mycompany'
+
+in :ref:`the configuration file <reference/cmdline/config_file>` set:
+
+.. code-block:: ini
+
+  [options]
+  dbfilter = ^mycompany.*$
+
+* Show only databases matching the first subdomain after ``www``: for example
+  the database "mycompany" will be shown if the incoming request
+  was sent to ``www.mycompany.com`` or ``mycompany.co.uk``, but not
+  for ``www2.mycompany.com`` or ``helpdesk.mycompany.com``.
+
+in :ref:`the configuration file <reference/cmdline/config_file>` set:
+
+.. code-block:: ini
+
+  [options]
+  dbfilter = ^%d$
+
+.. note::
+
+  Setting a proper :option:`--db-filter <odoo-bin --db-filter>` is an important part
+  of securing your deployment.
+  Once it is correctly working and only matching a single database per hostname, it
+  is strongly recommended to block access to the database manager screens,
+  and to use the ``--no-database-list`` startup parameter to prevent listing
+  your databases, and to block access to the database management screens.
+  See also security_.
+
+PostgreSQL
+==========
+
+By default, PostgreSQL only allows connection over UNIX sockets and loopback
+connections (from "localhost", the same machine the PostgreSQL server is
+installed on).
+
+UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same
+machine, and is the default when no host is provided, but if you want Odoo and
+PostgreSQL to execute on different machines [#different-machines]_ it will
+need to `listen to network interfaces`_ [#remote-socket]_, either:
+
+* Only accept loopback connections and `use an SSH tunnel`_ between the
+  machine on which Odoo runs and the one on which PostgreSQL runs, then
+  configure Odoo to connect to its end of the tunnel
+* Accept connections to the machine on which Odoo is installed, possibly
+  over ssl (see `PostgreSQL connection settings`_ for details), then configure
+  Odoo to connect over the network
+
+Configuration sample
+--------------------
+
+* Allow tcp connection on localhost
+* Allow tcp connection from 192.168.1.x network
+
+in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf`` set:
+
+.. code-block:: text
+
+  # IPv4 local connections:
+  host    all             all             127.0.0.1/32            md5
+  host    all             all             192.168.1.0/24          md5
+
+in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/postgresql.conf`` set:
+
+.. code-block:: text
+
+  listen_addresses = 'localhost,192.168.1.2'
+  port = 5432
+  max_connections = 80
+
+.. _setup/deploy/odoo:
+
+Configuring Odoo
+----------------
+
+Out of the box, Odoo connects to a local postgres over UNIX socket via port
+5432. This can be overridden using :ref:`the database options
+<reference/cmdline/server/database>` when your Postgres deployment is not
+local and/or does not use the installation defaults.
+
+The :ref:`packaged installers <setup/install/packaged>` will automatically
+create a new user (``odoo``) and set it as the database user.
+
+* The database management screens are protected by the ``admin_passwd``
+  setting. This setting can only be set using configuration files, and is
+  simply checked before performing database alterations. It should be set to
+  a randomly generated value to ensure third parties can not use this
+  interface.
+* All database operations use the :ref:`database options
+  <reference/cmdline/server/database>`, including the database management
+  screen. For the database management screen to work requires that the PostgreSQL user
+  have ``createdb`` right.
+* Users can always drop databases they own. For the database management screen
+  to be completely non-functional, the PostgreSQL user needs to be created with
+  ``no-createdb`` and the database must be owned by a different PostgreSQL user.
+
+  .. warning:: the PostgreSQL user *must not* be a superuser
+
+Configuration sample
+~~~~~~~~~~~~~~~~~~~~
+
+* connect to a PostgreSQL server on 192.168.1.2
+* port 5432
+* using an 'odoo' user account,
+* with 'pwd' as a password
+* filtering only db with a name beginning with 'mycompany'
+
+in :ref:`the configuration file <reference/cmdline/config_file>` set:
+
+.. code-block:: ini
+
+  [options]
+  admin_passwd = mysupersecretpassword
+  db_host = 192.168.1.2
+  db_port = 5432
+  db_user = odoo
+  db_password = pwd
+  dbfilter = ^mycompany.*$
+
+.. _postgresql_ssl_connect:
+
+SSL Between Odoo and PostgreSQL
+-------------------------------
+
+Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL.
+in Odoo the db_sslmode control the ssl security of the connection
+with value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca'
+or 'verify-full'
+
+`PostgreSQL Doc <https://www.postgresql.org/docs/12/static/libpq-ssl.html>`_
+
+.. _builtin_server:
+
+Builtin server
+==============
+
+Odoo includes built-in HTTP servers, using either multithreading or
+multiprocessing.
+
+For production use, it is recommended to use the multiprocessing server as it
+increases stability, makes somewhat better use of computing resources and can
+be better monitored and resource-restricted.
+
+* Multiprocessing is enabled by configuring :option:`a non-zero number of
+  worker processes <odoo-bin --workers>`, the number of workers should be based
+  on the number of cores in the machine (possibly with some room for cron
+  workers depending on how much cron work is predicted)
+* Worker limits can be configured based on the hardware configuration to avoid
+  resources exhaustion
+
+.. warning:: multiprocessing mode currently isn't available on Windows
+
+Worker number calculation
+-------------------------
+
+* Rule of thumb : (#CPU * 2) + 1
+* Cron workers need CPU
+* 1 worker ~= 6 concurrent users
+
+memory size calculation
+-----------------------
+
+* We consider 20% of the requests are heavy requests, while 80% are simpler ones
+* A heavy worker, when all computed field are well designed, SQL requests are well designed, ... is estimated to consume around 1GB of RAM
+* A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM
+
+Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) + (heavy_worker_ratio * heavy_worker_ram_estimation) )
+
+LiveChat
+--------
+
+In multiprocessing, a dedicated LiveChat worker is automatically started and
+listening on :option:`the gevent port <odoo-bin --gevent-port>` but
+the client will not connect to it.
+
+Instead you must have a proxy redirecting requests whose URL starts with
+``/websocket/`` to the gevent port. Other request should be proxied to
+the :option:`normal HTTP port <odoo-bin --http-port>`
+
+To achieve such a thing, you'll need to deploy a reverse proxy in front of Odoo,
+like nginx or apache. When doing so, you'll need to forward some more http Headers
+to Odoo, and activate the proxy_mode in Odoo configuration to have Odoo read those
+headers.
+
+Configuration sample
+--------------------
+
+* Server with 4 CPU, 8 Thread
+* 60 concurrent users
+
+* 60 users / 6 = 10 <- theoretical number of worker needed
+* (4 * 2) + 1 = 9 <- theoretical maximal number of worker
+* We'll use 8 workers + 1 for cron. We'll also use a monitoring system to measure cpu load, and check if it's between 7 and 7.5 .
+* RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo
+
+in :ref:`the configuration file <reference/cmdline/config_file>`:
+
+.. code-block:: ini
+
+  [options]
+  limit_memory_hard = 1677721600
+  limit_memory_soft = 629145600
+  limit_request = 8192
+  limit_time_cpu = 600
+  limit_time_real = 1200
+  max_cron_threads = 1
+  workers = 8
+
+.. _https_proxy:
+
+HTTPS
+=====
+
+Whether it's accessed via website/web client or web service, Odoo transmits
+authentication information in cleartext. This means a secure deployment of
+Odoo must use HTTPS\ [#switching]_. SSL termination can be implemented via
+just about any SSL termination proxy, but requires the following setup:
+
+* Enable Odoo's :option:`proxy mode <odoo-bin --proxy-mode>`. This should only be enabled when Odoo is behind a reverse proxy
+* Set up the SSL termination proxy (`Nginx termination example`_)
+* Set up the proxying itself (`Nginx proxying example`_)
+* Your SSL termination proxy should also automatically redirect non-secure
+  connections to the secure port
+
+Configuration sample
+--------------------
+
+* Redirect http requests to https
+* Proxy requests to odoo
+
+in :ref:`the configuration file <reference/cmdline/config_file>` set:
+
+.. code-block:: ini
+
+  proxy_mode = True
+
+in ``/etc/nginx/sites-enabled/odoo.conf`` set:
+
+.. code-block:: nginx
+
+  #odoo server
+  upstream odoo {
+    server 127.0.0.1:8069;
+  }
+  upstream odoochat {
+    server 127.0.0.1:8072;
+  }
+  map $http_upgrade $connection_upgrade {
+    default upgrade;
+    ''      close;
+  }
+
+  # http -> https
+  server {
+    listen 80;
+    server_name odoo.mycompany.com;
+    rewrite ^(.*) https://$host$1 permanent;
+  }
+
+  server {
+    listen 443 ssl;
+    server_name odoo.mycompany.com;
+    proxy_read_timeout 720s;
+    proxy_connect_timeout 720s;
+    proxy_send_timeout 720s;
+
+    # SSL parameters
+    ssl_certificate /etc/ssl/nginx/server.crt;
+    ssl_certificate_key /etc/ssl/nginx/server.key;
+    ssl_session_timeout 30m;
+    ssl_protocols TLSv1.2;
+    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
+    ssl_prefer_server_ciphers off;
+
+    # log
+    access_log /var/log/nginx/odoo.access.log;
+    error_log /var/log/nginx/odoo.error.log;
+
+    # Redirect websocket requests to odoo gevent port
+    location /websocket {
+      proxy_pass http://odoochat;
+      proxy_set_header Upgrade $http_upgrade;
+      proxy_set_header Connection $connection_upgrade;
+      proxy_set_header X-Forwarded-Host $host;
+      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+      proxy_set_header X-Forwarded-Proto $scheme;
+      proxy_set_header X-Real-IP $remote_addr;
+    }
+
+    # Redirect requests to odoo backend server
+    location / {
+      # Add Headers for odoo proxy mode
+      proxy_set_header X-Forwarded-Host $host;
+      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+      proxy_set_header X-Forwarded-Proto $scheme;
+      proxy_set_header X-Real-IP $remote_addr;
+      proxy_redirect off;
+      proxy_pass http://odoo;
+    }
+
+    # common gzip
+    gzip_types text/css text/scss text/plain text/xml application/xml application/json application/javascript;
+    gzip on;
+  }
+
+Odoo as a WSGI Application
+==========================
+
+It is also possible to mount Odoo as a standard WSGI_ application. Odoo
+provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. That
+script should be customized (possibly after copying it from the setup directory) to correctly set the
+configuration directly in :mod:`odoo.tools.config` rather than through the
+command-line or a configuration file.
+
+However the WSGI server will only expose the main HTTP endpoint for the web
+client, website and webservice API. Because Odoo does not control the creation
+of workers anymore it can not setup cron or livechat workers
+
+Cron Workers
+------------
+
+To run cron jobs for an Odoo deployment as a WSGI application requires
+
+* A classical Odoo (run via ``odoo-bin``)
+* Connected to the database in which cron jobs have to be run (via
+  :option:`odoo-bin -d`)
+* Which should not be exposed to the network. To ensure cron runners are not
+  network-accessible, it is possible to disable the built-in HTTP server
+  entirely with :option:`odoo-bin --no-http` or setting ``http_enable = False``
+  in the configuration file
+
+LiveChat
+--------
+
+The second problematic subsystem for WSGI deployments is the LiveChat: where
+most HTTP connections are relatively short and quickly free up their worker
+process for the next request, LiveChat require a long-lived connection for
+each client in order to implement near-real-time notifications.
+
+This is in conflict with the process-based worker model, as it will tie
+up worker processes and prevent new users from accessing the system. However,
+those long-lived connections do very little and mostly stay parked waiting for
+notifications.
+
+The solutions to support livechat/motifications in a WSGI application are:
+
+* Deploy a threaded version of Odoo (instead of a process-based preforking
+  one) and redirect only requests to URLs starting with ``/websocket/`` to
+  that Odoo, this is the simplest and the websocket URL can double up as the cron
+  instance.
+* Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting
+  with ``/websocket/`` to
+  :option:`the gevent port <odoo-bin --gevent-port>`.
+
+.. _deploy/streaming:
+
+Serving static files and attachments
+====================================
+
+For development convenience, Odoo directly serves all static files and attachments in its modules.
+This may not be ideal when it comes to performances, and static files should generally be served by
+a static HTTP server.
+
+Serving static files
+--------------------
+
+Odoo static files are located in each module's :file:`static/` folder, so static files can be served
+by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module
+(and file) in the various addons paths.
+
+.. example::
+   Say Odoo has been installed via the **debian packages** for Community and Enterprise and the
+   :option:`--addons-path <odoo-bin --addons-path>` is ``'/usr/lib/python3/dist-packages/odoo/addons'``.
+
+   Using the above NGINX (https) configuration, the following location block should be added to
+   serve static files via NGINX.
+
+   .. code-block:: nginx
+
+       location @odoo {
+           # copy-paste the content of the / location block
+       }
+
+       # Serve static files right away
+       location ~ ^/[^/]+/static/.+$ {
+           root /usr/lib/python3/dist-packages/odoo/addons;
+           try_files $uri @odoo;
+           expires 24h;
+       }
+
+.. example::
+   Say Odoo has been installed via the **source**. The two git repositories for Community and
+   Enterprise have been cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise`
+   respectively and the :option:`--addons-path <odoo-bin --addons-path>` is
+   ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``.
+
+   Using the above NGINX (https) configuration, the following location block should be added to
+   serve static files via NGINX.
+
+   .. code-block:: nginx
+
+       location @odoo {
+           # copy-paste the content of the / location block
+       }
+
+       # Serve static files right away
+       location ~ ^/[^/]+/static/.+$ {
+           root /opt/odoo;
+           try_files /community/odoo/addons$uri /community/addons$uri /enterprise$uri @odoo;
+           expires 24h;
+       }
+
+.. warning::
+   The actual NGINX configuration you need is highly dependent on your own installation. The two
+   above snippets only highlight two possible configurations and may not be used as-is.
+
+Serving attachments
+-------------------
+
+Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be
+directly accessed via a static web server as accessing them requires multiple lookups in the
+database to determine where the files are stored and whether the current user can access them or
+not.
+
+Nevertheless, once the file has been located and the access rights verified by Odoo, it is a good
+idea to serve the file using the static web server instead of Odoo. For Odoo to delegate serving
+files to the static web server, the `X-Sendfile <https://tn123.org/mod_xsendfile/>`_ (apache) or
+`X-Accel <https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/>`_ (nginx) extensions
+must be enabled and configured on the static web server. Once it is set up, start Odoo with the
+:option:`--x-sendfile <odoo-bin --x-sendfile>` CLI flag (this unique flag is used for both
+X-Sendfile and X-Accel).
+
+
+.. note::
+   - The X-Sendfile extension for apache (and compatible web servers) does not require any
+     supplementary configuration.
+   - The X-Accel extension for NGINX **does** require the following additionnal configuration:
+
+     .. code-block:: nginx
+
+         location /web/filestore {
+             internal;
+             alias /path/to/odoo/data-dir/filestore;
+         }
+
+     In case you don't know what is the path to your filestore, start Odoo with the
+     :option:`--x-sendfile <odoo-bin --x-sendfile>` option and navigate to the ``/web/filestore`` URL
+     directly via Odoo (don't navigate to the URL via NGINX). This logs a warnings, the message
+     contains the configuration you need.
+
+
+.. _security:
+
+Security
+========
+
+For starters, keep in mind that securing an information system is a continuous process,
+not a one-shot operation. At any moment, you will only be as secure as the weakest link
+in your environment.
+
+So please do not take this section as the ultimate list of measures that will prevent
+all security problems. It's only intended as a summary of the first important things
+you should be sure to include in your security action plan. The rest will come
+from best security practices for your operating system and distribution,
+best practices in terms of users, passwords, and access control management, etc.
+
+When deploying an internet-facing server, please be sure to consider the following
+security-related topics:
+
+- Always set a strong super-admin admin password, and restrict access to the database
+  management pages as soon as the system is set up. See :ref:`db_manager_security`.
+
+- Choose unique logins and strong passwords for all administrator accounts on all databases.
+  Do not use 'admin' as the login. Do not use those logins for day-to-day operations,
+  only for controlling/managing the installation.
+  *Never* use any default passwords like admin/admin, even for test/staging databases.
+
+- Do **not** install demo data on internet-facing servers. Databases with demo data contain
+  default logins and passwords that can be used to get into your systems and cause significant
+  trouble, even on staging/dev systems.
+
+- Use appropriate database filters ( :option:`--db-filter <odoo-bin --db-filter>`)
+  to restrict the visibility of your databases according to the hostname.
+  See :ref:`db_filter`.
+  You may also use :option:`-d <odoo-bin -d>` to provide your own (comma-separated)
+  list of available databases to filter from, instead of letting the system fetch
+  them all from the database backend.
+
+- Once your ``db_name`` and ``db_filter`` are configured and only match a single database
+  per hostname, you should set ``list_db`` configuration option to ``False``, to prevent
+  listing databases entirely, and to block access to the database management screens
+  (this is also exposed as the :option:`--no-database-list <odoo-bin --no-database-list>`
+  command-line option)
+
+- Make sure the PostgreSQL user (:option:`--db_user <odoo-bin --db_user>`) is *not* a super-user,
+  and that your databases are owned by a different user. For example they could be owned by
+  the ``postgres`` super-user if you are using a dedicated non-privileged ``db_user``.
+  See also :ref:`setup/deploy/odoo`.
+
+- Keep installations updated by regularly installing the latest builds,
+  either via GitHub or by downloading the latest version from
+  https://www.odoo.com/page/download or http://nightly.odoo.com
+
+- Configure your server in multi-process mode with proper limits matching your typical
+  usage (memory/CPU/timeouts). See also :ref:`builtin_server`.
+
+- Run Odoo behind a web server providing HTTPS termination with a valid SSL certificate,
+  in order to prevent eavesdropping on cleartext communications. SSL certificates are
+  cheap, and many free options exist.
+  Configure the web proxy to limit the size of requests, set appropriate timeouts,
+  and then enable the :option:`proxy mode <odoo-bin --proxy-mode>` option.
+  See also :ref:`https_proxy`.
+
+- If you need to allow remote SSH access to your servers, make sure to set a strong password
+  for **all** accounts, not just `root`. It is strongly recommended to entirely disable
+  password-based authentication, and only allow public key authentication. Also consider
+  restricting access via a VPN, allowing only trusted IPs in the firewall, and/or
+  running a brute-force detection system such as `fail2ban` or equivalent.
+
+- Consider installing appropriate rate-limiting on your proxy or firewall, to prevent
+  brute-force attacks and denial of service attacks. See also :ref:`login_brute_force`
+  for specific measures.
+
+  Many network providers provide automatic mitigation for Distributed Denial of
+  Service attacks (DDOS), but this is often an optional service, so you should consult
+  with them.
+
+- Whenever possible, host your public-facing demo/test/staging instances on different
+  machines than the production ones. And apply the same security precautions as for
+  production.
+
+- If your public-facing Odoo server has access to sensitive internal network resources
+  or services (e.g. via a private VLAN), implement appropriate firewall rules to
+  protect those internal resources. This will ensure that the Odoo server cannot
+  be used accidentally (or as a result of malicious user actions) to access or disrupt
+  those internal resources.
+  Typically this can be done by applying an outbound default DENY rule on the firewall,
+  then only explicitly authorizing access to internal resources that the Odoo server
+  needs to access.
+  `Systemd IP traffic access control <http://0pointer.net/blog/ip-accounting-and-access-lists-with-systemd.html>`_
+  may also be useful to implement per-process network access control.
+
+- If your public-facing Odoo server is behind a Web Application Firewall, a load-balancer,
+  a transparent DDoS protection service (like CloudFlare) or a similar network-level
+  device, you may wish to avoid direct access to the Odoo system. It is generally
+  difficult to keep the endpoint IP addresses of your Odoo servers secret. For example
+  they can appear in web server logs when querying public systems, or in the headers
+  of emails posted from Odoo.
+  In such a situation you may want to configure your firewall so that the endpoints
+  are not accessible publicly except from the specific IP addresses of your WAF,
+  load-balancer or proxy service. Service providers like CloudFlare usually maintain
+  a public list of their IP address ranges for this purpose.
+
+- If you are hosting multiple customers, isolate customer data and files from each other
+  using containers or appropriate "jail" techniques.
+
+- Setup daily backups of your databases and filestore data, and copy them to a remote
+  archiving server that is not accessible from the server itself.
+
+
+.. _login_brute_force:
+
+Blocking Brute Force Attacks
+----------------------------
+
+For internet-facing deployments, brute force attacks on user passwords are very common, and this
+threat should not be neglected for Odoo servers. Odoo emits a log entry whenever a login attempt
+is performed, and reports the result: success or failure, along with the target login and source IP.
+
+The log entries will have the following form.
+
+Failed login::
+
+      2018-07-05 14:56:31,506 24849 INFO db_name odoo.addons.base.res.res_users: Login failed for db:db_name login:admin from 127.0.0.1
+
+Successful login::
+
+      2018-07-05 14:56:31,506 24849 INFO db_name odoo.addons.base.res.res_users: Login successful for db:db_name login:admin from 127.0.0.1
+
+
+These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`.
+
+For example, the following fail2ban filter definition should match a
+failed login::
+
+    [Definition]
+    failregex = ^ \d+ INFO \S+ \S+ Login failed for db:\S+ login:\S+ from <HOST>
+    ignoreregex =
+
+This could be used with a jail definition to block the attacking IP on HTTP(S).
+
+Here is what it could look like for blocking the IP for 15 minutes when
+10 failed login attempts are detected from the same IP within 1 minute::
+
+    [odoo-login]
+    enabled = true
+    port = http,https
+    bantime = 900  ; 15 min ban
+    maxretry = 10  ; if 10 attempts
+    findtime = 60  ; within 1 min  /!\ Should be adjusted with the TZ offset
+    logpath = /var/log/odoo.log  ;  set the actual odoo log path here
+
+.. _db_manager_security:
+
+Database Manager Security
+-------------------------
+
+:ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing.
+
+This setting is used on all database management screens (to create, delete,
+dump or restore databases).
+
+If the management screens must not be accessible at all, you should set ``list_db``
+configuration option to ``False``, to block access to all the database selection and
+management screens.
+
+.. warning::
+
+  It is strongly recommended to disable the Database Manager for any internet-facing
+  system! It is meant as a development/demo tool, to make it easy to quickly create
+  and manage databases. It is not designed for use in production, and may even expose
+  dangerous features to attackers. It is also not designed to handle large databases,
+  and may trigger memory limits.
+
+  On production systems, database management operations should always be performed by
+  the system administrator, including provisioning of new databases and automated backups.
+
+Be sure to setup an appropriate ``db_name`` parameter
+(and optionally, ``db_filter`` too) so that the system can determine the target database
+for each request, otherwise users will be blocked as they won't be allowed to choose the
+database themselves.
+
+If the management screens must only be accessible from a selected set of machines,
+use the proxy server's features to block access to all routes starting with ``/web/database``
+except (maybe) ``/web/database/selector`` which displays the database-selection screen.
+
+If the database-management screen should be left accessible, the
+``admin_passwd`` setting must be changed from its ``admin`` default: this
+password is checked before allowing database-alteration operations.
+
+It should be stored securely, and should be generated randomly e.g.
+
+.. code-block:: console
+
+    $ python3 -c 'import base64, os; print(base64.b64encode(os.urandom(24)))'
+
+which will generate a 32 characters pseudorandom printable string.
+
+Supported Browsers
+==================
+
+Odoo supports all the major desktop and mobile browsers available on the market,
+as long as they are supported by their publishers.
+
+Here are the supported browsers:
+
+- Google Chrome
+- Mozilla Firefox
+- Microsoft Edge
+- Apple Safari
+
+.. warning:: Please make sure your browser is up-to-date and still supported by
+    its publisher before filing a bug report.
+
+.. note::
+
+    Since Odoo 13.0, ES6 is supported.  Therefore, IE support is dropped.
+
+.. [#different-machines]
+    to have multiple Odoo installations use the same PostgreSQL database,
+    or to provide more computing resources to both software.
+.. [#remote-socket]
+    technically a tool like socat_ can be used to proxy UNIX sockets across
+    networks, but that is mostly for software which can only be used over
+    UNIX sockets
+.. [#switching]
+    or be accessible only over an internal packet-switched network, but that
+    requires secured switches, protections against `ARP spoofing`_ and
+    precludes usage of WiFi. Even over secure packet-switched networks,
+    deployment over HTTPS is recommended, and possible costs are lowered as
+    "self-signed" certificates are easier to deploy on a controlled
+    environment than over the internet.
+
+.. _regular expression: https://docs.python.org/3/library/re.html
+.. _ARP spoofing: https://en.wikipedia.org/wiki/ARP_spoofing
+.. _Nginx termination example:
+    https://nginx.com/resources/admin-guide/nginx-ssl-termination/
+.. _Nginx proxying example:
+    https://nginx.com/resources/admin-guide/reverse-proxy/
+.. _socat: http://www.dest-unreach.org/socat/
+.. _PostgreSQL connection settings:
+.. _listen to network interfaces:
+    https://www.postgresql.org/docs/12/static/runtime-config-connection.html
+.. _use an SSH tunnel:
+    https://www.postgresql.org/docs/12/static/ssh-tunnels.html
+.. _WSGI: https://wsgi.readthedocs.org/
+.. _POSBox: https://www.odoo.com/page/point-of-sale-hardware#part_2

content/administration/install/install.rst

@@ -0,0 +1,745 @@
+
+.. _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 `Odoo Online`_ 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.
+
+Odoo Online
+-----------
+
+Trivial to start with, fully managed and migrated by Odoo S.A., `Odoo Online`_
+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, `Odoo Online`_ 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 Community 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
+-----
+
+Prepare
+~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Debian/Ubuntu
+
+      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
+
+   .. group-tab:: Fedora
+
+      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
+~~~~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Debian/Ubuntu
+
+      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:
+
+      .. code-block:: console
+
+          $ wget -q -O - https://nightly.odoo.com/odoo.key | sudo gpg --dearmor -o /usr/share/keyrings/odoo-archive-keyring.gpg
+          $ echo 'deb [signed-by=/usr/share/keyrings/odoo-archive-keyring.gpg] https://nightly.odoo.com/{CURRENT_MAJOR_BRANCH}/nightly/deb/ ./' | sudo tee /etc/apt/sources.list.d/odoo.list
+          $ sudo apt-get update && sudo apt-get install odoo
+
+      You can then use the usual `apt-get upgrade` command to keep your installation up-to-date.
+
+   .. group-tab:: Fedora
+
+      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/{CURRENT_MAJOR_BRANCH}/nightly/rpm/odoo.repo
+         $ sudo dnf install -y odoo
+         $ sudo systemctl enable odoo
+         $ sudo systemctl start odoo
+
+.. note::
+   At this moment, there is no nightly repository for the Enterprise Edition.
+
+Distribution package
+~~~~~~~~~~~~~~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Debian/Ubuntu
+
+      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_>`_.
+
+      .. note::
+         Odoo {CURRENT_MAJOR_VERSION} 'deb' package currently supports `Debian 11 (Bullseye)`_,
+         `Ubuntu 22.04 (Jammy)`_ or above.
+
+      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
+
+         - 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
+
+   .. group-tab:: Fedora
+
+      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_>`_.
+
+      .. note::
+         Odoo {CURRENT_MAJOR_VERSION} 'rpm' package supports Fedora 36.
+
+      Once downloaded, the package can be installed using the 'dnf' package manager:
+
+      .. code-block:: console
+
+         $ sudo dnf localinstall odoo_{CURRENT_MAJOR_BRANCH}.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.
+
+It can be more convenient for module developers as the Odoo source is more easily accessible than
+using packaged installation.
+
+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.
+
+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_>`_
+
+.. _setup/install/source/git:
+
+Git
+~~~
+
+The following requires `Git <git_>`_ to be installed on your machine and that you have basic
+knowledge of Git commands. To clone a Git repository, you must choose between cloning with HTTPS or
+SSH. If you do not know the difference between the two, the best option is most likely HTTPS. If you
+are following the :doc:`Getting started </developer/tutorials/getting_started>` developer tutorial,
+or plan on contributing to Odoo source code, choose SSH.
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      .. tabs::
+
+         .. tab:: Clone with HTTPS
+
+            .. code-block:: doscon
+
+               C:\> git clone https://github.com/odoo/odoo.git
+               C:\> git clone https://github.com/odoo/enterprise.git
+
+         .. tab:: Clone with SSH
+
+            .. code-block:: doscon
+
+               C:\> git clone git@github.com:odoo/odoo.git
+               C:\> git clone git@github.com:odoo/enterprise.git
+
+   .. group-tab:: Linux
+
+      .. tabs::
+
+         .. tab:: Clone with HTTPS
+
+            .. code-block:: console
+
+               $ git clone https://github.com/odoo/odoo.git
+               $ git clone https://github.com/odoo/enterprise.git
+
+         .. tab:: Clone with SSH
+
+            .. code-block:: console
+
+               $ git clone git@github.com:odoo/odoo.git
+               $ git clone git@github.com:odoo/enterprise.git
+
+   .. group-tab:: Mac OS
+
+      .. tabs::
+
+         .. tab:: Clone with HTTPS
+
+            .. code-block:: console
+
+               $ git clone https://github.com/odoo/odoo.git
+               $ git clone https://github.com/odoo/enterprise.git
+
+         .. tab:: Clone with SSH
+
+            .. code-block:: console
+
+               $ git clone git@github.com:odoo/odoo.git
+               $ git clone git@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. See
+   :ref:`setup/install/editions` to get access to the Enterprise repository.
+
+.. _setup/install/source/prepare:
+
+Prepare
+-------
+
+Python
+~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      Odoo requires Python 3.8 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.7 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
+
+   .. group-tab:: Linux
+
+      Odoo requires Python 3.8 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.7 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
+
+   .. group-tab:: Mac OS
+
+      Odoo requires Python 3.8 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.7 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
+~~~~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      Odoo uses PostgreSQL as database management system. `Download and install PostgreSQL
+      <https://www.postgresql.org/download/windows/>`_ (supported version: 12.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:
+         :file:`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`.
+
+   .. group-tab:: Linux
+
+      Odoo uses PostgreSQL as database management system. Use your package manager to download and
+      install PostgreSQL (supported version: 12.0 and later).
+
+      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.
+
+   .. group-tab:: Mac OS
+
+      Odoo uses PostgreSQL as database management system. Use `postgres.app
+      <https://postgresapp.com>`_ to download and install PostgreSQL (supported version: 12.0 and
+      later).
+
+      .. tip::
+         To make the command line tools bundled with `postgres.app` available, make sure to setup your
+         `$PATH` variable by following the `Postgres.app CLI Tools Instructions
+         <https://postgresapp.com/documentation/cli-tools.html>`_.
+
+      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.
+
+.. _install/dependencies:
+
+Dependencies
+~~~~~~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      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
+
+      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: :file:`C:\\Users\\<user>\\AppData\\Roaming\\npm\\`).
+
+   .. group-tab:: Linux
+
+      Using your **distribution packages** is the preferred way of installing dependencies.
+      Alternatively, you can install the python dependencies with **pip**.
+
+      .. tabs::
+
+         .. tab:: Debian/Ubuntu
+
+            For Debian-based systems, the packages are listed in the `debian/control
+            <{GITHUB_PATH}/debian/control>`_ file of the Odoo sources.
+
+            On Debian/Ubuntu, the following commands should install the required packages:
+
+            .. code-block:: console
+
+               $ cd /CommunityPath
+               $ sed -n -e '/^Depends:/,/^Pre/ s/ python3-\(.*\),/python3-\1/p' debian/control | sudo xargs apt-get install -y
+
+         .. tab:: Install with pip
+
+            As some of the python packages need a compilation step, they require system libraries to
+            be installed.
+
+            On Debian/Ubuntu-based systems, the following command should install these required
+            libraries:
+
+            .. code-block:: console
+
+               $ sudo apt install python3-pip libldap2-dev libpq-dev libsasl2-dev
+
+            Odoo dependencies are listed in the :file:`requirements.txt` file located at the root of
+            the Odoo community directory.
+
+            .. note::
+               | The python packages in :file:`requirements.txt` are based on their stable/LTS
+                 Debian/Ubuntu corresponding version at the moment of the Odoo release.
+               | E.g., for Odoo 15.0, the `python3-babel` package version is 2.8.0 in Debian
+                 Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is then chosen in the
+                 :file:`requirements.txt`.
+
+            .. 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 (:file:`CommunityPath`) and run
+            **pip** on the requirements file to install the requirements for the current user.
+
+            .. code-block:: console
+
+               $ cd /CommunityPath
+               $ pip install -r requirements.txt
+
+      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
+
+   .. group-tab:: Mac OS
+
+      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.
+
+      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
+
+.. important::
+   `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.
+
+.. _setup/install/source/running_odoo:
+
+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:
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      .. 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 name of the
+      PostgreSQL database.
+
+   .. group-tab:: Linux
+
+      .. 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 name
+      of the PostgreSQL database.
+
+   .. group-tab:: Mac OS
+
+      .. 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 name
+      of the PostgreSQL database.
+
+After the server has started (the INFO log `odoo.modules.loading: Modules loaded.` is printed), open
+http://localhost:8069 in your web browser and log in with the base administrator account: Use
+`admin` for the :guilabel:`Email` and, again, `admin` for the :guilabel:`Password`. That's it, you
+just logged into your own Odoo database!
+
+.. tip::
+   - From there, you can create and manage new :doc:`users
+     </applications/general/users/manage_users>`.
+   - The user account you use to log into Odoo's web interface differs from the :option:`--db_user
+     <odoo-bin -r>` CLI argument.
+
+.. seealso::
+   :doc:`The exhaustive list of CLI arguments for odoo-bin </developer/reference/cli>`.
+
+.. _setup/install/docker:
+
+Docker
+======
+
+The full documentation on how to use Odoo with Docker can be found on the
+official Odoo `docker image <https://hub.docker.com/_/odoo/>`_ page.
+
+.. _Debian 11 (Bullseye): https://www.debian.org/releases/bullseye/
+.. _demo: https://demo.odoo.com
+.. _docker: https://www.docker.com
+.. _download: https://www.odoo.com/page/download
+.. _Ubuntu 22.04 (Jammy): https://releases.ubuntu.com/22.04/
+.. _EPEL: https://fedoraproject.org/wiki/EPEL
+.. _PostgreSQL: https://www.postgresql.org
+.. _the official installer:
+.. _install pip:
+    https://pip.pypa.io/en/latest/installing.html#install-pip
+.. _Quilt: https://en.wikipedia.org/wiki/Quilt_(software)
+.. _Odoo Online: https://www.odoo.com/page/start
+.. _the wkhtmltopdf download page: https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.5
+.. _UAC: https://en.wikipedia.org/wiki/User_Account_Control
+.. _wkhtmltopdf: https://wkhtmltopdf.org
+.. _pip: https://pip.pypa.io
+.. _macports: https://www.macports.org
+.. _homebrew: https://brew.sh
+.. _wheels: https://wheel.readthedocs.org/en/latest/
+.. _virtualenv: https://pypi.python.org/pypi/virtualenv
+.. _virtualenvwrapper: https://virtualenvwrapper.readthedocs.io/en/latest/
+.. _pywin32: https://sourceforge.net/projects/pywin32/files/pywin32/
+.. _community-repository: https://github.com/odoo/odoo
+.. _enterprise-repository: https://github.com/odoo/enterprise
+.. _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,18 @@
+:nosearch:
+
+========
+Maintain
+========
+
+.. toctree::
+
+    maintain/domain_names
+    maintain/azure_oauth
+    maintain/google_oauth
+    maintain/mailjet_api
+    maintain/update
+    maintain/enterprise
+    maintain/hosting_changes
+    maintain/odoo_online
+    maintain/on_premise
+    maintain/supported_versions

content/administration/maintain/azure_oauth.rst

@@ -0,0 +1,220 @@
+=======================================================
+Connect Microsoft Outlook 365 to Odoo using Azure OAuth
+=======================================================
+
+Odoo is compatible with Microsoft's Azure OAuth for Microsoft 365. In order to send and receive
+secure emails from a custom domain, all that is required is to configure a few settings on the
+Azure platform and on the back end of the Odoo database. This configuration works with either a
+personal email address or an address created by a custom domain.
+
+.. seealso::
+   `Microsoft Learn: Register an application with the Microsoft identity platform
+   <https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app>`_
+
+.. seealso::
+   - :doc:`/applications/general/auth/azure`
+   - :doc:`/applications/productivity/calendar/outlook`
+
+Setup in Microsoft Azure Portal
+===============================
+
+Create a new application
+------------------------
+
+To get started, go to `Microsoft's Azure Portal <https://portal.azure.com/>`_. Log in with the
+:guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise log in with the
+personal :guilabel:`Microsoft account`. A user with administrative access to the Azure Settings
+will need to connect and perform the following configuration. Next, navigate to the section
+labeled :guilabel:`Manage Azure Active Directory`.
+
+Now, click on :guilabel:`Add (+)`, located in the top menu, and then select :guilabel:`App
+registration`. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` to
+`Odoo` or something recognizable. Under the :guilabel:`Supported account types` section select
+:guilabel:`Accounts in any organizational directory (Any Azure AD directory - Multitenant) and
+personal Microsoft accounts (e.g. Skype, Xbox)`.
+
+Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input
+`https://<odoo base url>/microsoft_outlook/confirm` in the :guilabel:`URL` field. The Odoo base URL
+is the canonical domain at which your Odoo instance can be reached in the URL field.
+
+.. example::
+   *mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the database's subdomain,
+   assuming it's hosted on Odoo.com
+
+After the URL has been added to the field, :guilabel:`Register` the application so it is created.
+
+API permissions
+---------------
+
+The :guilabel:`API permissions` should be set next. Odoo will need specific API permissions to be
+able to read (IMAP) and send (SMTP) emails in the Microsoft 365 setup. First, click the
+:guilabel:`API permissions` link, located in the left menu bar. Next, click on the :guilabel:`(+)
+Add a Permission` button and select :guilabel:`Microsoft Graph` under :guilabel:`Commonly Used
+Microsoft APIs`. After, select the :guilabel:`Delegated Permissions` option.
+
+In the search bar, search for the following :guilabel:`Deregulated permissions` and click
+:guilabel:`Add permissions` for each one:
+
+- :guilabel:`SMTP.Send`
+- :guilabel:`IMAP.AccessAsUser.All`
+
+.. note::
+   The :guilabel:`User.Read` permission will be added by default.
+
+.. image:: azure_oauth/permissions.png
+   :align: center
+   :alt: API permissions needed for Odoo integration are listed under the Microsoft Graph.
+
+Assign users and groups
+=======================
+
+After adding the API permissions, navigate back to the :guilabel:`Overview` of the
+:guilabel:`Application` in the top of the left sidebar menu.
+
+Now, add users to this application. Under the :guilabel:`Essentials` overview table, click on the
+link labeled :guilabel:`Managed Application in Local Directory`, or the last option on the bottom
+right-hand side of the table.
+
+.. image:: azure_oauth/managed-application.png
+   :align: center
+   :alt: Add users/groups by clicking the Managed application in local directory link for the
+         created application.
+
+In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click on :guilabel:`(+) Add
+User/Group`. Depending on the account, either a :guilabel:`Group` and a :guilabel:`User` can be
+added, or only :guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` to be
+added.
+
+Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None Selected` and add the users
+or group of users that will be sending emails from the :guilabel:`Microsoft account` in Odoo.
+:guilabel:`Add` the users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to the
+application.
+
+Create credentials
+------------------
+
+Now that the Microsoft Azure app is set up, credentials need to be created for the Odoo setup.
+These include the :guilabel:`Client ID` and :guilabel:`Client Secret`. To start, the
+:guilabel:`Client ID` can be copied from the :guilabel:`Overview` page of the app. The
+:guilabel:`Client ID` or :guilabel:`Application ID` is located under the :guilabel:`Display Name`
+in the :guilabel:`Essentials` overview of the app.
+
+.. image:: azure_oauth/application-id.png
+   :align: center
+   :alt: Application/Client ID located in the Overview of the app.
+
+Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this value, click on
+:guilabel:`Certificates & Secrets` in the left sidebar menu. Then, a :guilabel:`Client Secret`
+needs to be produced. In order to do this, click on the :guilabel:`(+) New Client Secret` button.
+
+A window on the right will populate with a button labeled :guilabel:`Add a client secret`. Under
+:guilabel:`Description`, type in `Odoo Fetchmail` or something recognizable, and then set the
+:guilabel:`expiration date`.
+
+.. important::
+   A new :guilabel:`Client Secret` will need to be produced and configured if the first one
+   expires. In this event, there could be an interruption of service, so the expiration date should
+   be noted and set to the furthest possible date.
+
+Next, click on :guilabel:`Add` when these two values are entered. A :guilabel:`Client Secret Value`
+and :guilabel:`Secret ID` will be created. It is important to copy the :guilabel:`Value` or
+:guilabel:`Client Secret Value` into a notepad as it will become encrypted after leaving this page.
+The :guilabel:`Secret ID` is not needed.
+
+.. image:: azure_oauth/secretvalue.png
+   :align: center
+   :alt: Client Secret Value or Value in the app's credentials.
+
+After these steps, the following items should be ready to be set up in Odoo:
+
+- A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)
+- A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)
+
+This completes the setup on the :guilabel:`Microsoft Azure Portal` side.
+
+Setup in Odoo
+=============
+
+Enter Microsoft Outlook credentials
+-----------------------------------
+
+First, open the Odoo database and navigate to the :guilabel:`Apps` module. Then, remove the
+:guilabel:`Apps` filter from the search bar and type in `Outlook`. After that, install the module
+called :guilabel:`Microsoft Outlook`.
+
+Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss`
+section, ensure that the checkbox for :guilabel:`Custom Email Servers` is checked. This populates
+a new option for :guilabel:`Outlook Credentials`.
+
+:guilabel:`Save` the progress.
+
+Then, copy and paste the :guilabel:`Client ID` (Application ID) and :guilabel:`Client Secret
+(Client Secret Value)` into the respective fields and :guilabel:`Save` the settings.
+
+.. image:: azure_oauth/outlookcreds.png
+   :align: center
+   :alt: Outlook Credentials in Odoo General Settings.
+
+Configure outgoing email server
+-------------------------------
+
+On the :guilabel:`General Settings` page, under the :guilabel:`Custom Email Servers` setting,
+click the :guilabel:`Outgoing Email Servers` link to configure the Microsoft account.
+
+Then, create a new email server and check the box for :guilabel:`Outlook`. Next, fill in the
+:guilabel:`Name` (it can be anything) and the Microsoft Outlook email :guilabel:`Username`.
+
+If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address
+<email_communication/default>`.
+
+Then, click on :guilabel:`Connect your Outlook account`.
+
+A new window from Microsoft opens to complete the :guilabel:`authorization process`. Select the
+appropriate email address that is being configured in Odoo.
+
+.. image:: azure_oauth/verify-outlook.png
+   :align: center
+   :alt: Permission page to grant access between newly created app and Odoo.
+
+Then, allow Odoo to access the Microsoft account by clicking on :guilabel:`Yes`. After this, the
+page will navigate back to the newly configured :guilabel:`Outgoing Mail Server` in Odoo. The
+configuration automatically loads the :guilabel:`token` in Odoo, and a tag stating
+:guilabel:`Outlook Token Valid` appears in green.
+
+.. image:: azure_oauth/outlook-token.png
+   :align: center
+   :alt: Valid Outlook Token indicator.
+
+Finally, click :guilabel:`Test Connection`. A confirmation message should appear. The Odoo database
+can now send safe, secure emails through Microsoft Outlook using OAuth authentication.
+
+Multiple user configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Each user should have a separate server set up. The :guilabel:`from-filter` should be set so that
+only the user's email is sent from that server. In other words, only a user with an email address
+that matches the set :guilabel:`from-filter` is able to use this server.
+
+After setting the :guilabel:`from-filter`, set up a fallback email account to allow for the sending
+of :guilabel:`notifications`. The fallback email must be configured as a :guilabel:`general
+transactional server`. The :guilabel:`mail.default.from` system parameter must be set to the
+:guilabel:`username` of the general transactional server account. For more information see
+:ref:`Use a default email address <email_communication/default>`.
+
+.. note::
+   The :guilabel:`System Parameters` can be accessed by activating
+   :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical
+   --> Parameters --> System Parameters` menu.
+
+Configure incoming email server
+-------------------------------
+
+The incoming account should be configured in a similar way to the outgoing email account. Navigate
+to the :guilabel:`Incoming Mail Servers` in the :guilabel:`Technical Menu` and :guilabel:`Create` a
+new configuration. Check or Select the button next to :guilabel:`Outlook Oauth Authentication` and
+enter the :guilabel:`Microsoft Outlook username`.  Click on :guilabel:`Connect your Outlook
+account`. Odoo will state: :guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the
+account. The account should be ready to receive email to the Odoo database.
+
+.. seealso::
+   :doc:`../../applications/general/email_communication/email_servers`

content/administration/maintain/domain_names.rst

@@ -0,0 +1,366 @@
+============
+Domain names
+============
+
+A **domain name** works as an address for your website. It makes the Internet much more accessible
+as it allows users to type a meaningful web address, such as ``www.odoo.com``, rather than its
+server's IP address with a series of numbers.
+
+You can use a custom domain name to access your Odoo database and websites:
+
+- By :ref:`registering a free domain name with Odoo <domain-name/odoo-register>` (for Odoo Online
+  databases)
+- By :ref:`configuring a custom domain that you already own <domain-name/existing>`.
+
+.. note::
+   Odoo Online and Odoo.sh databases, including their websites, use by default a subdomain of
+   ``odoo.com`` for both the URL and the emails (e.g., ``https://example.odoo.com``).
+
+.. important::
+   Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to all Odoo Online
+   databases for one year. Visitors can then access your website with an address such as
+   ``www.example.com`` rather than the default ``example.odoo.com``.
+
+.. seealso::
+   - `Odoo Tutorials: Register a Free Domain Name
+     <https://www.odoo.com/slides/slide/register-a-free-domain-name-1663>`_
+   - `Odoo Quick Tips: Get a free domain name! <https://www.youtube.com/watch?v=eAfgeNOHLP4>`_
+
+.. _domain-name/about:
+
+About domain names
+==================
+
+Having a **good domain name** is as important to your branding as the name of your business or
+organization as it is the first thing your visitors will notice. We recommend you keep them *simple,
+short, easy to remember and spell*.
+
+A **subdomain** is a domain that is a part of another domain. It often refers to the additional part
+that comes before the main domain name. Traditionally, most websites use the ``www.`` subdomain,
+but any string of letters can be used as well. You can use subdomains to direct your visitors to
+other websites than your main website or to specific pages (e.g., ``experience.odoo.com`` points to
+a specific page.)
+
+All domain names are referenced in the **Domain Name System**, or **DNS**, which works as a giant
+directory for the Internet. There are many DNS servers, so any modification to the DNS can take up
+to 72 hours to propagate worldwide on all servers.
+
+.. _domain-name/indexing:
+
+Indexing of domain names by search engines
+------------------------------------------
+
+Search engines, such as Google and Bing, rely on web crawlers (:dfn:`robots that explore and analyze
+the web`) to index all websites and their related domain names. These crawlers discover new URLs
+thanks to links on known web pages. As a result, search engines should index domain names
+automatically after a while, as long as their URLs are mentioned elsewhere on the Internet.
+
+Improving the appearance and positioning of web pages on search engines is a practice named "Search
+Engine Optimization" (SEO).
+
+.. tip::
+   Adding relevant content, optimizing metadata, and building high-quality backlinks can all help
+   improve a website's search engine visibility.
+
+Some search engines provide tools for web admins, such as
+`Google Search Console <https://search.google.com/search-console>`_ and
+`Bing Webmaster Tools <https://www.bing.com/webmasters>`_, to help you analyze and improve your
+page ranking. To use these services, you must prove that you are the owner of your domain name. One
+way to verify the ownership of your domain name is by adding a DNS record. You can do this for
+:ref:`domain names registered with Odoo <domain-name/odoo-manage>` and for domain names managed by
+other providers.
+
+.. seealso::
+   - :doc:`/applications/websites/website/pages/seo`
+   - `Google Search Console Help - Verify your site ownership <https://support.google.com/webmasters/answer/9008080>`_
+   - `Bing Webmaster Tools - Add and Verify site <https://www.bing.com/webmasters/help/add-and-verify-site-12184f8b>`_
+
+.. _domain-name/odoo-register:
+
+Register a free domain name with Odoo
+=====================================
+
+You can register a domain name for your Odoo Online database directly from Odoo Website or your
+database manager.
+
+.. important::
+   - Your domain name is **free for one year** if you register it with Odoo!
+   - The domain name is registered with `Gandi <https://www.gandi.net/>`_, the domain name
+     registrar.
+   - You are the owner of the domain name and can use it for other purposes.
+   - Odoo manages payment and technical support for you.
+   - This offer doesn't include any mailbox. However, you can :ref:`configure your MX records
+     <domain-name/odoo-manage>` to use your own email server or solution such as Google Workspace.
+
+To do so, go to :menuselection:`Website --> Domain Name`. Alternatively, open your `database manager
+<https://www.odoo.com/my/databases>`_, click on the :guilabel:`settings` button next to your
+database, then on :guilabel:`Domain names`.
+
+.. image:: domain_names/register-menu.png
+   :align: center
+   :alt: Clicking on Domain Names from an Odoo website
+
+Search for the domain name of your choice to check its availability, then select the one you want to
+register for your website.
+
+.. image:: domain_names/register-search.png
+   :align: center
+   :alt: The search of the domain name example.com shows which associated domains are available.
+
+Next, fill in the form with your information to become the domain name owner.
+
+Your domain name is directly linked to your database, but you still have to :ref:`map your domain
+name with your website <domain-name/website-map>`.
+
+.. note::
+   - Free domain names are also available for free Odoo Online databases (if you installed one app
+     only, for example). In this case, Odoo reviews your request and your website to avoid abuse.
+     This process may take up to three days.
+   - This is not available for Odoo.sh databases yet.
+
+.. _domain-name/odoo-manage:
+
+Manage your domain name registered with Odoo
+--------------------------------------------
+
+To manage the DNS records of your domain name registered with Odoo or to visualize the contacts
+associated with it, open your `database manager <https://www.odoo.com/my/databases>`_, click on the
+:guilabel:`settings` button next to your database, on :guilabel:`Domain names`, and then on
+:guilabel:`Contacts` or :guilabel:`DNS`.
+
+.. image:: domain_names/manage.png
+   :align: center
+   :alt: Management of the domain names linked to an Odoo database
+
+.. note::
+   Please `submit a support ticket <https://www.odoo.com/help>`_ if you need further assistance to
+   manage your domain name.
+
+.. _domain-name/existing:
+
+Configure your existing domain name
+===================================
+
+If you already own a domain name, you can use it to point to your website.
+
+To avoid any issue with the :ref:`SSL certificate validation <domain-name/ssl>`, we highly recommend
+that you proceed with the following actions in this order:
+
+#. :ref:`Add a CNAME record <domain-name/cname>` on your domain name's DNS zone.
+#. :ref:`Map your domain name with your Odoo database <domain-name/db-map>`.
+#. :ref:`Map your domain name with your Odoo website <domain-name/website-map>`.
+
+.. _domain-name/cname:
+
+Add a CNAME record
+------------------
+
+A **CNAME record** is a type of DNS record that points to the domain of another website rather than
+directly to an IP address.
+
+You need a CNAME record that points to your Odoo database. The requirements are detailed in your
+database manager.
+
+.. tabs::
+
+   .. group-tab:: Odoo Online
+
+      The target address is the current address of your database, as defined at its creation (e.g.,
+      ``example.odoo.com``)
+
+   .. group-tab:: Odoo.sh
+
+      Your project's main address is defined in :menuselection:`Settings --> Project Name`.
+
+      If you want to target a specific branch (production, staging or development), go to
+      :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, and click on
+      :guilabel:`How to set up my domain?`. A message indicates which address your CNAME record
+      should target.
+
+#. Open your domain name's manager dashboard.
+#. Open the **DNS zone** management page for the domain name you want to configure.
+#. Create a **CNAME record** pointing to the address of your database.
+
+While Odoo suggests creating a CNAME record for your ``www.`` subdomain (``www.example.com``), you
+can of course use any domain name of your choice, with any subdomain (e.g.,
+``anything.example.com``).
+
+.. example::
+   You own the domain name ``example.com``, and you have an Odoo Online database at the address
+   ``example.odoo.com``. You want to access your Odoo database primarily with the domain
+   ``www.example.com`` but also with the :ref:`naked domain <domain-name/naked-domain>`
+   ``example.com``.
+
+   To do so, you create a CNAME record for the ``www`` subdomain, with ``example.odoo.com`` as the
+   target. The DNS zone manager generates the following rule and adds it to your DNS zone: ``www IN
+   CNAME example.odoo.com.``
+
+   You also create a redirection from ``example.com`` to ``wwww.example.com``.
+
+   Your new DNS records are propagated to all DNS servers.
+
+.. note::
+   Here are some specific guidelines to create a CNAME record:
+
+   - `GoDaddy <https://www.godaddy.com/help/add-a-cname-record-19236>`_
+   - `Namecheap <https://www.namecheap.com/support/knowledgebase/article.aspx/9646/2237/how-to-create-a-cname-record-for-your-domain>`_
+   - `OVH <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/#add-a-new-dns-record>`_
+   - `CloudFlare <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_
+   - `Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_
+
+.. _domain-name/naked-domain:
+
+Naked domain
+~~~~~~~~~~~~
+
+A **naked domain** is a domain name that doesn't have any subdomain at the beginning of the address
+(e.g., ``odoo.com`` instead of ``www.odoo.com``).
+
+You may want your naked domain to redirect to your website as some visitors may not type the full
+domain name to access your website.
+
+#. Open your domain name's manager dashboard.
+#. Create a **redirection** from the naked domain (``example.com``) to your main domain name
+   (``www.example.com``).
+
+.. note::
+   Depending on your domain name registrar, this redirection may be already pre-configured.
+
+.. _domain-name/db-map:
+
+Map your domain name with your Odoo database
+--------------------------------------------
+
+.. tabs::
+
+   .. group-tab:: Odoo Online
+
+      Open your `database manager <https://www.odoo.com/my/databases>`_, click on the
+      :guilabel:`settings` button next to your database, on :guilabel:`Domain names`, and then on
+      :guilabel:`Use my own domain` at the bottom of the right column.
+
+      Type the domain name you want to add to this database, then click on :guilabel:`Verify` to
+      check if the CNAME record is correctly configured. Once done, click on :guilabel:`I confirm,
+      it's done`.
+
+      .. image:: domain_names/online-map.png
+         :align: center
+         :alt: Verification of the CNAME records of a domain name before mapping it with a database
+
+   .. group-tab:: Odoo.sh
+
+      Go to :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, type
+      the domain name you want to add to this database, then click on :guilabel:`Add domain`.
+
+      .. image:: domain_names/odoo-sh-map.png
+         :align: center
+         :alt: Mapping a domain name with an Odoo.sh branch
+
+      .. seealso::
+         - :ref:`Odoo.sh branches: settings tab <odoosh-gettingstarted-branches-tabs-settings>`
+
+.. warning::
+   Make sure to :ref:`add a CNAME record <domain-name/cname>` to your domain name's DNS **before**
+   mapping your domain name with your Odoo database.
+
+   Failing to do so may impede the validation of the :ref:`SSL certificate <domain-name/ssl>` and
+   would result in a *certificate name mismatch* error. This is often displayed by web browsers as a
+   warning such as *"Your connection is not private"*.
+
+   If this is the case and you have added the domain name to your database's settings less than five
+   days ago, wait 24 hours as the validation may still happen. Otherwise, please `submit a support
+   ticket <https://www.odoo.com/help>`_ including screenshots of your CNAME records.
+
+.. _domain-name/ssl:
+
+SSL encryption (HTTPS protocol)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**SSL encryption** is an encryption-based Internet security protocol. It allows your visitors to
+navigate your website through a secure connection, which appears as an ``https://`` protocol at the
+beginning of your web address, rather than a non-secure ``http://`` protocol.
+
+Odoo generates a separate SSL certificate for each domain :ref:`mapped in the database manager
+<domain-name/db-map>`, using integration with `Let's Encrypt Certificate Authority and ACME protocol
+<https://letsencrypt.org/how-it-works/>`_.
+
+.. note::
+   - The certificate generation may take up to 24h.
+   - Several attempts to validate your certificate are made during the five days following the
+     moment you add your domain name in your database's settings.
+   - If you already use another service, you can keep using it or simply change for Odoo.
+
+.. _domain-name/web-base-url:
+
+Web base URL of a database
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. note::
+   If you have Odoo Website, you can disregard this part and directly :ref:`map your domain name
+   with your website <domain-name/website-map>`.
+
+The **web base URL** of a database, or **root URL** affects your main website address and all the
+links sent to your customers (e.g., quotations, portal links, etc.).
+
+To configure it, access your Odoo database with your custom address, then log in as an administrator
+of your database (any user in the *Settings* group) from the login screen.
+
+.. warning::
+   Connecting to your database with the original Odoo subdomain address (e.g., ``example.odoo.com``
+   also updates the web base URL of your database. See below to prevent these automatic updates.
+
+Alternatively, you can do it manually. To do so, activate the :ref:`developer mode
+<developer-mode>`, then go to :menuselection:`Settings --> Technical --> System Parameters`.
+
+Find the key called ``web.base.url`` (or create it if it does not exist) and enter the full address
+of your website as value, such as ``https://www.example.com``.
+
+.. note::
+   The URL must include the protocol ``https://`` (or ``http://``) and must not end with a slash
+   (``/``).
+
+To prevent the automatic update of the web base URL when an administrator logs in the database, you
+can create the following System Parameter:
+
+- key: ``web.base.url.freeze``
+- value: ``True``
+
+.. _domain-name/website-map:
+
+Map your domain name with your website
+======================================
+
+Mapping your domain name to your website isn't the same as mapping it with your database:
+
+- It defines your domain name as the main one for your website, helping search engines to index your
+  website properly.
+- It defines your domain name as the base URL for your database, including the portal links sent by
+  email to your customers.
+- If you have multiple websites, it maps your domain name with the appropriate website.
+
+Go to :menuselection:`Website --> Configuration --> Settings --> Website Info`. If you have multiple
+websites, select the one you want to configure.
+
+In the :guilabel:`Domain` field, fill in the web address of your website (e.g.,
+``https://www.example.com``) and click on :guilabel:`Save`.
+
+.. image:: domain_names/website-settings.png
+   :align: center
+   :alt: Configuring https://www.example.com as the Domain of the website
+
+.. warning::
+   Mapping your domain name with your Odoo website prevents Google from indexing both your custom
+   domain name ``www.example.com`` and your original odoo database address ``example.odoo.com``.
+
+   If both addresses are already indexed, it may take some time before Google removes the indexation
+   of the second address. You may also try using the `Google Search Console
+   <https://search.google.com/search-console>`_ to fix this.
+
+.. note::
+   If you have multiple websites and companies on your database, make sure that you select the
+   right :guilabel:`Company` in the website settings, next to the :guilabel:`Domain` settings. Doing
+   so indicates Odoo which URL to use as the :ref:`base URL <domain-name/web-base-url>` according to
+   the company in use.
+
+.. seealso::
+  - :doc:`/applications/general/email_communication/email_servers`

content/administration/maintain/enterprise.rst

@@ -0,0 +1,106 @@
+
+.. _setup/enterprise:
+
+===================================
+Switch from Community to Enterprise
+===================================
+
+Depending on your current installation, there are multiple ways to upgrade
+your community version.
+In any case the basic guidelines are:
+
+* Backup your community database
+
+  .. image:: enterprise/db_manager.png
+    :class: img-fluid
+
+* Shutdown your server
+
+* Install the web_enterprise module
+
+* Restart your server
+
+* Enter your Odoo Enterprise Subscription code
+
+.. image:: enterprise/enterprise_code.png
+  :class: img-fluid
+
+On Linux, using an installer
+============================
+
+* Backup your community database
+
+* Stop the odoo service
+
+  .. code-block:: console
+
+    $ sudo service odoo stop
+
+* Install the enterprise .deb (it should install over the community package)
+
+  .. code-block:: console
+
+    $ sudo dpkg -i <path_to_enterprise_deb>
+
+* Update your database to the enterprise packages using
+
+  .. code-block:: console
+
+    $ python3 /usr/bin/odoo-bin -d <database_name> -i web_enterprise --stop-after-init
+
+* You should be able to connect to your Odoo Enterprise instance using your usual mean of identification.
+  You can then link your database with your Odoo Enterprise Subscription by entering the code you received
+  by e-mail in the form input
+
+
+On Linux, using the source code
+===============================
+
+There are many ways to launch your server when using sources, and you probably
+have your own favourite. You may need to adapt sections to your usual workflow.
+
+* Shutdown your server
+* Backup your community database
+* Update the ``--addons-path`` parameter of your launch command (see :ref:`setup/install/source`)
+* Install the web_enterprise module by using
+
+  .. code-block:: console
+
+    $ -d <database_name> -i web_enterprise --stop-after-init
+
+  Depending on the size of your database, this may take some time.
+
+* Restart your server with the updated addons path of point 3.
+  You should be able to connect to your instance. You can then link your database with your
+  Odoo Enterprise Subscription by entering the code you received by e-mail in the form input
+
+On Windows
+==========
+
+* Backup your community database
+
+* Uninstall Odoo Community (using the Uninstall executable in the installation folder) -
+  PostgreSQL will remain installed
+
+  .. image:: enterprise/windows_uninstall.png
+    :class: img-fluid
+
+* Launch the Odoo Enterprise Installer and follow the steps normally. When choosing
+  the installation path, you can set the folder of the Community installation
+  (this folder still contains the PostgreSQL installation).
+  Uncheck ``Start Odoo`` at the end of the installation
+
+  .. image:: enterprise/windows_setup.png
+   :class: img-fluid
+
+* Using a command window, update your Odoo Database using this command (from the Odoo
+  installation path, in the server subfolder)
+
+  .. code-block:: console
+
+    $ ..\python\python.exe odoo-bin -d <database_name> -i web_enterprise --stop-after-init
+
+* No need to manually launch the server, the service is running.
+  You should be able to connect to your Odoo Enterprise instance using your usual
+  mean of identification. You can then link your database with your Odoo Enterprise
+  Subscription by entering the code you received by e-mail in the form input

content/administration/maintain/google_oauth.rst

@@ -12,7 +12,7 @@ email address or an address created by a custom domain.
    <https://support.google.com/cloud/answer/6158849>`_ on setting up OAuth.
 
 .. seealso::
-   - :doc:`/applications/general/users/google`
+   - :doc:`/applications/general/auth/google`
    - :doc:`/applications/productivity/calendar/google`
 
 Setup in Google

content/administration/maintain/hosting_changes.rst

@@ -0,0 +1,87 @@
+
+.. _db_management/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.
+
+From on-premises to Odoo Online
+===============================
+
+1. Create a :ref:`duplicate <duplicate_premise>` of your database: in this duplicate, uninstall all the **non-standard apps**.
+2. Grab a "dump with filestore" of your database by using the Database Manager.
+3. **If you have time constraints, contact us earlier to schedule the transfer.**
+4. `Create a support ticket <https://www.odoo.com/help>`_ and attach the dump (if the file is too large, use any file transfer service and attach the link to your ticket). Also include your subscription number and the URL you want to use for your database (e.g.: my-company.odoo.com).
+5. We will make sure your database is compatible and upload it to our cloud. In case of technical issues, we will get in touch with you.
+6. It's done!
+
+.. important::
+   - Odoo Online is not compatible with **non-standard apps**.
+   - The database you are moving to Odoo Online must be in a :doc:`supported version
+     <supported_versions>`.
+
+From on-premises to Odoo.sh
+===========================
+
+1. Follow the :ref:`Import your database section of the Odoo.sh documentation <odoo_sh_import_your_database>`.
+2. ...and voilà!
+
+From Odoo Online to on-premises
+===============================
+
+1. Log into `your Odoo Online user portal <https://accounts.odoo.com/my/databases/manage>`_ and look for the version number of your database.
+2. If your database does not run a :ref:`major version <supported_versions>` of Odoo, you cannot host it on-premises yet, you have to upgrade it first to a new major version. (*e.g.: If your database runs Odoo 12.3 which is not a major version, you have to upgrade it first to Odoo 13.0 or 14.0.*)
+3. Download a backup of your database by clicking on the "Gear" icon next to your database name then :menuselection:`Download` (if the download fails due to your backup file being too large, contact `our support <https://www.odoo.com/help>`_)
+4. Restore it from the database manager on your local server.
+
+From Odoo Online to Odoo.sh
+===========================
+
+1. Log into `your Odoo Online user portal <https://accounts.odoo.com/my/databases/manage>`_ and look for the version number of your database.
+2. If your database does not run a :ref:`major version <supported_versions>` of Odoo, you cannot host it on Odoo.sh yet, you have to upgrade it first to a new major version. (*e.g.: If your database runs Odoo 12.3 which is not a major version, you have to upgrade it first to Odoo 13.0 or 14.0.*)
+3. Download a backup of your database by clicking on the "Gear" icon next to your database name then :menuselection:`Download` (if the download fails due to your backup file being too large, contact `our support <https://www.odoo.com/help>`_)
+4. Follow the :ref:`Import your database section of the Odoo.sh documentation <odoo_sh_import_your_database>`.
+
+From Odoo.sh to Odoo Online
+===========================
+
+#. Uninstall all the **non-standard apps**.
+#. `Create a support ticket <https://www.odoo.com/help>`_ and include the following:
+
+   - Your subscription number
+   - The URL you want to use for your database (e.g., `example.odoo.com`)
+   - Which branch you want to migrate
+   - In which region you want to be hosted:
+
+     - Americas
+     - Europe
+     - Asia
+
+   - Which user(s) will be the administrator(s)
+   - When (and in which timezone) you want the database to be up and running
+
+#. We will make sure your database is compatible and upload it to our cloud. In case of technical
+   issues, we will get in touch with you.
+#. All done!
+
+.. important::
+   - Odoo Online is not compatible with **non-standard apps**.
+   - Make sure to uninstall all the **non-standard apps** in a staging build before doing it in your
+     production build.
+
+.. note::
+   - Make sure you select the **region** that is closest to your users to reduce latency.
+   - The future **administrator(s)** must have an odoo.com account.
+   - The specific **date and time** at which you want the database to be up and running are mainly
+     helpful to organize the switch from the odoo.sh server to the Odoo Online servers.
+   - Databases are **not reachable** during their migration.
+   - **If you have time constraints, contact us earlier to schedule the transfer**.
+
+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/mailjet_api.rst

@@ -210,8 +210,9 @@ Connection`.
 
    For more information see :ref:`Using a default email address <email_communication/default>`.
 
-   The :guilabel:`System Parameters` can be accessed by activating the :ref:`developer mode
-   <developer-mode>`.
+   The :guilabel:`System Parameters` can be accessed by activating
+   :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical
+   --> Parameters --> System Parameters` menu.
 
 Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass
 mailing or transactional emails!

content/administration/maintain/odoo_online.rst

@@ -0,0 +1,134 @@
+===============================
+Odoo Online database management
+===============================
+
+To manage a database, go to the `database manager <https://www.odoo.com/my/databases>`_ and sign in
+as the database administrator.
+
+All the main database management options are available by clicking the database name, except the
+upgrade option, which can be accessed by clicking the **arrow in a circle** icon next to the
+database name. It is only displayed if an upgrade is available.
+
+.. image:: odoo_online/database-manager.png
+   :alt: Accessing the database management options
+
+- :ref:`odoo_online/upgrade`
+- :ref:`odoo_online/duplicate`
+- :ref:`odoo_online/rename`
+- :ref:`odoo_online/download`
+- :ref:`odoo_online/domains`
+- :ref:`odoo_online/tags`
+- :ref:`odoo_online/delete`
+- :ref:`odoo_online/contact-support`
+- :ref:`odoo_online/users`
+
+.. _odoo_online/upgrade:
+
+Upgrade
+=======
+
+Trigger a database upgrade.
+
+.. seealso::
+   For more information about the upgrade process, check out the :doc:`Odoo Online upgrade
+   documentation <../upgrade/odoo_online>`.
+
+.. _odoo_online/duplicate:
+
+Duplicate
+=========
+
+Create an exact copy of the database, which can be used to perform testing without compromising
+daily operations.
+
+.. important::
+   - By checking :guilabel:`For testing purposes`, all external actions (emails, payments, delivery
+     orders, etc.) are disabled by default on the duplicated database.
+   - Duplicated databases expire automatically after 15 days.
+
+.. _odoo_online/rename:
+
+Rename
+======
+
+Rename the database and its URL.
+
+.. _odoo_online/download:
+
+Download
+========
+
+Download a ZIP file containing a backup of the database.
+
+.. note::
+   Databases are backed up daily as per the `Odoo Cloud Hosting SLA
+   <https://www.odoo.com/cloud-sla>`_.
+
+.. _odoo_online/domains:
+
+Domain names
+============
+
+Use a custom :doc:`domain name <domain_names>` to access the database via another URL.
+
+.. tip::
+   You can :ref:`register a domain name for free <domain-name/odoo-register>`.
+
+.. _odoo_online/tags:
+
+Tags
+====
+
+Add tags to easily identify and sort your databases.
+
+.. tip::
+   You can search for tags in the search bar.
+
+.. _odoo_online/delete:
+
+Delete
+======
+
+Delete a database instantly.
+
+.. danger::
+   Deleting a database means that all data is permanently lost. The deletion is instant and applies
+   to all users. It is recommended to create a backup of the database before deleting it.
+
+Carefully read the warning message and only proceed if the implications of deleting a database are
+fully understood.
+
+.. image:: odoo_online/delete.png
+   :alt: The warning message displayed before deleting a database
+
+.. note::
+   - Only an administrator can delete a database.
+   - The database name is immediately made available to anyone.
+   - Deleting a database if it has expired or is linked to a subscription is impossible. In that
+     case, contact `Odoo Support <https://www.odoo.com/help>`_.
+
+.. _odoo_online/contact-support:
+
+Contact us
+==========
+
+Access the `Odoo.com support page <https://www.odoo.com/help>`_ with the database's details already
+pre-filled.
+
+.. _odoo_online/users:
+
+Invite / remove users
+=====================
+
+To invite users, fill out the new user's email address and click :guilabel:`Invite`. To add multiple
+users, click :guilabel:`Add more users`.
+
+.. image:: odoo_online/invite-users.png
+   :alt: Inviting a user on a database
+
+To remove users, select them and click :guilabel:`Remove`.
+
+.. seealso::
+   - :doc:`../../applications/general/users/manage_users`
+   - :doc:`../../applications/general/users/delete_account`
+

content/administration/maintain/on_premise.rst

@@ -0,0 +1,168 @@
+==============================
+On-premise database management
+==============================
+
+Register a database
+===================
+
+To register your database, you just need to enter your Subscription Code in the
+banner in the App Switcher. Make sure you do not add extra spaces before or after
+your subscription code. If the registration is successful, it will turn green and
+will provide you with the Expiration Date of your freshly-registered database. You
+can check this Expiration Date in the About menu (Odoo 9) or in the Settings Dashboard
+(Odoo 10).
+
+Registration Error Message
+--------------------------
+
+If you are unable to register your database, you will likely encounter this
+message:
+
+.. 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
+
+Solutions
+~~~~~~~~~
+
+* Do you have a valid Enterprise subscription?
+
+  * Check if your subscription details get the tag "In Progress" on
+    your `Odoo Account
+    <https://accounts.odoo.com/my/subscription>`__ or with your Account Manager
+
+* Have you already linked a database with your subscription reference?
+
+  * You can link only one database per subscription.
+    (Need a test or a development database? `Find a partner
+    <https://www.odoo.com/partners>`__)
+
+  * You can unlink the old database yourself on your `Odoo Contract
+    <https://accounts.odoo.com/my/subscription>`__ with the button "Unlink database"
+
+    .. 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:: on_premise/unlink_confirm_enterprise_edition.png
+       :align: center
+
+* Do you have the updated version of Odoo 9?
+
+  * From July 2016 onward, Odoo 9 now automatically change the uuid of a
+    duplicated database; a manual operation is no longer required.
+
+  * If it's not the case, you may have multiple databases sharing the same
+    UUID. Please check on your `Odoo Contract
+    <https://accounts.odoo.com/my/subscription>`__, a short message will appear
+    specifying which database is problematic:
+
+    .. image:: on_premise/unlink_db_name_collision.png
+       :align: center
+
+    In this case, you need to change the UUID on your test databases to solve this
+    issue. You will find more information about this in :ref:`this section <duplicate_premise>`.
+
+    For your information, we identify database with UUID. Therefore, each database
+    should have a distinct UUID to ensure that registration and invoicing proceed
+    effortlessly for your and for us.
+
+* Check your network and firewall settings
+
+  * The Update notification must be able to reach Odoo's subscription
+    validation servers. In other words, make sure that the Odoo server is able
+    to open outgoing connections towards:
+
+      * services.odoo.com on port 443 (or 80)
+      * services.openerp.com on port 443 (or 80) for older deployments
+
+  * Once you activated your database, you must keep these ports open, as the
+    Update notification runs once a week.
+
+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:: on_premise/add_more_users.png
+   :align: center
+   :alt: This database will expire in X days, you have more users than your subscription allows
+
+
+When the message appears you have 30 days before the expiration.
+The countdown is updated everyday.
+
+Solutions
+~~~~~~~~~
+
+- **Add more users** on your subscription: follow the link and Validate
+  the upsell quotation and pay for the extra users.
+- **Deactivate users** as explained in this `documentation <documentation.html#deactivating-users>`_
+  and **Reject** the upsell quotation.
+
+Once your database has the correct number of users, the expiration message
+will disappear automatically after a few days, when the next verification occurs.
+We understand that it can be a bit frightening to see the countdown,
+so you can :ref:`force an Update Notification <force_ping>`  to make the message disappear
+right away.
+
+Database expired error message
+------------------------------
+
+If your database reaches its expiration date before your renew your subscription,
+you will encounter this message:
+
+.. image:: on_premise/database_expired.png
+   :align: center
+   :alt: This database has expired.
+
+This **blocking** message appears after a non-blocking message that lasts 30 days.
+If you fail to take action before the end of the countdown, the database is expired.
+
+Solutions
+~~~~~~~~~
+
+* Renew your subscription: follow the link and renew your subscription - note that
+    if you wish to pay by Wire Transfer, your subscription will effectively be renewed
+    only when the payment arrives, which can take a few days. Credit card payments are
+    processed immediately.
+* Contact our `Support <https://www.odoo.com/help>`__
+
+None of those solutions worked for you? Please contact our
+`Support <https://www.odoo.com/help>`__
+
+.. _force_ping:
+
+.. _duplicate_premise:
+
+Duplicate a database
+====================
+
+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:: on_premise/db_manager.gif
+   :align: center
+
+When you duplicate a local database, it is **strongly** advised to change
+the duplicated database's uuid (Unniversally Unique Identifier), since this
+uuid is how your database identifies itself with our servers. Having two
+databases with the same uuid could result in invoicing problems or registration
+problems down the line.
+
+.. note::
+   From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a
+   manual operation is no longer required.
+
+The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical -->
+System Parameters`, we advise you to use a `uuid generator <https://www.uuidtools.com>`_ or to
+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:: on_premise/db_uuid.png
+   :align: center

content/administration/maintain/supported_versions.rst

@@ -0,0 +1,182 @@
+
+.. _supported_versions:
+
+==================
+Supported versions
+==================
+
+Odoo provides support and bug fixing **for the 3 last major versions** of Odoo.
+
+.. note::
+   Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online
+   <odoo_online>` hosting every two months. Odoo Online users can then benefit from the latest
+   features of Odoo.
+
+   - Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` them regularly.
+   - Online versions are *not* released for Odoo.sh and On-Premise installations.
+   - Online versions are listed below as *SaaS*.
+
+What's the support status of my Odoo?
+=====================================
+
+This matrix shows the support status of every version.
+
+**Major releases are in bold type.**
+
+.. list-table::
+   :header-rows: 1
+   :widths: auto
+
+   * -
+     - Odoo Online
+     - Odoo.sh
+     - On-Premise
+     - Release date
+     - End of support
+   * - Odoo saas~16.3
+     - |green|
+     - N/A
+     - N/A
+     - June 2023
+     - September 2023 (planned)
+   * - Odoo saas~16.2
+     - |green|
+     - N/A
+     - N/A
+     - March 2023
+     - July 2023 (planned)
+   * - Odoo saas~16.1
+     - |red|
+     - N/A
+     - N/A
+     - February 2023
+     - April 2023
+   * - **Odoo 16.0**
+     - |green|
+     - |green|
+     - |green|
+     - October 2022
+     - October 2025 (planned)
+   * - Odoo saas~15.2
+     - |red|
+     - N/A
+     - N/A
+     - March 2022
+     - January 2023
+   * - Odoo saas~15.1
+     - |red|
+     - N/A
+     - N/A
+     - February 2022
+     - July 2022
+   * - **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**
+     - |red|
+     - |red|
+     - |red|
+     - October 2019
+     - October 2022
+   * - Odoo saas~12.3
+     - |red|
+     - N/A
+     - N/A
+     - August 2019
+     -
+   * - **Odoo 12.0**
+     - |red|
+     - |red|
+     - |red|
+     - October 2018
+     - October 2021
+   * - Odoo saas~11.3
+     - |red|
+     - N/A
+     - N/A
+     - April 2018
+     -
+   * - **Odoo 11.0**
+     - |red|
+     - |red|
+     - |red|
+     - October 2017
+     - October 2020
+   * - Odoo 10.saas~15
+     - |red|
+     - N/A
+     - N/A
+     - March 2017
+     -
+   * - Odoo 10.saas~14
+     - |red|
+     - N/A
+     - N/A
+     - January 2017
+     -
+   * - **Odoo 10.0**
+     - |red|
+     - |red|
+     - |red|
+     - October 2016
+     - October 2019
+   * - Odoo 9.saas~11
+     - |red|
+     - N/A
+     - N/A
+     - May 2016
+     -
+   * - **Odoo 9.0**
+     - |red|
+     - N/A
+     - |red|
+     - October 2015
+     - October 2018
+   * - Odoo 8.saas~6
+     - |red|
+     - N/A
+     - N/A
+     - February 2015
+     -
+   * - **Odoo 8.0**
+     - |red|
+     - N/A
+     - |red|
+     - September 2014
+     - October 2017
+
+.. note::
+
+    |green| Supported version
+
+    |red| End-of-support
+
+    N/A Never released for this platform
+
+    🏁 Future version, not released yet
+
+.. |green| raw:: html
+
+   <span class="text-success" style="font-size: 32px; line-height: 0.5">●</span>
+
+.. |red| raw:: html
+
+   <span class="text-danger" style="font-size: 32px; line-height: 0.5">●</span>
+
+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

@@ -46,7 +46,7 @@ Updating Odoo is accomplished by simply reinstalling the latest version of your
 Edition on top of your current installation. This will preserve your data without any alteration,
 as long as you do not uninstall PostgreSQL (the database engine that comes with Odoo).
 
-The main reference for updating is logically our :doc:`installation guide <../on_premise>`,
+The main reference for updating is logically our :ref:`installation guide <setup/install>`,
 which explains the common installation methods.
 
 Updating is also most appropriately accomplished by the person who deployed Odoo initially,
@@ -110,7 +110,7 @@ to replace the installation directory with a newer version. First download the l
 from Odoo.com. They are updated daily and include the latest security fixes (see step #1)
 After downloading the package, extract it to a temporary location on your server.
 
-You will get a folder labeled with the version of the source code, for example "odoo-13.0+e.20190719",
+You will get a folder labelled with the version of the source code, for example "odoo-13.0+e.20190719",
 that contains a folder "odoo.egg-info" and the actual source code folder named "odoo" (for Odoo 10
 and later) or "openerp" for older versions.
 You can ignore the odoo.egg-info folder. Locate the folder where your current installation is deployed,

content/administration/mobile.rst

@@ -1,67 +0,0 @@
-================
-Odoo mobile apps
-================
-
-Two kind of Odoo mobile app exist: the progressive web app (PWA) and store apps. Using the PWA is
-recommended.
-
-Progressive web app (PWA)
-=========================
-
-PWAs are web-based applications designed to function across different devices and platforms,
-leveraging web browsers to deliver user experiences similar to native apps.
-
-The Odoo PWA features include:
-
-- Quick access by adding the PWA to a device's home screen
-- Seamless and borderless navigation experience
-- Push notifications
-- SSO authentication
-
-To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an Odoo database. The
-instructions to install a PWA depend on the platform and browser used.
-
-.. tabs::
-
-   .. tab:: Android
-
-      **Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install app`, and tap
-      :guilabel:`Install`.
-
-      **Firefox**: open Firefox's menu (:guilabel:`⋮`), select :guilabel:`Install`, and either touch
-      and hold the Odoo icon or tap :guilabel:`Add automatically`.
-
-      The PWA can also be installed with **Samsung Internet**, **Edge**, and **Opera**.
-
-   .. tab:: iOS
-
-      **Safari**: open the **Share** menu by tapping the square with an arrow pointing upwards icon,
-      select :guilabel:`Add to Home Screen`, edit the PWA details if desired, and tap
-      :guilabel:`Add`.
-
-      On iOS 16.4 and above, the PWA can also be installed with **Chrome**, **Firefox**, and
-      **Edge**.
-
-   .. tab:: Desktop
-
-      **Chrome** and **Edge**: click the installation icon at the right of the address bar and click
-      :guilabel:`Install`.
-
-.. seealso::
-   - `Google Chrome Help: Use progressive web apps
-     <https://support.google.com/chrome/answer/9658361>`_
-   - `MDN Web Docs: Installing and uninstalling web apps
-     <https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Installing>`_
-   - `Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge <https://support.microsoft.com/en-us/topic/install-manage-or-uninstall-apps-in-microsoft-edge-0c156575-a94a-45e4-a54f-3a84846f6113>`_
-
-Store apps
-==========
-
-The Odoo mobile apps are available for download on the `Google Play Store
-<https://play.google.com/store/apps/details?id=com.odoo.mobile>`_ and `Apple App Store
-<https://apps.apple.com/app/odoo/id1272543640>`_.
-
-.. important::
-   The iOS app cannot be updated and will be deprecated at some point in the future.
-
-While the store apps support multi-accounts, they are not compatible with SS0 authentication.

content/administration/neutralized_database.rst

@@ -1,36 +0,0 @@
-====================
-Neutralized database
-====================
-
-A neutralized database is a non-production database on which several parameters are deactivated.
-This enables one to carry out tests without the risk of launching specific automated processes that
-could impact production data (e.g., sending emails to customers). Live access is removed and
-turned into a testing environment.
-
-.. note::
-   **Any testing database created is a neutralized database:**
-
-   - testing backup databases
-   - duplicate databases
-   - for Odoo.sh: staging and development databases
-
-.. important::
-   A database can also be neutralized when upgrading, as it is vital to do some tests before
-   switching to a new version.
-
-Deactivated features
-====================
-
-Here is a non-exhaustive list of the deactivated features:
-
-- all planned actions (e.g., automatic invoicing of subscriptions, mass mailing, etc.)
-- outgoing emails
-- bank synchronization
-- payment providers
-- delivery methods
-- :abbr:`IAP (In-App Purchase)` tokens
-- website visibility (prevent search engines from indexing your site)
-
-.. note::
-   **A red banner at the top of the screen is displayed on the neutralized database so that it can
-   be seen immediately.**

content/administration/odoo_accounts.rst

@@ -1,80 +0,0 @@
-=================
-Odoo.com accounts
-=================
-
-This documentation is dedicated to edits made to an Odoo.com account. The following processes
-describe how to delete an Odoo.com account, and how to change the password on an Odoo.com account.
-
-Delete Odoo.com account
-=======================
-
-To delete an Odoo.com account, start by clicking the profile icon in the upper-right corner
-(represented by the username and icon) to reveal a drop-down menu. From the drop-down menu, select
-:guilabel:`My Odoo.com account`, which reveals the user portal.
-
-From the user portal, the delete option can be accessed by going to :menuselection:`My Account -->
-Edit Security Settings --> Delete Account`. It can also be accessed by going to
-`https://www.odoo.com/my/home <https://www.odoo.com/my/home>`_.
-
-.. danger::
-   Deleting an Odoo account is irreversible. Be careful performing this action, as the Odoo.com
-   account is **not** retrievable once deleted.
-
-Upon clicking the :guilabel:`Delete Account` button, a pop-up window appears, requesting
-confirmation for the account deletion.
-
-.. image:: odoo_account/delete-account.png
-   :align: center
-   :alt: Clicking on the Delete Account button will populate a window verifying the change.
-
-To confirm the deletion, enter the :guilabel:`Password` and the :guilabel:`Login` for the account
-being deleted. Then, click the :guilabel:`Delete Account` button to confirm the deletion.
-
-.. _odoocom/change_password:
-
-Odoo.com account password change
-================================
-
-To change an Odoo.com account password, first login into the Odoo.com user account from the Odoo.com
-login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼
-(down arrow)` icon next to the profile icon. Then, select :guilabel:`My Account`, and a portal
-dashboard appears.
-
-To change the Odoo.com password, click on the :guilabel:`Edit Security Settings` link, below the
-:menuselection:`Account Security` section. Next, make the necessary changes by typing in the current
-:guilabel:`Password`, :guilabel:`New Password`, and verify the new password. Lastly, click on
-:guilabel:`Change Password` to complete the password change.
-
-.. note::
-   If a customer would like to change the login, contact Odoo support `here
-   <https://www.odoo.com/help>`_.
-
-.. note::
-   Passwords for Odoo.com users and portal users remain separate, even if the same email address is
-   used.
-
-Add two-factor authentication
-=============================
-
-To add two-factor authentication, login into the Odoo.com user account from the Odoo.com login page.
-After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down
-arrow)` icon next to the :guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal
-dashboard appears.
-
-If the user would like to turn on two-factor authentication (2FA) for Odoo.com access, click on the
-:guilabel:`Edit Security Settings` link below the :menuselection:`Account Security` section.
-
-Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA (two-factor
-authentication)`. Then, confirm the current password in the :guilabel:`Password` field. Next, click
-on :guilabel:`Confirm Password`. Following that, activate :abbr:`2FA (two-factor authentication)` in
-a :abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, etc.), by scanning the
-:guilabel:`QR code` or entering a :guilabel:`Verification Code`.
-
-Finally, click on :guilabel:`Enable two-factor authentication` to complete the setup.
-
-.. note::
-   Under :guilabel:`My Account` Odoo.com users can also access the following:
-
-   - :guilabel:`My Partner dashboard`
-   - :guilabel:`My In-App Services`
-   - :guilabel:`My Apps Dashboard`

content/administration/odoo_online.rst

@@ -1,151 +0,0 @@
-===========
-Odoo Online
-===========
-
-`Odoo Online <https://www.odoo.com/trial>`_ provides private databases which are fully managed and
-hosted by Odoo. It can be used for long-term production or to test Odoo thoroughly, including
-customizations that don't require code.
-
-.. note::
-   Odoo Online is incompatible with custom modules or the Odoo App Store.
-
-Odoo Online databases are accessed using any web browser and do not require a local installation.
-
-To quickly try out Odoo, shared `demo <https://demo.odoo.com>`_ instances are available. No
-registration is required, but each instance only lives for a few hours.
-
-Database management
-===================
-
-To manage a database, go to the `database manager <https://www.odoo.com/my/databases>`_ and sign in
-as the database administrator.
-
-All the main database management options are available by clicking the database name, except the
-upgrade option, which can be accessed by clicking the **arrow in a circle** icon next to the
-database name. It is only displayed if an upgrade is available.
-
-.. image:: odoo_online/database-manager.png
-   :alt: Accessing the database management options
-
-- :ref:`odoo_online/upgrade`
-- :ref:`odoo_online/duplicate`
-- :ref:`odoo_online/rename`
-- :ref:`odoo_online/download`
-- :ref:`odoo_online/domains`
-- :ref:`odoo_online/tags`
-- :ref:`odoo_online/delete`
-- :ref:`odoo_online/contact-support`
-- :ref:`odoo_online/users`
-
-.. _odoo_online/upgrade:
-
-Upgrade
-=======
-
-Trigger a database upgrade.
-
-.. seealso::
-   For more information about the upgrade process, check out the :ref:`Odoo Online upgrade
-   documentation <upgrade-request-test>`.
-
-.. _odoo_online/duplicate:
-
-Duplicate
-=========
-
-Create an exact copy of the database, which can be used to perform testing without compromising
-daily operations.
-
-.. important::
-   - By checking :guilabel:`For testing purposes`, all external actions (emails, payments, delivery
-     orders, etc.) are disabled by default on the duplicated database.
-   - Duplicated databases expire automatically after 15 days.
-   - A maximum of five duplicates can be made per database. Under extraordinary circumstances,
-     contact `support <https://www.odoo.com/help>`_ to raise the limit.
-
-.. _odoo_online/rename:
-
-Rename
-======
-
-Rename the database and its URL.
-
-.. _odoo_online/download:
-
-Download
-========
-
-Download a ZIP file containing a backup of the database.
-
-.. note::
-   Databases are backed up daily as per the `Odoo Cloud Hosting SLA
-   <https://www.odoo.com/cloud-sla>`_.
-
-.. _odoo_online/domains:
-
-Domain names
-============
-
-Use a custom :doc:`domain name </applications/websites/website/configuration/domain_names>` to
-access the database via another URL.
-
-.. tip::
-   You can :ref:`register a domain name for free <domain-name/register>`.
-
-.. _odoo_online/tags:
-
-Tags
-====
-
-Add tags to easily identify and sort your databases.
-
-.. tip::
-   You can search for tags in the search bar.
-
-.. _odoo_online/delete:
-
-Delete
-======
-
-Delete a database instantly.
-
-.. danger::
-   Deleting a database means that all data is permanently lost. The deletion is instant and applies
-   to all users. It is recommended to create a backup of the database before deleting it.
-
-Carefully read the warning message and only proceed if the implications of deleting a database are
-fully understood.
-
-.. image:: odoo_online/delete.png
-   :alt: The warning message displayed before deleting a database
-
-.. note::
-   - Only an administrator can delete a database.
-   - The database name is immediately made available to anyone.
-   - Deleting a database if it has expired or is linked to a subscription is impossible. In that
-     case, contact `Odoo Support <https://www.odoo.com/help>`_.
-
-.. _odoo_online/contact-support:
-
-Contact us
-==========
-
-Access the `Odoo.com support page <https://www.odoo.com/help>`_ with the database's details already
-pre-filled.
-
-.. _odoo_online/users:
-
-Invite / remove users
-=====================
-
-To invite users, fill out the new user's email address and click :guilabel:`Invite`. To add multiple
-users, click :guilabel:`Add more users`.
-
-.. image:: odoo_online/invite-users.png
-   :alt: Inviting a user on a database
-
-To remove users, select them and click :guilabel:`Remove`.
-
-.. seealso::
-   - :doc:`/applications/general/users`
-   - :doc:`odoo_accounts`

content/administration/odoo_sh/advanced/frequent_technical_questions.rst

@@ -29,32 +29,3 @@ We advise that:
 - Your scheduled actions should be
   `idempotent <https://stackoverflow.com/a/1077421/3332416>`_: they must not
   cause side-effects if they are started more often than expected.
-
-.. _ip-address-change:
-
-How can I automate tasks when an IP address change occurs?
-----------------------------------------------------------
-
-**Odoo.sh notifies project administrators of IP address changes.**
-Additionally, when the IP address of a production instance changes, an HTTP `GET` request is made
-to the path `/_odoo.sh/ip-change` with the new IP address included as a query string parameter
-(`new`), along with the previous IP address as an additional parameter (`old`).
-
-This mechanism allows custom actions to be applied in response to the IP address change
-(e.g., sending an email, contacting a firewall API, configuring database objects, etc.)
-
-For security reasons, the `/_odoo.sh/ip-change` route is accessible only internally by the platform
-itself and returns a `403` response if accessed through any other means.
-
-Here is a pseudo-implementation example:
-
-.. code-block:: python
-
-    class IPChangeController(http.Controller):
-
-        @http.route('/_odoo.sh/ip-change', auth='public')
-        def ip_change(self, old=None, new=None):
-            _logger.info("IP address changed from %s to %s", old, new)
-            # Then perform whatever action required for your use case, e.g., update an
-            # ir.config_parameter, send an email, contact an external firewall service's API, ...
-            return 'ok'

content/administration/odoo_sh/getting_started/branches.rst

@@ -99,7 +99,7 @@ disable the tests or allow specific tests to be run with custom tags in the :ref
 <odoosh-gettingstarted-branches-tabs-settings>`.
 
 Similar to staging branches, the emails are not sent but are intercepted by a mailcatcher and
-scheduled actions are not triggered as long as the database is not in use.
+scheduled actions are not triggered as often is the database is not in use.
 
 The databases created for development branches are meant to live around three days.
 After that, they can be automatically garbage collected to make room for new databases without prior notice.
@@ -295,7 +295,7 @@ Upgrade
 Available for production and staging branches for valid projects.
 
 .. seealso::
-    :doc:`Upgrade documentation <../../upgrade>`
+    :doc:`Upgrade - Odoo.sh <../../upgrade/odoo_sh>`
 
 .. _odoosh-gettingstarted-branches-tabs-settings:
 

content/administration/odoo_sh/getting_started/create.rst

@@ -91,7 +91,7 @@ Import your database
 ====================
 
 You can import your database in your Odoo.sh project as long as it is in a :doc:`supported version
-</administration/supported_versions>` of Odoo.
+</administration/maintain/supported_versions>` of Odoo.
 
 Push your modules in production
 -------------------------------
@@ -202,4 +202,4 @@ therefore removed, 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 :doc:`database registration documentation
-<../../on_premise>` for instructions.
+<../../maintain/on_premise>` for instructions.

content/administration/odoo_sh/getting_started/first_module.rst

@@ -85,7 +85,7 @@ From the Odoo.sh editor, in a terminal:
 
   $ odoo-bin scaffold my_module ~/src/user/
 
-Or, from your computer, if you have an :doc:`installation of Odoo <../../on_premise/source>`:
+Or, from your computer, if you have an :ref:`installation of Odoo <setup/install/source>`:
 
 .. code-block:: bash
 

content/administration/odoo_sh/getting_started/settings.rst

@@ -33,17 +33,17 @@ Manage the Github users who can access your project.
 .. image:: settings/interface-settings-collaborators.png
    :align: center
 
-There are three levels of users:
+There are two levels of users:
 
-- :guilabel:`Admin`: has access to all features of an Odoo.sh project.
+* Admin: has access to all features of Odoo.sh.
+* User: does not have access to the project settings nor to the production and staging databases.
 
-- :guilabel:`Tester`: has access to the *Staging* and *Development* databases and their tooling.
-  This role is for users conducting User Acceptance Tests. Testers can work with copies of
-  production data but cannot access the production database through the Odoo.sh tooling.
+The user group is meant for developers who can make modifications in your code but are not allowed
+to access the production data. Users of this group cannot connect to the production and staging
+databases using the *1-click connect* feature, but they can of course use their regular account on
+these databases if they have one, using their regular credentials.
 
-- :guilabel:`Developer`: has access only to the *Development* databases and their tooling. This
-  role is for developers who propose code modifications but are not allowed to access production
-  and staging databases through the Odoo.sh tooling.
+In addition, they cannot use the webshell nor have access to the server logs.
 
 .. list-table::
    :header-rows: 1
@@ -51,145 +51,83 @@ There are three levels of users:
 
    * -
      -
-     - Developer
-     - Tester
+     - User
      - Admin
    * - Development
      - History
      - |green|
      - |green|
-     - |green|
    * -
      - 1-click connect
      - |green|
      - |green|
-     - |green|
    * -
      - Logs
      - |green|
      - |green|
-     - |green|
    * -
      - Shell/SSH
      - |green|
      - |green|
-     - |green|
    * -
      - Mails
      - |green|
      - |green|
+   * -
+     - Upgrade
+     - |green|
      - |green|
    * -
      - Settings
      - |green|
      - |green|
-     - |green|
-   * - Staging
+   * - Production & Staging
      - History
      - |green|
      - |green|
-     - |green|
    * -
      - 1-click connect
      -
      - |green|
-     - |green|
    * -
      - Logs
      -
      - |green|
-     - |green|
    * -
      - Shell/SSH
      -
      - |green|
-     - |green|
    * -
      - Mails
      -
      - |green|
-     - |green|
    * -
      - Monitoring
      -
      - |green|
-     - |green|
    * -
      - Backups
      -
-     -
      - |green|
    * -
      - Upgrade
      -
      - |green|
-     - |green|
    * -
      - Settings
-     -
-     - |green|
-     - |green|
-   * - Production
-     - History
-     - |green|
-     - |green|
-     - |green|
-   * -
-     - 1-click connect
-     -
-     -
-     - |green|
-   * -
-     - Logs
-     -
-     -
-     - |green|
-   * -
-     - Shell/SSH
-     -
-     -
-     - |green|
-   * -
-     - Mails
-     -
-     -
-     - |green|
-   * -
-     - Monitoring
-     -
-     -
-     - |green|
-   * -
-     - Backups
-     -
-     -
-     - |green|
-   * -
-     - Upgrade
-     -
-     -
-     - |green|
-   * -
-     - Settings
-     -
-     -
+     - |green|\*
      - |green|
    * - Status
      -
      - |green|
      - |green|
-     - |green|
    * - Settings
-     -
      -
      -
      - |green|
 
-.. warning::
-   Those roles only apply to the usage of Odoo.sh. It is important to reflect the user roles
-   attribution within the repository on GitHub.  Please refer to the GitHub documentation section on
-   `Managing a branch protection rule <https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule>`_
-   for detailed guidance.
+.. note::
+    \* Only in staging branches
 
 .. |green| raw:: html
 
@@ -211,32 +149,15 @@ Allow public access to your development builds.
 .. image:: settings/interface-settings-public.png
    :align: center
 
-If activated, this option exposes the Builds page publicly, allowing visitors to view logs of development builds.
+If activated, this option exposes the Builds page publicly, allowing visitors to connect to your
+development builds.
+
+In addition, visitors have access to the logs, shell and mails of your development builds.
 
 Production and staging builds are excluded, visitors can only see their status.
 
 .. _odoosh-gettingstarted-settings-modules-installation:
 
-GitHub commit statuses
-======================
-
-This option enables Odoo.sh to push commit statuses to your GitHub repository when a build is
-created or updated. It requires a GitHub token with permissions to push commit statuses to the
-repository. Refer to `GitHub's documentation on personal access tokens <https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens>`_
-for instructions to create yours.
-
-.. note::
-    GitHub's **fine-grained personal tokens** have an expiration date and will be disabled if they
-    fail to update the commit status. You can replace the token at any time on Odoo.sh.
-
-The commit statuses pushed to GitHub can have the following contexts:
-
-- :guilabel:`ci/odoo.sh (dev)`: status of a development build
-- :guilabel:`ci/odoo.sh (staging)`: status of a staging build
-- :guilabel:`ci/odoo.sh (production)`: status of a production build
-- :guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page will push a test
-  status on the last commit of your repository
-
 Custom domains
 ==============
 

content/administration/on_premise.rst

@@ -1,123 +0,0 @@
-:show-content:
-
-==========
-On-premise
-==========
-
-Register a database
-===================
-
-To register your database, enter your subscription code in the banner in the app dashboard. If the
-registration is successful, the banner will turn green and display the database expiration date.
-
-.. tip::
-   The expiration date is also displayed at the bottom of the Settings page.
-
-.. _on-premise/duplicate:
-
-Duplicate a database
-====================
-
-Duplicate a database by accessing the database manager on your server
-(`<odoo-server>/web/database/manager`). Typically, you want to duplicate your production database
-into a neutralized testing database. It can be done by checking the neutralize box when prompted,
-which executes all :file:`neutralize.sql` scripts for every installed module.
-
-Common error messages and solutions
-===================================
-
-Registration error
-------------------
-
-In case of a registration error, the following message should be displayed.
-
-.. image:: on_premise/error-message-sub-code.png
-   :alt: Database registration error message
-
-To resolve the issue:
-
-- Check the **validity of your Odoo Enterprise subscription** by verifying if your subscription
-  details have the tag :guilabel:`In Progress` on your `Odoo Account
-  <https://accounts.odoo.com/my/subscription>`_ or contact your Account Manager.
-
-- Ensure that **no other database is linked** to the subscription code, as only one database can be
-  linked per subscription.
-
-  .. tip::
-     If a test or a development database is needed, you can :ref:`duplicate a database
-     <on-premise/duplicate>`.
-
-- Verify that **no databases share the same UUID** (Universally Unique Identifier) by opening your
-  `Odoo Contract <https://accounts.odoo.com/my/subscription>`_. If two or more databases share the
-  same UUID, their name will be displayed.
-
-  .. image:: on_premise/unlink-db-name-collision.png
-     :alt: Database UUID error message
-
-  If that is the case, manually change the database(s) UUID or `send a support ticket
-  <https://www.odoo.com/help>`_.
-
-- As the update notification must be able to reach Odoo's subscription validation servers, ensure
-  your **network and firewall settings** allow the Odoo server to open outgoing connections
-  towards:
-
-  - Odoo 18.0 and above: `services.odoo.com` on port `443` (or `80`)
-  - Odoo 17.0 and below: `services.openerp.com` on port `443` (or `80`)
-
-  These ports must be kept open even after registering a database, as the update notification runs
-  once a week.
-
-Too many users error
---------------------
-
-If you have more users in a local database than provisioned in your Odoo Enterprise subscription,
-the following message should be displayed.
-
-.. image:: on_premise/add-more-users.png
-   :alt: Too many users on a database error message
-
-When the message appears, you have 30 days to act before the database expires. The countdown is
-updated every day.
-
-To resolve the issue, either:
-
-- **Add more users** to your subscription by clicking the :guilabel:`Upgrade your subscription` link
-  displayed in the message to validate the upsell quotation and pay for the extra users.
-- :ref:`Deactivate users <users/deactivate>` and **reject** the upsell quotation.
-
-.. important::
-   If you are on a monthly subscription plan, the database will automatically update to reflect the
-   added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the
-   database. You can create the upsell quotation by clicking the banner to update the subscription
-   or `send a support ticket <https://www.odoo.com/help>`_ to resolve the issue.
-
-Once your database has the correct number of users, the expiration message disappears automatically
-after a few days, when the next verification occurs.
-
-Database expired error
-----------------------
-
-If your database expires before you renew your subscription, the following message should be
-displayed.
-
-.. image:: on_premise/database-expired.png
-   :alt: Database expired error message
-
-This message appears if you fail to act before the end of the 30-day countdown.
-
-To resolve the issue, either:
-
-- Click the :guilabel:`Renew your subscription` link displayed in the message and complete the
-  process. If you pay by wire transfer, your subscription will be renewed when the payment arrives
-  which can take a few days. Credit card payments are processed immediately.
-- `Send a support ticket <https://www.odoo.com/help>`_.
-
-.. toctree::
-
-   on_premise/packages
-   on_premise/source
-   on_premise/update
-   on_premise/deploy
-   on_premise/email_gateway
-   on_premise/geo_ip
-   on_premise/community_to_enterprise

content/administration/on_premise/community_to_enterprise.rst

@@ -1,106 +0,0 @@
-
-.. _setup/enterprise:
-
-===================================
-Switch from Community to Enterprise
-===================================
-
-Depending on your current installation, there are multiple ways to upgrade
-your community version.
-In any case the basic guidelines are:
-
-* Backup your community database
-
-  .. image:: community_to_enterprise/db_manager.png
-     :class: img-fluid
-
-* Shutdown your server
-
-* Install the web_enterprise module
-
-* Restart your server
-
-* Enter your Odoo Enterprise Subscription code
-
-.. image:: community_to_enterprise/enterprise_code.png
-   :class: img-fluid
-
-On Linux, using an installer
-============================
-
-* Backup your community database
-
-* Stop the odoo service
-
-  .. code-block:: console
-
-    $ sudo service odoo stop
-
-* Install the enterprise .deb (it should install over the community package)
-
-  .. code-block:: console
-
-    $ sudo dpkg -i <path_to_enterprise_deb>
-
-* Update your database to the enterprise packages using
-
-  .. code-block:: console
-
-    $ python3 /usr/bin/odoo-bin -d <database_name> -i web_enterprise --stop-after-init
-
-* You should be able to connect to your Odoo Enterprise instance using your usual mean of identification.
-  You can then link your database with your Odoo Enterprise Subscription by entering the code you received
-  by e-mail in the form input
-
-
-On Linux, using the source code
-===============================
-
-There are many ways to launch your server when using sources, and you probably
-have your own favourite. You may need to adapt sections to your usual workflow.
-
-* Shutdown your server
-* Backup your community database
-* Update the ``--addons-path`` parameter of your launch command (see :doc:`../on_premise/source`)
-* Install the web_enterprise module by using
-
-  .. code-block:: console
-
-    $ -d <database_name> -i web_enterprise --stop-after-init
-
-  Depending on the size of your database, this may take some time.
-
-* Restart your server with the updated addons path of point 3.
-  You should be able to connect to your instance. You can then link your database with your
-  Odoo Enterprise Subscription by entering the code you received by e-mail in the form input
-
-On Windows
-==========
-
-* Backup your community database
-
-* Uninstall Odoo Community (using the Uninstall executable in the installation folder) -
-  PostgreSQL will remain installed
-
-  .. image:: community_to_enterprise/windows_uninstall.png
-    :class: img-fluid
-
-* Launch the Odoo Enterprise Installer and follow the steps normally. When choosing
-  the installation path, you can set the folder of the Community installation
-  (this folder still contains the PostgreSQL installation).
-  Uncheck ``Start Odoo`` at the end of the installation
-
-  .. image:: community_to_enterprise/windows_setup.png
-     :class: img-fluid
-
-* Using a command window, update your Odoo Database using this command (from the Odoo
-  installation path, in the server subfolder)
-
-  .. code-block:: console
-
-    $ ..\python\python.exe odoo-bin -d <database_name> -i web_enterprise --stop-after-init
-
-* No need to manually launch the server, the service is running.
-  You should be able to connect to your Odoo Enterprise instance using your usual
-  mean of identification. You can then link your database with your Odoo Enterprise
-  Subscription by entering the code you received by e-mail in the form input

content/administration/on_premise/deploy.rst

@@ -1,930 +0,0 @@
-====================
-System configuration
-====================
-
-This document describes basic steps to set up Odoo in production or on an
-internet-facing server. It follows :doc:`installation <../on_premise>`, and is
-not generally necessary for a development systems that is not exposed on the
-internet.
-
-.. warning:: If you are setting up a public server, be sure to check our :ref:`security` recommendations!
-
-.. _db_filter:
-
-dbfilter
-========
-
-Odoo is a multi-tenant system: a single Odoo system may run and serve a number
-of database instances. It is also highly customizable, with customizations
-(starting from the modules being loaded) depending on the "current database".
-
-This is not an issue when working with the backend (web client) as a logged-in
-company user: the database can be selected when logging in, and customizations
-loaded afterwards.
-
-However it is an issue for non-logged users (portal, website) which aren't
-bound to a database: Odoo needs to know which database should be used to load
-the website page or perform the operation. If multi-tenancy is not used that is not an
-issue, there's only one database to use, but if there are multiple databases
-accessible Odoo needs a rule to know which one it should use.
-
-That is one of the purposes of :option:`--db-filter <odoo-bin --db-filter>`:
-it specifies how the database should be selected based on the hostname (domain)
-that is being requested. The value is a `regular expression`_, possibly
-including the dynamically injected hostname (``%h``) or the first subdomain
-(``%d``) through which the system is being accessed.
-
-For servers hosting multiple databases in production, especially if ``website``
-is used, dbfilter **must** be set, otherwise a number of features will not work
-correctly.
-
-Configuration samples
----------------------
-
-* Show only databases with names beginning with 'mycompany'
-
-in :ref:`the configuration file <reference/cmdline/config_file>` set:
-
-.. code-block:: ini
-
-  [options]
-  dbfilter = ^mycompany.*$
-
-* Show only databases matching the first subdomain after ``www``: for example
-  the database "mycompany" will be shown if the incoming request
-  was sent to ``www.mycompany.com`` or ``mycompany.co.uk``, but not
-  for ``www2.mycompany.com`` or ``helpdesk.mycompany.com``.
-
-in :ref:`the configuration file <reference/cmdline/config_file>` set:
-
-.. code-block:: ini
-
-  [options]
-  dbfilter = ^%d$
-
-.. note::
-
-  Setting a proper :option:`--db-filter <odoo-bin --db-filter>` is an important part
-  of securing your deployment.
-  Once it is correctly working and only matching a single database per hostname, it
-  is strongly recommended to block access to the database manager screens,
-  and to use the ``--no-database-list`` startup parameter to prevent listing
-  your databases, and to block access to the database management screens.
-  See also security_.
-
-PostgreSQL
-==========
-
-By default, PostgreSQL only allows connection over UNIX sockets and loopback
-connections (from "localhost", the same machine the PostgreSQL server is
-installed on).
-
-UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same
-machine, and is the default when no host is provided, but if you want Odoo and
-PostgreSQL to execute on different machines [#different-machines]_ it will
-need to `listen to network interfaces`_ [#remote-socket]_, either:
-
-* Only accept loopback connections and `use an SSH tunnel`_ between the
-  machine on which Odoo runs and the one on which PostgreSQL runs, then
-  configure Odoo to connect to its end of the tunnel
-* Accept connections to the machine on which Odoo is installed, possibly
-  over ssl (see `PostgreSQL connection settings`_ for details), then configure
-  Odoo to connect over the network
-
-Configuration sample
---------------------
-
-* Allow tcp connection on localhost
-* Allow tcp connection from 192.168.1.x network
-
-in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf`` set:
-
-.. code-block:: text
-
-  # IPv4 local connections:
-  host    all             all             127.0.0.1/32            md5
-  host    all             all             192.168.1.0/24          md5
-
-in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/postgresql.conf`` set:
-
-.. code-block:: text
-
-  listen_addresses = 'localhost,192.168.1.2'
-  port = 5432
-  max_connections = 80
-
-.. _setup/deploy/odoo:
-
-Configuring Odoo
-----------------
-
-Out of the box, Odoo connects to a local postgres over UNIX socket via port
-5432. This can be overridden using :ref:`the database options
-<reference/cmdline/server/database>` when your Postgres deployment is not
-local and/or does not use the installation defaults.
-
-The :doc:`packaged installers <packages>` will automatically
-create a new user (``odoo``) and set it as the database user.
-
-* The database management screens are protected by the ``admin_passwd``
-  setting. This setting can only be set using configuration files, and is
-  simply checked before performing database alterations. It should be set to
-  a randomly generated value to ensure third parties can not use this
-  interface.
-* All database operations use the :ref:`database options
-  <reference/cmdline/server/database>`, including the database management
-  screen. For the database management screen to work requires that the PostgreSQL user
-  have ``createdb`` right.
-* Users can always drop databases they own. For the database management screen
-  to be completely non-functional, the PostgreSQL user needs to be created with
-  ``no-createdb`` and the database must be owned by a different PostgreSQL user.
-
-  .. warning:: the PostgreSQL user *must not* be a superuser
-
-Configuration sample
-~~~~~~~~~~~~~~~~~~~~
-
-* connect to a PostgreSQL server on 192.168.1.2
-* port 5432
-* using an 'odoo' user account,
-* with 'pwd' as a password
-* filtering only db with a name beginning with 'mycompany'
-
-in :ref:`the configuration file <reference/cmdline/config_file>` set:
-
-.. code-block:: ini
-
-  [options]
-  admin_passwd = mysupersecretpassword
-  db_host = 192.168.1.2
-  db_port = 5432
-  db_user = odoo
-  db_password = pwd
-  dbfilter = ^mycompany.*$
-
-.. _postgresql_ssl_connect:
-
-SSL Between Odoo and PostgreSQL
--------------------------------
-
-Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL.
-in Odoo the db_sslmode control the ssl security of the connection
-with value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca'
-or 'verify-full'
-
-`PostgreSQL Doc <https://www.postgresql.org/docs/12/static/libpq-ssl.html>`_
-
-.. _builtin_server:
-
-Builtin server
-==============
-
-Odoo includes built-in HTTP, cron, and live-chat servers, using either multi-threading or
-multi-processing.
-
-The **multi-threaded** server is a simpler server primarily used for development, demonstrations,
-and its compatibility with various operating systems (including Windows). A new thread is spawned
-for every new HTTP request, even for long-lived connections such as websocket. Extra daemonic cron
-threads are spawned too. Due to a Python limitation (GIL), it doesn't make the best use of the
-hardware.
-
-The multi-threaded server is the default server, also for docker containers. It is selected by
-leaving the :option:`--workers <odoo-bin --workers>` option out or setting it to ``0``.
-
-The **multi-processing** server is a full-blown server primarily used for production. It is not
-liable to the same Python limitation (GIL) on resource usage and hence makes the best use of the
-hardware. A pool of workers is created upon server startup. New HTTP requests are queued by the OS
-until there are workers ready to process them. An extra event-driven HTTP worker for the live chat
-is spawned on an alternative port. Extra cron workers are spawned too. A configurable process
-reaper monitors resource usage and can kill/restart failed workers.
-
-The multi-processing server is opt-in. It is selected by setting the :option:`--workers
-<odoo-bin --workers>` option to a non-null integer.
-
-.. note::
-   Because it is highly customized for Linux servers, the multi-processing server is not available
-   on Windows.
-
-Worker number calculation
--------------------------
-
-* Rule of thumb : (#CPU * 2) + 1
-* Cron workers need CPU
-* 1 worker ~= 6 concurrent users
-
-memory size calculation
------------------------
-
-* We consider 20% of the requests are heavy requests, while 80% are simpler ones
-* A heavy worker, when all computed field are well designed, SQL requests are well designed, ... is estimated to consume around 1GB of RAM
-* A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM
-
-Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) + (heavy_worker_ratio * heavy_worker_ram_estimation) )
-
-LiveChat
---------
-
-In multi-processing, a dedicated LiveChat worker is automatically started and listens on
-the :option:`--gevent-port <odoo-bin --gevent-port>`. By default, the HTTP requests will keep
-accessing the normal HTTP workers instead of the LiveChat one. You must deploy a proxy in front of
-Odoo and redirect incoming requests whose path starts with ``/websocket/`` to the LiveChat worker.
-You must also start Odoo in :option:`--proxy-mode <odoo-bin --proxy-mode>` so it uses the real
-client headers (such as hostname, scheme, and IP) instead of the proxy ones.
-
-Configuration sample
---------------------
-
-* Server with 4 CPU, 8 Thread
-* 60 concurrent users
-
-* 60 users / 6 = 10 <- theoretical number of worker needed
-* (4 * 2) + 1 = 9 <- theoretical maximal number of worker
-* We'll use 8 workers + 1 for cron. We'll also use a monitoring system to measure cpu load, and check if it's between 7 and 7.5 .
-* RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo
-
-in :ref:`the configuration file <reference/cmdline/config_file>`:
-
-.. code-block:: ini
-
-  [options]
-  limit_memory_hard = 1677721600
-  limit_memory_soft = 629145600
-  limit_request = 8192
-  limit_time_cpu = 600
-  limit_time_real = 1200
-  max_cron_threads = 1
-  workers = 8
-
-.. _https_proxy:
-
-HTTPS
-=====
-
-Whether it's accessed via website/web client or web service, Odoo transmits
-authentication information in cleartext. This means a secure deployment of
-Odoo must use HTTPS\ [#switching]_. SSL termination can be implemented via
-just about any SSL termination proxy, but requires the following setup:
-
-* Enable Odoo's :option:`proxy mode <odoo-bin --proxy-mode>`. This should only be enabled when Odoo is behind a reverse proxy
-* Set up the SSL termination proxy (`Nginx termination example`_)
-* Set up the proxying itself (`Nginx proxying example`_)
-* Your SSL termination proxy should also automatically redirect non-secure
-  connections to the secure port
-
-Configuration sample
---------------------
-
-* Redirect http requests to https
-* Proxy requests to odoo
-
-in :ref:`the configuration file <reference/cmdline/config_file>` set:
-
-.. code-block:: ini
-
-  proxy_mode = True
-
-in ``/etc/nginx/sites-enabled/odoo.conf`` set:
-
-.. code-block:: nginx
-
-  #odoo server
-  upstream odoo {
-    server 127.0.0.1:8069;
-  }
-  upstream odoochat {
-    server 127.0.0.1:8072;
-  }
-  map $http_upgrade $connection_upgrade {
-    default upgrade;
-    ''      close;
-  }
-
-  # http -> https
-  server {
-    listen 80;
-    server_name odoo.mycompany.com;
-    rewrite ^(.*) https://$host$1 permanent;
-  }
-
-  server {
-    listen 443 ssl;
-    server_name odoo.mycompany.com;
-    proxy_read_timeout 720s;
-    proxy_connect_timeout 720s;
-    proxy_send_timeout 720s;
-
-    # SSL parameters
-    ssl_certificate /etc/ssl/nginx/server.crt;
-    ssl_certificate_key /etc/ssl/nginx/server.key;
-    ssl_session_timeout 30m;
-    ssl_protocols TLSv1.2;
-    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
-    ssl_prefer_server_ciphers off;
-
-    # log
-    access_log /var/log/nginx/odoo.access.log;
-    error_log /var/log/nginx/odoo.error.log;
-
-    # Redirect websocket requests to odoo gevent port
-    location /websocket {
-      proxy_pass http://odoochat;
-      proxy_set_header Upgrade $http_upgrade;
-      proxy_set_header Connection $connection_upgrade;
-      proxy_set_header X-Forwarded-Host $http_host;
-      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-      proxy_set_header X-Forwarded-Proto $scheme;
-      proxy_set_header X-Real-IP $remote_addr;
-
-      add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";
-      proxy_cookie_flags session_id samesite=lax secure;  # requires nginx 1.19.8
-    }
-
-    # Redirect requests to odoo backend server
-    location / {
-      # Add Headers for odoo proxy mode
-      proxy_set_header X-Forwarded-Host $http_host;
-      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-      proxy_set_header X-Forwarded-Proto $scheme;
-      proxy_set_header X-Real-IP $remote_addr;
-      proxy_redirect off;
-      proxy_pass http://odoo;
-
-      add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";
-      proxy_cookie_flags session_id samesite=lax secure;  # requires nginx 1.19.8
-    }
-
-    # common gzip
-    gzip_types text/css text/scss text/plain text/xml application/xml application/json application/javascript;
-    gzip on;
-  }
-
-HTTPS Hardening
----------------
-
-Add the `Strict-Transport-Security` header to all requests, in order to prevent
-browsers from ever sending a plain HTTP request to this domain. You will need
-to maintain a working HTTPS service with a valid certificate on this domain at
-all times, otherwise your users will see security alerts or be entirely unable
-to access it.
-
-Force HTTPS connections during a year for every visitor in NGINX with the line:
-
-.. code-block:: nginx
-
-  add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";
-
-Additional configuration can be defined for the `session_id` cookie. The `Secure`
-flag can be added to ensure it is never transmitted over HTTP and `SameSite=Lax`
-to prevent authenticated `CSRF`_.
-
-.. code-block:: nginx
-
-  # requires nginx 1.19.8
-  proxy_cookie_flags session_id samesite=lax secure;
-
-
-Odoo as a WSGI Application
-==========================
-
-It is also possible to mount Odoo as a standard WSGI_ application. Odoo
-provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. That
-script should be customized (possibly after copying it from the setup directory) to correctly set the
-configuration directly in :mod:`odoo.tools.config` rather than through the
-command-line or a configuration file.
-
-However the WSGI server will only expose the main HTTP endpoint for the web
-client, website and webservice API. Because Odoo does not control the creation
-of workers anymore it can not setup cron or livechat workers
-
-Cron Workers
-------------
-
-Starting one of the built-in Odoo servers next to the WSGI server is required to process cron jobs.
-That server must be configured to only process crons and not HTTP requests using the
-:option:`--no-http <odoo-bin --no-http>` cli option or the ``http_enable = False`` configuration
-file setting.
-
-On Linux-like systems, using the multi-processing server over the multi-threading one is recommended
-to benefit from better hardware usage and increased stability, i.e., using
-the :option:`--workers=-1 <odoo-bin --workers>` and :option:`--max-cron-threads=n
-<odoo-bin --max-cron-threads>` cli options.
-
-LiveChat
---------
-
-Using a gevent-compatible WSGI server is required for the correct operation of the live chat
-feature. That server should be able to handle many simultaneous long-lived connections but doesn't
-need a lot of processing power. All requests whose path starts with ``/websocket/`` should be
-directed to that server. A regular (thread/process-based) WSGI server should be used for all other
-requests.
-
-The Odoo cron server can also be used to serve the live chat requests. Just drop
-the :option:`--no-http <odoo-bin --no-http>` cli option from the cron server and make sure requests
-whose path starts with ``/websocket/`` are directed to this server, either on
-the :option:`--http-port <odoo-bin --http-port>` (multi-threading server) or on
-the :option:`--gevent-port <odoo-bin --gevent-port>` (multi-processing server).
-
-.. _deploy/streaming:
-
-Serving static files and attachments
-====================================
-
-For development convenience, Odoo directly serves all static files and attachments in its modules.
-This may not be ideal when it comes to performances, and static files should generally be served by
-a static HTTP server.
-
-Serving static files
---------------------
-
-Odoo static files are located in each module's :file:`static/` folder, so static files can be served
-by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module
-(and file) in the various addons paths.
-
-It is recommended to set the ``Content-Security-Policy: default-src 'none'`` header on all images
-delivered by the web server. It is not strictly necessary as users cannot modify/inject content
-inside of modules' :file:`static/` folder and existing images are final (they do not fetch new
-resources by themselves). However, it is good practice.
-
-Using the above NGINX (https) configuration, the following ``map`` and ``location`` blocks should be
-added to serve static files via NGINX.
-
-.. code-block:: nginx
-
-    map $sent_http_content_type $content_type_csp {
-        default "";
-        ~image/ "default-src 'none'";
-    }
-
-    server {
-        # the rest of the configuration
-
-        location @odoo {
-            # copy-paste the content of the / location block
-        }
-
-        # Serve static files right away
-        location ~ ^/[^/]+/static/.+$ {
-            # root and try_files both depend on your addons paths
-            root ...;
-            try_files ... @odoo;
-            expires 24h;
-            add_header Content-Security-Policy $content_type_csp;
-        }
-    }
-
-The actual ``root`` and ``try_files`` directives are dependant on your installation, specifically on
-your :option:`--addons-path <odoo-bin --addons-path>`.
-
-.. example::
-
-   .. tabs::
-
-      .. group-tab:: Debian package
-
-         Say Odoo has been installed via the **debian packages** for Community and Enterprise, and
-         that the :option:`--addons-path <odoo-bin --addons-path>` is
-         ``'/usr/lib/python3/dist-packages/odoo/addons'``.
-
-         The ``root`` and ``try_files`` should be:
-
-         .. code-block:: nginx
-
-            root /usr/lib/python3/dist-packages/odoo/addons;
-            try_files $uri @odoo;
-
-      .. group-tab:: Git sources
-
-         Say Odoo has been installed via the **sources**, that both the Community and Enterprise git
-         repositories were cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise`
-         respectively, and that the :option:`--addons-path <odoo-bin --addons-path>` is
-         ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``.
-
-         The ``root`` and ``try_files`` should be:
-
-         .. code-block:: nginx
-
-            root /opt/odoo;
-            try_files /community/odoo/addons$uri /community/addons$uri /enterprise$uri @odoo;
-
-Serving attachments
--------------------
-
-Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be
-directly accessed via a static web server as accessing them requires multiple lookups in the
-database to determine where the files are stored and whether the current user can access them or
-not.
-
-Nevertheless, once the file has been located and the access rights verified by Odoo, it is a good
-idea to serve the file using the static web server instead of Odoo. For Odoo to delegate serving
-files to the static web server, the `X-Sendfile <https://tn123.org/mod_xsendfile/>`_ (apache) or
-`X-Accel <https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/>`_ (nginx) extensions
-must be enabled and configured on the static web server. Once it is set up, start Odoo with the
-:option:`--x-sendfile <odoo-bin --x-sendfile>` CLI flag (this unique flag is used for both
-X-Sendfile and X-Accel).
-
-
-.. note::
-   - The X-Sendfile extension for apache (and compatible web servers) does not require any
-     supplementary configuration.
-   - The X-Accel extension for NGINX **does** require the following additionnal configuration:
-
-     .. code-block:: nginx
-
-         location /web/filestore {
-             internal;
-             alias /path/to/odoo/data-dir/filestore;
-         }
-
-     In case you don't know what is the path to your filestore, start Odoo with the
-     :option:`--x-sendfile <odoo-bin --x-sendfile>` option and navigate to the ``/web/filestore`` URL
-     directly via Odoo (don't navigate to the URL via NGINX). This logs a warnings, the message
-     contains the configuration you need.
-
-
-.. _security:
-
-Security
-========
-
-For starters, keep in mind that securing an information system is a continuous process,
-not a one-shot operation. At any moment, you will only be as secure as the weakest link
-in your environment.
-
-So please do not take this section as the ultimate list of measures that will prevent
-all security problems. It's only intended as a summary of the first important things
-you should be sure to include in your security action plan. The rest will come
-from best security practices for your operating system and distribution,
-best practices in terms of users, passwords, and access control management, etc.
-
-When deploying an internet-facing server, please be sure to consider the following
-security-related topics:
-
-- Always set a strong super-admin admin password, and restrict access to the database
-  management pages as soon as the system is set up. See :ref:`db_manager_security`.
-
-- Choose unique logins and strong passwords for all administrator accounts on all databases.
-  Do not use 'admin' as the login. Do not use those logins for day-to-day operations,
-  only for controlling/managing the installation.
-  *Never* use any default passwords like admin/admin, even for test/staging databases.
-
-- Do **not** install demo data on internet-facing servers. Databases with demo data contain
-  default logins and passwords that can be used to get into your systems and cause significant
-  trouble, even on staging/dev systems.
-
-- Use appropriate database filters ( :option:`--db-filter <odoo-bin --db-filter>`)
-  to restrict the visibility of your databases according to the hostname.
-  See :ref:`db_filter`.
-  You may also use :option:`-d <odoo-bin -d>` to provide your own (comma-separated)
-  list of available databases to filter from, instead of letting the system fetch
-  them all from the database backend.
-
-- Once your ``db_name`` and ``db_filter`` are configured and only match a single database
-  per hostname, you should set ``list_db`` configuration option to ``False``, to prevent
-  listing databases entirely, and to block access to the database management screens
-  (this is also exposed as the :option:`--no-database-list <odoo-bin --no-database-list>`
-  command-line option)
-
-- Make sure the PostgreSQL user (:option:`--db_user <odoo-bin --db_user>`) is *not* a super-user,
-  and that your databases are owned by a different user. For example they could be owned by
-  the ``postgres`` super-user if you are using a dedicated non-privileged ``db_user``.
-  See also :ref:`setup/deploy/odoo`.
-
-- Keep installations updated by regularly installing the latest builds,
-  either via GitHub or by downloading the latest version from
-  https://www.odoo.com/page/download or http://nightly.odoo.com
-
-- Configure your server in multi-process mode with proper limits matching your typical
-  usage (memory/CPU/timeouts). See also :ref:`builtin_server`.
-
-- Run Odoo behind a web server providing HTTPS termination with a valid SSL certificate,
-  in order to prevent eavesdropping on cleartext communications. SSL certificates are
-  cheap, and many free options exist.
-  Configure the web proxy to limit the size of requests, set appropriate timeouts,
-  and then enable the :option:`proxy mode <odoo-bin --proxy-mode>` option.
-  See also :ref:`https_proxy`.
-
-- If you need to allow remote SSH access to your servers, make sure to set a strong password
-  for **all** accounts, not just `root`. It is strongly recommended to entirely disable
-  password-based authentication, and only allow public key authentication. Also consider
-  restricting access via a VPN, allowing only trusted IPs in the firewall, and/or
-  running a brute-force detection system such as `fail2ban` or equivalent.
-
-- Consider installing appropriate rate-limiting on your proxy or firewall, to prevent
-  brute-force attacks and denial of service attacks. See also :ref:`login_brute_force`
-  for specific measures.
-
-  Many network providers provide automatic mitigation for Distributed Denial of
-  Service attacks (DDOS), but this is often an optional service, so you should consult
-  with them.
-
-- Whenever possible, host your public-facing demo/test/staging instances on different
-  machines than the production ones. And apply the same security precautions as for
-  production.
-
-- If your public-facing Odoo server has access to sensitive internal network resources
-  or services (e.g. via a private VLAN), implement appropriate firewall rules to
-  protect those internal resources. This will ensure that the Odoo server cannot
-  be used accidentally (or as a result of malicious user actions) to access or disrupt
-  those internal resources.
-  Typically this can be done by applying an outbound default DENY rule on the firewall,
-  then only explicitly authorizing access to internal resources that the Odoo server
-  needs to access.
-  `Systemd IP traffic access control <http://0pointer.net/blog/ip-accounting-and-access-lists-with-systemd.html>`_
-  may also be useful to implement per-process network access control.
-
-- If your public-facing Odoo server is behind a Web Application Firewall, a load-balancer,
-  a transparent DDoS protection service (like CloudFlare) or a similar network-level
-  device, you may wish to avoid direct access to the Odoo system. It is generally
-  difficult to keep the endpoint IP addresses of your Odoo servers secret. For example
-  they can appear in web server logs when querying public systems, or in the headers
-  of emails posted from Odoo.
-  In such a situation you may want to configure your firewall so that the endpoints
-  are not accessible publicly except from the specific IP addresses of your WAF,
-  load-balancer or proxy service. Service providers like CloudFlare usually maintain
-  a public list of their IP address ranges for this purpose.
-
-- If you are hosting multiple customers, isolate customer data and files from each other
-  using containers or appropriate "jail" techniques.
-
-- Setup daily backups of your databases and filestore data, and copy them to a remote
-  archiving server that is not accessible from the server itself.
-
-- Deploying Odoo on Linux is strongly recommended over Windows. Should you choose nevertheless
-  to deploy on a Windows platform, a thorough security hardening review of the server should be
-  conducted and is outside of the scope of this guide.
-
-
-.. _login_brute_force:
-
-Blocking Brute Force Attacks
-----------------------------
-
-For internet-facing deployments, brute force attacks on user passwords are very common, and this
-threat should not be neglected for Odoo servers. Odoo emits a log entry whenever a login attempt
-is performed, and reports the result: success or failure, along with the target login and source IP.
-
-The log entries will have the following form.
-
-Failed login::
-
-      2018-07-05 14:56:31,506 24849 INFO db_name odoo.addons.base.res.res_users: Login failed for db:db_name login:admin from 127.0.0.1
-
-Successful login::
-
-      2018-07-05 14:56:31,506 24849 INFO db_name odoo.addons.base.res.res_users: Login successful for db:db_name login:admin from 127.0.0.1
-
-
-These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`.
-
-For example, the following fail2ban filter definition should match a
-failed login::
-
-    [Definition]
-    failregex = ^ \d+ INFO \S+ \S+ Login failed for db:\S+ login:\S+ from <HOST>
-    ignoreregex =
-
-This could be used with a jail definition to block the attacking IP on HTTP(S).
-
-Here is what it could look like for blocking the IP for 15 minutes when
-10 failed login attempts are detected from the same IP within 1 minute::
-
-    [odoo-login]
-    enabled = true
-    port = http,https
-    bantime = 900  ; 15 min ban
-    maxretry = 10  ; if 10 attempts
-    findtime = 60  ; within 1 min  /!\ Should be adjusted with the TZ offset
-    logpath = /var/log/odoo.log  ;  set the actual odoo log path here
-
-.. _db_manager_security:
-
-Database Manager Security
--------------------------
-
-:ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing.
-
-This setting is used on all database management screens (to create, delete,
-dump or restore databases).
-
-If the management screens must not be accessible at all, you should set ``list_db``
-configuration option to ``False``, to block access to all the database selection and
-management screens.
-
-.. warning::
-
-  It is strongly recommended to disable the Database Manager for any internet-facing
-  system! It is meant as a development/demo tool, to make it easy to quickly create
-  and manage databases. It is not designed for use in production, and may even expose
-  dangerous features to attackers. It is also not designed to handle large databases,
-  and may trigger memory limits.
-
-  On production systems, database management operations should always be performed by
-  the system administrator, including provisioning of new databases and automated backups.
-
-Be sure to setup an appropriate ``db_name`` parameter
-(and optionally, ``db_filter`` too) so that the system can determine the target database
-for each request, otherwise users will be blocked as they won't be allowed to choose the
-database themselves.
-
-If the management screens must only be accessible from a selected set of machines,
-use the proxy server's features to block access to all routes starting with ``/web/database``
-except (maybe) ``/web/database/selector`` which displays the database-selection screen.
-
-If the database-management screen should be left accessible, the
-``admin_passwd`` setting must be changed from its ``admin`` default: this
-password is checked before allowing database-alteration operations.
-
-It should be stored securely, and should be generated randomly e.g.
-
-.. code-block:: console
-
-    $ python3 -c 'import base64, os; print(base64.b64encode(os.urandom(24)))'
-
-which generates a 32-character pseudorandom printable string.
-
-Reset the master password
--------------------------
-
-There may be instances where the master password is misplaced, or compromised, and needs to be
-reset. The following process is for system administrators of an Odoo on-premise database detailing
-how to manually reset and re-encrypt the master password.
-
-.. seealso::
-   For more information about changing an Odoo.com account password, see this documentation:
-   :ref:`odoocom/change_password`.
-
-When creating a new on-premise database, a random master password is generated. Odoo recommends
-using this password to secure the database. This password is implemented by default, so there is a
-secure master password for any Odoo on-premise deployment.
-
-.. warning::
-   When creating an Odoo on-premise database the installation is accessible to anyone on the
-   internet, until this password is set to secure the database.
-
-The master password is specified in the Odoo configuration file (`odoo.conf` or `odoorc` (hidden
-file)). The Odoo master password is needed to modify, create, or delete a database through the
-graphical user interface (GUI).
-
-Locate configuration file
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden file)).
-
-.. tabs::
-
-   .. tab:: Windows
-
-      The configuration file is located at: `c:\\ProgramFiles\\Odoo{VERSION}\\server\\odoo.conf`
-
-   .. tab:: Linux
-
-      Depending on how Odoo is installed on the Linux machine, the configuration file is located in
-      one of two different places:
-
-      - Package installation: `/etc/odoo.conf`
-      - Source installation: `~/.odoorc`
-
-Change old password
-~~~~~~~~~~~~~~~~~~~
-
-Once the appropriate file has been opened, proceed to modify the old password in the configuration
-file to a temporary password.
-
-.. tabs::
-
-   .. group-tab:: Graphical user interface
-
-      After locating the configuration file, open it using a (:abbr:`GUI (graphical user
-      interface)`). This can be achieved by simply double clicking on the file. Then, the device
-      should have a default :abbr:`GUI (graphical user interface)` to open the file with.
-
-      Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to `admin_passwd =
-      newpassword1234`, for example. This password can be anything, as long as it is saved
-      temporarily. Make sure to modify all characters after the `=`.
-
-      .. example::
-         The line appears like this:
-         `admin_passwd =
-         $pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`
-
-         The modified line appears like this: `admin_passwd = newpassword1234`
-
-   .. group-tab:: Command-line interface
-
-      Modify the master password line using the following Unix command detailed below.
-
-      Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and edit the
-      configuration file. To modify the configuration file, enter the following command:
-      :command:`sudo nano /etc/odoo.conf`
-
-      After opening the configuration file, modify the master password line `admin_passwd =
-      $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This password can be anything, as long as
-      it is saved temporarily. Make sure to modify all characters after the `=`.
-
-      .. example::
-         The line appears like this:
-         `admin_passwd =
-         $pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`
-
-         The modified line appears like this: `admin_passwd = newpassword1234`
-
-.. important::
-   It is essential that the password is changed to something else, rather than triggering a new
-   password reset by adding a semicolon `;` at the beginning of the line. This ensures the database
-   is secure throughout the entire password reset process.
-
-Restart Odoo server
-~~~~~~~~~~~~~~~~~~~
-
-After setting the temporary password, a restart of the Odoo server is **required**.
-
-.. tabs::
-
-   .. group-tab:: Graphical user interface
-
-      To restart the Odoo server, first, type `services` into the Windows :guilabel:`Search` bar.
-      Then, select the :guilabel:`Services` application, and scroll down to the :guilabel:`Odoo`
-      service.
-
-      Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or :guilabel:`Restart`.
-      This action manually restarts the Odoo server.
-
-   .. group-tab:: Command-line interface
-
-      Restart the Odoo server by typing the command: :command:`sudo service odoo15 restart`
-
-      .. note::
-         Change the number after `odoo` to fit the specific version the server is running on.
-
-Use web interface to re-encrypt password
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-First, navigate to `/web/database/manager` or `http://server_ip:port/web/database/manager` in a
-browser.
-
-.. note::
-   Replace `server_ip` with the IP address of the database. Replace `port` with the numbered port
-   the database is accessible from.
-
-Next, click :guilabel:`Set Master Password`, and type in the previously-selected temporary password
-into the :guilabel:`Master Password` field. Following this step, type in a :guilabel:`New Master
-Password`. The :guilabel:`New Master Password` is hashed (or encrypted), once the
-:guilabel:`Continue` button is clicked.
-
-At this point, the password has been successfully reset, and a hashed version of the new password
-now appears in the configuration file.
-
-.. seealso::
-   For more information on Odoo database security, see this documentation:
-   :ref:`db_manager_security`.
-
-Supported Browsers
-==================
-
-Odoo supports all the major desktop and mobile browsers available on the market,
-as long as they are supported by their publishers.
-
-Here are the supported browsers:
-
-- Google Chrome
-- Mozilla Firefox
-- Microsoft Edge
-- Apple Safari
-
-.. warning:: Please make sure your browser is up-to-date and still supported by
-    its publisher before filing a bug report.
-
-.. note::
-
-    Since Odoo 13.0, ES6 is supported.  Therefore, IE support is dropped.
-
-.. [#different-machines]
-    to have multiple Odoo installations use the same PostgreSQL database,
-    or to provide more computing resources to both software.
-.. [#remote-socket]
-    technically a tool like socat_ can be used to proxy UNIX sockets across
-    networks, but that is mostly for software which can only be used over
-    UNIX sockets
-.. [#switching]
-    or be accessible only over an internal packet-switched network, but that
-    requires secured switches, protections against `ARP spoofing`_ and
-    precludes usage of WiFi. Even over secure packet-switched networks,
-    deployment over HTTPS is recommended, and possible costs are lowered as
-    "self-signed" certificates are easier to deploy on a controlled
-    environment than over the internet.
-
-.. _regular expression: https://docs.python.org/3/library/re.html
-.. _CSRF: https://en.wikipedia.org/wiki/Cross-site_request_forgery
-.. _ARP spoofing: https://en.wikipedia.org/wiki/ARP_spoofing
-.. _Nginx termination example:
-    https://nginx.com/resources/admin-guide/nginx-ssl-termination/
-.. _Nginx proxying example:
-    https://nginx.com/resources/admin-guide/reverse-proxy/
-.. _socat: http://www.dest-unreach.org/socat/
-.. _PostgreSQL connection settings:
-.. _listen to network interfaces:
-    https://www.postgresql.org/docs/12/static/runtime-config-connection.html
-.. _use an SSH tunnel:
-    https://www.postgresql.org/docs/12/static/ssh-tunnels.html
-.. _WSGI: https://wsgi.readthedocs.org/
-.. _POSBox: https://www.odoo.com/page/point-of-sale-hardware#part_2

content/administration/on_premise/geo_ip.rst

@@ -1,70 +0,0 @@
-======
-Geo IP
-======
-
-.. note::
-   This documentation only applies to On-premise databases.
-
-Installation
-============
-
-.. warning::
-   Please note that the installation depends on your computer's operating system and distribution.
-   We will assume that a Linux operating system is being used.
-
-#. Install `geoip2 <https://pypi.org/project/geoip2/>`__ Python library
-    .. code-block:: bash
-
-      pip install geoip2
-
-#. Download the `GeoLite2 City database <https://dev.maxmind.com/geoip/geoip2/geolite2/>`_. You
-   should end up with a file called ``GeoLite2-City.mmdb``
-#. Move the file to the folder ``/usr/share/GeoIP/``
-    .. code-block:: bash
-
-        mv ~/Downloads/GeoLite2-City.mmdb /usr/share/GeoIP/
-
-#. Restart the server
-
-.. note::
-   If you can't/don't want to locate the geoip database in ``/usr/share/GeoIP/``, you can use the
-   ``--geoip-db`` option of the Odoo command line interface. This option takes the absolute path to
-   the GeoIP database file and uses it as the GeoIP database. For example:
-
-   .. code-block:: bash
-
-      ./odoo-bin --geoip-db= ~/Downloads/GeoLite2-City.mmdb
-
-   .. seealso::
-      - :doc:`CLI documentation </developer/reference/cli>`.
-
-.. warning::
-   ``GeoIP`` Python library can also be used. However this version is discontinued since January
-   1.    See `GeoLite Legacy databases are now discontinued
-   <https://support.maxmind.com/geolite-legacy-discontinuation-notice/>`_
-
-How to test GeoIP geolocation in your Odoo website
-==================================================
-
-1. Go to your website. Open the web page that you want to test ``GeoIP``.
-2. Choose :menuselection:`Customize --> HTML/CSS/JS Editor`.
-3. Add the following piece of XML in the page :
-
-.. code-block:: xml
-
-    <h1 class="text-center" t-esc="request.session.get('geoip')"/>
-
-You should end up with a dictionary indicating the location of the IP address.
-
-.. image:: geo_ip/on-premise_geo-ip-installation01.png
-    :align: center
-
-.. note::
-   If the curly braces are empty ``{}``, it can be for any of the following reasons :
-
-   - The browsing IP address is the localhost (``127.0.0.1``) or a local area network one
-     (``192.168.*.*``)
-   - If a reversed proxy is used, make sure to configure it correctly. See :option:`proxy mode
-     <odoo-bin --proxy-mode>`
-   - ``geoip2`` is not installed or the GeoIP database file wasn't found
-   - The GeoIP database was unable to resolve the given IP address

content/administration/on_premise/packages.rst

@@ -1,167 +0,0 @@
-===================
-Packaged installers
-===================
-
-Odoo provides packaged installers for Debian-based Linux distributions (Debian, Ubuntu, etc.),
-RPM-based Linux distributions (Fedora, CentOS, RHEL, etc.), and Windows for the Community and
-Enterprise editions.
-
-Official **Community** nightly packages with all relevant dependency requirements are available on
-the `nightly server <https://nightly.odoo.com>`_.
-
-.. note::
-   Nightly packages may be difficult to keep up to date.
-
-Official **Community** and **Enterprise** packages can be downloaded from the `Odoo download page
-<https://www.odoo.com/page/download>`_.
-
-.. note::
-   It is required to be logged in as a paying on-premise customer or partner to download the
-   Enterprise packages.
-
-.. _install/packages/linux:
-
-Linux
-=====
-
-Prepare
--------
-
-Odoo needs a `PostgreSQL <https://www.postgresql.org/>`_ server to run properly.
-
-.. tabs::
-
-   .. group-tab:: Debian/Ubuntu
-
-      The default configuration for the Odoo 'deb' package is to use the PostgreSQL server on the
-      same host as the Odoo instance. Execute the following command to install the PostgreSQL
-      server:
-
-      .. code-block:: console
-
-         $ sudo apt install postgresql -y
-
-   .. group-tab:: Fedora
-
-      Make sure that the `sudo` command is available and well configured and, only then, execute the
-      following command 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.6
-   <https://github.com/wkhtmltopdf/packaging/releases/tag/0.12.6.1-3>`_ for it to support headers
-   and footers. Check out the `wkhtmltopdf 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 to install the **Community** edition by executing
-the following commands:
-
-.. tabs::
-
-   .. group-tab:: Debian/Ubuntu
-
-      .. code-block:: console
-
-         $ wget -q -O - https://nightly.odoo.com/odoo.key | sudo gpg --dearmor -o /usr/share/keyrings/odoo-archive-keyring.gpg
-         $ echo 'deb [signed-by=/usr/share/keyrings/odoo-archive-keyring.gpg] https://nightly.odoo.com/{CURRENT_MAJOR_BRANCH}/nightly/deb/ ./' | sudo tee /etc/apt/sources.list.d/odoo.list
-         $ sudo apt-get update && sudo apt-get install odoo
-
-      Use the usual `apt-get upgrade` command to keep the installation up-to-date.
-
-   .. group-tab:: Fedora
-
-      .. code-block:: console
-
-         $ sudo dnf config-manager --add-repo=https://nightly.odoo.com/{CURRENT_MAJOR_BRANCH}/nightly/rpm/odoo.repo
-         $ sudo dnf install -y odoo
-         $ sudo systemctl enable odoo
-         $ sudo systemctl start odoo
-
-.. note::
-   Currently, there is no nightly repository for the Enterprise edition.
-
-Distribution package
---------------------
-
-Instead of using the repository, packages for both the **Community** and **Enterprise** editions can
-be downloaded from the `Odoo download page <https://www.odoo.com/page/download>`_.
-
-.. tabs::
-
-   .. group-tab:: Debian/Ubuntu
-
-      .. note::
-         Odoo {CURRENT_MAJOR_VERSION} 'deb' package currently supports `Debian Buster
-         <https://www.debian.org/releases/buster/>`_ and `Ubuntu 18.04
-         <https://releases.ubuntu.com/18.04>`_ or above.
-
-      Once downloaded, execute the following commands **as root** to install Odoo as a service,
-      create the necessary PostgreSQL user, and automatically start the server:
-
-      .. 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>
-
-      .. warning::
-         - The `python3-xlwt` Debian package, needed to export into the XLS format, does not exist
-           in Debian Buster nor Ubuntu 18.04. If needed, install it manually with the following:
-
-           .. code-block:: console
-
-              $ sudo pip3 install xlwt
-
-         - The `num2words` Python package - needed to render textual amounts - does not exist in
-           Debian Buster nor Ubuntu 18.04, which could cause problems with the `l10n_mx_edi` module.
-           If needed, install it manually with the following:
-
-           .. code-block:: console
-
-              $ sudo pip3 install num2words
-
-   .. group-tab:: Fedora
-
-      .. note::
-         Odoo {CURRENT_MAJOR_VERSION} 'rpm' package supports Fedora 36.
-
-      Once downloaded, the package can be installed using the 'dnf' package manager:
-
-      .. code-block:: console
-
-         $ sudo dnf localinstall odoo_{CURRENT_MAJOR_BRANCH}.latest.noarch.rpm
-         $ sudo systemctl enable odoo
-         $ sudo systemctl start odoo
-
-.. _install/packages/windows:
-
-Windows
-=======
-
-   .. warning::
-      Windows packaging is offered for the convenience of testing or running single-user local
-      instances but production deployment is discouraged due to a number of limitations and risks
-      associated with deploying Odoo on a Windows platform.
-
-#. Download the installer from the `nightly server <https://nightly.odoo.com>`_ (Community only) or
-   the Windows installer from the `Odoo download page <https://www.odoo.com/page/download>`_ (any
-   edition.
-#. Execute the downloaded file.
-
-   .. warning::
-      On Windows 8 and later, a warning titled *Windows protected your PC* may be displayed. Click
-      **More Info** and then **Run anyway** to proceed.
-
-#. Accept the `UAC <https://en.wikipedia.org/wiki/User_Account_Control>`_ prompt.
-#. Go through the installation steps.
-
-Odoo launches automatically at the end of the installation.

content/administration/on_premise/source.rst

@@ -1,488 +0,0 @@
-==============
-Source install
-==============
-
-The source 'installation' is not about installing Odoo but running it directly from the source
-instead.
-
-Using the Odoo source can be more convenient for module developers as it is more easily accessible
-than using packaged installers.
-
-It makes starting and stopping Odoo more flexible and explicit than the services set up by the
-packaged installers. Also, it 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 setup and allows to more easily keep (and
-run) multiple versions of Odoo side-by-side.
-
-Fetch the sources
------------------
-
-There are two ways to obtain the source code of Odoo: as a ZIP **archive** or through **Git**.
-
-Archive
-~~~~~~~
-
-Community edition:
-
-- `Odoo download page <https://www.odoo.com/page/download>`_
-- `GitHub Community repository <https://github.com/odoo/odoo>`_
-- `Nightly server <https://nightly.odoo.com>`_
-
-Enterprise edition:
-
-- `Odoo download page <https://www.odoo.com/page/download>`_
-- `GitHub Enterprise repository <https://github.com/odoo/enterprise>`_
-
-.. _install/source/git:
-
-Git
-~~~
-
-.. note::
-   It is required to have `Git <https://git-scm.com/>`_ installed, and it is recommended to have a
-   basic knowledge of Git commands to proceed.
-
-To clone a Git repository, choose between cloning with HTTPS or SSH. In most cases, the best option
-is HTTPS. However, choose SSH to contribute to Odoo source code or when following the :doc:`Getting
-Started developer tutorial </developer/tutorials/getting_started>`.
-
-.. tabs::
-
-   .. group-tab:: Linux
-
-      .. tabs::
-
-         .. tab:: Clone with HTTPS
-
-            .. code-block:: console
-
-               $ git clone https://github.com/odoo/odoo.git
-               $ git clone https://github.com/odoo/enterprise.git
-
-         .. tab:: Clone with SSH
-
-            .. code-block:: console
-
-               $ git clone git@github.com:odoo/odoo.git
-               $ git clone git@github.com:odoo/enterprise.git
-
-   .. group-tab:: Windows
-
-      .. tabs::
-
-         .. tab:: Clone with HTTPS
-
-            .. code-block:: doscon
-
-               C:\> git clone https://github.com/odoo/odoo.git
-               C:\> git clone https://github.com/odoo/enterprise.git
-
-         .. tab:: Clone with SSH
-
-            .. code-block:: doscon
-
-               C:\> git clone git@github.com:odoo/odoo.git
-               C:\> git clone git@github.com:odoo/enterprise.git
-
-   .. group-tab:: Mac OS
-
-      .. tabs::
-
-         .. tab:: Clone with HTTPS
-
-            .. code-block:: console
-
-               $ git clone https://github.com/odoo/odoo.git
-               $ git clone https://github.com/odoo/enterprise.git
-
-         .. tab:: Clone with SSH
-
-            .. code-block:: console
-
-               $ git clone git@github.com:odoo/odoo.git
-               $ git clone git@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 edition. Running the
-   Enterprise version means running the server from the Community version with the `addons-path`
-   option set to the folder with the Enterprise edition. It is required to clone both the Community
-   and Enterprise repositories to have a working Odoo Enterprise installation.
-
-.. _install/source/prepare:
-
-Prepare
--------
-
-Python
-~~~~~~
-
-Odoo requires **Python 3.7** or later to run.
-
-.. tabs::
-
-   .. group-tab:: Linux
-
-      Use a package manager to download and install Python 3 if needed.
-
-   .. group-tab:: Windows
-
-      `Download the latest version of Python 3 <https://www.python.org/downloads/windows/>`_ and
-      install it.
-
-      During installation, check **Add Python 3 to PATH**, then click **Customize Installation** and
-      make sure that **pip** is checked.
-
-   .. group-tab:: Mac OS
-
-      Use a package manager (`Homebrew <https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)
-      to download and install Python 3 if needed.
-
-.. note::
-   If Python 3 is already installed, make sure that the version is 3.7 or above, as previous
-   versions are not compatible with Odoo.
-
-   .. tabs::
-
-      .. group-tab:: Linux
-
-         .. code-block:: console
-
-            $ python3 --version
-
-      .. group-tab:: Windows
-
-         .. code-block:: doscon
-
-            C:\> python --version
-
-      .. group-tab:: Mac OS
-
-         .. code-block:: console
-
-            $ python3 --version
-
-   Verify that `pip <https://pip.pypa.io>`_ is also installed for this version.
-
-   .. tabs::
-
-      .. group-tab:: Linux
-
-         .. code-block:: console
-
-            $ pip3 --version
-
-      .. group-tab:: Windows
-
-         .. code-block:: doscon
-
-            C:\> pip --version
-
-      .. group-tab:: Mac OS
-
-         .. code-block:: console
-
-            $ pip3 --version
-
-PostgreSQL
-~~~~~~~~~~
-
-Odoo uses PostgreSQL as its database management system.
-
-.. tabs::
-
-   .. group-tab:: Linux
-
-      Use a package manager to download and install PostgreSQL (supported versions: 12.0 or above).
-      It can be achieved by executing the following:
-
-      .. code-block:: console
-
-         $ sudo apt install postgresql postgresql-client
-
-   .. group-tab:: Windows
-
-      `Download PostgreSQL <https://www.postgresql.org/download/windows>`_ (supported versions: 12.0
-      or above) and install it.
-
-   .. group-tab:: Mac OS
-
-      Use `Postgres.app <https://postgresapp.com>`_ to download and install PostgreSQL (supported
-      version: 12.0 or above).
-
-      .. tip::
-         To make the command line tools bundled with Postgres.app available, make sure to set up the
-         `$PATH` variable by following the `Postgres.app CLI tools instructions
-         <https://postgresapp.com/documentation/cli-tools.html>`_.
-
-By default, the only user is `postgres`. As Odoo forbids connecting as `postgres`, create a new
-PostgreSQL user.
-
-.. tabs::
-
-   .. group-tab:: Linux
-
-      .. code-block:: console
-
-         $ sudo -u postgres createuser -d -R -S $USER
-         $ createdb $USER
-
-      .. note::
-         Because the PostgreSQL user has the same name as the Unix login, it is possible to connect
-         to the database without a password.
-
-   .. group-tab:: Windows
-
-      #. Add PostgreSQL's `bin` directory (by default:
-         :file:`C:\\Program Files\\PostgreSQL\\<version>\\bin`) to the `PATH`.
-      #. Create a postgres user with a password using the pg admin gui:
-
-         #. Open **pgAdmin**.
-         #. Double-click the server to create a connection.
-         #. Select :menuselection:`Object --> Create --> Login/Group Role`.
-         #. Enter the username in the **Role Name** field (e.g., `odoo`).
-         #. Open the **Definition** tab, enter a password (e.g., `odoo`), and click **Save**.
-         #. Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?**
-            to `Yes`.
-
-   .. group-tab:: Mac OS
-
-      .. code-block:: console
-
-         $ sudo -u postgres createuser -d -R -S $USER
-         $ createdb $USER
-
-      .. note::
-         Because the PostgreSQL user has the same name as the Unix login, it is possible to connect
-         to the database without a password.
-
-.. _install/dependencies:
-
-Dependencies
-~~~~~~~~~~~~
-
-.. tabs::
-
-   .. group-tab:: Linux
-
-      Using **distribution packages** is the preferred way of installing dependencies.
-      Alternatively, install the Python dependencies with **pip**.
-
-      .. tabs::
-
-         .. tab:: Debian/Ubuntu
-
-            On Debian/Ubuntu, the following commands should install the required packages:
-
-            .. code-block:: console
-
-               $ cd odoo #CommunityPath
-               $ sudo ./setup/debinstall.sh
-
-            The `setup/debinstall.sh` script will parse the `debian/control
-            <{GITHUB_PATH}/debian/control>`_ file and install the found packages.
-
-         .. tab:: Install with pip
-
-            .. warning::
-
-               Using pip may lead to security issues and broken dependencies; only do this if you
-               know what you are doing.
-
-            As some of the Python packages need a compilation step, they require system libraries to
-            be installed.
-
-            On Debian/Ubuntu, the following command should install these required libraries:
-
-            .. code-block:: console
-
-               $ sudo apt install python3-pip libldap2-dev libpq-dev libsasl2-dev
-
-            Odoo dependencies are listed in the :file:`requirements.txt` file located at the root of
-            the Odoo Community directory.
-
-            .. note::
-               The Python packages in :file:`requirements.txt` are based on their stable/LTS
-               Debian/Ubuntu corresponding version at the moment of the Odoo release. For example,
-               for Odoo 15.0, the `python3-babel` package version is 2.8.0 in Debian Bullseye and
-               2.6.0 in Ubuntu Focal. The lowest version is then chosen in the
-               :file:`requirements.txt`.
-
-            .. tip::
-               It can be preferable not to mix Python module packages between different instances of
-               Odoo or with the system. However, it is possible to use `virtualenv
-               <https://pypi.org/project/virtualenv/>`_ to create isolated Python environments.
-
-            Navigate to the path of the Odoo Community installation (:file:`CommunityPath`) and run
-            **pip** on the requirements file to install the requirements for the current user.
-
-            .. code-block:: console
-
-               $ cd /CommunityPath
-               $ pip install -r requirements.txt
-
-   .. group-tab:: Windows
-
-      Before installing the dependencies, download and install the `Build Tools for Visual
-      Studio <https://visualstudio.microsoft.com/downloads/>`_. Select **C++ build tools** in the
-      **Workloads** tab and install them when prompted.
-
-      Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
-      Community directory.
-
-         .. tip::
-            It can be preferable not to mix Python module packages between different instances of
-            Odoo or with the system. However, it is possible to use `virtualenv
-            <https://pypi.org/project/virtualenv/>`_ to create isolated Python environments.
-
-      Navigate to the path of the 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
-
-   .. group-tab:: Mac OS
-
-      Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
-      Community directory.
-
-         .. tip::
-            It can be preferable not to mix Python module packages between different instances of
-            Odoo or with the system. However, it is possible to use `virtualenv
-            <https://pypi.org/project/virtualenv/>`_ to create isolated Python environments.
-
-      Navigate to the path of the 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 must be installed with a package manager (`Homebrew
-         <https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_).
-
-         #. Download and install the **Command Line Tools**:
-
-            .. code-block:: console
-
-               $ xcode-select --install
-
-         #. Use the package manager to install non-Python dependencies.
-
-.. note::
-   For languages using a **right-to-left interface** (such as Arabic or Hebrew), the `rtlcss`
-   package is required.
-
-   .. tabs::
-
-      .. group-tab:: Linux
-
-         #. Download and install **nodejs** and **npm** with a package manager.
-         #. Install `rtlcss`:
-
-            .. code-block:: console
-
-               $ sudo npm install -g rtlcss
-
-      .. group-tab:: Windows
-
-         #. 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: :file:`C:\\Users\\<user>\\AppData\\Roaming\\npm\\`).
-
-      .. group-tab:: Mac OS
-
-         #. Download and install **nodejs** with a package manager (`Homebrew <https://brew.sh/>`_,
-            `MacPorts <https://www.macports.org>`_).
-         #. Install `rtlcss`:
-
-            .. code-block:: console
-
-               $ sudo npm install -g rtlcss
-
-.. warning::
-   `wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.6
-   <https://github.com/wkhtmltopdf/packaging/releases/tag/0.12.6.1-3>`_ for it to support headers
-   and footers. Check out the `wkhtmltopdf wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_
-   for more details on the various versions.
-
-.. _install/source/running_odoo:
-
-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, either specify :ref:`command-line arguments <reference/cmdline/server>` or
-a :ref:`configuration file <reference/cmdline/config>`.
-
-.. tip::
-   For the Enterprise edition, add the path to the `enterprise` add-ons to the `addons-path`
-   argument. Note that it must come before the other paths in `addons-path` for add-ons to be loaded
-   correctly.
-
-Common necessary configurations are:
-
-- PostgreSQL user and password.
-- Custom addon paths beyond the defaults to load custom modules.
-
-A typical way to run the server would be:
-
-.. tabs::
-
-   .. group-tab:: Linux
-
-      .. 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 name
-      of the PostgreSQL database.
-
-   .. group-tab:: Windows
-
-      .. 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 name of the
-      PostgreSQL database.
-
-   .. group-tab:: Mac OS
-
-      .. 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 name
-      of the PostgreSQL database.
-
-After the server has started (the INFO log `odoo.modules.loading: Modules loaded.` is printed), open
-http://localhost:8069 in a web browser and log into the Odoo database with the base administrator
-account: use `admin` as the email and, again, `admin` as the password.
-
-.. tip::
-   - From there, create and manage new :doc:`users <../../applications/general/users>`.
-   - The user account used to log into Odoo's web interface differs from the :option:`--db_user
-     <odoo-bin -r>` CLI argument.
-
-.. seealso::
-   :doc:`The list of CLI arguments for odoo-bin </developer/reference/cli>`

content/administration/supported_versions.rst

@@ -1,101 +0,0 @@
-:hide-page-toc:
-
-.. _supported_versions:
-
-==================
-Supported versions
-==================
-
-Odoo provides support and bug fixing **for the 3 last major versions** of Odoo.
-
-.. note::
-   Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online
-   <odoo_online>` hosting every two months. Odoo Online users can then benefit from the latest
-   features of Odoo.
-
-   - Admins of Odoo Online databases are invited to :doc:`upgrade <upgrade>` them regularly.
-   - Online versions are *not* released for Odoo.sh and On-Premise installations.
-   - Online versions are listed below as *SaaS*.
-
-This matrix shows the support status of every version.
-
-**Major releases are in bold type.**
-
-.. list-table::
-   :header-rows: 1
-   :widths: auto
-
-   * -
-     - Odoo Online
-     - Odoo.sh
-     - On-Premise
-     - Release date
-     - End of support
-   * - **Odoo 18.0**
-     - |green|
-     - |green|
-     - |green|
-     - October 2024
-     - October 2027 (planned)
-   * - Odoo SaaS 17.4
-     - |green|
-     - N/A
-     - N/A
-     - July 2024
-     -
-   * - Odoo SaaS 17.2
-     - |green|
-     - N/A
-     - N/A
-     - April 2024
-     -
-   * - **Odoo 17.0**
-     - |green|
-     - |green|
-     - |green|
-     - November 2023
-     - October 2026 (planned)
-   * - **Odoo 16.0**
-     - |green|
-     - |green|
-     - |green|
-     - October 2022
-     - October 2025 (planned)
-   * - **Odoo 15.0**
-     - |red|
-     - |red|
-     - |red|
-     - October 2021
-     - October 2024
-   * - **Odoo 14.0**
-     - |red|
-     - |red|
-     - |red|
-     - October 2020
-     - November 2023
-   * - Older versions
-     - |red|
-     - |red|
-     - |red|
-     - Before 2020
-     - Before 2023
-
-.. admonition:: Legend
-
-    |green| Supported version
-
-    |red| End-of-support
-
-    N/A Never released for this platform
-
-.. important::
-   Even though we don't support older versions, you can always `upgrade from any version
-   <https://upgrade.odoo.com/>`_.
-
-.. |green| raw:: html
-
-   <span class="text-success" style="font-size: 32px; line-height: 0.5">●</span>
-
-.. |red| raw:: html
-
-   <span class="text-danger" style="font-size: 32px; line-height: 0.5">●</span>

content/administration/upgrade.rst

@@ -1,399 +1,223 @@
+:show-content:
+
+.. |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
 =======
 
-An upgrade involves moving a database from an older version to a newer supported version (e.g., from
-Odoo 15.0 to Odoo 17.0). Regular upgrades are crucial as each version offers new features, bug
-fixes, and security patches. Using a :doc:`supported version <supported_versions>` is strongly
-recommended. Each major version is supported for three years.
+.. toctree::
+   :titlesonly:
 
-Depending on the hosting type and Odoo version used, a database upgrade can be **mandatory**.
+   upgrade/odoo_online
+   upgrade/odoo_sh
+   upgrade/on_premise
+   upgrade/faq
 
-.. tabs::
-
-   .. group-tab:: Odoo Online
-
-      - If a database is on a **major version** (e.g., 15.0, 16.0, 17.0), an upgrade is mandatory
-        every two years.
-      - If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade is mandatory
-        a few weeks after the next version is released. Minor versions are usually released every
-        three months.
-
-   .. group-tab:: Odoo.sh
-
-      After the initial three years of support, you will have another two years to complete the
-      upgrade. You will be notified when an upgrade is required.
-
-      .. image:: upgrade/odoo-sh-message.png
-         :alt: The "unsupported version" popup on Odoo.sh.
-
-   .. group-tab:: On-premise
-
-      You can stay on the same version indefinitely, even if it is not recommended. Note that the
-      smaller the version gap, the easier the upgrade should be.
-
-.. spoiler:: Automatic upgrades: Odoo Online's Rolling Release process
-
-   You will receive a notification in your database a few weeks before a mandatory upgrade will be
-   automatically carried out. You are in control of the process as long as the deadline is not
-   reached.
-
-   .. image:: upgrade/rr-upgrade-message.png
-      :alt: The upgrade message prompt on the top right of the database
-
-   Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every database that should be
-   upgraded. If the test is successful and lasts less than 20 minutes, you can directly trigger the
-   upgrade from the database. If the test fails, you can test an upgrade using the `database manager
-   <https://www.odoo.com/my/databases>`_.
-
-   When you are invited to upgrade, it is strongly recommended to :ref:`request an upgraded test
-   database <upgrade-request-test>` first and spend time :ref:`testing <upgrade-testing>` it.
-
-   An automatic upgrade to the next version will be triggered if no action is taken before the
-   specified due date.
+An upgrade is switching to a newer version of Odoo (e.g., Odoo 14.0 to Odoo 15.0).
 
 An upgrade does not cover:
 
-  - Downgrading to a previous version of Odoo
-  - :doc:`Switching editions <on_premise/community_to_enterprise>` (e.g., from Community to
-    Enterprise)
-  - :ref:`Changing hosting type <hosting/change-solution>` (e.g., from on-premise to Odoo Online)
-  - Migrating from another ERP to Odoo
+* 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 Odoo Online
+  or Odoo.sh)
+* Migration from another ERP to Odoo
 
-.. warning::
-   If your database contains custom modules, it cannot be upgraded until a version of your custom
-   modules is available for the target version of Odoo. For customers maintaining their own custom
-   modules, we recommend to parallelize the process by :ref:`requesting an upgraded database
-   <upgrade-request-test>` while also :doc:`upgrading the source code of your custom
-   modules </developer/howtos/upgrade_custom_db>`.
+.. note:: |assistance-contact|
 
-.. _upgrade-nutshell:
+.. seealso::
+   - :ref:`upgrade/sla`
 
-Upgrading in a nutshell
+.. _upgrade/process-workflow:
+
+Process workflow
+================
+
+The upgrade process in a nutshell:
+
+#. You create a test upgrade request.
+#. Odoo processes the request automatically by running the database through an upgrade script, which
+   takes between 20 and 120 minutes.
+#. 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 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 Odoo Online).
+
+.. seealso::
+   - :doc:`Upgrade process for Odoo Online <upgrade/odoo_online>`
+   - :doc:`Upgrade process for Odoo.sh <upgrade/odoo_sh>`
+   - :doc:`Upgrade process for On-Premise <upgrade/on_premise>`
+
+.. _upgrade/testing-phase:
+
+Testing
+=======
+
+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, :ref:`report your issues <upgrade/test-assistance>` and :ref:`request
+a new test database <upgrade/test-db-request>` when the reported issues are fixed in the upgrade
+script.
+
+If you do not find any discrepancies, you can move on to the upgrade of your production database.
+
+.. important::
+   A test database is only intended for testing and remains completely unrelated to your present or
+   future production database. Any data you add, or changes you make, will not be reflected in your
+   upgraded production database.
+
+.. note::
+   Test databases are neutered and features are disabled to prevent them from having an impact on
+   the production database:
+
+   #. The serial number of the database is modified (to prevent it from sending information as if it
+      was the production database).
+   #. The :ref:`base URL of the database <domain-name/web-base-url>` is reset to
+      ``http://localhost:8069`` and the email domain to ``localhost``.
+   #. Scheduled actions are disabled (the calendar synchronization, the bank statement
+      synchronization, the planned automated actions, the fetching of incoming mail servers, etc.).
+   #. Outgoing mail servers are disabled by archiving the existing ones and adding a
+      fake/non-working one.
+   #. Payment providers and delivery carriers are reset to test environment.
+   #. Accounting localization Electronic Data Interchange (EDI) services are disabled.
+   #. A system parameter is set to tell the database has been neutered.
+
+.. _upgrade/test-db-request:
+
+Request a test database
 =======================
 
-#. Request an upgraded test database (see :ref:`obtaining an upgraded test database
-   <upgrade-request-test>`).
-#. If applicable, upgrade the source code of your custom module to be compatible with the new
-   version of Odoo (see :doc:`/developer/howtos/upgrade_custom_db`).
-#. Thoroughly test the upgraded database (see :ref:`testing the new version of the database
-   <upgrade-testing>`).
-#. Report any issue encountered during the testing to Odoo by going to the `Support page and
-   selecting "An issue related to my future upgrade (I am testing an upgrade)"
-   <https://www.odoo.com/help?stage=migration>`_.
-#. Once all issues are resolved and you are confident that the upgraded database can be used as
-   your main database without any issues, plan the upgrade of your production database.
-#. Request the upgrade for the production database, rendering it unavailable for the time it takes
-   to complete the process (see :ref:`upgrading the production database <upgrade-production>`).
-#. Report any issue encountered during the upgrade to Odoo by going to the `Support page and
-   selecting "An issue related to my upgrade (production)"
-   <https://www.odoo.com/help?stage=post_upgrade>`_.
+Follow the instructions available per hosting type on the `website form
+<https://upgrade.odoo.com>`_ and select *Testing* purpose.
 
-.. _upgrade-request-test:
+.. image:: upgrade/test-purpose.png
+   :align: center
+   :alt: Selection of the "Testing" purpose in the upgrade form on Odoo
 
-Obtaining an upgraded test database
-===================================
+.. _upgrade/test-guidance:
 
-The `Upgrade page <https://upgrade.odoo.com>`_ is the main platform for requesting an upgraded
-database. However, depending on the hosting type, you can upgrade from the command line
-(on-premise), the Odoo Online `database manager <https://www.odoo.com/my/databases>`_, or your
-`Odoo.sh project <https://www.odoo.sh/project>`_.
+Test guidance
+=============
+
+Every business and organization has its own operational needs and has to test its specific Odoo
+database individually. 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:: 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. 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.
 
 .. note::
-   The Upgrade platform follows the same `Privacy Policy <https://www.odoo.com/privacy>`_ as the
-   other Odoo.com services. Visit the `General Data Protection Regulation page
-   <https://www.odoo.com/gdpr>`_ to learn more about how Odoo handles your data and privacy.
-
-.. tabs::
-
-   .. group-tab:: Odoo Online
-
-      Odoo Online databases can be manually upgraded via the `database manager
-      <https://www.odoo.com/my/databases>`_.
-
-      The database manager displays all databases associated with the user's account. Databases
-      not on the most recent version of Odoo display an arrow in a circle icon next to their name,
-      indicating that they can be upgraded.
-
-      .. image:: upgrade/databases-page.png
-         :alt: The database manager with an upgrade button next to the name of a database.
-
-      Click the **arrow in a circle** icon to start the upgrade process. In the popup, fill in:
-
-      - The **version** of Odoo you want to upgrade to, usually the latest version
-      - The **email** address that should receive the link to the upgraded database
-      - The :guilabel:`Purpose` of the upgrade, which is automatically set to :guilabel:`Test` for
-        your first upgrade request
-
-      .. image:: upgrade/upgrade-popup.png
-         :alt: The "Upgrade your database" popup.
-
-      The :guilabel:`Upgrade in progress` tag is displayed next to the database name until
-      completion. Once the process succeeds, an email containing a link to the upgraded test
-      database is sent to the address provided. The database can also be accessed from the database
-      manager by clicking the dropdown arrow before the database name.
-
-      .. image:: upgrade/access-upgraded-db.png
-         :alt: Clicking the menu arrow displays the upgraded test database.
-
-   .. group-tab:: Odoo.sh
-
-      Odoo.sh is integrated with the upgrade platform to simplify the upgrade process.
-
-      .. image:: upgrade/odoo-sh-staging.png
-         :alt: Odoo.sh project and tabs
-
-      The **latest production daily automatic backup** is then sent to the Upgrade platform.
-
-      Once the upgrade platform is done upgrading the backup and uploading it on the branch, it is
-      put in a **special mode**: each time a **commit is pushed** on the branch, a **restore
-      operation** of the upgraded backup and an **update of all the custom modules** occur. This
-      allows you to test your custom modules on a pristine copy of the upgraded database. The log
-      file of the upgrade process can be found in your newly upgraded staging build by going to
-      :file:`~/logs/upgrade.log`.
-
-      .. important::
-         In databases where custom modules are installed, their source code must be up-to-date with
-         the target version of Odoo before the upgrade can be performed. If there are none, the
-         "update on commit" mode is skipped, the upgraded database is built as soon as it is
-         transferred from the upgrade platform, and the upgrade mode is exited.
-
-         Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information.
-
-   .. group-tab:: On-premise
-
-      The standard upgrade process can be initiated by entering the following command line on the
-      machine where the database is hosted:
-
-      .. code-block:: console
-
-         $ python <(curl -s https://upgrade.odoo.com/upgrade) test -d <your db name> -t <target version>
-
-      .. note::
-         This command has some requirements on the environment it runs in:
-
-         - Some external commands that must be provided by the operating system, normally found in
-           any Linux distribution (including WSL). An error will be displayed if one or several of
-           them are missing.
-         - The system user that executes the command needs to be configured with access to the
-           database. Please refer to the PostgreSQL documentation of the `client environment
-           <https://www.postgresql.org/docs/current/libpq-envars.html>`_ or the `client password
-           file <https://www.postgresql.org/docs/current/libpq-pgpass.html>`_ for this requirement.
-         - The script needs to be able to reach one or multiple servers of the upgrade platform
-           both on TCP port 443 and to any random TCP port in the range between 32768 and 60999.
-           This can be in conflict with your restrictive firewall and may need an exception added
-           to the firewall configuration.
-
-      The following command can be used to display the general help and the main commands:
-
-      .. code-block:: console
-
-         $ python <(curl -s https://upgrade.odoo.com/upgrade) --help
-
-      An upgraded test database can also be requested via the `Upgrade page
-      <https://upgrade.odoo.com>`_.
-
-      .. important::
-         In databases where custom modules are installed, their source code must be up-to-date with
-         the target version of Odoo before the upgrade can be performed. Check out the
-         :doc:`/developer/howtos/upgrade_custom_db` page for more information.
-
-      .. note::
-         - For security reasons, only the person who submitted the upgrade request can download it.
-         - For storage reasons, the database's copy is submitted without a filestore to the upgrade
-           server. Therefore, the upgraded database does not contain the production filestore.
-         - Before restoring the upgraded database, its filestore must be merged with the production
-           filestore to be able to perform tests in the same conditions as it would be in the new
-           version.
-         - The upgraded database contains:
-
-           - A `dump.sql` file containing the upgraded database
-           - A `filestore` folder containing files extracted from in-database records into
-             attachments (if there are any) and new standard Odoo files from the targeted Odoo
-             version (e.g., new images, icons, payment provider's logos, etc.).
-             This is the folder that should be merged with the production filestore
-             in order to get the full upgraded filestore.
-
-.. note::
-   You can request multiple test databases if you wish to test an upgrade more than once.
-
-.. note::
-   When an upgrade request is completed, an upgrade report is attached to the successful upgrade
-   email, and it becomes available in the Discuss app for users who are part of the "Administration
-   / Settings" group. This report provides important information about the changes introduced by
-   the new version.
-
-.. _upgrade-testing:
-
-Testing the new version of the database
-=======================================
-
-It is essential to test the upgraded test database to ensure that you are not stuck in your
-day-to-day activities by a change in views, behavior, or an error message once the upgrade goes
-live.
-
-.. note::
-   Test databases are neutralized, and some features are disabled to prevent them from impacting the
-   production database:
-
-   #. Scheduled actions are disabled.
-   #. Outgoing mail servers are disabled by archiving the existing ones and adding a fake one.
-   #. Payment providers and delivery carriers are reset to the test environment.
-   #. Bank synchronization is disabled. Should you want to test the synchronization, contact your
-      bank synchronization provider to get sandbox credentials.
-
-Testing as many of your business flows as possible is strongly recommended to ensure they are
-working correctly and to get more familiar with the new version.
-
-.. admonition:: Basic test checklist
-
-   - Are there views that are deactivated in your test database but active in your production
-     database?
-   - Are your usual views still displayed correctly?
-   - Are your reports (invoice, sales order, etc.) correctly generated?
-   - Are your website pages working correctly?
-   - Are you able to create and modify records? (sales orders, invoices, purchases, users, contacts,
-     companies, etc.)
-   - Are there any issues with your mail templates?
-   - Are there any issues with saved translations?
-   - Are your search filters still present?
-   - Can you export your data?
-
-.. spoiler:: Example of end-to-end testing
-
-   - Checking a random product in your product catalog and comparing its test and production data to
-     verify everything is the same (product category, selling price, cost price, vendor, accounts,
-     routes, etc.).
-   - Buying this product (Purchase app).
-   - Confirming the reception of this product (Inventory app).
-   - Checking if the route to receive this product is the same in your production database
-     (Inventory app).
-   - Selling this product (Sales app) to a random customer.
-   - Opening your customer database (Contacts app), selecting a customer (or company), and checking
-     its data.
-   - Shipping this product (Inventory app).
-   - Checking if the route to ship this product is the same as in your production database
-     (Inventory app).
-   - Validating a customer invoice (Invoicing or Accounting app).
-   - Crediting the invoice (issuing a credit note) and checking if it behaves as in your production
+   * The purpose of the test phase is not to correct existing data or configurations in your
      database.
-   - Checking your reports' results (Accounting app).
-   - Randomly checking your taxes, currencies, bank accounts, and fiscal year (Accounting app).
-   - Making an online order (Website apps) from the product selection in your shop until the
-     checkout process and checking if everything behaves as in your production database.
+   * |assistance-contact|
 
-   This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo.
+.. _upgrade/steps-production:
 
-If you face an issue while testing your upgraded test database, you can request the assistance of
-Odoo by going to the `Support page and selecting "An issue related to my future upgrade (I am
-testing an upgrade)" <https://www.odoo.com/help?stage=migration>`_. In any case, it is essential to
-report any problem encountered during the testing to fix it before upgrading your production
-database.
+The production launch
+=====================
 
-You might encounter significant differences with standard views, features, fields, and models during
-testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced
-by a new version breaks a customization, it is the responsibility of the maintainer of your custom
-module to make it compatible with the new version of Odoo.
+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.
 
-.. tip::
-   Do not forget to test:
-
-   - Integrations with external software (EDI, APIs, etc.)
-   - Workflows between different apps (online sales with eCommerce, converting a lead all the way to
-     a sales order, delivery of products, etc.)
-   - Data exports
-   - Automated actions
-   - Server actions in the action menu on form views, as well as by selecting multiple records on
-     list views
-
-.. _upgrade-production:
-
-Upgrading the production database
-=================================
-
-Once the :ref:`tests <upgrade-testing>` are completed and you are confident that the upgraded
-database can be used as your main database without any issues, it is time to plan the go-live day.
-
-Your production database will be unavailable during its upgrade. Therefore, we recommend planning
-the upgrade at a time when the use of the database is minimal.
-
-As the standard upgrade scripts and your database are constantly evolving, it is also recommended
-to frequently request another upgraded test database to ensure that the upgrade process is still
-successful, especially if it takes a long time to finish. **Fully rehearsing the upgrade process the
-day before upgrading the production database is also recommended.**
+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.
 
 .. important::
    Going into production without first testing may lead to:
 
-   - Users failing to adjust to the changes and new features
-   - Business interruptions (e.g., no longer having the possibility to validate an action)
-   - Poor customer experience (e.g., an eCommerce website that does not work correctly)
+   - 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)
 
-The process of upgrading a production database is similar to upgrading a test database, but with a
-few exceptions.
+.. _upgrade/production-assistance:
 
-.. tabs::
+Assistance
+----------
 
-   .. group-tab:: Odoo Online
+If you encounter issues or problems in the **production database**, please get in touch with **Odoo
+Support**:
 
-      The process is similar to :ref:`obtaining an upgraded test database
-      <upgrade-request-test>`, except for the purpose option, which must be set to
-      :guilabel:`Production` instead of :guilabel:`Test`.
+#. 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*.
 
-      .. warning::
-         Once the upgrade is requested, the database will be unavailable until the upgrade is
-         finished. Once the process is completed, it is impossible to revert to the previous
-         version.
+   .. note::
+      After upgrading to production, the support will be provided by the Support team instead of the
+      Upgrade team.
 
-   .. group-tab:: Odoo.sh
+#. 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.
 
-      The process is similar to :ref:`obtaining an upgraded test database <upgrade-request-test>` on
-      the :guilabel:`Production` branch.
+   .. 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.
 
-      .. image:: upgrade/odoo-sh-prod.png
-         :alt: View from the upgrade tab
+.. _upgrade/assistance:
 
-      The process is **triggered as soon as a new commit is made** on the branch. This
-      allows the upgrade process to be synchronized with the deployment of the custom modules'
-      upgraded source code.
-      If there are no custom modules, the upgrade process is triggered immediately.
+Help
+====
 
-      .. important::
-         The database is unavailable throughout the process. If anything goes wrong, the platform
-         automatically reverts the upgrade, as it would be for a regular update. In case of success,
-         a backup of the database before the upgrade is created.
+.. _upgrade/contact:
 
-      The update of your custom modules must be successful to complete the entire upgrade process.
-      Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in
-      production. More information on how to upgrade your custom modules can be found on
-      :doc:`/developer/howtos/upgrade_custom_db`.
+Contact our upgrade service support
+-----------------------------------
 
-   .. group-tab:: On-premise
+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.
 
-      The command to upgrade a database to production is similar to the one of upgrading a test
-      database except for the argument `test`, which must be replaced by `production`:
+.. _upgrade/supported-versions:
 
-      .. code-block:: console
+Supported versions
+------------------
 
-         $ python <(curl -s https://upgrade.odoo.com/upgrade) production -d <your db name> -t <target version>
+Please note that Odoo provides support and bug fixing only for the three last major versions of
+Odoo.
 
-      An upgraded production database can also be requested via the `Upgrade page
-      <https://upgrade.odoo.com>`_.
+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).
 
-      Once the database is uploaded, any modification to your production database will **not** be
-      present on your upgraded database. This is why we recommend not using it during the upgrade
-      process.
+.. seealso::
+   :doc:`maintain/supported_versions`
 
-      .. important::
-         When requesting an upgraded database for production purposes, the copy is submitted without
-         a filestore. Therefore, the upgraded database filestore must be merged with the production
-         filestore before deploying the new version.
-
-In case of an issue with your production database, you can request the assistance of Odoo by going
-to the `Support page and selecting "An issue related to my future upgrade (I am testing an upgrade)"
-<https://www.odoo.com/help?stage=migration>`_.
-
-.. _upgrade-sla:
+.. _upgrade/sla:
 
 Service-level agreement (SLA)
 =============================
@@ -405,8 +229,6 @@ Information about the upgrade services included in the Enterprise Licence is ava
 :ref:`Odoo Enterprise Subscription Agreement <upgrade>`. However, this section clarifies what
 upgrade services you can expect.
 
-.. _upgrade-sla-covered:
-
 Upgrade services covered by the SLA
 -----------------------------------
 
@@ -422,8 +244,6 @@ benefit from upgrade services at all times for:
 Upgrade services are limited to the technical conversion and adaptation of a database (standard
 modules and data) to make it compatible with the version targeted by the upgrade.
 
-.. _upgrade-sla-not-covered:
-
 Upgrade services not covered by the SLA
 ---------------------------------------
 
@@ -436,6 +256,9 @@ The following upgrade-related services are **not** included:
   <studio/automated-actions/action>`; and
 - **training** on using the upgraded version's features and workflows.
 
+.. note:: |assistance-contact|
+
 .. seealso::
+   - :doc:`Upgrade FAQ <upgrade/faq>`
    - :doc:`Odoo.sh documentation <odoo_sh>`
-   - :doc:`Supported Odoo versions <supported_versions>`
+   - :doc:`Supported Odoo versions <maintain/supported_versions>`

content/administration/upgrade/faq.rst

@@ -0,0 +1,228 @@
+.. |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 to be similar to the
+production upgrade.
+
+.. _upgrade-faq/project:
+
+Duration of 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/upgrade-or-migration:
+
+Upgrade or Migration
+====================
+
+An upgrade is switching to a newer version of Odoo, while a migration reflects the change of
+:ref:`editions <upgrade-faq/editions-change>` or change of :ref:`hosting type
+<upgrade-faq/hosting-types-switch>`.
+
+.. 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::
+    If you need assistance on this matter,  please contact us via the `Odoo Support page
+    <https://www.odoo.com/help>`_.
+
+.. seealso::
+   - `Editions <https://www.odoo.com/page/editions>`_
+
+.. _upgrade-faq/hosting-types-switch:
+
+Switching the hosting types (On-premise vs. Odoo 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
+<../maintain/hosting_changes>`.
+
+.. note:: |assistance-contact|
+
+.. _upgrade-faq/upgrade-report:
+
+The Upgrade Report
+==================
+
+When an upgrade request completes successfully (test or production), you receive an email
+notification about it that includes an 'Upgrade Report'. This report is also sent to you via the
+Discuss app. It contains valuable information regarding changes that occurred during the upgrade.
+While it serves as a guide to possible issues to look out for, it is not an exhaustive list. It
+remains imperative that you test the upgraded database thoroughly and report any discrepancies you
+might find, before you decide to upgrade your production database.
+
+.. _upgrade-faq/custom-views:
+
+Custom views
+============
+
+During the upgrade, some custom views might get disabled for technical reasons. Therefore they might
+have to be fixed after the upgrade. The :ref:`Upgrade Report <upgrade-faq/upgrade-report>` that is
+generated after the upgrade is available in the Discuss app, and lists all the custom views that
+might be impacted by this.
+
+.. _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 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>`_.
+
+Rolling Release (applicable to Odoo Online databases)
+=====================================================
+
+This feature allows customers to upgrade their database directly from a message prompt sent to the
+database administrator as soon as the new version is released. Odoo first tests the upgrade to the
+next version. The rolling release upgrade option is displayed if the automated tests are successful.
+The message offers two options:
+
+#. To 'Upgrade Now', which immediately triggers the upgrade of your live production database.
+
+#. To take you to your `database manager <https://www.odoo.com/my/databases/>`_ where you can
+   `request an upgraded test database <https://upgrade.odoo.com/#online/>`_ and check the upgraded
+   test database for any discrepancies.
+
+When you choose to proceed with the production upgrade directly, make sure all users have saved
+their work and are logged out. The upgrade takes approximately 15 minutes. During this time your
+database is unreachable. If you notice any problem after the upgrade, please report it via the `Odoo
+Support page <https://www.odoo.com/help>`_.
+
+.. note::
+   If you are using the Website or Studio app, we recommend you always do a test upgrade before
+   upgrading your production instance.

content/administration/upgrade/odoo_online.rst

@@ -0,0 +1,92 @@
+===========
+Odoo Online
+===========
+
+Odoo databases can be manually upgraded directly from the main Odoo website. To upgrade an Odoo
+database, navigate to the `database manager <https://www.odoo.com/my/databases>`_ page and sign in.
+
+The database manager page displays all of the Odoo databases associated with the user's account. Any
+databases that are not already on the most recent version of Odoo display an **arrow in a circle**
+icon next to the database name, indicating that the database can be upgraded.
+
+.. image:: odoo_online/databases-page.png
+   :align: center
+   :alt: The database manager page with an upgrade button next to the name of a database.
+
+.. important::
+   - If the database's version is **lower** than the latest major release: the database must be
+     upgraded within two months. After these two months, an automatic upgrade is initiated.
+   - If the database's version is **equal** to or **higher** than the latest major release:
+     you can disregard the invitation to upgrade, as the database probably would not benefit from
+     new features every two months.
+
+If a database is *not* on the latest online version, its administrator should receive an invitation
+to upgrade on the database's dashboard, displayed as an **arrow in a circle**.
+
+.. image:: odoo_online/database-notification.png
+   :alt: Invitation to upgrade on the database dashboard.
+
+.. note::
+   Versions that are not supported anymore become deprecated and must be updated to avoid
+   security issues. It is recommended to initiate the upgrade yourself and not wait for the
+   automatic upgrade, as the former method allows you to request a test upgrade of the database to
+   check for any discrepancies.
+
+Test database
+=============
+
+Click on the **arrow in a circle** icon to start the upgrade process. On the :guilabel:`Upgrade your
+database` pop-up, select the version of Odoo that the platform will be upgraded to. In the
+:guilabel:`Email to notify` field, enter an email address that will receive email notifications
+about the database upgrade.
+
+There is also a :guilabel:`Purpose` section on the pop-up that is used to specify the reason for the
+upgrade. However, at this stage of the process, the only selectable option is :guilabel:`Test`, as
+Odoo requires users to create a test copy of the upgraded database before converting the actual
+database.
+
+.. image:: odoo_online/upgrade-pop-up.png
+   :align: center
+   :alt: The "Upgrade your database" pop-up.
+
+After filling out the form, click the :guilabel:`Upgrade` button. The pop-up disappears and the
+database being upgraded shows a red :guilabel:`Upgrade in progress` tag next to its name. An email
+confirming that the upgrade is in progress is also sent to the email address specified on the
+pop-up.
+
+.. image:: odoo_online/upgrade-in-progress.png
+   :align: center
+   :alt: The "Upgrade in progress" tag next to the database name.
+
+Once the upgrade is complete, a new test database appears on the `database manager
+<https://www.odoo.com/my/databases>`_ page. To access the test database, click the drop-down arrow
+(:guilabel:`⯆`) to the left of the main database's name. Doing so makes the test version appear
+below it. Finally, click the green :guilabel:`Connect` button on the right side of the test
+version's row to go to the database.
+
+.. image:: odoo_online/test-database.png
+   :align: center
+   :alt: A test database on the database manager page.
+
+Except for being on the newer version of Odoo, the test database is an exact copy of the one being
+upgraded. It is important to do extensive testing in this database to ensure that the upgrade has
+not altered or corrupted any data, and that all workflows still proceed as expected.
+
+Production database
+===================
+
+After confirming the integrity of the new version, return to the `database manager
+<https://www.odoo.com/my/databases>`_ page. Once again, click on the **arrow in a circle** icon next
+to the database being upgraded. The :guilabel:`Upgrade your database` pop-up appears as before,
+except that there is now a :guilabel:`Production` option under the :guilabel:`Purpose` section.
+
+Select the :guilabel:`Production` option and then click :guilabel:`Upgrade` to begin the upgrade
+process. As before, a notification email is sent to the email address provided and a red
+:guilabel:`Upgrade in progress` tag appears next to the name of the database.
+
+The production database is then taken offline and will be upgraded automatically. The time it takes
+to upgrade the production database should be similar to the time that was necessary to upgrade the
+test database. Make sure to inform database users of the scheduled downtime.
+
+After the upgrade is finished, the :guilabel:`Upgrade in progress` tag disappears and the database
+is upgraded to the version specified.