[ADD] inventory: packaging

closes odoo/documentation#8024 X-original-commit: a8659727e3 Signed-off-by: Zachary Straub (zst) <zst@odoo.com> Signed-off-by: Felicia Kuan (feku) <feku@odoo.com> Co-authored-by: hojo-odoo <123424465+hojo-odoo@users.noreply.github.com> Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
[FIX] deploy: enable HSTS also for websocket
2024-03-07 02:53:28 +00:00 · 2024-03-06 12:07:41 +00:00 · 2024-03-06 10:33:01 +00:00 · 2024-03-05 17:05:29 +00:00 · 2024-03-04 22:36:31 +00:00 · 2024-03-04 12:21:51 +00:00
4520 changed files with 87635 additions and 497449 deletions
@@ -1,152 +1,63 @@
 [main]
 host = https://www.transifex.com

-[o:odoo:p:odoo-18-doc:r:administration]
-file_filter            = locale/<lang>/LC_MESSAGES/administration.po
-source_file            = locale/sources/administration.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = administration
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
+[o:odoo:p:odoo-16-doc:r:administration]
+file_filter = locale/<lang>/LC_MESSAGES/administration.po
+source_file = locale/sources/administration.pot
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:applications]
-file_filter            = locale/<lang>/LC_MESSAGES/applications.po
-source_file            = locale/sources/applications.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = applications
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
+[o:odoo:p:odoo-16-doc:r:applications]
+file_filter = locale/<lang>/LC_MESSAGES/applications.po
+source_file = locale/sources/applications.pot
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:essentials]
-file_filter            = locale/<lang>/LC_MESSAGES/essentials.po
-source_file            = locale/sources/essentials.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = essentials
-replace_edited_strings = false
-keep_translations      = false
-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
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:finance]
-file_filter            = locale/<lang>/LC_MESSAGES/finance.po
-source_file            = locale/sources/finance.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = finance
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
+[o:odoo:p:odoo-16-doc:r:general]
+file_filter = locale/<lang>/LC_MESSAGES/general.po
+source_file = locale/sources/general.pot
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:general]
-file_filter            = locale/<lang>/LC_MESSAGES/general.po
-source_file            = locale/sources/general.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = general
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
+[o:odoo:p:odoo-16-doc:r:index]
+file_filter = locale/<lang>/LC_MESSAGES/index.po
+source_file = locale/sources/index.pot
+source_lang = en

-[o:odoo:p:odoo-18-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
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
+[o:odoo:p:odoo-16-doc:r:inventory_and_mrp]
+file_filter = locale/<lang>/LC_MESSAGES/inventory_and_mrp.po
+source_file = locale/sources/inventory_and_mrp.pot
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:index]
-file_filter            = locale/<lang>/LC_MESSAGES/index.po
-source_file            = locale/sources/index.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = index
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
+[o:odoo:p:odoo-16-doc:r:marketing]
+file_filter = locale/<lang>/LC_MESSAGES/marketing.po
+source_file = locale/sources/marketing.pot
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:inventory_and_mrp]
-file_filter            = locale/<lang>/LC_MESSAGES/inventory_and_mrp.po
-source_file            = locale/sources/inventory_and_mrp.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = inventory_and_mrp
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
+[o:odoo:p:odoo-16-doc:r:productivity]
+file_filter = locale/<lang>/LC_MESSAGES/productivity.po
+source_file = locale/sources/productivity.pot
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:marketing]
-file_filter            = locale/<lang>/LC_MESSAGES/marketing.po
-source_file            = locale/sources/marketing.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = marketing
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
+[o:odoo:p:odoo-16-doc:r:sales]
+file_filter = locale/<lang>/LC_MESSAGES/sales.po
+source_file = locale/sources/sales.pot
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:productivity]
-file_filter            = locale/<lang>/LC_MESSAGES/productivity.po
-source_file            = locale/sources/productivity.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = productivity
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
+[o:odoo:p:odoo-16-doc:r:services]
+file_filter = locale/<lang>/LC_MESSAGES/services.po
+source_file = locale/sources/services.pot
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:sales]
-file_filter            = locale/<lang>/LC_MESSAGES/sales.po
-source_file            = locale/sources/sales.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = sales
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
+[o:odoo:p:odoo-16-doc:r:user_settings]
+file_filter = locale/<lang>/LC_MESSAGES/settings.po
+source_file = locale/sources/settings.pot
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:services]
-file_filter            = locale/<lang>/LC_MESSAGES/services.po
-source_file            = locale/sources/services.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = services
-replace_edited_strings = false
-keep_translations      = false
-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
+source_lang = en

-[o:odoo:p:odoo-18-doc:r:user_settings]
-file_filter            = locale/<lang>/LC_MESSAGES/settings.po
-source_file            = locale/sources/settings.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = settings
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
-
-[o:odoo:p:odoo-18-doc:r:studio]
-file_filter            = locale/<lang>/LC_MESSAGES/studio.po
-source_file            = locale/sources/studio.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = studio
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
-
-[o:odoo:p:odoo-18-doc:r:websites]
-file_filter            = locale/<lang>/LC_MESSAGES/websites.po
-source_file            = locale/sources/websites.pot
-type                   = POT
-minimum_perc           = 0
-resource_name          = websites
-replace_edited_strings = false
-keep_translations      = false
-source_lang            = en
@@ -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)/master
+  HTML_BUILD_DIR := $(HTML_BUILD_DIR)/saas-16.1
 endif
 ifneq ($(CURRENT_LANG),en)
  HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)
@@ -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

@@ -21,8 +21,8 @@ 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 a/b/rc tags. Acts as replacement for |release|.
-version = release = 'master'
+# `release` is the full version, including alpha/beta/rc tags. Acts as replacement for |release|.
+version = release = 'saas-16.1'

 # `current_branch` is the technical name of the current branch.
 # E.g., saas-15.4 -> saas-15.4; 12.0 -> 12.0, master -> master (*).
@@ -116,7 +116,7 @@ else:
    odoo.addons.__path__.append(str(odoo_dir) + '/addons')
    from odoo import release as odoo_release  # Don't collide with Sphinx's 'release' config option
    odoo_version = '.'.join(str(s) for s in odoo_release.version_info[:2]).replace('~', '-')  # Change saas~XX.Y to saas-XX.Y
-    odoo_version = 'master' if odoo_release.ALPHA in odoo_release.version_info else odoo_version
+    odoo_version = 'master' if 'alpha' in odoo_release.version else odoo_version
    if release != odoo_version:
        _logger.warning(
            "Found Odoo sources in %(directory)s but with version '%(odoo_version)s' incompatible "
@@ -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,13 +213,16 @@ 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",
-    'saas-18.1': "Odoo Online",
-    '18.0': "Odoo 18",
-    'saas-17.4': "Odoo Online",
-    'saas-17.2': "Odoo Online",
+    'saas-17.1': "Odoo Online",
    '17.0': "Odoo 17",
+    'saas-16.4': "Odoo Online",
+    '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",
 }

 # The language names that should be shown in the language switcher, if the config option `languages`
@@ -246,19 +231,11 @@ languages_names = {
    'de': 'DE',
    'en': 'EN',
    'es': 'ES',
-    'es_419': 'ES (LATAM)',
    'fr': 'FR',
-    'id': 'ID',
    'it': 'IT',
-    'ja': 'JA',
-    'ko': 'KR',
    'nl': 'NL',
    'pt_BR': 'PT',
-    'ro': 'RO',
-    'sv': 'SV',
-    'th': 'TH',
    'uk': 'UA',
-    'vi': 'VI',
    'zh_CN': 'ZH (CN)',
    'zh_TW': 'ZH (TW)'
 }
@@ -269,9 +246,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'
@@ -392,9 +366,6 @@ def setup(app):
    app.add_config_value('is_remote_build', None, 'env')  # Whether the build is remotely deployed
    app.add_config_value('source_read_replace_vals', {}, 'env')
    app.connect('source-read', source_read_replace)
-    # TODO uncomment after moving to >= v7.2.5 to also substitute placeholders in included  files.
-    #  See https://github.com/sphinx-doc/sphinx/commit/ff1831
-    #  app.connect('include-read', source_read_replace)

    app.add_lexer('json', JsonLexer)
    app.add_lexer('xml', XmlLexer)
@@ -474,7 +445,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
@@ -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
@@ -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.
@@ -0,0 +1,50 @@
+:show-content:
+
+=======
+Install
+=======
+
+Depending on the intended use case, there are multiple ways to install Odoo - or not install it at
+all.
+
+- :doc:`Online <install/online>` is the easiest way to use Odoo in production or to try it.
+
+- :doc:`Packaged installers <install/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 <install/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 <maintain/enterprise>` at any time (except for the
+   source install).
+
+.. toctree::
+
+   install/online
+   install/packages
+   install/source
+   install/deploy
+   install/cdn
+   install/email_gateway
+   install/geo_ip
@@ -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
@@ -3,13 +3,13 @@ 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
+internet-facing server. It follows :doc:`installation <../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!

-.. _dbfilter:
+.. _db_filter:

 dbfilter
 ========
@@ -573,12 +573,12 @@ security-related topics:

 - Use appropriate database filters ( :option:`--db-filter <odoo-bin --db-filter>`)
  to restrict the visibility of your databases according to the hostname.
-  See :ref:`dbfilter`.
+  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 ``dbfilter`` are configured and only match a single database
+- 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>`
@@ -722,7 +722,7 @@ management screens.
  the system administrator, including provisioning of new databases and automated backups.

 Be sure to setup an appropriate ``db_name`` parameter
-(and optionally, ``dbfilter`` too) so that the system can determine the target database
+(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.

@@ -740,143 +740,7 @@ It should be stored securely, and should be generated randomly e.g.

    $ 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`.
+which will generate a 32 characters pseudorandom printable string.

 Supported Browsers
 ==================
@@ -33,6 +33,7 @@ In you alias config (:file:`/etc/aliases`):
   - `Postfix aliases <http://www.postfix.org/aliases.5.html>`_
   - `Postfix virtual <http://www.postfix.org/virtual.8.html>`_

+
 For Exim
 --------

@@ -46,5 +47,5 @@ For Exim
   - `Exim <https://www.exim.org/docs.html>`_

 .. tip::
-   If you do not have access/manage your email server, use :ref:`incoming mail servers
-   <email-inbound-custom-domain-incoming-server>`.
+   If you don't have access/manage your email server, use :ref:`inbound messages
+   <email_communication/inbound_messages>`.
@@ -0,0 +1,21 @@
+======
+Online
+======
+
+Online instances are accessed using any web browser and do not require a local installation.
+
+Demo
+----
+
+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.
+
+Odoo Online
+-----------
+
+`Odoo Online <https://www.odoo.com/trial>`_ provides private instances 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.
@@ -132,7 +132,7 @@ be downloaded from the `Odoo download page <https://www.odoo.com/page/download>`
   .. group-tab:: Fedora

      .. note::
-         Odoo {CURRENT_MAJOR_VERSION} 'rpm' package supports Fedora 38.
+         Odoo {CURRENT_MAJOR_VERSION} 'rpm' package supports Fedora 36.

      Once downloaded, the package can be installed using the 'dnf' package manager:

@@ -1,6 +1,6 @@
-==============
-Source install
-==============
+======
+Source
+======

 The source 'installation' is not about installing Odoo but running it directly from the source
 instead.
@@ -45,7 +45,7 @@ Git

 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/server_framework_101>`.
+Started developer tutorial </developer/tutorials/getting_started>`.

 .. tabs::

@@ -118,11 +118,7 @@ Prepare
 Python
 ~~~~~~

-Odoo requires **Python 3.10** or later to run.
-
-.. versionchanged:: 17
-    Minimum requirement updated from Python 3.7 to Python 3.10.
-
+Odoo requires **Python 3.7** or later to run.

 .. tabs::

@@ -144,7 +140,7 @@ Odoo requires **Python 3.10** or later to run.
      to download and install Python 3 if needed.

 .. note::
-   If Python 3 is already installed, make sure that the version is 3.10 or above, as previous
+   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::
@@ -277,22 +273,18 @@ Dependencies

         .. 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 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.
+               $ cd /CommunityPath
+               $ sed -n -e '/^Depends:/,/^Pre/ s/ python3-\(.*\),/python3-\1/p' debian/control | sudo xargs apt-get install -y

         .. 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.

@@ -483,7 +475,7 @@ http://localhost:8069 in a web browser and log into the Odoo database with the b
 account: use `admin` as the email and, again, `admin` as the password.

 .. tip::
-   - From there, create and manage new :doc:`users <../../applications/general/users>`.
+   - From there, create and manage new :doc:`users <../../applications/general/users/manage_users>`.
   - The user account used to log into Odoo's web interface differs from the :option:`--db_user
     <odoo-bin -r>` CLI argument.

@@ -0,0 +1,19 @@
+: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/neutralized_database
+    maintain/supported_versions
@@ -12,7 +12,7 @@ personal email address or an address created by a custom domain.
   <https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app>`_

 .. seealso::
-   - :doc:`/applications/general/users/azure`
+   - :doc:`/applications/general/auth/azure`
   - :doc:`/applications/productivity/calendar/outlook`

 Setup in Microsoft Azure Portal
@@ -34,14 +34,14 @@ registration`. On the :guilabel:`Register an application` screen, rename the :gu
 and personal Microsoft accounts (e.g. Skype, Xbox)`.

 Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input
-`https://<web base url>/microsoft_outlook/confirm` in the :guilabel:`URL` field. The `web.base.url`
-is subject to change depending on the URL used to log in to the database.
+`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.

-.. note::
-   The documentation about the :ref:`web.base.url <domain-name/web-base-url>` explains how to freeze
-   a unique URL. It is also possible to add different redirect URLs on the Microsoft app.
+.. 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.
+After the URL has been added to the field, :guilabel:`Register` the application so it is created.

 API permissions
 ---------------
@@ -165,7 +165,7 @@ Then, create a new email server and check the box for :guilabel:`Outlook`. Next,
 :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-outbound-unique-address>`.
+<email_communication/default>`.

 Then, click on :guilabel:`Connect your Outlook account`.

@@ -203,8 +203,7 @@ This address must also match the `{mail.default.from}@{mail.catchall.domain}` ke
 system parameters.

 .. seealso::
-   Visit the :ref:`From Filtering documentation <email-outbound-different-servers-personalized-from-filtering>` for more
-   information.
+   For more information on the from filter visit: :ref:`email_communication/default`.

 .. note::
   The :guilabel:`System Parameters` can be accessed by activating :ref:`developer-mode` in the
@@ -245,8 +244,7 @@ so that only the user's email is sent from that server. In other words, only a u
 address that matches the set :guilabel:`FROM Filtering` is able to use this server.

 .. seealso::
-   Visit the :ref:`From Filtering documentation <email-outbound-different-servers-personalized-from-filtering>` for more
-   information.
+   For more information on the from filter visit: :ref:`email_communication/default`.

 A :ref:`fallback server <azure_oauth/notifications>` must be setup to allow for the sending of
 :guilabel:`notifications`. The :guilabel:`FROM Filtering` for this server should have the value of
@@ -263,7 +261,7 @@ the `{mail.default.from}@{mail.catchall.domain}`.

   .. seealso::
      For more information on setting the mass-mailing email server visit
-      :ref:`email-outbound-custom-domain-smtp-server`.
+      :ref:`email_communication/mass_mails`.

 .. example::
   Multiple user outgoing mail server configuration:
@@ -290,3 +288,6 @@ new configuration. Check or Select the button next to :guilabel:`Outlook Oauth A
 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`
@@ -37,13 +37,12 @@ Search for the desired domain name and check its availability.
   Ensure the Website app is installed if the domain name registration option does not appear.

 Select the desired domain name, fill in the :guilabel:`Domain Owner` form, and click
-:guilabel:`Register`. The chosen domain name is directly linked to the database.
+:guilabel:`Register`. The chosen domain name is directly linked to the database, but you still need
+to :ref:`map your domain name to your Odoo website <domain-name/db-map>`.

 .. image:: domain_names/domain-owner.png
   :alt: Filling in the domain owner information

-Next, you should :ref:`map your domain name to your Odoo website <domain-name/website-map>`.
-
 .. important::
   A verification email from `noreply@domainnameverification.net` will be sent to the email address
   provided in the :guilabel:`Domain Owner` form. It is essential to verify your email address to
@@ -113,8 +112,8 @@ Then, add the alias domain as your *own domain* by clicking :guilabel:`Use my ow
 the alias domain (e.g., `subdomain.yourdomain.com`), clicking :guilabel:`Verify`, and then
 :guilabel:`I confirm, it's done`.

-Finally, go to your database and open the :guilabel:`Settings`. Under the :guilabel:`Alias Domain`
-field, enter the alias domain (e.g., `subdomain.yourdomain.com`), click :guilabel:`Create`, and then
+Finally, go to your database and open the :guilabel:`Settings`. Enable :guilabel:`Custom Email
+Servers` field, enter the :guilabel:`Alias Domain` (e.g., `subdomain.yourdomain.com`) and click
 :guilabel:`Save`.

 Use an external email provider
@@ -150,7 +149,8 @@ If you already have a domain name, you can use it for your Odoo website.
 Add a CNAME record
 ------------------

-Adding a CNAME record to forward your domain name to the address of your Odoo database is required.
+Creating a CNAME record to forward your domain name to the address of your Odoo database is
+required.

 .. tabs::

@@ -161,7 +161,7 @@ Adding a CNAME record to forward your domain name to the address of your Odoo da

   .. group-tab:: Odoo.sh

-      The CNAME record's target address should be the project's main address, which can be found on
+      The CNAME record's target address can be the project's main address, which can be found on
      Odoo.sh by going to :menuselection:`Settings --> Project Name`, or a specific branch
      (production, staging or development) by going to :menuselection:`Branches --> select the
      branch --> Settings --> Custom domains`, and clicking :guilabel:`How to set up my domain?`. A
@@ -174,83 +174,21 @@ The specific instructions depend on your DNS hosting service.
   - `Namecheap: How to create a CNAME record for your domain <https://www.namecheap.com/support/knowledgebase/article.aspx/9646/2237/how-to-create-a-cname-record-for-your-domain>`_
   - `OVHcloud: Add a new DNS record <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/#add-a-new-dns-record>`_
   - `Cloudflare: Manage DNS records
-     <https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/>`_
+     <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_

-.. important::
-   Odoo only supports subdomains. To use your naked domain name :dfn:`(a domain name without any
-   subdomains or prefixes)` (`yourdomain.com`), create a redirection 301 to redirect visitors to
-   `www.yourdomain.com`.
+Creating a CNAME record to map the `www` subdomain (`www.yourdomain.com`) as some visitors are used
+to typing `www.` before entering a domain name.

 .. example::
   You own the domain name `yourdomain.com`, and your Odoo Online database's address is
   `mycompany.odoo.com`. You want to access your Odoo database primarily with the domain
-   `www.yourdomain.com` and also with the naked domain `yourdomain.com`.
+   `www.yourdomain.com` but also with the naked domain :dfn:`(a domain name without any subdomains
+   or prefixes)` `yourdomain.com`.

-   To do so, create a CNAME record for the `www` subdomain, with `mycompany.odoo.com` as the target.
-   Next, create a redirect (301 permanent or visible redirect) to redirect visitors from
+   To do so, create a CNAME record for the `www` subdomain, with `mycompany.odoo.com` as the
+   target. Next, create a redirect (301 permanent or visible redirect) to redirect visitors from
   `yourdomain.com` to `wwww.yourdomain.com`.

-Using Cloudflare to secure and redirect a naked domain
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To redirect a naked domain with a secure HTTPS connection, we recommend using Cloudflare, as most
-DNS hosting services do not offer an easy way to do so.
-
-#. `Sign up and log in to Cloudflare <https://dash.cloudflare.com/sign-up>`_.
-#. Enter your domain name on `Cloudflare's dashboard <https://dash.cloudflare.com/login>`_ and
-   select :guilabel:`Quick scan for DNS records`.
-#. Choose a plan (the free plan is sufficient).
-#. Follow Cloudflare's instructions and recommendations to complete the activation.
-#. Add a CNAME record to redirect your naked domain (`yourdomain.com`) to the `www` subdomain
-   (e.g., `www.yourdomain.com`) by clicking :guilabel:`DNS` in the navigation menu, then clicking
-   the :guilabel:`Add record` button, and using the following configuration:
-
-   - :guilabel:`Type`: CNAME
-   - :guilabel:`Name`: `@` (or `yourdomain.com`)
-   - :guilabel:`Target`: e.g., `www.yourdomain.com`
-   - :guilabel:`Proxy status`: Proxied
-
-   .. image:: domain_names/cloudflare-cname-www.png
-      :alt: Adding a CNAME DNS record to Cloudflare to redirect a naked domain to a www subdomain
-
-#. Add another second CNAME record to redirect the `www` subdomain (e.g., `www.yourdomain.com`) to
-   your database address (e.g., `mycompany.odoo.com`) using the following configuration:
-
-   - :guilabel:`Type`: CNAME
-   - :guilabel:`Name`: e.g., `www.yourdomain.com`
-   - :guilabel:`Target`: e.g., `mycompany.odoo.com`
-   - :guilabel:`Proxy status`: DNS only
-
-   .. image:: domain_names/cloudflare-cname-db.png
-      :alt: Adding a CNAME DNS record to Cloudflare to redirect a www subdomain to an Odoo database
-
-#. Define a redirect rule to permanently redirect (301) your naked domain (e.g., `yourdomain.com`)
-   to both `http://` and `https://` by going to :menuselection:`Rules --> Redirect Rules --> Create
-   rule`, and:
-
-   - Enter any :guilabel:`Rule name`.
-   - Under the :guilabel:`If incoming requests match...` section, select :guilabel:`Custom filter
-     expression` and use the following configuration:
-
-     - :guilabel:`Field`: Hostname
-     - :guilabel:`Operator`: equals
-     - :guilabel:`Value`: e.g., `yourdomain.com`
-
-   - Under the :guilabel:`Then...` section, use the following configuration:
-
-     - :guilabel:`Type`: Dynamic
-     - :guilabel:`Expression`: e.g., `concat("https://www.yourdomain.com/", http.request.uri.path)`
-     - :guilabel:`Status code`: 301
-     - :guilabel:`Preserve query string`: enabled
-
-   .. image:: domain_names/cloudflare-redirect-rule.png
-      :alt: Defining a Cloudflare redirect rule to create a permanent redirect (301)
-
-#. Go to :guilabel:`SSL/TLS` and set the encryption mode to :guilabel:`Full`.
-
-   .. image:: domain_names/cloudflare-encryption.png
-      :alt: Setting the encryption mode to full on Cloudflare
-
 .. _domain-name/db-map:

 Map a domain name to an Odoo database
@@ -274,8 +212,8 @@ Map a domain name to an Odoo database

      Open the `database manager <https://www.odoo.com/my/databases>`_, click the gear icon
      (:guilabel:`⚙️`) next to the database name, and go to :menuselection:`Domain Names --> Use my
-      own domain`. Then, enter the domain name (e.g., `www.yourdomain.com`), click
-      :guilabel:`Verify` and :guilabel:`I confirm, it's done`.
+      own domain`. Then, enter the domain name (e.g., `yourdomain.com`), click :guilabel:`Verify`
+      and :guilabel:`I confirm, it's done`.

      .. image:: domain_names/map-database-online.png
         :alt: Mapping a domain name to an Odoo Online database
@@ -330,7 +268,7 @@ To make your custom domain name the *web base URL* of your database, access your
 custom domain name and log in as an administrator :dfn:`(a user part of the Settings access right
 group under Administration)`.

-.. important::
+.. warning::
   If you access your database with the original Odoo address (e.g., `mycompany.odoo.com`), the *web
   base URL* of your database will be updated accordingly. To prevent the automatic update of the
   *web base URL* when an administrator logs in to the database, activate the :ref:`developer mode
@@ -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 :doc:`../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
@@ -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
@@ -0,0 +1,111 @@
+=======================
+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 <duplicate_premise>` of the database.
+#. 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>` cannot be hosted on-premise as
+   that type of hosting does not support those versions. 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.
+
+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.
@@ -18,6 +18,7 @@ page. Next, navigate to the :guilabel:`Senders & Domains` section and click on :
 SEND API Settings`.

 .. image:: mailjet_api/api-settings.png
+   :align: center
   :alt: SMTP and Send API Settings link in the Senders & Domains section of Mailjet.

 Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration settings onto a notepad.
@@ -32,10 +33,11 @@ port number. The settings are needed to configure Mailjet in Odoo, which is cove
   <https://documentation.mailjet.com/hc/articles/360043229473>`_

 .. important::
-   Odoo :ref:`blocks port 25 <email-outbound-port-restriction>` on Odoo Online and Odoo.sh
-   databases.
+   Odoo blocks `port 25` on Odoo Online and Odoo.sh databases. :ref:`See reference here
+   <email_servers/restriction>`.

 .. image:: mailjet_api/smtp-config.png
+   :align: center
   :alt: SMTP configuration from Mailjet.

 Next, click on the button labeled :guilabel:`Retrieve your API credentials` to retrieve the Mailjet
@@ -55,6 +57,7 @@ email address or domain is approved to send emails using Mailjet's servers. Firs
 :guilabel:`Add a Sender Domain or Address` link under the :guilabel:`Senders & Domains` section.

 .. image:: mailjet_api/add-domain-email.png
+   :align: center
   :alt: Add a sender domain or address in the Mailjet interface.

 Determine if a sender's email address or the entire domain needs to be added to the Mailjet
@@ -122,6 +125,7 @@ Copy the TXT record information to a notepad and then navigate to the domain's :
 Name System)` provider to complete validation.

 .. image:: mailjet_api/host-value-dns.png
+   :align: center
   :alt: The TXT record information to input on the domain's DNS.

 Setup in the domain's DNS
@@ -147,6 +151,7 @@ Next, click :guilabel:`Check Now` to validate the TXT record that was added on t
 success screen will appear if the domain is configured correctly.

 .. image:: mailjet_api/check-dns.png
+   :align: center
   :alt: Check DNS record in Mailjet.

 After successfully setting up the domain, there is an option to :guilabel:`Authenticate this domain
@@ -158,6 +163,7 @@ Identified Mail) records to input into the :abbr:`DNS (Domain Name System)` prov
   360042412734-Authenticating-Domains-with-SPF-DKIM>`_

 .. image:: mailjet_api/authenticate.png
+   :align: center
   :alt: Authenticate the domain with SPF/DKIM records in Mailjet.

 .. _maintain/mailjet-api/odoo-setup:
@@ -185,4 +191,28 @@ than that of any transactional email server(s). Finally, save the settings and :
 Connection`.

 .. image:: mailjet_api/server-settings.png
+   :align: center
   :alt: Odoo outgoing email server settings.
+
+.. important::
+   In order for the notifications feature to work using Mailjet, there are three settings that need
+   to be set in Odoo.
+
+   #. The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended
+      to set it as a domain and not a full email address. It should match the domain in the two
+      proceeding steps. More information can be referenced :ref:`here
+      <email_communication/from_filter>`.
+   #. The :guilabel:`mail.default.from` system parameter must have the value
+      `notifications\@yourdomain.com`.
+   #. The :guilabel:`mail.default.from_filter` system parameter must have the value
+      `yourdomain.com`. Replace `yourdomain` with the custom domain for the Odoo database. If there
+      isn't one, then use the :guilabel:`mail.catchall.domain` system parameter.
+
+   For more information see :ref:`Using a default email address <email_communication/default>`.
+
+   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!
@@ -21,7 +21,7 @@ turned into a testing environment.
 Deactivated features
 ====================

-Here is a non-exhaustive list of the deactivated features:
+Here is a non-exhaustive list of the deactivated parameters:

 - all planned actions (e.g., automatic invoicing of subscriptions, mass mailing, etc.)
 - outgoing emails
@@ -29,7 +29,6 @@ Here is a non-exhaustive list of the deactivated features:
 - 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
@@ -1,21 +1,6 @@
-===========
-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
-===================
+===============================
+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.
@@ -46,7 +31,7 @@ Trigger a database upgrade.

 .. seealso::
   For more information about the upgrade process, check out the :ref:`Odoo Online upgrade
-   documentation <upgrade-request-test>`.
+   documentation <upgrade/request-test-database>`.

 .. _odoo_online/duplicate:

@@ -60,8 +45,6 @@ daily operations.
   - 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:

@@ -86,8 +69,7 @@ Download a ZIP file containing a backup of the database.
 Domain names
 ============

-Use a custom :doc:`domain name </applications/websites/website/configuration/domain_names>` to
-access the database via another URL.
+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/register>`.
@@ -147,5 +129,5 @@ users, click :guilabel:`Add more users`.
 To remove users, select them and click :guilabel:`Remove`.

 .. seealso::
-   - :doc:`/applications/general/users`
-   - :doc:`odoo_accounts`
+   - :doc:`/applications/general/users/manage_users`
+   - :doc:`/applications/general/users/odoo_account`
@@ -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
@@ -0,0 +1,131 @@
+: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 saas~17.1
+     - |green|
+     - N/A
+     - N/A
+     - January 2024
+     -
+   * - **Odoo 17.0**
+     - |green|
+     - |green|
+     - |green|
+     - November 2023
+     - October 2026 (planned)
+   * - Odoo saas~16.4
+     - |green|
+     - N/A
+     - N/A
+     - August 2023
+     -
+   * - Odoo saas~16.3
+     - |red|
+     - N/A
+     - N/A
+     - June 2023
+     -
+   * - Odoo saas~16.2
+     - |red|
+     - N/A
+     - N/A
+     - March 2023
+     -
+   * - Odoo saas~16.1
+     - |red|
+     - N/A
+     - N/A
+     - February 2023
+     -
+   * - **Odoo 16.0**
+     - |green|
+     - |green|
+     - |green|
+     - October 2022
+     - November 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
+     - November 2024 (planned)
+   * - **Odoo 14.0**
+     - |red|
+     - |red|
+     - |red|
+     - October 2020
+     - November 2023
+   * - **Odoo 13.0**
+     - |red|
+     - |red|
+     - |red|
+     - October 2019
+     - October 2022
+   * - Older versions
+     - |red|
+     - |red|
+     - |red|
+     - Before 2019
+     - Before 2022
+
+.. 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>
@@ -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 :doc:`installation guide <../install>`,
 which explains the common installation methods.

 Updating is also most appropriately accomplished by the person who deployed Odoo initially,
@@ -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 SSO authentication.
@@ -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`
@@ -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'
@@ -402,9 +402,9 @@ we are considering the feature if there is enough demand.

 In case the domain of your users email addresses use SPF (Sender Policy Framework) or DKIM
 (DomainKeys Identified Mail), don't forget to authorize Odoo as a sending host in your domain name
-settings to increase the deliverability of your outgoing emails. The configuration steps are
-explained in the documentation about :ref:`SPF <email-domain-spf>` and :ref:`DKIM
-<email-domain-dkim>`.
+settings to increase the deliverability of your outgoing emails.
+The configuration steps are explained in the documentation about :ref:`SPF
+<email_communication/spf_compliant>` and :ref:`DKIM <email_communication/dkim_compliant>`.

 .. Warning::
  Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host can lead to the
@@ -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.
@@ -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 :doc:`installation of Odoo <../../install/source>`:

 .. code-block:: bash

@@ -146,7 +146,7 @@ Manually
 --------

 If you want to create your module structure manually,
-you can follow the :doc:`/developer/tutorials/server_framework_101` tutorial to understand
+you can follow the :doc:`/developer/tutorials/getting_started` tutorial to understand
 the structure of a module and the content of each file.

 Push the development branch
@@ -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
 ==============

@@ -1,117 +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 `80`
-  - Odoo 17.0 and below: `services.openerp.com` on port `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.
-
-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
@@ -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
@@ -1,107 +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 SaaS 18.1
-     - |green|
-     - N/A
-     - N/A
-     - January 2025
-     -
-   * - **Odoo 18.0**
-     - |green|
-     - |green|
-     - |green|
-     - October 2024
-     - October 2027 (planned)
-   * - Odoo SaaS 17.4
-     - |red|
-     - N/A
-     - N/A
-     - July 2024
-     - October 2024
-   * - Odoo SaaS 17.2
-     - |red|
-     - N/A
-     - N/A
-     - April 2024
-     - October 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>
@@ -2,102 +2,83 @@
 Upgrade
 =======

-An upgrade involves moving a database from an older version to a newer supported version (e.g., from
-Odoo 16.0 to Odoo 18.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.
+.. _administration/upgrade:

-Depending on the hosting type and Odoo version used, a database upgrade can be **mandatory**.
+An upgrade is the process of moving your database from an older version to a newer :doc:`supported
+version <maintain/supported_versions>` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is
+essential as each version comes with new and improved features, bug fixes, and security patches.

-.. tabs::
-
-   .. group-tab:: Odoo Online
-
-      - If a database is on a **major version** (e.g., 16.0, 17.0, 18.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
-        two 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.
+.. _upgrade_faq/rolling_release:

 .. 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.
+   The Rolling Release process allows Odoo Online customers to upgrade their database directly from
+   a message prompt sent to the database administrator as soon as a new version is released. The
+   invitation to upgrade is only sent if no issues are detected during the automatic tests.

   .. 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>`_.
+   It is strongly recommended to manually :ref:`test the upgrade first <upgrade/test_your_db>`.
+   Clicking :guilabel:`I want to test first` redirects to `the database manager
+   <https://www.odoo.com/my/databases/>`_, where it is possible to request an upgraded test database
+   and check it for any discrepancies.

-   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.
+   It is **not** recommended to click :guilabel:`Upgrade Now` without testing first, as it
+   immediately triggers the live production database upgrade.

-   An automatic upgrade to the next version will be triggered if no action is taken before the
-   specified due date.
+   If the Rolling Release process detects an issue with the upgrade, it will be deactivated until
+   the issue is resolved.

 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)
+  - :doc:`Switching editions <maintain/enterprise>` (e.g., from Community to Enterprise)
+  - :doc:`Changing hosting type </administration/maintain/hosting_changes>` (e.g., from on-premise
+    to Odoo Online)
  - Migrating 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
+   <upgrade/request-test-database>` while also :doc:`upgrading the source code of your custom
   modules </developer/howtos/upgrade_custom_db>`.

-.. _upgrade-nutshell:

 Upgrading in a nutshell
-=======================
+-----------------------

 #. Request an upgraded test database (see :ref:`obtaining an upgraded test database
-   <upgrade-request-test>`).
+   <upgrade/request-test-database>`).
+
 #. 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>`_.
+   <upgrade/test_your_db>`).
+
+#. Report any issue encountered during the testing to Odoo via the `support page
+   <https://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>`_.

-.. _upgrade-request-test:
+#. 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/upgrade-prod>`).
+
+#. Report any issue encountered during the upgrade to Odoo via the `support page
+   <https://odoo.com/help?stage=post_upgrade>`__.
+
+.. _upgrade/request-test-database:

 Obtaining an upgraded test database
-===================================
+-----------------------------------

-The `Upgrade page <https://upgrade.odoo.com>`_ is the main platform for requesting an upgraded
+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>`_.
+(on-premise), the `Odoo Online database manager <https://odoo.com/my/databases>`_, or your `Odoo.sh
+project <https://odoo.sh/project>`_.

 .. note::
   The Upgrade platform follows the same `Privacy Policy <https://www.odoo.com/privacy>`_ as the
@@ -109,7 +90,7 @@ database. However, depending on the hosting type, you can upgrade from the comma
   .. group-tab:: Odoo Online

      Odoo Online databases can be manually upgraded via the `database manager
-      <https://www.odoo.com/my/databases>`_.
+      <https://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,
@@ -143,7 +124,8 @@ database. However, depending on the hosting type, you can upgrade from the comma
      .. 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.
+      The **latest production daily automatic backup** is then sent to the `upgrade platform
+      <https://upgrade.odoo.com>`_.

      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
@@ -169,21 +151,6 @@ database. However, depending on the hosting type, you can upgrade from the comma

         $ 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
@@ -191,7 +158,7 @@ database. However, depending on the hosting type, you can upgrade from the comma
         $ 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>`_.
+      <https://upgrade.odoo.com/>`_.

      .. important::
         In databases where custom modules are installed, their source code must be up-to-date with
@@ -217,20 +184,22 @@ database. However, depending on the hosting type, you can upgrade from the comma
 .. note::
   You can request multiple test databases if you wish to test an upgrade more than once.

+.. _upgrade/upgrade_report:
+
 .. 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:
+.. _upgrade/test_your_db:

 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.
+It is essential to spend some time testing 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
@@ -285,10 +254,9 @@ working correctly and to get more familiar with the new version.
   This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo.

 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.
+Odoo via the `support page <https://odoo.com/help?stage=migration>`__ by selecting the option
+related to testing the upgrade. In any case, it is essential to report any
+problem encountered during the testing to fix it before upgrading your production database.

 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
@@ -306,38 +274,40 @@ module to make it compatible with the new version of Odoo.
   - Server actions in the action menu on form views, as well as by selecting multiple records on
     list views

-.. _upgrade-production:
+.. _upgrade/upgrade-prod:

 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.
+Once the :ref:`tests <upgrade/test_your_db>` 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. It
+can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page
+<https://odoo.com/help>`__.

 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.**
+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.**

 .. important::
-   Going into production without first testing may lead to:
+   - 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)
+     - 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)

-The process of upgrading a production database is similar to upgrading a test database, but with a
-few exceptions.
+The process of upgrading a production database is similar to upgrading a test database with a few
+exceptions.

 .. tabs::

   .. group-tab:: Odoo Online

      The process is similar to :ref:`obtaining an upgraded test database
-      <upgrade-request-test>`, except for the purpose option, which must be set to
+      <upgrade/request-test-database>`, except for the purpose option, which must be set to
      :guilabel:`Production` instead of :guilabel:`Test`.

      .. warning::
@@ -347,8 +317,8 @@ few exceptions.

   .. group-tab:: Odoo.sh

-      The process is similar to :ref:`obtaining an upgraded test database <upgrade-request-test>` on
-      the :guilabel:`Production` branch.
+      The process is similar to :ref:`obtaining an upgraded test database
+      <upgrade/request-test-database>` on the :guilabel:`Production` branch.

      .. image:: upgrade/odoo-sh-prod.png
         :alt: View from the upgrade tab
@@ -378,8 +348,7 @@ few exceptions.
         $ python <(curl -s https://upgrade.odoo.com/upgrade) production -d <your db name> -t <target version>

      An upgraded production database can also be requested via the `Upgrade page
-      <https://upgrade.odoo.com>`_.
-
+      <https://upgrade.odoo.com/>`_.
      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.
@@ -389,14 +358,15 @@ few exceptions.
         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 upgrade (production)"
-<https://www.odoo.com/help?stage=post_upgrade>`_.
+In case of an issue with your production database, you can request the assistance of Odoo via the
+`support page <https://odoo.com/help?stage=post_upgrade>`__ by selecting the option related to
+the upgrade in production.

-.. _upgrade-sla:
+
+.. _upgrade/sla:

 Service-level agreement (SLA)
-=============================
+-----------------------------

 With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including
 any support required to rectify potential discrepancies in the upgraded database.
@@ -405,10 +375,8 @@ 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
-----------------------------------
+===================================

 Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can
 benefit from upgrade services at all times for:
@@ -422,18 +390,18 @@ 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
---------------------------------------
+=======================================

 The following upgrade-related services are **not** included:

 - the **cleaning** of pre-existing data and configurations while upgrading;
- the upgrade of **additional modules not covered by a maintenance contract** that are created
-  in-house or by third parties, including Odoo partners; and
+- the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;
+- lines of **code added to standard modules**, i.e., customizations created outside the Studio app,
+  code entered manually, and :ref:`automated actions using Python code
+  <studio/automated-actions/action>`; and
 - **training** on using the upgraded version's features and workflows.

 .. seealso::
   - :doc:`Odoo.sh documentation <odoo_sh>`
-   - :doc:`Supported Odoo versions <supported_versions>`
+   - :doc:`Supported Odoo versions <maintain/supported_versions>`
@@ -14,7 +14,6 @@ Discover our user guides and configuration tutorials per application.
 .. toctree::
    :maxdepth: 2

-    applications/essentials
    applications/finance
    applications/sales
    applications/websites
@@ -23,5 +22,4 @@ Discover our user guides and configuration tutorials per application.
    applications/marketing
    applications/services
    applications/productivity
-    applications/studio
    applications/general
@@ -1,13 +0,0 @@
-===============
-Odoo essentials
-===============
-
-.. toctree::
-
-   essentials/activities
-   essentials/reporting
-   essentials/search
-   essentials/contacts
-   essentials/export_import_data
-   essentials/in_app_purchase
-   essentials/keyboard_shortcuts
@@ -1,345 +0,0 @@
-==========
-Activities
-==========
-
-.. |clock| replace:: :icon:`fa-clock-o` :guilabel:`(clock)` icon
-
-*Activities* are follow-up tasks tied to a record in an Odoo database.
-
-.. _activities/important:
-
-The icon used to display activities varies, depending on the :ref:`activity type
-<activities/types>`:
-
- :icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon.
- :icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled.
- :icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled.
- :icon:`fa-check` :guilabel:`(check)` icon: a "to-do" is scheduled.
- :icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled.
- :icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be uploaded.
- :icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature request is scheduled.
-
-Schedule activities
-===================
-
-Activities can be scheduled on any page of the database that contains a :ref:`chatter
-<activities/chatter>` thread, :ref:`Kanban view <activities/kanban>`, :ref:`list view
-<activities/list>`, or :ref:`activities view <activities/activity>` of an application.
-
-.. _activities/chatter:
-
-Chatter
-------
-
-Activities can be created from the chatter on any record.
-
-To schedule a new activity, click the :guilabel:`Activities` button, located at the top of the
-chatter. In the :guilabel:`Schedule Activity` pop-up window that appears, :ref:`fill out the
-Schedule Activity form <activities/form>`.
-
-.. image:: activities/chatter.png
-   :align: center
-   :alt: New activity type form.
-
-.. _activities/kanban:
-
-Kanban view
-----------
-
-Activities can also be created from the :icon:`oi-view-kanban` :guilabel:`(Kanban)` view.
-
-To do so, click on the |clock| located at the bottom of an individual record.
-
-Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the Schedule Activity form
-<activities/form>`.
-
-.. image:: activities/schedule-kanban-activity.png
-   :align: center
-   :alt: Kanban view of the CRM pipeline and the option to schedule an activity.
-
-.. note::
-   If a record already has a scheduled activity, the |clock| is replaced by the icon that represents
-   the existing scheduled activity. Click on the activity type's icon to schedule another activity.
-
-.. _activities/list:
-
-List view
---------
-
-Activities can also be created from a :icon:`oi-view-list` :guilabel:`(list)` view.
-
-If the :guilabel:`Activities` column is hidden, reveal it using the :icon:`oi-settings-adjust`
-:guilabel:`(settings adjust)` icon in the far-right of the top row.
-
-Then, click on the |clock| for the record the activity is being added to, and click :guilabel:`+
-Schedule an activity`. Proceed to :ref:`fill out the Schedule Activity form <activities/form>` that
-appears.
-
-.. note::
-   If a record already has a scheduled activity, the |clock| is replaced by the icon that represents
-   the existing scheduled activity. Click on the activity type's icon to schedule another activity.
-
-.. image:: activities/schedule-list-activity.png
-   :align: center
-   :alt: List view of the CRM pipeline and the option to schedule an activity.
-
-.. _activities/activity:
-
-Activity view
-------------
-
-Most applications in Odoo have an *Activity* view available. If available, a |clock| is visible in
-the top-right corner of the main menu bar, amongst the other view option icons.
-
-To open the activity view, click the |clock|.
-
-.. image:: activities/activities.png
-   :align: center
-   :alt: Top-right menu with the Activities icon called out.
-
-In this view, all the available activities are listed in the columns, while the horizontal entries
-represent all the individual records.
-
-Activities that appear green have a due date in the future, activities that appear orange are due
-today, while activities appearing red are overdue.
-
-Color bars in each column represent records for specific activity types, and display a number
-indicating how many activities are scheduled for that type.
-
-If multiple activity types are scheduled for a record, a number appears in the box, indicating the
-total number of scheduled activities.
-
-.. note::
-   Activity colors, and their relation to an activity's due date, are consistent throughout Odoo,
-   regardless of the activity type, or the view.
-
-To schedule an activity for a record, hover over the corresponding field. Click the :icon:`fa-plus`
-:guilabel:`(plus)` icon that appears, and then :ref:`fill out the Schedule Activity form
-<activities/form>`.
-
-.. image:: activities/activity-view.png
-   :align: center
-   :alt: Activity view of the CRM pipeline and the option to schedule an activity.
-
-.. _activities/form:
-
-Schedule Activity form
----------------------
-
-Activities can be scheduled from many different places, such as from the :ref:`chatter
-<activities/chatter>` of a record, or from one of multiple views in an application, when available:
-the :ref:`Kanban view <activities/kanban>`, :ref:`list view <activities/list>`, or :ref:`activity
-view <activities/activity>`.
-
-Enter the following information on the form:
-
- :guilabel:`Activity Type`: select the type of activity from the drop-down menu. The default
-  options are: :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, or :guilabel:`To-Do`.
-  Depending on what other applications are installed, additional options may be available.
- :guilabel:`Summary`: enter a short title for the activity, such as `Discuss Proposal`.
- :guilabel:`Due Date`: using the calendar popover, select the activity's deadline.
- :guilabel:`Assigned to`: by default, the current user populates this field. To assign a different
-  user to the activity, select them from the drop-down menu.
- :guilabel:`Notes`: add any additional information for the activity in this field.
-
-When the :guilabel:`Schedule Activity` pop-up window is completed, click one of the following
-buttons:
-
- :guilabel:`Open Calendar`: opens the user's calendar to add and schedule the activity.
-
-  Click on the desired date and time for the activity, and a :guilabel:`New Event` pop-up window
-  appears. The summary from the *Schedule Activity* pop-up window populates the :guilabel:`Title`
-  field.
-
-  Enter the information in the :guilabel:`New Event` pop-up window, then click :guilabel:`Save &
-  Close` to schedule it. Once scheduled, the activity is added to the chatter under the
-  :guilabel:`Planned Activities` section.
-
-  .. important::
-    The :guilabel:`Open Calendar` button **only** appears if the :guilabel:`Activity Type` is set
-    to either :guilabel:`Call` or :guilabel:`Meeting`.
-
- :guilabel:`Schedule`: schedules the activity, and adds the activity to the chatter under
-  :guilabel:`Planned Activities`.
- :guilabel:`Schedule & Mark as Done`: adds the details of the activity to the chatter under
-  :guilabel:`Today`. The activity is not scheduled, and is automatically marked as done.
- :guilabel:`Done & Schedule Next`: adds the details of the activity to the chatter under
-  :guilabel:`Today`. The activity is not scheduled, is automatically marked as done, and a new
-  :guilabel:`Schedule Activity` pop-up window appears.
- :guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule Activity` pop-up window.
-
-.. image:: activities/schedule-pop-up.png
-   :align: center
-   :alt: View of CRM leads and the option to schedule an activity.
-
-.. _activities/all:
-
-All scheduled activities
-========================
-
-To view a consolidated list of activities, organized by application, click the |clock| in the header
-menu, located in the top-right corner.
-
-If any activities are scheduled, the number of activities appear in a red bubble on the
-|clock|.
-
-All activities for each application are further divided into subsections, indicating where in the
-application the activity is to be completed. Each sub-section lists the number of scheduled
-activities that are :guilabel:`Late`, due :guilabel:`Today`, and scheduled in the
-:guilabel:`Future`.
-
-.. example::
-   In the *Time Off* application, one activity is scheduled to be done in the *All Time Off*
-   requests dashboard, and six activities are scheduled to be done in the *Allocations* dashboard.
-
-   These requests appear in two separate lists in the all activities drop-down menu: one labeled
-   `Time Off` and one labeled `Time Off Allocation`.
-
-   .. image:: activities/activities-menu.png
-      :align: center
-      :alt: The list of activities that is accessed from the main menu bar. Two entries for the Time
-            Off application are highlighted.
-
-Request a document
------------------
-
-The option to :guilabel:`Request a Document` is available at the bottom of the list of :ref:`all
-scheduled activities <activities/all>`, the option to :guilabel:`Request a Document` appears. Click
-:guilabel:`Request a Document`, and a :guilabel:`Request a file` pop-up window appears.
-
-Enter the following information on the form:
-
- :guilabel:`Document Name`: enter a name for the document being requested.
- :guilabel:`Request To`: select the user the document is being requested from using the drop-down
-  menu.
- :guilabel:`Due Date In`: enter a numerical value indicating when the document is due. Next to
-  this field, a :guilabel:`Days` field is visible. Click :guilabel:`Days`, the default option, to
-  reveal a drop-down menu. Select the desired time-frame option from the list. The options are
-  :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`.
- :guilabel:`Workspace`: using the drop-down menu, select the specific :ref:`Workspace
-  <documents/workspaces>` the document is being uploaded to.
- :guilabel:`Tags`: select any desired tags from the drop-down menu. The available tags displayed
-  are based on the tags configured for the selected :guilabel:`Workspace`.
- :guilabel:`Message`: enter a message to clarify the document request in this field.
-
-When all the fields are completed, click :guilabel:`Request` to send the document request.
-
-.. image:: activities/request-doc.png
-   :align: center
-   :alt: The Request a file form, with all fields filled out to request a contract.
-
-.. _activities/types:
-
-Activity types
-==============
-
-To view the currently configured types of activities in the database, navigate to
-:menuselection:`Settings app --> Discuss section --> Activities setting --> Activity Types`.
-
-.. image:: activities/settings-activities-types.png
-   :align: center
-   :alt: Activity Types button in the Settings application under the Discuss section.
-
-Doing so reveals the :guilabel:`Activity Types` page, where the existing activity types are found.
-
-.. tip::
-   Individual applications have a list of *Activity Types* dedicated to that application. For
-   example, to view and edit the activities available for the *CRM* application, go to
-   :menuselection:`CRM app --> Configuration --> Activity Types`.
-
-.. image:: activities/activity-list.png
-   :align: center
-   :alt: The list of activity types already configured and available.
-
-Edit activity types
-------------------
-
-To edit an existing :ref:`activity type <activities/types>`, click on the activity type, and the
-activity type form loads.
-
-Make any desired changes to the activity type form. The form automatically saves, but it can be
-saved manually at any time by clicking the :guilabel:`Save Manually` option, represented by a
-:icon:`fa-cloud-upload` :guilabel:`(cloud upload)` icon, located in the top-left corner of the page.
-
-Create new activity types
-------------------------
-
-To create a new :ref:`activity type <activities/types>`, click :guilabel:`New` from the
-:guilabel:`Activity Types` page, and a blank activity type form loads.
-
-Enter a :guilabel:`Name` for the activity type at the top of the form, then enter the following
-information on the form.
-
-Activity Settings section
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
- :guilabel:`Action`: using the drop-down menu, select an action associated with this new activity
-  type. Some actions trigger specific behaviors after an activity is scheduled, such as:
-
-  - :guilabel:`Upload Document`: if selected, a link to upload a document is automatically added to
-    the planned activity in the chatter.
-  - :guilabel:`Call` or :guilabel:`Meeting`: if selected, users have the option to open their
-    calendar to select a date and time for the activity.
-  - :guilabel:`Request Signature`: if selected, a link to open a signature request pop-up window is
-    automatically added to the planned activity in the chatter. This requires the Odoo *Sign*
-    application to be installed.
-
-  .. note::
-     Available activity types vary based on the installed applications in the database.
-
- :guilabel:`Folder`: select a specific :ref:`workspace <documents/workspaces>` folder to save a
-  document to. This field **only** appears if :guilabel:`Upload Document` is selected for the
-  :guilabel:`Action`.
-
-  Using the drop-down menu, select the :guilabel:`Folder` the document is saved to.
-
- :guilabel:`Default User`: select a user from the drop-down menu to automatically assign this
-  activity to the selected user when this activity type is scheduled. If this field is left blank,
-  the activity is assigned to the user who creates the activity.
- :guilabel:`Default Summary`: enter a note to include whenever this activity type is created.
-
-  .. note::
-     The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are
-     included when an activity is created. However, they can be altered before the activity is
-     scheduled or saved.
-
- :guilabel:`Keep Done`: tick this checkbox to keep activities that have been marked as `Done`
-  visible in the :ref:`activity view <activities/activity>`.
- :guilabel:`Default Note`: enter any notes to appear with the activity.
-
-Next Activity section
-~~~~~~~~~~~~~~~~~~~~~
-
-It is possible to have another activity either suggested or triggered. To do so, configure the
-:guilabel:`Next Activity` section.
-
- :guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` or :guilabel:`Trigger
-  Next Activity` from the drop-down menu. Depending on the selected option, either the
-  :guilabel:`Suggest` or :guilabel:`Trigger` field is displayed.
-
-  .. note::
-     The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload Document` is
-     selected for the :guilabel:`Action`.
-
- :guilabel:`Suggest/Trigger`: depending on what is selected for the :guilabel:`Chaining Type`, this
-  field either displays :guilabel:`Suggest` or :guilabel:`Trigger`. Using the drop-down menu, select
-  the activity to recommend or schedule as a follow-up task to the activity type.
- :guilabel:`Schedule`: configure when the next activity is suggested or triggered.
-
-  First, enter a numerical value indicating when the activity is suggested or triggered.
-
-  Next to this field, a :guilabel:`Days` field is visible. Click :guilabel:`Days`, the default
-  option, to reveal a drop-down menu. Select the desired time-frame option from the list. The
-  options are :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`.
-
-  Lastly, using the drop-down menu, select whether the activity is scheduled or triggered either
-  :guilabel:`after previous activity deadline` or :guilabel:`after completion date`.
-
-.. image:: activities/new-activity.png
-   :align: center
-   :alt: A new Activity form with all the fields filled out.
-
-.. seealso::
-   - :doc:`../productivity/discuss`
-   - :doc:`../productivity/discuss/team_communication`
-   - :doc:`../sales/crm/optimize/utilize_activities`
--- a/Show More
+++ b/Show More