[IMP] tests: make post_install the default

2024-01-30 14:29:26 +01:00
2020 changed files with 33000 additions and 62302 deletions
@@ -21,16 +21,6 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en

-[o:odoo:p:odoo-17-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-17-doc:r:finance]
 file_filter            = locale/<lang>/LC_MESSAGES/finance.po
 source_file            = locale/sources/finance.pot
@@ -51,16 +41,6 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en

-[o:odoo:p:odoo-17-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-17-doc:r:index]
 file_filter            = locale/<lang>/LC_MESSAGES/index.po
 source_file            = locale/sources/index.pot
@@ -131,16 +111,6 @@ replace_edited_strings = false
 keep_translations      = false
 source_lang            = en

-[o:odoo:p:odoo-17-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-17-doc:r:websites]
 file_filter            = locale/<lang>/LC_MESSAGES/websites.po
 source_file            = locale/sources/websites.pot
@@ -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

@@ -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,8 +213,6 @@ 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-17.2': "Odoo Online",
-    'saas-17.1': "Odoo Online",
    '17.0': "Odoo 17",
    'saas-16.4': "Odoo Online",
    'saas-16.3': "Odoo Online",
@@ -252,11 +232,8 @@ languages_names = {
    'es': 'ES',
    'fr': 'FR',
    'it': 'IT',
-    'ko': 'KO',
    'nl': 'NL',
    'pt_BR': 'PT',
-    'ro': 'RO',
-    'sv': 'SV',
    'uk': 'UA',
    'zh_CN': 'ZH (CN)',
    'zh_TW': 'ZH (TW)'
@@ -268,9 +245,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'
@@ -470,7 +444,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
@@ -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
 ========
@@ -334,9 +334,6 @@ in ``/etc/nginx/sites-enabled/odoo.conf`` set:
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_set_header X-Real-IP $remote_addr;
-
-      add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";
-      proxy_cookie_flags session_id samesite=lax secure;  # requires nginx 1.19.8
    }

    # Redirect requests to odoo backend server
@@ -349,8 +346,10 @@ in ``/etc/nginx/sites-enabled/odoo.conf`` set:
      proxy_redirect off;
      proxy_pass http://odoo;

+      # Enable HSTS
      add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";
-      proxy_cookie_flags session_id samesite=lax secure;  # requires nginx 1.19.8
+      # requires nginx 1.19.8
+      proxy_cookie_flags session_id samesite=lax secure;
    }

    # common gzip
@@ -573,12 +572,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 +721,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.

@@ -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.
@@ -16,8 +16,8 @@ Official **Community** and **Enterprise** packages can be downloaded from the `O
 <https://www.odoo.com/page/download>`_.

 .. note::
-   It is required to be logged in as a paying on-premise customer or partner to download the
-   Enterprise packages.
+   It is required to be logged in as a paying customer or partner to download the Enterprise
+   packages.

 .. _install/packages/linux:

@@ -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::

@@ -144,7 +144,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::
@@ -479,7 +479,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,18 @@
+:nosearch:
+
+========
+Maintain
+========
+
+.. toctree::
+
+    maintain/domain_names
+    maintain/azure_oauth
+    maintain/google_oauth
+    maintain/mailjet_api
+    maintain/update
+    maintain/enterprise
+    maintain/hosting_changes
+    maintain/odoo_online
+    maintain/on_premise
+    maintain/supported_versions
@@ -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
@@ -290,4 +290,4 @@ account`. Odoo will state: :guilabel:`Outlook Token Valid` Now :guilabel:`Test a
 account. The account should be ready to receive email to the Odoo database.

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

 * Backup your community database

-  .. image:: community_to_enterprise/db_manager.png
-     :class: img-fluid
+  .. image:: enterprise/db_manager.png
+    :class: img-fluid

 * Shutdown your server

@@ -22,8 +22,8 @@ In any case the basic guidelines are:

 * Enter your Odoo Enterprise Subscription code

-.. image:: community_to_enterprise/enterprise_code.png
-   :class: img-fluid
+.. image:: enterprise/enterprise_code.png
+  :class: img-fluid

 On Linux, using an installer
 ============================
@@ -61,7 +61,7 @@ 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`)
+* Update the ``--addons-path`` parameter of your launch command (see :doc:`../install/source`)
 * Install the web_enterprise module by using

  .. code-block:: console
@@ -82,7 +82,7 @@ On Windows
 * Uninstall Odoo Community (using the Uninstall executable in the installation folder) -
  PostgreSQL will remain installed

-  .. image:: community_to_enterprise/windows_uninstall.png
+  .. image:: enterprise/windows_uninstall.png
    :class: img-fluid

 * Launch the Odoo Enterprise Installer and follow the steps normally. When choosing
@@ -90,8 +90,8 @@ On Windows
  (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
+  .. 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)
@@ -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
@@ -1,9 +1,4 @@
-=======
-Hosting
-=======
-
-.. _hosting/change-solution:
-
+=======================
 Change hosting solution
 =======================

@@ -20,7 +15,7 @@ To Odoo Online
   - 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>`.
+#. 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:
@@ -59,11 +54,6 @@ Transferring an Odoo Online database
      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
 -------------

@@ -210,8 +210,9 @@ Connection`.

   For more information see :ref:`Using a default email address <email_communication/default>`.

-   The :guilabel:`System Parameters` can be accessed by activating the :ref:`developer mode
-   <developer-mode>`.
+   The :guilabel:`System Parameters` can be accessed by activating
+   :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical
+   --> Parameters --> System Parameters` menu.

 Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass
 mailing or transactional emails!
@@ -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.
@@ -84,11 +69,10 @@ 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>`.
+   You can :ref:`register a domain name for free <domain-name/odoo-register>`.

 .. _odoo_online/tags:

@@ -145,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
@@ -13,7 +13,7 @@ Odoo provides support and bug fixing **for the 3 last major versions** of Odoo.
   <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.
+   - 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*.

@@ -31,24 +31,12 @@ This matrix shows the support status of every version.
     - On-Premise
     - Release date
     - End of support
-   * - Odoo saas~17.2
-     - |green|
-     - N/A
-     - N/A
-     - April 2024
-     -
-   * - Odoo saas~17.1
-     - |green|
-     - N/A
-     - N/A
-     - January 2024
-     -
   * - **Odoo 17.0**
     - |green|
     - |green|
     - |green|
     - November 2023
-     - October 2026 (planned)
+     - November 2026 (planned)
   * - Odoo saas~16.4
     - |green|
     - N/A
@@ -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 SS0 authentication.
@@ -1,35 +0,0 @@
-====================
-Neutralized database
-====================
-
-A neutralized database is a non-production database on which several parameters are deactivated.
-This enables one to carry out tests without the risk of launching specific automated processes that
-could impact production data (e.g., sending emails to customers). Live access is removed and
-turned into a testing environment.
-
-.. note::
-   **Any testing database created is a neutralized database:**
-
-   - testing backup databases
-   - duplicate databases
-   - for Odoo.sh: staging and development databases
-
-.. important::
-   A database can also be neutralized when upgrading, as it is vital to do some tests before
-   switching to a new version.
-
-Deactivated features
-====================
-
-Here is a non-exhaustive list of the deactivated parameters:
-
- all planned actions (e.g., automatic invoicing of subscriptions, mass mailing, etc.)
- outgoing emails
- bank synchronization
- payment providers
- delivery methods
- :abbr:`IAP (In-App Purchase)` tokens
-
-.. note::
-   **A red banner at the top of the screen is displayed on the neutralized database so that it can
-   be seen immediately.**
@@ -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
@@ -1,123 +0,0 @@
-:show-content:
-
-==========
-On-premise
-==========
-
-Register a database
-===================
-
-To register your database, enter your subscription code in the banner in the app dashboard. If the
-registration is successful, the banner will turn green and display the database expiration date.
-
-.. tip::
-   The expiration date is also displayed at the bottom of the Settings page.
-
-.. _on-premise/duplicate:
-
-Duplicate a database
-====================
-
-Duplicate a database by accessing the database manager on your server
-(`<odoo-server>/web/database/manager`). Typically, you want to duplicate your production database
-into a neutralized testing database. It can be done by checking the neutralize box when prompted,
-which executes all :file:`neutralize.sql` scripts for every installed module.
-
-Common error messages and solutions
-===================================
-
-Registration error
------------------
-
-In case of a registration error, the following message should be displayed.
-
-.. image:: on_premise/error-message-sub-code.png
-   :alt: Database registration error message
-
-To resolve the issue:
-
- Check the **validity of your Odoo Enterprise subscription** by verifying if your subscription
-  details have the tag :guilabel:`In Progress` on your `Odoo Account
-  <https://accounts.odoo.com/my/subscription>`_ or contact your Account Manager.
-
- Ensure that **no other database is linked** to the subscription code, as only one database can be
-  linked per subscription.
-
-  .. tip::
-     If a test or a development database is needed, you can :ref:`duplicate a database
-     <on-premise/duplicate>`.
-
- Verify that **no databases share the same UUID** (Universally Unique Identifier) by opening your
-  `Odoo Contract <https://accounts.odoo.com/my/subscription>`_. If two or more databases share the
-  same UUID, their name will be displayed.
-
-  .. image:: on_premise/unlink-db-name-collision.png
-     :alt: Database UUID error message
-
-  If that is the case, manually change the database(s) UUID or `send a support ticket
-  <https://www.odoo.com/help>`_.
-
- As the update notification must be able to reach Odoo's subscription validation servers, ensure
-  your **network and firewall settings** allow the Odoo server to open outgoing connections
-  towards:
-
-  - `services.odoo.com` on port `443` (or `80`)
-  - for older deployments, `services.openerp.com` on port `443` (or `80`)
-
-  These ports must be kept open even after registering a database, as the update notification runs
-  once a week.
-
-Too many users error
--------------------
-
-If you have more users in a local database than provisioned in your Odoo Enterprise subscription,
-the following message should be displayed.
-
-.. image:: on_premise/add-more-users.png
-   :alt: Too many users on a database error message
-
-When the message appears, you have 30 days to act before the database expires. The countdown is
-updated every day.
-
-To resolve the issue, either:
-
- **Add more users** to your subscription by clicking the :guilabel:`Upgrade your subscription` link
-  displayed in the message to validate the upsell quotation and pay for the extra users.
- :ref:`Deactivate users <users/deactivate>` and **reject** the upsell quotation.
-
-.. important::
-   If you are on a monthly subscription plan, the database will automatically update to reflect the
-   added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the
-   database. You can create the upsell quotation by clicking the banner to update the subscription
-   or `send a support ticket <https://www.odoo.com/help>`_ to resolve the issue.
-
-Once your database has the correct number of users, the expiration message disappears automatically
-after a few days, when the next verification occurs.
-
-Database expired error
----------------------
-
-If your database expires before you renew your subscription, the following message should be
-displayed.
-
-.. image:: on_premise/database-expired.png
-   :alt: Database expired error message
-
-This message appears if you fail to act before the end of the 30-day countdown.
-
-To resolve the issue, either:
-
- Click the :guilabel:`Renew your subscription` link displayed in the message and complete the
-  process. If you pay by wire transfer, your subscription will be renewed when the payment arrives
-  which can take a few days. Credit card payments are processed immediately.
- `Send a support ticket <https://www.odoo.com/help>`_.
-
-.. toctree::
-
-   on_premise/packages
-   on_premise/source
-   on_premise/update
-   on_premise/deploy
-   on_premise/email_gateway
-   on_premise/geo_ip
-   on_premise/community_to_enterprise
@@ -5,8 +5,8 @@ Upgrade
 .. _administration/upgrade:

 An upgrade is the process of moving your database from an older version to a newer :doc:`supported
-version <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.
+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.

 .. _upgrade_faq/rolling_release:

@@ -33,9 +33,9 @@ each version comes with new and improved features, bug fixes, and security patch
 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::
@@ -404,4 +404,4 @@ The following upgrade-related services are **not** included:

 .. 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,11 +0,0 @@
-===============
-Odoo essentials
-===============
-
-.. toctree::
-
-   essentials/activities
-   essentials/reporting
-   essentials/search
-   essentials/export_import_data
-   essentials/in_app_purchase
@@ -1,478 +0,0 @@
-======================
-Export and import data
-======================
-
-In Odoo, it is sometimes necessary to export or import data for running reports, or for data
-modification. This document covers the export and import of data into and out of Odoo.
-
-.. important::
-   Sometimes, users run into a 'time out' error, or a record does not process, due to its size. This
-   can occur with large exports, or in cases where the import file is too large. To circumvent this
-   limitation surrounding the size of the records, process exports or imports in smaller batches.
-
-.. _export-data:
-
-Export data from Odoo
-=====================
-
-When working with a database, it is sometimes necessary to export data in a distinct file. Doing so
-can aid in reporting on activities, although, Odoo provides a precise and easy reporting tool with
-each available application.
-
-With Odoo, the values can be exported from any field in any record. To do so, activate the list view
-(:guilabel:`≣ (four horizontal lines)` icon), on the items that need to be exported, and then
-select the records that should be exported. To select a record, tick the checkbox next to the
-corresponding record. Finally, click on :guilabel:`⚙️ Action`, and then :guilabel:`Export`.
-
-.. image:: export_import_data/list-view-export.png
-   :align: center
-   :alt: View of the different things to enable/click to export data.
-
-When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over window appears, with
-several options for the data to export:
-
-.. image:: export_import_data/export-data-overview.png
-   :align: center
-   :alt: Overview of options to consider when exporting data in Odoo..
-
-#. With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system
-   only shows the fields that can be imported. This is helpful in the case where the existing
-   records need to be updated. This works like a filter. Leaving the box unticked, gives many more
-   field options because it shows all the fields, not just the ones that can be imported.
-#. When exporting, there is the option to export in two formats: `.csv` and `.xls`. With `.csv`,
-   items are separated by a comma, while `.xls` holds information about all the worksheets in a
-   file, including both content and formatting.
-#. These are the items that can be exported. Use the :guilabel:`> (right arrow)` icon to display
-   more sub-field options. Use the :guilabel:`Search` bar to find specific fields. To use the
-   :guilabel:`Search` option more efficiently, click on all the :guilabel:`> (right arrows)` to
-   display all fields.
-#. The :guilabel:`+ (plus sign)` icon button is present to add fields to the :guilabel:`Fields to
-   export` list.
-#. The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be used to move the
-   fields up and down, to change the order in which they are displayed in the exported file.
-   Drag-and-drop using the :guilabel:`↕️ (up-down arrow)` icon.
-#. The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the :guilabel:`🗑️ (trash
-   can)` icon to remove the field.
-#. For recurring reports, it is helpful to save export presets. Select all the needed fields, and
-   click on the template drop-down menu. Once there, click on :guilabel:`New template`, and give a
-   unique name to the export just created. Click the :guilabel:`💾 (floppy drive)` icon to save the
-   configuration. The next time the same list needs to be exported, select the related template that
-   was previously saved from the drop-down menu.
-
-.. tip::
-   It is helpful to know the field's external identifier. For example, :guilabel:`Related Company`
-   in the export user interface is equal to *parent_id* (external identifier). This is helpful
-   because then, the only data exported is what should be modified and re-imported.
-
-.. _import-data:
-
-Import data into Odoo
-=====================
-
-Importing data into Odoo is extremely helpful during implementation, or in times where data needs to
-be updated in bulk. The following documentation covers how to import data into an Odoo database.
-
-.. warning::
-   Imports are permanent and **cannot** be undone. However, it is possible to use filters (`created
-   on` or `last modified`) to identify records changed or created by the import.
-
-.. tip::
-   Activating :ref:`developer mode <developer-mode>` changes the visible import settings in the left
-   menu. Doing so reveals an :menuselection:`Advanced` menu. Included in this advanced menu are two
-   options: :guilabel:`Track history during import` and :guilabel:`Allow matching with subfields`.
-
-   .. image:: export_import_data/advanced-import.png
-      :align: center
-      :alt: Advanced import options when developer mode is activated.
-
-   If the model uses openchatter, the :guilabel:`Track history during import` option sets up
-   subscriptions and sends notifications during the import, but leads to a slower import.
-
-   Should the :guilabel:`Allow matching with subfields` option be selected, then all subfields
-   within a field are used to match under the :guilabel:`Odoo Field` while importing.
-
-Get started
-----------
-
-Data can be imported on any Odoo business object using either Excel (`.xlsx`) or :abbr:`CSV
-(Comma-separated Values)` (`.csv`) formats. This includes: contacts, products, bank statements,
-journal entries, and orders.
-
-Open the view of the object to which the data should be imported/populated, and click on
-:menuselection:`⚙️ (Action) --> Import records`.
-
-.. image:: export_import_data/import-button.png
-   :align: center
-   :alt:  Action menu revealed with the import records option highlighted.
-
-After clicking :guilabel:`Import records`, Odoo reveals a separate page with templates that can be
-downloaded and populated with the company's own data. Such templates can be imported in one click,
-since the data mapping is already done. To download a template click :guilabel:`Import Template for
-Customers` at the center of the page.
-
-.. important::
-   When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting`
-   options. These options do **not** appear when importing the proprietary Excel file type (`.xls`,
-   `.xlsx`).
-
-   .. image:: export_import_data/formatting.png
-      :align: center
-      :alt: Formatting options presented when a CVS file is imported in Odoo.
-
-Make necessary adjustments to the *Formatting* options, and ensure all columns in the
-:guilabel:`Odoo field` and :guilabel:`File Column` are free of errors. Finally, click
-:guilabel:`Import` to import the data.
-
-Adapt a template
----------------
-
-Import templates are provided in the import tool of the most common data to import (contacts,
-products, bank statements, etc.). Open them with any spreadsheet software (*Microsoft Office*,
-*OpenOffice*, *Google Drive*, etc.).
-
-Once the template is downloaded, proceed to follow these steps:
-
- Add, remove, and sort columns to best fit the data structure.
- It is strongly advised to **not** remove the :guilabel:`External ID` (ID) column (see why in the
-  next section).
- Set a unique ID to every record by dragging down the ID sequencing in the :guilabel:`External ID`
-  (ID) column.
-
-.. image:: export_import_data/dragdown.gif
-   :align: center
-   :alt: An animation of the mouse dragging down the ID column, so each record has a unique ID.
-
-.. note::
-   When a new column is added, Odoo may not be able to map it automatically, if its label does not
-   fit any field within Odoo. However, new columns can be mapped manually when the import is tested.
-   Search the drop-down menu for the corresponding field.
-
-   .. image:: export_import_data/field_list.png
-      :align: center
-      :alt: Drop-down menu expanded in the initial import screen on Odoo.
-
-   Then, use this field's label in the import file to ensure future imports are successful.
-
-.. tip::
-   Another useful way to find out the proper column names to import is to export a sample file
-   using the fields that should be imported. This way, if there is not a sample import template,
-   the names are accurate.
-
-Import from another application
-------------------------------
-
-The :guilabel:`External ID` (ID) is a unique identifier for the line item. Feel free to use one
-from previous software to facilitate the transition to Odoo.
-
-Setting an ID is not mandatory when importing, but it helps in many cases:
-
- Update imports: import the same file several times without creating duplicates.
- :ref:`Import relation fields <export_import_data/relation-fields>`.
-
-To recreate relationships between different records, the unique identifier from the original
-application should be used to map it to the :guilabel:`External ID` (ID) column in Odoo.
-
-When another record is imported that links to the first one, use **XXX/ID** (XXX/External ID) for
-the original unique identifier. This record can also be found using its name.
-
-.. warning::
-   It should be noted that there will be a conflict if two or more records have the same name.
-
-The :guilabel:`External ID` (ID) can also be used to update the original import, if modified data
-needs to be re-imported later, therefore, it is a good practice to specify it whenever possible.
-
-Field missing to map column
---------------------------
-
-Odoo heuristically tries to find the type of field for each column inside the imported file, based
-on the first ten lines of the files.
-
-For example, if there is a column only containing numbers, only the fields with the *integer* type
-are presented as options.
-
-While this behavior might be beneficial in most cases, it is also possible that it could fail, or
-the column may be mapped to a field that is not proposed by default.
-
-If this happens, check the :guilabel:`Show fields of relation fields (advanced) option`, then a
-complete list of fields becomes available for each column.
-
-.. image:: export_import_data/field_list.png
-   :align: center
-   :alt: Searching for the field to match the tax column.
-
-Change data import format
-------------------------
-
-.. note::
-   Odoo can automatically detect if a column is a date, and tries to guess the date format from a
-   set of most commonly used date formats. While this process can work for many date formats, some
-   date formats are not recognizable. This can cause confusion, due to day-month inversions; it is
-   difficult to guess which part of a date format is the day, and which part is the month, in a
-   date, such as `01-03-2016`.
-
-When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting`
-options.
-
-To view which date format Odoo has found from the file, check the :guilabel:`Date Format` that is
-shown when clicking on options under the file selector. If this format is incorrect, change it to
-the preferred format using *ISO 8601* to define the format.
-
-.. important::
-   *ISO 8601* is an international standard, covering the worldwide exchange, along with the
-   communication of date and time-related data. For example, the date format should be `YYYY-MM-DD`.
-   So, in the case of July 24th 1981, it should be written as `1981-07-24`.
-
-.. tip::
-   When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to store dates. This
-   maintains locale date formats for display, regardless of how the date is formatted in Odoo. When
-   importing a :abbr:`CSV (Comma-separated Values)` file, use Odoo's :guilabel:`Formatting` section
-   to select the date format columns to import.
-
-Import numbers with currency signs
----------------------------------
-
-Odoo fully supports numbers with parenthesis to represent negative signs, as well as numbers with
-currency signs attached to them. Odoo also automatically detects which thousand/decimal separator is
-used. If a currency symbol unknown to Odoo is used, it might not be recognized as a number, and the
-import crashes.
-
-.. note::
-   When importing a :abbr:`CSV (Comma-separated Values)` file, the :guilabel:`Formatting` menu
-   appears on the left-hand column. Under these options, the :guilabel:`Thousands Separator` can be
-   changed.
-
-Examples of supported numbers (using 'thirty-two thousand' as the figure):
-
- 32.000,00
- 32000,00
- 32,000.00
- -32000.00
- (32000.00)
- $ 32.000,00
- (32000.00 €)
-
-Example that will not work:
-
- ABC 32.000,00
- $ (32.000,00)
-
-.. important::
-   A :guilabel:`() (parenthesis)` around the number indicates that the number is a negative value.
-   The currency symbol **must** be placed within the parenthesis for Odoo to recognize it as a
-   negative currency value.
-
-Import preview table not displayed correctly
--------------------------------------------
-
-By default, the import preview is set on commas as field separators, and quotation marks as text
-delimiters. If the :abbr:`CSV (Comma-separated Values)` file does not have these settings, modify
-the :guilabel:`Formatting` options (displayed under the :guilabel:`Import` :abbr:`CSV
-(Comma-separated Values)` file bar after selecting the :abbr:`CSV (Comma-separated Values)` file).
-
-.. important::
-   If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a separator, Odoo does
-   **not** detect the separations. The file format options need to be modified in the spreadsheet
-   application. See the following :ref:`Change CSV file format <export_import_data/change-csv>`
-   section.
-
-.. _export_import_data/change-csv:
-
-Change CSV file format in spreadsheet application
-------------------------------------------------
-
-When editing and saving :abbr:`CSV (Comma-separated Values)` files in spreadsheet applications, the
-computer's regional settings are applied for the separator and delimiter. Odoo suggests using
-*OpenOffice* or *LibreOffice*, as both applications allow modifications of all three options (from
-*LibreOffice* application, go to :menuselection:`'Save As' dialog box --> Check the box 'Edit filter
-settings' --> Save`).
-
-Microsoft Excel can modify the encoding when saving (:menuselection:`'Save As' dialog box -->
-'Tools' drop-down menu --> Encoding tab`).
-
-Difference between Database ID and External ID
----------------------------------------------
-
-Some fields define a relationship with another object. For example, the country of a contact is a
-link to a record of the 'Country' object. When such fields are imported, Odoo has to recreate links
-between the different records. To help import such fields, Odoo provides three mechanisms.
-
-.. important::
-   **Only one** mechanism should be used per field that is imported.
-
-For example, to reference the country of a contact, Odoo proposes three different fields to import:
-
- :guilabel:`Country`: the name or code of the country
- :guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by the ID PostgreSQL
-  column
- :guilabel:`Country/External ID`: the ID of this record referenced in another application (or the
-  `.XML` file that imported it)
-
-For the country of Belgium, for example, use one of these three ways to import:
-
- :guilabel:`Country`: `Belgium`
- :guilabel:`Country/Database ID`: `21`
- :guilabel:`Country/External ID`: `base.be`
-
-According to the company's need, use one of these three ways to reference records in relations. Here
-is an example when one or the other should be used, according to the need:
-
- Use :guilabel:`Country`: this is the easiest way when data comes from :abbr:`CSV (Comma-separated
-  Values)` files that have been created manually.
- Use :guilabel:`Country/Database ID`: this should rarely be used. It is mostly used by developers
-  as the main advantage is to never have conflicts (there may be several records with the same name,
-  but they always have a unique Database ID)
- Use :guilabel:`Country/External ID`: use *External ID* when importing data from a third-party
-  application.
-
-When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` files with the
-:guilabel:`External ID` (ID) column defining the *External ID* of each record that is imported.
-Then, a reference can be made to that record with columns, like `Field/External ID`. The following
-two :abbr:`CSV (Comma-separated Values)` files provide an example for products and their categories.
-
- :download:`CSV file for categories
-  <export_import_data/External_id_3rd_party_application_product_categories.csv>`
- :download:`CSV file for Products
-  <export_import_data/External_id_3rd_party_application_products.csv>`
-
-.. _export_import_data/relation-fields:
-
-Import relation fields
----------------------
-
-An Odoo object is always related to many other objects (e.g. a product is linked to product
-categories, attributes, vendors, etc.). To import those relations, the records of the related object
-need to be imported first, from their own list menu.
-
-This can be achieved by using either the name of the related record, or its ID, depending on the
-circumstances. The ID is expected when two records have the same name. In such a case add `/ ID`
-at the end of the column title (e.g. for product attributes: `Product Attributes / Attribute / ID`).
-
-Options for multiple matches on fields
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If, for example, there are two product categories with the child name `Sellable` (e.g. `Misc.
-Products/Sellable` & `Other Products/Sellable`), the validation is halted, but the data may still be
-imported. However, Odoo recommends that the data is not imported because it will all be linked to
-the first `Sellable` category found in the *Product Category* list (`Misc. Products/Sellable`).
-Odoo, instead, recommends modifying one of the duplicate's values, or the product category
-hierarchy.
-
-However, if the company does not wish to change the configuration of product categories, Odoo
-recommends making use of the *External ID* for this field, 'Category'.
-
-Import many2many relationship fields
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The tags should be separated by a comma, without any spacing. For example, if a customer needs to be
-linked to both tags: `Manufacturer` and `Retailer` then 'Manufacturer,Retailer' needs to be encoded
-in the same column of the :abbr:`CSV (Comma-separated Values)` file.
-
- :download:`CSV file for Manufacturer, Retailer <export_import_data/m2m_customers_tags.csv>`
-
-Import one2many relationships
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If a company wants to import a sales order with several order lines, a specific row **must** be
-reserved in the :abbr:`CSV (Comma-separated Values)` file for each order line. The first order line
-is imported on the same row as the information relative to order. Any additional lines need an
-additional row that does not have any information in the fields relative to the order.
-
-As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some quotations that can be
-imported, based on demo data:
-
- :download:`File for some Quotations
-  <export_import_data/purchase.order_functional_error_line_cant_adpat.csv>`
-
-The following :abbr:`CSV (Comma-separated Values)` file shows how to import purchase orders with
-their respective purchase order lines:
-
- :download:`Purchase orders with their respective purchase order lines
-  <export_import_data/o2m_purchase_order_lines.csv>`
-
-The following :abbr:`CSV (Comma-separated Values)` file shows how to import customers and their
-respective contacts:
-
- :download:`Customers and their respective contacts
-  <export_import_data/o2m_customers_contacts.csv>`
-
-Import records several times
----------------------------
-
-If an imported file contains one of the columns: :guilabel:`External ID` or :guilabel:`Database ID`,
-records that have already been imported are modified, instead of being created. This is extremely
-useful as it allows users to import the same :abbr:`CSV (Comma-separated Values)` file several
-times, while having made some changes in between two imports.
-
-Odoo takes care of creating or modifying each record, depending if it is new or not.
-
-This feature allows a company to use the *Import/Export tool* in Odoo to modify a batch of records
-in a spreadsheet application.
-
-Value not provided for a specific field
---------------------------------------
-
-If all fields are not set in the CSV file, Odoo assigns the default value for every non-defined
-field. But, if fields are set with empty values in the :abbr:`CSV (Comma-separated Values)` file,
-Odoo sets the empty value in the field, instead of assigning the default value.
-
-Export/import different tables from an SQL application to Odoo
--------------------------------------------------------------
-
-If data needs to be imported from different tables, relations need to be recreated between records
-belonging to different tables. For instance, if companies and people are imported, the link between
-each person and the company they work for needs to be recreated.
-
-To manage relations between tables, use the `External ID` facilities of Odoo. The `External ID` of a
-record is the unique identifier of this record in another application. The `External ID` must be
-unique across all records of all objects. It is a good practice to prefix this `External ID` with
-the name of the application or table. (like, 'company_1', 'person_1' - instead of '1')
-
-As an example, suppose there is an SQL database with two tables that are to be imported: companies
-and people. Each person belongs to one company, so the link between a person and the company they
-work for must be recreated.
-
-Test this example, with a :download:`sample of a PostgreSQL database
-<export_import_data/database_import_test.sql>`.
-
-First, export all companies and their *External ID*. In PSQL, write the following command:
-
-.. code-block:: sh
-
-   > copy (select 'company_'||id as "External ID",company_name as "Name",'True' as "Is a Company" from companies) TO '/tmp/company.csv' with CSV HEADER;
-
-This SQL command creates the following :abbr:`CSV (Comma-separated Values)` file:
-
-.. code-block:: text
-
-   External ID,Name,Is a Company
-   company_1,Bigees,True
-   company_2,Organi,True
-   company_3,Boum,True
-
-To create the :abbr:`CSV (Comma-separated Values)` file for people linked to companies, use the
-following SQL command in PSQL:
-
-.. code-block:: sh
-
-    > copy (select 'person_'||id as "External ID",person_name as "Name",'False' as "Is a Company",'company_'||company_id as "Related Company/External ID" from persons) TO '/tmp/person.csv' with CSV
-
-It produces the following :abbr:`CSV (Comma-separated Values)` file:
-
-.. code-block:: text
-
-   External ID,Name,Is a Company,Related Company/External ID
-   person_1,Fabien,False,company_1
-   person_2,Laurence,False,company_1
-   person_3,Eric,False,company_2
-   person_4,Ramsy,False,company_3
-
-In this file, Fabien and Laurence are working for the Bigees company (`company_1`), and Eric is
-working for the Organi company. The relation between people and companies is done using the
-*External ID* of the companies. The *External ID* is prefixed by the name of the table to avoid a
-conflict of ID between people and companies (`person_1` and `company_1`, who shared the same ID 1 in
-the original database).
-
-The two files produced are ready to be imported in Odoo without any modifications. After having
-imported these two :abbr:`CSV (Comma-separated Values)` files, there are four contacts and three
-companies (the first two contacts are linked to the first company). Keep in mind to first import
-the companies, and then the people.
@@ -1,214 +0,0 @@
-=================================
-Search, filter, and group records
-=================================
-
-Odoo allows for the searching, filtering, and grouping of records in a view to display only the most
-relevant records. The search bar is located at the top of the view, start typing to :ref:`search for
-values <search/values>`, or click the :guilabel:`🔽 (down arrow)` icon to access the :ref:`Filter
-<search/filters>`, :ref:`Group By <search/group>`, and :ref:`Favorites <search/favorites>` drop-down
-menus.
-
-.. _search/values:
-
-Search for values
-=================
-
-Use the search field to quickly look for specific values, and add them as a filter. Type the value
-to search for, and select the desired option from the drop-down menu to apply the search filter.
-
-.. example::
-   Instead of adding a :ref:`custom filter <search/custom-filters>` to select records where
-   *Mitchell Admin* is the salesperson on the *Sales Analysis* report (:menuselection:`Sales app -->
-   Reporting --> Sales`), search for `Mitch`, and click the :guilabel:`⏵ (right arrow)` next to
-   :guilabel:`Search Salesperson for: Mitch`, and select :guilabel:`Mitchell Admin`.
-
-   .. image:: search/search-values.png
-      :align: center
-      :alt: Searching for a specific value on the Sales Analysis report
-
-.. note::
-   Using the search field is equivalent to using the *contains* operator when adding a :ref:`custom
-   filter <search/custom-filters>`. If a partial value is entered, and the desired field is directly
-   selected (without selecting the :guilabel:`⏵ (right arrow)`), *all* records containing the typed
-   characters for the selected field are included.
-
-.. _search/filters:
-
-Filters
-=======
-
-Filters are used to select records that meet specific criteria. The default selection of records is
-specific to each view, but can be modified by selecting one (or several) :ref:`preconfigured filters
-<search/preconfigured-filters>`, or by adding a :ref:`custom filter <search/custom-filters>`.
-
-.. _search/preconfigured-filters:
-
-Preconfigured filters
---------------------
-
-Modify the default selection of records by clicking the :guilabel:`🔽 (down arrow)` icon from the
-search bar, and selecting one (or several) *preconfigured filters* from the :guilabel:`Filters`
-drop-down menu.
-
-.. example::
-   On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> Sales`), only records
-   that are at the *sales order* stage, with an *order date* within the last 365 days, are selected
-   by default.
-
-   To also include records at the *quotation* stage, select :guilabel:`Quotations` from the
-   :guilabel:`Filters`.
-
-   Furthermore, to *only* include sales order and quotation records from a specific year, like
-   2024, for example, first remove the existing `Order Date: Last 365 Days` filter, by clicking the
-   :guilabel:`❌ (remove)` icon, then select :menuselection:`Order Date --> 2024`.
-
-   .. image:: search/preconfigured-filters.png
-      :align: center
-      :alt: Using preconfigured filters on the Sales Analysis report
-
-.. note::
-   The preconfigured :guilabel:`Filters` are grouped, and each group is separated by a horizontal
-   line. Selecting preconfigured filters from the same group allows records to match *any* of the
-   applied conditions. However, selecting filters from different groups requires records to match
-   *all* of the applied conditions.
-
-.. _search/custom-filters:
-
-Custom filters
--------------
-
-If the :ref:`preconfigured filters <search/preconfigured-filters>` are not specific enough, add a
-custom filter. To do so, click the :guilabel:`🔽 (down arrow)` icon in the search bar, then select
-:menuselection:`Filters --> Add Custom Filter`.
-
-The :guilabel:`Add Custom Filter` pop-up window displays the matching option, filter rule, and a
-toggle to :guilabel:`Include archived` records.
-
-.. image:: search/custom-filter.png
-   :align: center
-   :alt: The Add Custom Filter pop-up window.
-
-The default matching configuration is to :guilabel:`Match any of the following rules`, indicating
-that each filter rule is applied independently. To change the matching configuration to
-:guilabel:`Match all of the following rules`, at least two filter rules must be added to the custom
-filter.
-
- :guilabel:`Match all 🔽 of the following rules`: **all** of the filter rules must be met.
-  Logically, this is an *AND* (`&`) operation.
- :guilabel:`Match any 🔽 of the following rules`: **any** of the filter rules can be met.
-  Logically, this is an *OR* (`|`) operation.
-
-By default, a single filter rule is added to the custom filter. The following describes the
-structure of a filter rule:
-
-#. The first inline field is the *field name* to filter by. Some fields have refined parameters that
-   are nested within another field. These fields have an :guilabel:`> (arrow)` icon beside them,
-   which can be selected to reveal the nested fields.
-#. The second inline field is the conditional *operator* used to compare the field name to the
-   value. The :ref:`available conditional operators <reference/orm/domains>` are specific to the
-   field's data type.
-#. The third inline field is the variable *value* of the field name. The value input may appear as a
-   drop-down menu, a text input, a number input, a date/time input, a boolean selector, or it may be
-   blank, depending on the operator used and the field's data type.
-
-Three inline buttons are also available to the right of the rule's filter criteria:
-
-#. :guilabel:`➕ (plus sign)`: adds a new rule below the existing rule.
-#. :guilabel:`(Add branch)`: adds a new group of rules below the existing rule, with the
-   :guilabel:`any` and :guilabel:`all` matching options available to define how each rule within
-   this branch is applied to the filter. If the matching option is set to the same as the parent
-   group, the fields are moved to join the parent group.
-
-   .. example::
-      If the matching option is set to :guilabel:`Match all 🔽 of the following rules`, and a new
-      branch is added with its matching option changed from :guilabel:`any 🔽 of` to :guilabel:`all
-      🔽 of`, the newly-added branch disappears, and its group of rules are moved to the parent
-      group.
-
-#. :guilabel:`🗑️ (garbage can)`: deletes the node. If a branch node is deleted, all children of
-   that node are deleted, as well.
-
-A new filter rule can be added to the custom filter by clicking the :guilabel:`New Rule` button.
-
-Once the filter criteria are defined, click :guilabel:`Add` to add the custom filter to the view.
-
-.. example::
-   To target all leads and opportunities from the :menuselection:`CRM` app that are in the *Won*
-   stage, and have an expected revenue greater than $1,000, the following should be entered:
-
-   :guilabel:`Match all 🔽 (down arrow) of the following rules:`
-
-   #. :guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`
-   #. :guilabel:`Expected Revenue` :guilabel:`>` `1,000`
-   #. :guilabel:`any 🔽 (down arrow)` :guilabel:`of:`
-
-      - :guilabel:`Type` :guilabel:`=` :guilabel:`Lead`
-      - :guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`
-
-   .. image:: search/custom-filter-example.png
-      :align: center
-      :alt: Adding a custom filter to filter specific records in CRM.
-
-.. tip::
-   Activate :ref:`developer-mode` to reveal each field's technical name and data type, as well as
-   the :guilabel:`# Code editor` text area below the filter rules, to view and edit the domain
-   manually.
-
-.. _search/group:
-
-Group records
-=============
-
-The display of records in a view can be clustered together, according to one of the *preconfigured
-groups*. To do so, click the :guilabel:`🔽 (down arrow)` icon in the search bar, then select one of
-the :guilabel:`Group By` options from the drop-down menu.
-
-.. example::
-   To group the records by salesperson on the *Sales Analysis* report (:menuselection:`Sales app -->
-   Reporting --> Sales`), click the :guilabel:`Salesperson` option from the :guilabel:`Group By`
-   drop-down menu. The view changes to group the records by salesperson, without filtering out any
-   records.
-
-   .. image:: search/group.png
-      :align: center
-      :alt: Grouping records on the Sales Analysis report
-
-It is possible to *customize groups* by using a field present on the model. To do so, click
-:menuselection:`Add Custom Group`, and select a field from the drop-down menu.
-
-.. note::
-   Several groups can be used at the same time. The first group that is selected is the main
-   cluster, the next one that is added further divides the main group's categories, and so on.
-   Furthermore, filters and groups can be used together to refine the view even more.
-
-.. _search/favorites:
-
-Favorites
-=========
-
-Favorites are a way to save a specific search for future use, or as the new default filter for the
-view.
-
-To save the current view as a favorite, click the :guilabel:`🔽 (down arrow)` icon in the search
-bar, then select the :guilabel:`Save current search` drop-down menu to display the following
-options:
-
- Filter name: name of the favorited search.
- :guilabel:`Default filter`: sets the favorited search as the default filter for the view.
- :guilabel:`Shared`: makes the favorited search available to all users. By default, the favorited
-  search is only available to the user who created it.
-
-Once the options are set, click :guilabel:`Save` to save the favorited search.
-
-.. image:: search/favorites.png
-   :align: center
-   :alt: Saving a favorite search on the Sales Analysis report
-
-Saved favorites can be accessed by clicking the :guilabel:`🔽 (down arrow)` icon in the search bar,
-then selecting the saved filter in the :guilabel:`Favorites` drop-down menu. To remove a saved
-favorite, click the :guilabel:`🗑️ (garbage can)` icon next to the favorited search.
-
-.. tip::
-   To view *all* favorited searches, first activate :ref:`developer-mode`, and navigate to
-   :menuselection:`Settings app --> Technical --> User Interface: User-defined Filters`. From here,
-   all favorited searches can be viewed, edited, archived, or deleted.
@@ -8,5 +8,8 @@ Finance

    finance/accounting
    finance/expenses
+    finance/documents
+    finance/sign
+    finance/spreadsheet
    finance/payment_providers
    finance/fiscal_localizations
@@ -27,19 +27,11 @@ Odoo supports multiple file formats to import transactions:
 - Quicken Interchange Format (.QIF);
 - Belgium: Coded Statement of Account (.CODA).

-To import a file, go to the **Accounting Dashboard**, and in the :guilabel:`Bank` journal,
-click on :guilabel:`Import File`.
+To import a file, go to the :guilabel:`Accounting Dashboard`, and in the :guilabel:`Bank` journal,
+click on :guilabel:`Import Transactions`.

-.. tip::
-   Alternatively, you can also:
-
-   - click :guilabel:`⋮` on the :guilabel:`Bank` journal and select :guilabel:`Import file`;
-   - or access the transaction list by clicking :guilabel:`⋮` on the :guilabel:`Bank` journal and
-     selecting :guilabel:`Transactions`, then click the gear icon :guilabel:`(⚙)` and select
-     :guilabel:`Import records`.
-
-     .. image:: transactions/import-transactions.png
-        :alt: Import bank transactions from the bank journal
+.. image:: transactions/import-transactions.png
+   :alt: Import bank transactions from the bank journal

 Next, select the file and upload it.

@@ -47,7 +39,7 @@ After setting the necessary formatting options and mapping the file columns with
 fields, you can run a :guilabel:`Test` and :guilabel:`Import` your bank transactions.

 .. seealso::
-   :doc:`/applications/essentials/export_import_data`
+   :doc:`/applications/general/export_import_data`

 .. _transactions/register:

@@ -47,7 +47,9 @@ Draft invoices
 --------------

 The system generates invoice which are initially set to the Draft state.
-While these invoices remain unvalidated, they have no accounting impact within the system.
+While these invoices
+
+remain unvalidated, they have no accounting impact within the system.
 There is nothing to stop users from creating their own draft invoices.

 Let's create a customer invoice with following information:
--- a/Show More
+++ b/Show More