Update web_services.rst

X-original-commit: e8c29ef8c2
[I18N] *: export source terms
2023-04-13 19:20:49 +02:00 · 2023-04-13 17:57:26 +02:00 · 2023-04-13 16:40:41 +02:00 · 2023-04-13 16:39:45 +02:00 · 2023-04-13 05:07:57 +02:00 · 2023-04-13 05:07:52 +02:00
1700 changed files with 67831 additions and 51940 deletions
@@ -1,63 +1,63 @@
 [main]
 host = https://www.transifex.com
-type = PO

-[odoo-14-doc.applications]
+[o:odoo:p:odoo-16-doc:r:administration]
+file_filter = locale/<lang>/LC_MESSAGES/administration.po
+source_file = locale/sources/administration.pot
+source_lang = en
+
+[o:odoo:p:odoo-16-doc:r:applications]
 file_filter = locale/<lang>/LC_MESSAGES/applications.po
 source_file = locale/sources/applications.pot
 source_lang = en

-[odoo-14-doc.finance]
+[o:odoo:p:odoo-16-doc:r:finance]
 file_filter = locale/<lang>/LC_MESSAGES/finance.po
 source_file = locale/sources/finance.pot
 source_lang = en

-[odoo-14-doc.general]
+[o:odoo:p:odoo-16-doc:r:general]
 file_filter = locale/<lang>/LC_MESSAGES/general.po
 source_file = locale/sources/general.pot
 source_lang = en

-[odoo-14-doc.index]
+[o:odoo:p:odoo-16-doc:r:index]
 file_filter = locale/<lang>/LC_MESSAGES/index.po
 source_file = locale/sources/index.pot
 source_lang = en

-[odoo-14-doc.inventory_and_mrp]
+[o:odoo:p:odoo-16-doc:r:inventory_and_mrp]
 file_filter = locale/<lang>/LC_MESSAGES/inventory_and_mrp.po
 source_file = locale/sources/inventory_and_mrp.pot
 source_lang = en

-[odoo-14-doc.marketing]
+[o:odoo:p:odoo-16-doc:r:marketing]
 file_filter = locale/<lang>/LC_MESSAGES/marketing.po
 source_file = locale/sources/marketing.pot
 source_lang = en

-[odoo-14-doc.productivity]
+[o:odoo:p:odoo-16-doc:r:productivity]
 file_filter = locale/<lang>/LC_MESSAGES/productivity.po
 source_file = locale/sources/productivity.pot
 source_lang = en

-[odoo-14-doc.sales]
+[o:odoo:p:odoo-16-doc:r:sales]
 file_filter = locale/<lang>/LC_MESSAGES/sales.po
 source_file = locale/sources/sales.pot
 source_lang = en

-[odoo-14-doc.services]
+[o:odoo:p:odoo-16-doc:r:services]
 file_filter = locale/<lang>/LC_MESSAGES/services.po
 source_file = locale/sources/services.pot
 source_lang = en

-[odoo-14-doc.theme]
-file_filter = locale/<lang>/LC_MESSAGES/sphinx.po
-source_file = locale/sources/sphinx.pot
-source_lang = en
-
-[odoo-14-doc.user_settings]
+[o:odoo:p:odoo-16-doc:r:user_settings]
 file_filter = locale/<lang>/LC_MESSAGES/settings.po
 source_file = locale/sources/settings.pot
 source_lang = en

-[odoo-14-doc.websites]
+[o:odoo:p:odoo-16-doc:r:websites]
 file_filter = locale/<lang>/LC_MESSAGES/websites.po
 source_file = locale/sources/websites.pot
 source_lang = en
+
@@ -42,6 +42,7 @@ help:
 	@echo "  html         to build the documentation to HTML"
 	@echo "  fast         to build the documentation to HTML with shallow menu (faster)"
 	@echo "  clean        to delete the build files"
+	@echo "  test         to run the guidelines tests"

 clean:
 	@echo "Cleaning build files..."
@@ -82,3 +83,6 @@ fast: html
 static: $(HTML_BUILD_DIR)/_static/style.css
 	cp -r extensions/odoo_theme/static/* $(HTML_BUILD_DIR)/_static/
 	cp -r static/* $(HTML_BUILD_DIR)/_static/
+
+test:
+	@python tests/main.py $(SOURCE_DIR)/administration $(SOURCE_DIR)/applications $(SOURCE_DIR)/contributing $(SOURCE_DIR)/developer $(SOURCE_DIR)/services redirects
@@ -165,6 +165,9 @@ extensions = [
    # Content tabs
    'sphinx_tabs.tabs',

+    # Cards
+    'cards',
+
    # Spoilers
    'spoilers',

@@ -210,8 +213,9 @@ 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-16.2': "Odoo Online",
+    'saas-16.1': "Odoo Online",
    '16.0': "Odoo 16",
-    'saas-15.3': "Odoo Online",
    'saas-15.2': "Odoo Online",
    '15.0': "Odoo 15",
    '14.0': "Odoo 14",
@@ -225,10 +229,12 @@ languages_names = {
    'en': 'EN',
    'es': 'ES',
    'fr': 'FR',
+    'it': 'IT',
    'nl': 'NL',
    'pt_BR': 'PT',
    'uk': 'UA',
-    'zh_CN': 'ZH',
+    'zh_CN': 'ZH (CN)',
+    'zh_TW': 'ZH (TW)'
 }

 # The directory in which files holding redirect rules used by the 'redirects' extension are listed.
@@ -313,6 +319,12 @@ latex_documents = [
     'odoo_partnership_agreement_es.tex', 'Odoo Partnership Agreement (ES)', '', 'howto'),
 ]

+# List of languages that have legal translations (excluding EN). The keys must be in
+# `languages_names`. These translations will have a link to their versions of the legal
+# contracts, instead of the default EN one. The main legal documents are not part of the
+# translations since they have legal meaning.
+legal_translations = ['de', 'es', 'fr', 'nl']
+
 # The name of an image file (relative to this directory) to place at the top of the title page.
 latex_logo = 'static/img/odoo_logo.png'

@@ -441,6 +453,10 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
                    )
                )

+        # Dynamic generation of localized legal doc links
+        context['legal_translations'] = legal_translations
+
+
    def _build_url(_version=None, _lang=None):
        if app.config.is_remote_build:
            # Project root like https://www.odoo.com/documentation
@@ -1,80 +1,109 @@
-===========================================
-Setting up a Content Delivery Network (CDN)
-===========================================
+=======================================
+Set up a content delivery network (CDN)
+=======================================

 .. _reference/cdn/keycdn:

-Deploying with KeyCDN_
-======================
+Deploying with KeyCDN
+=====================

-.. sectionauthor:: Fabien Meghazi
+A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, is a geographically
+distributed network of servers that provides high speed internet content. The :abbr:`CDN (Content
+Delivery Network)` provides quick, high-quality content delivery for content-heavy websites.

-This document will guide you through the setup of a KeyCDN_ account with your
-Odoo powered website.
+This document will guide you through the setup of a KeyCDN_ account with an Odoo powered website.

-Step 1: Create a pull zone in the KeyCDN dashboard
--------------------------------------------------
+Create a pull zone in the KeyCDN dashboard
+------------------------------------------

-.. image:: cdn/keycdn_create_a_pull_zone.png
-   :class: img-fluid
+On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` menu item on the left. On
+the form, give a value to the :guilabel:`Zone Name`, which will appear as part of the :abbr:`CDN
+(Content Delivery Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the :guilabel:`Zone
+Status` to :guilabel:`active` to engage the zone. For the :guilabel:`Zone Type` set the value to
+:guilabel:`Pull`, and then, finally, under the :guilabel:`Pull Settings`, enter the
+:guilabel:`Origin URL`— this address should be the full Odoo database :abbr:`URL (Uniform Resource
+Locator)`.

-When creating the zone, enable the CORS option in the
-:guilabel:`advanced features` submenu. (more on that later)
+.. example::
+   Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* subdomain prefix with the
+   actual name of the database. A custom :abbr:`URL (Uniform Resource Locator)` can be used, as
+   well, in place of the Odoo subdomain that was provided to the database.

-.. image:: cdn/keycdn_enable_CORS.png
-   :class: img-fluid
+.. image:: cdn/keycdn-zone.png
+   :align: center
+   :alt: KeyCDN's Zone configuration page.

-Once done, you'll have to wait a bit while KeyCDN_ is crawling your website.
+Under the :guilabel:`General Settings` heading below the zone form, click the :guilabel:`Show all
+settings` button to expand the zone options. This should be the last option on the page. After
+expanding the :guilabel:`General Settings` ensure that the :guilabel:`CORS` option is
+:guilabel:`enabled`.

-.. image:: cdn/keycdn_progressbar.png
-   :class: img-fluid
+Next, scroll to the bottom of the zone configuration page and :guilabel:`Save` the changes. KeyCDN
+will indicate that the new zone will be deployed. This can take about 10 minutes.

-.. note:: a new URL has been generated for your Zone, in this case it is
-          ``http://pulltest-b49.kxcdn.com``
+.. image:: cdn/zone-url.png
+   :align: center
+   :alt: KeyCDN deploying the new Zone.

-Step 2: Configure the odoo instance with your zone
--------------------------------------------------
+.. note::
+   A new :guilabel:`Zone URL` has been generated for your Zone, in this example it is
+   ``pulltest-xxxxx.kxcdn.com``. This value will differ for each database.

-In the Odoo back end, go to the :guilabel:`Website Settings`: menu, then
-activate the CDN support and copy/paste your zone URL in the
-:guilabel:`CDN Base URL` field. This field is only visible and configurable if
-you have developer mode activated.
+Copy this :guilabel:`Zone URL` to a text editor for later, as it will be used in the next steps.

-.. image:: cdn/odoo_cdn_base_url.png
-   :class: img-fluid
+Configure the Odoo instance with the new zone
+---------------------------------------------

-Now your website is using the CDN for the resources matching the
-:guilabel:`CDN filters` regular expressions.
+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 :doc:`Developer Mode <../../applications/general/developer_mode>` is activated.

-You can have a look to the HTML of your website in order to check if the CDN
-integration is properly working.
+.. note::
+   Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN Base URL` and one
+   forward slash (`/`) after the :guilabel:`CDN Base URL`.

-.. image:: cdn/odoo_check_your_html.png
-   :class: img-fluid
+:guilabel:`Save` the settings when complete.

+.. image:: cdn/cdn-base-url.png
+   :align: center
+   :alt: Activate the CDN setting in Odoo.

-Why should I activate CORS?
---------------------------
+Now the website is using the CDN for the resources matching the :guilabel:`CDN filters` regular
+expressions.

-A security restriction in some browsers (Firefox and Chrome at time of writing)
-prevents a remotely linked CSS file to fetch relative resources on this same
-external server.
+In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` integration is evidenced
+as working properly by checking the :abbr:`URL (Uniform Resource Locators)` of images. The *CDN Base
+URL* value can be seen by using your web browser's :guilabel:`Inspect` feature on the Odoo website.
+Look for it's record by searching within the :guilabel:`Network` tab inside of devtools.

-If you don't activate the CORS option in the CDN zone, the more obvious
-resulting problem on a default Odoo website will be the lack of font-awesome
-icons because the font file declared in the font-awesome CSS won't be loaded on
-the remote server.
+.. image:: cdn/test-pull.png
+   :align: center
+   :alt: The CDN Base URL can be seen using the inspect function on the Odoo website.

-Here's what you would see on your homepage in such a case:
+Prevent security issues by activating cross-origin resource sharing (CORS)
+--------------------------------------------------------------------------

-.. image:: cdn/odoo_font_file_not_loaded.png
-   :class: img-fluid
+A security restriction in some browsers (such as Mozilla Firefox and Google Chrome) prevents a
+remotely linked CSS file to fetch relative resources on this same external server.

-A security error message will also appear in the browser's console:
+If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in the :guilabel:`CDN
+Zone`, the more obvious resulting problem on a standard Odoo website will be the lack of *Font
+Awesome* icons because the font file declared in the *Font Awesome* CSS won't be loaded from the
+remote server.

-.. image:: cdn/odoo_security_message.png
-   :class: img-fluid
+When these cross-origin resource issues occur, a security error message similar to the output
+below will appear in the web browser's developer console:

-Enabling the CORS option in the CDN fixes this issue.
+``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from loading /shop:1 by
+Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the
+requested resource. Origin 'http://yourdatabase.odoo.com' is therefore not allowed access.``
+
+.. image:: cdn/odoo-security-message.png
+   :align: center
+   :alt: Error message populated in the browser console.
+
+Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the :abbr:`CDN (Content Delivery
+Network)` settings fixes this issue.

 .. _KeyCDN: https://www.keycdn.com
@@ -309,12 +309,6 @@ in ``/etc/nginx/sites-enabled/odoo.conf`` set:
    proxy_connect_timeout 720s;
    proxy_send_timeout 720s;

-    # Add Headers for odoo proxy mode
-    proxy_set_header X-Forwarded-Host $host;
-    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-    proxy_set_header X-Forwarded-Proto $scheme;
-    proxy_set_header X-Real-IP $remote_addr;
-
    # SSL parameters
    ssl_certificate /etc/ssl/nginx/server.crt;
    ssl_certificate_key /etc/ssl/nginx/server.key;
@@ -340,6 +334,11 @@ in ``/etc/nginx/sites-enabled/odoo.conf`` set:

    # Redirect requests to odoo backend server
    location / {
+      # Add Headers for odoo proxy mode
+      proxy_set_header X-Forwarded-Host $host;
+      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+      proxy_set_header X-Forwarded-Proto $scheme;
+      proxy_set_header X-Real-IP $remote_addr;
      proxy_redirect off;
      proxy_pass http://odoo;
    }
@@ -438,7 +437,7 @@ by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up
   Say Odoo has been installed via the **source**. The two git repositories for Community and
   Enterprise have been cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise`
   respectively and the :option:`--addons-path <odoo-bin --addons-path>` is
-   ``'/opt/odoo/community/odoo/addons,/opt/community/addons,/opt/odoo/enterprise'``.
+   ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``.

   Using the above NGINX (https) configuration, the following location block should be added to
   serve static files via NGINX.
@@ -608,6 +607,7 @@ security-related topics:

 Blocking Brute Force Attacks
 ----------------------------
+
 For internet-facing deployments, brute force attacks on user passwords are very common, and this
 threat should not be neglected for Odoo servers. Odoo emits a log entry whenever a login attempt
 is performed, and reports the result: success or failure, along with the target login and source IP.
@@ -4,19 +4,22 @@ Email gateway

 The Odoo mail gateway allows you to inject directly all the received emails in Odoo.

-Its principle is straightforward: your SMTP server executes the "mailgate" script for every new incoming email.
+Its principle is straightforward: your SMTP server executes the "mailgate" script for every new
+incoming email.

 The script takes care of connecting to your Odoo database through XML-RPC, and send the emails via
 the `MailThread.message_process()` feature.

 Prerequisites
 -------------
+
 - Administrator access to the Odoo database.
 - Your own mail server such as Postfix or Exim.
 - Technical knowledge on how to configure an email server.

 For Postfix
 -----------
+
 In you alias config (:file:`/etc/aliases`):

 .. code-block:: text
@@ -33,6 +36,7 @@ In you alias config (:file:`/etc/aliases`):

 For Exim
 --------
+
 .. code-block:: text

   *: |/odoo-directory/addons/mail/static/scripts/odoo-mailgate.py -d <database-name> -u <userid> -p <password>
@@ -279,8 +279,8 @@ Git
 The following requires `Git <git_>`_ to be installed on your machine and that you have basic
 knowledge of Git commands. To clone a Git repository, you must choose between cloning with HTTPS or
 SSH. If you do not know the difference between the two, the best option is most likely HTTPS. If you
-are following the :doc:`Getting started </developer/howtos/rdtraining>` developer tutorial, or plan
-on contributing to Odoo source code, choose SSH.
+are following the :doc:`Getting started </developer/tutorials/getting_started>` developer tutorial,
+or plan on contributing to Odoo source code, choose SSH.

 .. note::
   **The Enterprise Git repository does not contain the full Odoo source code**. It is only a
@@ -711,7 +711,7 @@ just logged into your own Odoo database!
     <odoo-bin -r>` CLI argument.

 .. seealso::
-   :doc:`The exhaustive list of CLI arguments for odoo-bin </developer/cli>`.
+   :doc:`The exhaustive list of CLI arguments for odoo-bin </developer/reference/cli>`.

 .. _setup/install/docker:

@@ -7,6 +7,7 @@ Maintain
 .. toctree::

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

   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/welcome>`_ to fix this.
+   <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
@@ -11,6 +11,10 @@ email address or an address created by a custom domain.
   For more information, visit `Google's documentation
   <https://support.google.com/cloud/answer/6158849>`_ on setting up OAuth.

+.. seealso::
+   - :doc:`/applications/general/auth/google`
+   - :doc:`/applications/productivity/calendar/google`
+
 Setup in Google
 ===============

@@ -201,14 +201,14 @@ Connection`.
   #. The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended
      to set it as a domain and not a full email address. It should match the domain in the two
      proceeding steps. More information can be referenced :ref:`here
-      <email_servers/outgoing-email-server>`.
+      <email_communication/from_filter>`.
   #. The :guilabel:`mail.default.from` system parameter must have the value
      `notifications\@yourdomain.com`.
   #. The :guilabel:`mail.default.from_filter` system parameter must have the value
      `yourdomain.com`. Replace `yourdomain` with the custom domain for the Odoo database. If there
      isn't one, then use the :guilabel:`mail.catchall.domain` system parameter.

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

   The :guilabel:`System Parameters` can be accessed by activating
   :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical
@@ -3,20 +3,22 @@ Odoo Online database management
 ===============================

 To manage a database, sign in to https://www.odoo.com and access the `database management page
-<https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on *My Databases*.
+<https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on
+:guilabel:`My Databases`.

 .. image:: odoo_online/my-databases.png
   :align: center
   :alt: Clicking on the user icon opens a drop-down menu. "My databases" button is highlighted.

 .. note::
-   Make sure you are connected as the administrator of the database you want to manage.
+   Make sure to connect as the administrator of the database that changes will be made on.

 .. image:: odoo_online/dropdown-menu.png
   :align: right
   :alt: Clicking on the gear icon opens the drop-down menu.

-Open the drop-down menu next to the database you want to manage by clicking on the gear icon.
+Open the drop-down menu next to the database that changes will be made on by clicking on the gear
+icon.

 Several actions are available:

@@ -35,22 +37,22 @@ Several actions are available:
 Upgrade
 =======

-If you are *not* on the latest **Online version**, you should receive an invitation to :doc:`upgrade
-<../upgrade>` your database. A **Rolling Release button** on your database's main screen proposes an
-upgrade to the latest version (e.g., 13.0 to 15.1).
+If the database is *not* on the latest **Online version**, the administrator should receive an
+invitation to :doc:`upgrade <../upgrade>` the database. A :guilabel:`Rolling Release`` button on the
+database's main screen proposes an upgrade to the latest version (e.g., 14.0 to 16.1).

 .. important::
-   - | **If your Odoo database's version is lower than the latest major release:**
-     | You must upgrade your database within two months. After these two months, an automatic
+   - | **If the Odoo database's version is lower than the latest major release:**
+     | The database must be upgraded within two months. After these two months, an automatic
       upgrade is initiated.
-   - | **If your Odoo database's version is equal to or higher than the latest major release:**
-     | You can disregard the invitation to upgrade as you probably wouldn't benefit from new
+   - | **If the Odoo database's version is equal to or higher than the latest major release:**
+     | Disregard the invitation to upgrade as the database probably wouldn't benefit from new
       features every two months.

 .. note::
   Versions that are not supported anymore become deprecated and need to be updated to avoid
-   security issues. We recommend you initiate the upgrade of the database yourself, as this method
-   allows you to request a test upgrade of your database to check for any discrepancies.
+   security issues. Odoo recommends that the company initiate the upgrade, as this method allows for
+   the company to request a test upgrade of the database to check for any discrepancies.

 .. seealso::
   - :doc:`../upgrade`
@@ -61,12 +63,12 @@ upgrade to the latest version (e.g., 13.0 to 15.1).
 Duplicate
 =========

-Make an exact copy of the database to be able to perform testing without compromising the daily
-operations.
+This allows to make an exact copy of the database to be able to perform testing without compromising
+the daily operations.

 .. important::
-   - By checking *For testing purposes*, all external communication (emails, payments, delivery
-     orders, etc.) are disabled by default on the duplicated database.
+   - By checking :guilabel:`For testing purposes`, all external communication (emails, payments,
+     delivery orders, etc.) are disabled by default on the duplicated database.
   - Duplicate databases expire automatically after 15 days.

 .. _odoo_online/rename:
@@ -81,7 +83,7 @@ Rename the database and its URL.
 Download
 ========

-Download instantly a ZIP file with a backup of the database.
+Instantly download a ZIP file with a backup of the database.

 .. note::
   Databases are backed up daily according to the `Odoo Cloud SLA
@@ -115,8 +117,8 @@ Delete a database instantly.
   Deleting a database means that all data is permanently lost. The deletion is instant and for all
   users. It is recommended to create a backup of the database before deleting it.

-Read carefully the warning message that pops up and proceed only if you fully understand the
-implications of deleting a database:
+Carefully read the warning message that pops up and proceed only if the implications of deleting a
+database are fully understood:

 .. image:: odoo_online/delete.png
   :align: center
@@ -127,7 +129,6 @@ implications of deleting a database:
   - The database name is immediately available for a new database.
   - It is not possible to delete a database if it is expired or linked to a subscription. If
     needed, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
-   - To delete your account, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.

 .. _odoo_online/contact-support:

@@ -142,14 +143,15 @@ pre-filled.
 Invite / Remove Users
 =====================

-To invite users, fill out the email address of the new user and click on *Invite*. To add multiple
-users, click on *Add more users*.
+To invite users, fill out the email address of the new user and click on :guilabel:`Invite`. To add
+multiple users, click on :guilabel:`Add more users`.

 .. image:: odoo_online/invite-users.png
   :align: center
   :alt: Clicking on "Add more users" adds additional email fields.

-To remove users, select the users to remove and click on *Remove*.
+To remove users, select the users to remove and click on :guilabel:`Remove`.

 .. seealso::
   - :doc:`/applications/general/users/manage_users`
+   - :doc:`/applications/general/users/delete_account`
@@ -19,12 +19,12 @@ 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
+   :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?

@@ -42,15 +42,13 @@ Solutions
    <https://accounts.odoo.com/my/subscription>`__ with the button "Unlink database"

    .. image:: on_premise/unlink_single_db.png
-        :align: center
-
+       :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
-
+       :align: center

 * Do you have the updated version of Odoo 9?

@@ -63,8 +61,7 @@ Solutions
    specifying which database is problematic:

    .. image:: on_premise/unlink_db_name_collision.png
-        :align: center
-
+       :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>`.
@@ -85,8 +82,6 @@ Solutions
  * 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
 -----------------------------------

@@ -94,16 +89,15 @@ 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
+   :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.
@@ -123,15 +117,14 @@ 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.
-
+   :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
@@ -142,7 +135,6 @@ Solutions
 None of those solutions worked for you? Please contact our
 `Support <https://www.odoo.com/help>`__

-
 .. _force_ping:

 .. _duplicate_premise:
@@ -155,8 +147,7 @@ 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
-
+   :align: center

 When you duplicate a local database, it is **strongly** advised to change
 the duplicated database's uuid (Unniversally Unique Identifier), since this
@@ -164,8 +155,9 @@ 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.
+.. 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
@@ -173,4 +165,4 @@ use the unix command ``uuidgen`` to generate a new uuid. You can then simply rep
 other record by clicking on it and using the edit button.

 .. image:: on_premise/db_uuid.png
-    :align: center
+   :align: center
@@ -26,11 +26,15 @@ This matrix shows the support status of every version.
 +-----------------+-------------+----------+-------------+----------------+------------------------+
 |                 | Odoo Online | Odoo.sh  | On-Premise  | Release date   | End of support         |
 +=================+=============+==========+=============+================+========================+
+| Odoo saas~16.2  | |green|     | N/A      | N/A         | March 2023     | June 2023 (planned)    |
+-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo saas~16.1  | |green|     | N/A      | N/A         | February 2023  | April 2023             |
+-----------------+-------------+----------+-------------+----------------+------------------------+
 | **Odoo 16.0**   | |green|     | |green|  | |green|     | October 2022   | October 2025 (planned) |
 +-----------------+-------------+----------+-------------+----------------+------------------------+
-| Odoo saas~15.2  | |green|     | N/A      | N/A         | March 2022     |                        |
+| Odoo saas~15.2  | |red|       | N/A      | N/A         | March 2022     | January 2023           |
 +-----------------+-------------+----------+-------------+----------------+------------------------+
-| Odoo saas~15.1  | |red|       | N/A      | N/A         | February 2022  |                        |
+| Odoo saas~15.1  | |red|       | N/A      | N/A         | February 2022  | July 2022              |
 +-----------------+-------------+----------+-------------+----------------+------------------------+
 | **Odoo 15.0**   | |green|     | |green|  | |green|     | October 2021   | October 2024 (planned) |
 +-----------------+-------------+----------+-------------+----------------+------------------------+
@@ -104,6 +104,7 @@ and you're all set.

 Source Install (Tarball)
 ------------------------
+
 If you have originally installed Odoo with the "tarball" version (source code archive), you have
 to replace the installation directory with a newer version. First download the latest tarball
 from Odoo.com. They are updated daily and include the latest security fixes (see step #1)
@@ -123,6 +124,7 @@ Finally, restart the Odoo service or reboot the machine, and you are all set.

 Source Install (Github)
 -----------------------
+
 If you have originally installed Odoo with a full Github clone of the official repositories, the
 update procedure requires you to pull the latest source code via git.
 Change into the directory for each repository (the main Odoo repository, and the Enterprise
@@ -1,8 +1,8 @@
 :nosearch:

-=================
+========
 Advanced
-=================
+========

 .. toctree::
   :titlesonly:
@@ -1,7 +1,7 @@

-==================================
+==========
 Containers
-==================================
+==========

 Overview
 ========
@@ -167,7 +167,7 @@ In the above commands, the argument:
 * ``--stop-after-init`` will immediately shutdown the server instance after it completed the operations you asked.

 More options are available and detailed in the
-:doc:`CLI documentation </developer/cli>`.
+:doc:`CLI documentation </developer/reference/cli>`.

 You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh to run your server.
 Look for "*odoo: addons paths*":
@@ -1,9 +1,9 @@

 .. _odoosh-advanced-frequent_technical_questions:

-==================================
+============================
 Frequent Technical Questions
-==================================
+============================

 "Scheduled actions do not run at the exact time they were expected"
 -------------------------------------------------------------------
@@ -1,9 +1,9 @@

 .. _odoosh-advanced-submodules:

-==================================
+==========
 Submodules
-==================================
+==========

 Overview
 ========
@@ -64,7 +64,7 @@ On Github, you can get the repository URL with the *Clone or download* button of
 .. _odoosh-advanced-submodules-withgit:

 With Git (advanced)
---------------------
+-------------------

 In a terminal, in the folder where your Git repository is cloned,
 checkout the branch in which you want to add a submodule:
@@ -1,8 +1,8 @@
 :nosearch:

-=================
+===========
 Get started
-=================
+===========

 .. toctree::
   :titlesonly:
@@ -1,7 +1,6 @@
-
-==================================
+========
 Branches
-==================================
+========

 Overview
 ========
@@ -14,7 +13,7 @@ The branches view gives you an overview of the different branches your repositor
 .. _odoosh-gettingstarted-branches-stages:

 Stages
-===============
+======

 Odoo.sh offers three different stages for your branches: production, staging and development.

@@ -27,6 +26,7 @@ You can change the stage of a branch by drag and dropping it into the stage sect

 Production
 ----------
+
 This is the branch holding the code on which your production database runs.
 There can be only one production branch.

@@ -42,7 +42,7 @@ instance will be held temporarily unavailable for maintenance reason.

 This method is equivalent to perform an upgrade of the module through the Apps menu,
 or through the :code:`-u` switch of
-:doc:`the command line </developer/cli>`.
+:doc:`the command line </developer/reference/cli>`.

 In the case the changes in the commit prevent the server to restart,
 or if the modules update fails,
@@ -59,6 +59,7 @@ will automatically be set back to the development stage after 30 days.

 Staging
 -------
+
 Staging branches are meant to test your new features using the production data without compromising
 the actual production database with test records. They will create databases that are neutralized
 duplicates of the production database.
@@ -83,9 +84,9 @@ The unit tests are not performed as, in Odoo, they currently rely on the demo da
 production database. In the future, if Odoo supports to run the unit tests without the demo data,
 Odoo.sh will then consider running the tests on staging databases.

-
 Development
 -----------
+
 Development branches create new databases using the demo data to run the unit tests.
 The installed modules are the ones included in your branches. You can change this list of modules
 to install in your :ref:`project Settings <odoosh-gettingstarted-settings-modules-installation>`.
@@ -107,6 +108,7 @@ After that, they can be automatically garbage collected to make room for new dat

 Merging your branches
 ---------------------
+
 You can merge your branches easily by drag and dropping them into each other.

 .. image:: branches/interface-branches-merge.png
@@ -147,10 +149,11 @@ If you test configuration changes in staging branches, and want them to be appli
 .. _odoosh-gettingstarted-branches-tabs:

 Tabs
-=============
+====

 History
 -------
+
 An overview of your branch history:

 * The messages of the commits and their authors,
@@ -168,6 +171,7 @@ When an operation is successful, you can access the database thanks to the *conn

 Mails
 -----
+
 This tab contains the mail catcher. It displays an overview of the emails sent by your database.
 The mail catcher is available for your development and
 staging branches as the emails of your production database are really sent instead of being intercepted.
@@ -178,6 +182,7 @@ staging branches as the emails of your production database are really sent inste

 Shell
 -----
+
 A shell access to your container. You can perform basic linux commands (:code:`ls`, :code:`top`)
 and open a shell on your database by typing :code:`psql`.

@@ -187,13 +192,13 @@ and open a shell on your database by typing :code:`psql`.
 You can open multiple tabs and drag-and-drop them to arrange the layout as you wish,
 for instance side by side.

-
 .. Note::
  Long running shell instances are not guaranteed. Idle shells can be
  disconnected at anytime in order to free up resources.

 Editor
 ------
+
 An online integrated development environment (IDE) to edit the source code.
 You can also open terminals, Python consoles and even Odoo Shell consoles.

@@ -205,6 +210,7 @@ for instance side by side.

 Monitoring
 ----------
+
 This link contains various monitoring metrics of the current build.

 .. image:: branches/interface-branches-monitoring.png
@@ -217,6 +223,7 @@ On the graphs, annotations help you relate to changes on the build (database imp

 Logs
 ----
+
 A viewer to have a look to your server logs.

 .. image:: branches/interface-branches-logs.png
@@ -240,6 +247,7 @@ The fetching is automatically stopped after 5 minutes. You can restart it using

 Backups
 -------
+
 A list of the backups available for download and restore, the ability to perform a manual backup and to import a
 database.

@@ -398,14 +406,13 @@ settings to increase the deliverability of your outgoing emails.
 The configuration steps are explained in the documentation about :ref:`SPF
 <email_communication/spf_compliant>` and :ref:`DKIM <email_communication/dkim_compliant>`.

-
 .. Warning::
  Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host can lead to the
  delivery of your emails as spam in your contacts inbox.

-
 Shell commands
 ==============
+
 In the top right-hand corner of the view, different shell commands are available.

 .. image:: branches/interface-branches-shellcommands.png
@@ -418,6 +425,7 @@ such as ``<URL>``, ``<PATH>``, ...

 Clone
 -----
+
 Download the Git repository.

 .. code-block:: bash
@@ -433,6 +441,7 @@ The *run* button is not available for this command, as it is meant to be used on

 Fork
 ----
+
 Create a new branch based on the current branch.

 .. code-block:: bash
@@ -449,6 +458,7 @@ Uploads the new branch *feature-1* on your remote repository.

 Merge
 -----
+
 Merge the current branch in another branch.

 .. code-block:: bash
@@ -465,8 +475,10 @@ Uploads the changes you just added in the *master* branch on your remote reposit

 SSH
 ---
+
 Setup
 ~~~~~
+
 In order to use SSH, you have to set up your profile SSH public key (if it is not already done).
 To do so, follow these steps:

@@ -506,7 +518,6 @@ you'll be granted ssh access to the build.
  Long running ssh connections are not guaranteed. Idle connections will be
  disconnected in order to free up resources.

-
 Submodule
 ---------

@@ -1,17 +1,18 @@

 .. _odoosh-gettingstarted-builds:

-==================================
+======
 Builds
-==================================
+======

 Overview
 ========

 In Odoo.sh, a build is considered as a database loaded by an Odoo server
-(`odoo/odoo <https://github.com/odoo/odoo>`_ & `odoo/enterprise <https://github.com/odoo/enterprise>`_)
-running on a specific revision of your project repository in a containerized environment.
-Its purpose is to test the well-behavior of the server, the database and the features with this revision.
+(`odoo/odoo <https://github.com/odoo/odoo>`_ & `odoo/enterprise
+<https://github.com/odoo/enterprise>`_) running on a specific revision of your project repository in
+a containerized environment. Its purpose is to test the well-behavior of the server, the database
+and the features with this revision.

 .. image:: builds/interface-builds.png
   :align: center
@@ -28,13 +29,13 @@ A successful build is highlighted in green.
 A build is considered failed if errors come up during its creation.
 A failed build is highlighted in red.

-If warnings come up during the creation, but there are no errors, the build is considered almost successful.
-It is highlighted in yellow to notify the developer warnings were raised.
+If warnings come up during the creation, but there are no errors, the build is considered almost
+successful. It is highlighted in yellow to notify the developer warnings were raised.

-Builds do not always create a database from scratch.
-For instance, when pushing a change on the production branch, the build created just starts the server
-with your new revision and tries to load the current production database on it.
-If no errors come up, the build is considered successful, and otherwise failed.
+Builds do not always create a database from scratch. For instance, when pushing a change on the
+production branch, the build created just starts the server with your new revision and tries to load
+the current production database on it. If no errors come up, the build is considered successful, and
+otherwise failed.

 Stages
 ======
@@ -48,14 +49,15 @@ If this build is successful, this database is considered as the production datab
 From then, pushes on the production branch will create new builds that attempt to load the database
 using a server running with the new revision.

-If the build is successful, or has warnings but no errors, the production database will now run with this build, along
-with the revision associated to this build.
+If the build is successful, or has warnings but no errors, the production database will now run with
+this build, along with the revision associated to this build.

-If the build fails to load or update the database, then the previous successful build is re-used to load the database,
-and therefore the database will run using a server running with the previous successful revision.
+If the build fails to load or update the database, then the previous successful build is re-used to
+load the database, and therefore the database will run using a server running with the previous
+successful revision.

-The build used to run the production database is always the first of the builds list. If a build fails, it is
-put after the build currently running the production database.
+The build used to run the production database is always the first of the builds list. If a build
+fails, it is put after the build currently running the production database.

 Staging
 -------
@@ -63,18 +65,17 @@ Staging
 Staging builds duplicate the production database,
 and try to load this duplicate with the revisions of the staging branches.

-Each time you push a new revision on a staging branch, the build created uses a new copy of the production database.
-The databases are not re-used between builds of the same branch. This ensures:
+Each time you push a new revision on a staging branch, the build created uses a new copy of the
+production database. The databases are not re-used between builds of the same branch. This ensures:

-* staging builds use databases that are close to what the production looks like,
-  so you do not make your tests with outdated data,
+* staging builds use databases that are close to what the production looks like, so you do not make
+  your tests with outdated data,

-* you can play around as much as you want in the same staging database,
-  and you can then ask for a rebuild when you want to restart with a new copy of the production.
+* you can play around as much as you want in the same staging database, and you can then ask for a
+  rebuild when you want to restart with a new copy of the production.

-Nevertheless, this means that if you make configuration changes in staging databases
-and do not apply them in the production,
-they will not be passed on the next build of the same staging branch.
+Nevertheless, this means that if you make configuration changes in staging databases and do not
+apply them in the production, they will not be passed on the next build of the same staging branch.

 Development
 -----------
@@ -86,30 +87,30 @@ as they are meant to raise errors if something wrong occurs.

 If all tests pass, and there is no error, the build will be considered successful.

-According to the list of modules to install and test, a development build can take up to 1 hour to be ready.
-This is due to the large number of tests set in the default Odoo modules suite.
+According to the list of modules to install and test, a development build can take up to 1 hour to
+be ready. This is due to the large number of tests set in the default Odoo modules suite.

 Features
 ========

-The production branch will always appear first,
-and then the other branches are ordered by last build created. You can filter out the branches.
+The production branch will always appear first, and then the other branches are ordered by last
+build created. You can filter out the branches.

 .. image:: builds/interface-builds-branches.png
   :align: center

-For each branch, you can access the last build's database using the *Connect* link and jump to the branch code using
-the *Github* link. For other branches than the production, you can create a new build which will use the latest revision
-of the branch using the link *rebuild*. This last link is not available when there is already a build in progress for
-the branch.
+For each branch, you can access the last build's database using the *Connect* link and jump to the
+branch code using the *Github* link. For other branches than the production, you can create a new
+build which will use the latest revision of the branch using the link *rebuild*. This last link is
+not available when there is already a build in progress for the branch.

 .. image:: builds/interface-builds-build.png
   :align: center

-For each build, you can access the revision changes using the button with the Github icon.
-You can access the build's database as the administrator using the *Connect* button.
-Also, you can access the database with another user using the *Connect as* button,
-in the dropdown menu of the *Connect* button.
+For each build, you can access the revision changes using the button with the Github icon. You can
+access the build's database as the administrator using the *Connect* button. Also, you can access
+the database with another user using the *Connect as* button, in the dropdown menu of the *Connect*
+button.

 .. _odoosh-gettingstarted-builds-download-dump:

@@ -118,6 +119,6 @@ in the dropdown menu of the *Connect* button.

 .. _odoosh-gettingstarted-builds-dropdown-menu:

-In the dropdown menu of the build, you can access the same features than in :ref:`the branches view <odoosh-gettingstarted-branches-tabs>`:
-*Logs*, *Web Shell*, *Editor*, *Outgoing e-mails*.
-You also have the possibility to *Download a dump* of the build's database.
+In the dropdown menu of the build, you can access the same features than in :ref:`the branches view
+<odoosh-gettingstarted-branches-tabs>`: *Logs*, *Web Shell*, *Editor*, *Outgoing e-mails*. You also
+have the possibility to *Download a dump* of the build's database.
@@ -1,9 +1,9 @@

 .. _odoosh-gettingstarted-create:

-==================================
+===================
 Create your project
-==================================
+===================

 Deploy your platform
 ====================
@@ -16,7 +16,8 @@ Go to `Odoo.sh <https://www.odoo.sh/>`_ and hit the *Deploy your platform* butto
 Sign in with Github
 ===================

-Sign in with your Github account. If you do not have an account yet, hit the *Create an account* link.
+Sign in with your Github account. If you do not have an account yet, hit the *Create an account*
+link.

 .. image:: create/github-signin.png
   :align: center
@@ -33,34 +34,44 @@ Odoo.sh basically needs:

 * to know your Github login and email,
 * to create a new repository in case you decide to start from scratch,
-* to read your existing repositories, including the ones of your organizations, in case you want to start from an existing repository,
+* to read your existing repositories, including the ones of your organizations, in case you want to
+  start from an existing repository,
 * to create a webhook to be notified each time you push changes,
-* to commit changes to make your deployment easier, merging branches or adding new `submodules <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ for example.
+* to commit changes to make your deployment easier, merging branches or adding new `submodules
+  <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ for example.

 Submit your project
 ===================

-Choose if you want to start from scratch by creating a new repository, or if you want to use an existing repository.
+Choose if you want to start from scratch by creating a new repository, or if you want to use an
+existing repository.

 Then, choose a name or select the repository you want to use.

-Choose the Odoo version you want to use. If you plan to import an existing database or an existing set of applications, you might need to choose the according version. If you start from scratch, use the latest version.
+Choose the Odoo version you want to use. If you plan to import an existing database or an existing
+set of applications, you might need to choose the according version. If you start from scratch, use
+the latest version.

-Enter your *subscription code*. This is also called *subscription referral*, *contract number* or *activation code*.
+Enter your *subscription code*. This is also called *subscription referral*, *contract number* or
+*activation code*.

 It should be the code of your Enterprise subscription that includes Odoo.sh.

-Partners can use their partnership codes to start a trial. Should their clients start a project, they ought to get an Enterprise subscription including Odoo.sh and use its subscription code. The partner will get the full amount as back commission.
-Contact your sales representative or account manager in order to get it.
+Partners can use their partnership codes to start a trial. Should their clients start a project,
+they ought to get an Enterprise subscription including Odoo.sh and use its subscription code. The
+partner will get 50% of the amount back as commission. Contact your sales representative or account
+manager in order to get it.

 When submitting the form, if you are notified your subscription is not valid, it either means:

 * it is not an existing subscription,
 * it is not a partnership subscription,
 * it is an enterprise subscription, but which does not include Odoo.sh,
-* it is neither a partnership subscription or an enterprise subscription (e.g. an online subscription).
+* it is neither a partnership subscription or an enterprise subscription (e.g. an online
+  subscription).

-In case of doubt with your subscription, please contact the `Odoo support <https://www.odoo.com/help>`_.
+In case of doubt with your subscription, please contact the `Odoo support
+<https://www.odoo.com/help>`_.

 .. image:: create/deploy-form.png
   :align: center
@@ -68,7 +79,8 @@ In case of doubt with your subscription, please contact the `Odoo support <https
 You're done !
 =============

-You can start using Odoo.sh. Your first build is about to be created. You will soon be able to connect to your first database.
+You can start using Odoo.sh. Your first build is about to be created. You will soon be able to
+connect to your first database.

 .. image:: create/deploy-done.png
   :align: center
@@ -88,9 +100,10 @@ If you use community or custom modules, add them in a branch in your Github repo
 Databases hosted on the Odoo.com online platform do not have any custom modules.
 Users of these databases can therefore skip this step.

-You can structure your modules as you wish, Odoo.sh will automatically detect the folders containing Odoo addons.
-For instance, you can put all your modules folder in the root directory of your repository,
-or group the modules in folders by categories that you define (accounting, project, ...).
+You can structure your modules as you wish, Odoo.sh will automatically detect the folders containing
+Odoo addons. For instance, you can put all your modules folder in the root directory of your
+repository, or group the modules in folders by categories that you define (accounting, project,
+...).

 For community modules available in public Git repositories,
 you can also consider to add them using :ref:`Submodules <odoosh-advanced-submodules>`.
@@ -111,7 +124,8 @@ Access the URL :file:`/web/database/manager` of your on-premise database and dow
  If you cannot access the database manager, it may have been disabled by your system administrator.
  See the :ref:`database manager security documentation <db_manager_security>`.

-You will need the master password of your database server. If you do not have it, contact your system administrator.
+You will need the master password of your database server. If you do not have it, contact your
+system administrator.

 .. image:: create/create-import-onpremise-backup.png
   :align: center
@@ -124,10 +138,11 @@ Choose a zip including the filestore as the backup format.
 Odoo Online databases
 ~~~~~~~~~~~~~~~~~~~~~

-`Access your databases manager <https://accounts.odoo.com/my/databases/manage>`_ and download a backup of your database.
+`Access your databases manager <https://accounts.odoo.com/my/databases/manage>`_ and download a
+backup of your database.

 .. image:: create/create-import-online-backup.png
-  :align: center
+   :align: center

 .. Warning::

@@ -136,52 +151,55 @@ Odoo Online databases
 Upload the backup
 -----------------

-Then, in your Odoo.sh project, in the backups tab of your production branch, import the backup you just downloaded.
+Then, in your Odoo.sh project, in the backups tab of your production branch, import the backup you
+just downloaded.

 .. image:: create/create-import-production.png
   :align: center

-Once the backup imported, you can access the database using the *Connect* button in the history of the branch.
+Once the backup imported, you can access the database using the *Connect* button in the history of
+the branch.

 .. image:: create/create-import-production-done.png
-  :align: center
+   :align: center

 Check your outgoing email servers
 ---------------------------------

 There is a default mail server provided with Odoo.sh.
 To use it, there must be no enabled outgoing mail server configured in your database in
-:menuselection:`Settings --> Technical --> Outgoing Mail Servers`
-(:ref:`Developer mode <developer-mode>` must be activated).
+:menuselection:`Settings --> Technical --> Outgoing Mail Servers` (:ref:`Developer mode
+<developer-mode>` must be activated).

-After the import of your database,
-all outgoing email servers are disabled so you use the Odoo.sh email server provided by default.
+After the import of your database, all outgoing email servers are disabled so you use the Odoo.sh
+email server provided by default.

-.. Warning::
-
-  Port 25 is (and will stay) closed. If you want to connect to an external SMTP server, you should use ports 465 and 587.
+.. warning::
+   Port 25 is (and will stay) closed. If you want to connect to an external SMTP server, you should
+   use ports 465 and 587.

 Check your scheduled actions
 ----------------------------

 All scheduled actions are disabled after the import.

-This is to prevent your newly imported database to perform actions that could impact your running production,
-such as sending the mails remaining in the queue, processing mass mailings, or third-party services synchronization
-(Calendars, files hosting, ...).
+This is to prevent your newly imported database to perform actions that could impact your running
+production, such as sending the mails remaining in the queue, processing mass mailings, or
+third-party services synchronization (Calendars, files hosting, ...).

 If you plan to make the imported database your production, enable the scheduled actions you need.
-You can check what is enabled in the database of origin and enable the same actions in the imported database.
-Scheduled actions are located under :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`.
+You can check what is enabled in the database of origin and enable the same actions in the imported
+database. Scheduled actions are located under :menuselection:`Settings --> Technical --> Automation
+--> Scheduled Actions`.

 Register your subscription
 --------------------------

 Your subscription is unlinked after the import.

-The imported database is considered a duplicate by default and the enterprise subscription is therefore removed,
-as you can only have one database linked per subscription.
+The imported database is considered a duplicate by default and the enterprise subscription is
+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 <../../maintain/on_premise>` for instructions.
+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
+<../../maintain/on_premise>` for instructions.
@@ -27,7 +27,7 @@ Create the development branch
 =============================

 From Odoo.sh
-------------
+------------

 In the branches view:

@@ -43,20 +43,18 @@ In the branches view:
 .. |pic2| image:: first_module/firstmodule-development-fork.png
   :width: 45%

-
 Once the build created, you can access the editor and browse to the folder *~/src/user* to access
 to the code of your development branch.

 .. image:: first_module/firstmodule-development-editor.png
-  :align: center
+   :align: center

 .. image:: first_module/firstmodule-development-editor-interface.png
-  :align: center
+   :align: center

 From your computer
 ------------------

-
 Clone your Github repository on your computer:

 .. code-block:: bash
@@ -72,7 +70,6 @@ Create a new branch:

  $ git checkout -b feature-1 master

-
 Create the module structure
 ===========================

@@ -119,11 +116,11 @@ The below structure will be generated:
      ├── templates.xml
      └── views.xml

-.. Warning::
+.. warning::

-  Do not use special characters other than the underscore ( _ ) for your module name, not even an
-  hyphen ( - ). This name is used for the Python classes of your module, and having classes name
-  with special characters other than the underscore is not valid in Python.
+   Do not use special characters other than the underscore ( _ ) for your module name, not even an
+   hyphen ( - ). This name is used for the Python classes of your module, and having classes name
+   with special characters other than the underscore is not valid in Python.

 Uncomment the content of the files:

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

 If you want to create your module structure manually,
-you can follow :doc:`Build an Odoo module </developer/howtos/backend>` 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
@@ -222,7 +219,6 @@ install.

 You can then play around with your module, create new records and test your features and buttons.

-
 Test with the production data
 =============================

@@ -237,12 +233,12 @@ You can either:
  title.

  .. image:: first_module/firstmodule-test-devtostaging.png
-    :align: center
+     :align: center

 * Merge it in an existing staging branch, by drag and dropping it onto the given staging branch.

  .. image:: first_module/firstmodule-test-devinstaging.png
-    :align: center
+     :align: center

 You can also use the :code:`git merge` command to merge your branches.

@@ -250,7 +246,7 @@ This will create a new staging build, which will duplicate the production databa
 using a server updated with your latest changes of your branch.

 .. image:: first_module/firstmodule-test-mergedinstaging.png
-  :align: center
+   :align: center

 Once the database ready, you can access it using the *Connect* button.

@@ -419,7 +415,7 @@ Or, from your computer terminal:
 The platform will then create a new build for the branch *feature-1*.

 .. image:: first_module/firstmodule-test-addachange-build.png
-  :align: center
+   :align: center

 Once you tested your changes, you can merge your changes in the production branch, for instance by
 drag-and-dropping the branch on the production branch in the Odoo.sh interface. As you increased the
@@ -1,9 +1,9 @@

 .. _odoosh-gettingstarted-online-editor:

-==================================
+=============
 Online Editor
-==================================
+=============

 Overview
 ========
@@ -120,24 +120,23 @@ In this last command,
 .. image:: online-editor/interface-editor-commit-push.png
   :align: center

-.. Note::
-  The SSH Github remote is not used because your SSH private key
-  is not hosted in your build containers (for obvious security concerns)
-  nor forwarded through an SSH Agent (as you access this editor through a web browser)
-  and you therefore cannot authenticate yourself to Github using SSH.
-  You have to use the HTTPS remote of your Github repository to push your changes,
-  which is added automatically named as *https* in your Git remotes.
-  You will be prompted to enter your Github username and password.
-  If you activated the two-factor authentication on Github,
-  you can create a
-  `personal access token <https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/>`_
-  and use it as password. Granting the ``repo`` permission suffices.
+.. note::
+   The SSH Github remote is not used because your SSH private key
+   is not hosted in your build containers (for obvious security concerns)
+   nor forwarded through an SSH Agent (as you access this editor through a web browser)
+   and you therefore cannot authenticate yourself to Github using SSH.
+   You have to use the HTTPS remote of your Github repository to push your changes,
+   which is added automatically named as *https* in your Git remotes.
+   You will be prompted to enter your Github username and password.
+   If you activated the two-factor authentication on Github,
+   you can create a `personal access token
+   <https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/>`_
+   and use it as password. Granting the ``repo`` permission suffices.

-
-.. Note::
-  The Git source folder *~/src/user* is not checked out on a branch but rather on a detached revision:
-  This is because builds work on specific revisions rather than branches.
-  In other words, this means you can have multiple builds on the same branch, but on different revisions.
+.. note::
+   The Git source folder *~/src/user* is not checked out on a branch but rather on a detached revision:
+   This is because builds work on specific revisions rather than branches.
+   In other words, this means you can have multiple builds on the same branch, but on different revisions.

 Once your changes are pushed,
 according to your :ref:`branch push behavior <odoosh-gettingstarted-branches-tabs-settings>`,
@@ -166,12 +165,11 @@ You can also open an Odoo Shell console to play around
 with the Odoo registry and model methods of your database. You can also directly read or write
 on your records.

-.. Warning::
-  In an Odoo Console, transactions are automatically committed.
-  This means, for instance, that changes in records are applied effectively in the database.
-  If you change the name of a user, the name of the user is changed in your database
-  as well.
-  You therefore should use Odoo consoles carefully on production databases.
+.. warning::
+   In an Odoo Console, transactions are automatically committed.
+   This means, for instance, that changes in records are applied effectively in the database.
+   If you change the name of a user, the name of the user is changed in your database as well.
+   You therefore should use Odoo consoles carefully on production databases.

 You can use *env* to invoke models of your database registry, e.g. :code:`env['res.users']`.

@@ -196,4 +194,4 @@ You can also use
 to display graphs.

 .. image:: online-editor/interface-editor-console-odoo-graph.png
-  :align: center
+   :align: center
@@ -1,7 +1,6 @@
-
-==================================
+========
 Settings
-==================================
+========

 Overview
 ========
@@ -21,8 +20,8 @@ The name of your project.

 This defines the address that will be used to access your production database.

-Addresses of your staging and development builds are derived from this name and assigned automatically.
-However, when you change your project name, only future builds will use the new name.
+Addresses of your staging and development builds are derived from this name and assigned
+automatically. However, when you change your project name, only future builds will use the new name.

 .. _odoosh-gettingstarted-settings-collaborators:

@@ -39,10 +38,10 @@ There are two levels of users:
 * Admin: has access to all features of Odoo.sh.
 * User: does not have access to the project settings nor to the production and staging databases.

-The user group is meant for developers who can make modifications in your code but are not allowed to access the
-production data.
-Users of this group cannot connect to the production and staging databases using the *1-click connect* feature,
-but they can of course use their regular account on these databases if they have one, using their regular credentials.
+The user group is meant for developers who can make modifications in your code but are not allowed
+to access the production data. Users of this group cannot connect to the production and staging
+databases using the *1-click connect* feature, but they can of course use their regular account on
+these databases if they have one, using their regular credentials.

 In addition, they cannot use the webshell nor have access to the server logs.

@@ -90,7 +89,8 @@ Allow public access to your development builds.
 .. image:: settings/interface-settings-public.png
   :align: center

-If activated, this option exposes the Builds page publicly, allowing visitors to connect to your development builds.
+If activated, this option exposes the Builds page publicly, allowing visitors to connect to your
+development builds.

 In addition, visitors have access to the logs, shell and mails of your development builds.

@@ -98,11 +98,11 @@ Production and staging builds are excluded, visitors can only see their status.

 .. _odoosh-gettingstarted-settings-modules-installation:

-
 Custom domains
 ==============

-To configure additional domains please refer to the corresponding branch's :ref:`settings tab <odoosh-gettingstarted-branches-tabs-settings>`.
+To configure additional domains please refer to the corresponding branch's :ref:`settings tab
+<odoosh-gettingstarted-branches-tabs-settings>`.

 .. _odoosh-gettingstarted-settings-submodules:

@@ -112,10 +112,10 @@ Submodules
 Configure the deploy keys for the private repositories you use
 as submodules in your branches to allow Odoo.sh to download them.

-.. Warning::
-  These settings are required for **private repositories** only.
-  If you are looking on how to set up your submodules,
-  instructions are available in the chapter :ref:`Submodules <odoosh-advanced-submodules>` of this documentation.
+.. warning::
+   These settings are required for **private repositories** only. If you are looking on how to set
+   up your submodules, instructions are available in the chapter :ref:`Submodules
+   <odoosh-advanced-submodules>` of this documentation.

 .. image:: settings/interface-settings-submodules.png
   :align: center
@@ -130,7 +130,8 @@ To configure the deploy key for a private repository, proceed as follows:
 * in the input, paste the SSH URL of your private sub-repository and click on *Add*,

  * e.g. *git@github.com:USERNAME/REPOSITORY.git*
-  * it can be another Git server than Github, such as Bitbucket, Gitlab or even your own self-hosted server
+  * it can be another Git server than Github, such as Bitbucket, Gitlab or even your own self-hosted
+    server

 * copy the public key,

@@ -157,8 +158,9 @@ Storage size is computed as follows:

 * the size of the disk files available in your container: database filestore, sessions storage directory...

-.. Warning::
-  In case you want to analyze disk usage, you can run the tool `ncdu <https://dev.yorhel.nl/ncdu/man>`_ in your Web Shell.
+.. warning::
+   In case you want to analyze disk usage, you can run the tool `ncdu
+   <https://dev.yorhel.nl/ncdu/man>`_ in your Web Shell.

 Should your production database size grow to exceed what's provisioned in your subscription, it
 will automatically be synchronized with it.
@@ -191,7 +193,8 @@ add more, it will automatically be synchronized with your subscription.
 Activation
 ==========

-Shows the status of the project's activation. You can change the project's activation code if needed.
+Shows the status of the project's activation. You can change the project's activation code if
+needed.

 .. image:: settings/interface-settings-activation.png
   :align: center
@@ -1,12 +1,12 @@
-
-==================================
+======
 Status
-==================================
+======

 Overview
 ========

-The status page shows statistics regarding the servers your project uses. It includes the servers availability.
+The status page shows statistics regarding the servers your project uses. It includes the servers
+availability.

 .. image:: status/interface-status.png
   :align: center
@@ -1,8 +1,8 @@
 :nosearch:

-=================
+========
 Overview
-=================
+========

 .. toctree::
   :titlesonly:
@@ -1,7 +1,6 @@
-
-==============================
+=======================
 Introduction to Odoo.sh
-==============================
+=======================

 .. youtube:: QuNsa9n9PMg
    :align: right
@@ -225,15 +225,14 @@ Service Level Agreement
 What is covered by the Enterprise Licence?
 ------------------------------------------

-Databases hosted on Odoo’s Cloud platforms (Odoo Online and Odoo.sh) or On-Premise (Self-Hosting)
+Databases hosted on Odoo's Cloud platforms (Odoo Online and Odoo.sh) or On-Premise (Self-Hosting)
 enjoy the following services at all times.

 The upgrade of:

 * standard applications
 * Studio customization (as long as the :guilabel:`Studio` app is still active)
-* customizations done by our consulting and developer services *if* they are covered by a
-  ‘Maintenance of Customisations’ subscription
+* customizations *if* they are covered by a "Maintenance of Customizations" subscription

 The Upgrade Service is limited to your database's technical conversion and adaptation (standard
 modules and data) to make it compatible with the targeted version.
@@ -244,6 +243,7 @@ What upgrading does NOT cover
 * The cleaning of pre-existing data & configuration while upgrading
 * Any new developments and/or upgrades of your own :ref:`custom modules
  <upgrade-faq/custom-modules>`
+* Lines of code added to standard modules that are not created with Odoo Studio.
 * `Training <https://www.odoo.com/learn>`_ on the latest version

 You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription
@@ -18,6 +18,7 @@ Discover our user guides and configuration tutorials per application.
    applications/sales
    applications/websites
    applications/inventory_and_mrp
+    applications/hr
    applications/marketing
    applications/services
    applications/productivity
@@ -4,11 +4,12 @@
 Finance
 =======

-
 .. toctree::

    finance/accounting
    finance/expenses
    finance/documents
    finance/sign
+    finance/spreadsheet
    finance/payment_providers
+    finance/fiscal_localizations
@@ -16,7 +16,7 @@ accounts, smart matching suggestions, etc.

 .. seealso::
   - `Odoo Tutorials: Accounting <https://www.odoo.com/slides/accounting-19>`_
-   - :doc:`Accounting Cheat Sheet <accounting/getting_started/memento>`
+   - :doc:`Accounting Cheat Sheet <accounting/getting_started/cheat_sheet>`


 .. toctree::
@@ -29,4 +29,3 @@ accounts, smart matching suggestions, etc.
   accounting/taxation
   accounting/reporting
   accounting/others
-   accounting/fiscal_localizations
@@ -8,6 +8,7 @@ Bank and cash
   :titlesonly:

   bank/setup
-   bank/feeds
-   bank/misc
+   bank/bank_synchronization
+   bank/transactions
   bank/reconciliation
+   bank/interbank
@@ -1,6 +1,8 @@
-======================================
-Bank synchronization: automatic import
-======================================
+:show-content:
+
+====================
+Bank synchronization
+====================

 Odoo can synchronize directly with your bank institution to get all bank statements imported
 automatically into your database.
@@ -15,9 +17,12 @@ To connect to the banks, Odoo uses multiple web-services:

 - **Plaid**: United States of America and Canada
 - **Yodlee**: Worldwide
- **Salt Edge**: Europe (:doc:`more information <saltedge>`)
- **Ponto**: Europe (:doc:`more information <ponto>`)
- **EnableBanking**: Scandinavian countries
+- :doc:`Salt Edge <bank_synchronization/saltedge>`: Europe
+- :doc:`Ponto <bank_synchronization/ponto>`: Europe
+- :doc:`Enable Banking <bank_synchronization/enablebanking>`: Scandinavian countries
+
+.. seealso::
+   :doc:`transactions`

 Configuration
 =============
@@ -196,7 +201,9 @@ You can update your credentials by going to :menuselection:`Accounting Dashboard
 Configuration --> Accounting: Online Synchronization`,open the connection you want to update your
 credentials and click on the :guilabel:`Update Credentials` button.

-.. seealso::
-   * :doc:`bank_statements`
-   * :doc:`ponto`
-   * :doc:`saltedge`
+.. toctree::
+   :titlesonly:
+
+   bank_synchronization/saltedge
+   bank_synchronization/ponto
+   bank_synchronization/enablebanking
@@ -0,0 +1,36 @@
+==============
+Enable Banking
+==============
+
+**Enable Banking** is a third-party provider aggregating banking information from bank accounts all
+in one place. It offers non-intrusive connectivity to ASPSPs' official APIs across Europe without
+storing data.
+
+.. image:: enablebanking/enablebanking.png
+   :align: center
+   :alt:   Enable Banking logo
+
+**Odoo** synchronizes directly with banks to get access to all bank transactions and automatically
+import them into your database.
+
+.. seealso::
+   - :doc:`../bank_synchronization`
+   - `Enable Banking website <https://enablebanking.com/>`_
+
+Configuration
+=============
+
+Link bank accounts with Odoo
+----------------------------
+
+#. Start synchronization by clicking on :menuselection:`Accounting --> Configuration -->
+   Add a Bank Account`;
+#. Select your bank;
+#. Make sure you give your consent to share your account information with Odoo by clicking
+   :guilabel:`Continue authentication`;
+
+   .. image:: enablebanking/enablebankingauth.png
+      :align: center
+      :alt: Enable Banking authentication page
+
+#. Finally, you are redirected to your bank's login page.
@@ -1,6 +1,6 @@
-======================================
-Ponto as bank synchronization provider
-======================================
+=====
+Ponto
+=====

 **Ponto** is a service that allows companies and professionals to aggregate their accounts in one
 place and directly see all their transactions within one app. It is a third-party solution that is
@@ -16,9 +16,9 @@ into your database.
 Ponto is a paid third-party provider that can handle the synchronization between your bank accounts
 and Odoo. `Its pricing is 4€/month per account/integration <https://myponto.com/en#pricing>`_.

-.. note::
-   You can find more information about bank synchronization :doc:`on this page
-   <bank_synchronization>`.
+.. seealso::
+   - :doc:`../bank_synchronization`
+   - :doc:`../transactions`

 Configuration
 =============
@@ -115,10 +115,3 @@ and we advise you to contact Ponto directly.
 .. important::
   Using an institution in beta is beneficial for Ponto, it allows them to have real
   feedback on the connection with the institution.
-
-
-.. seealso::
-
-   * :doc:`bank_synchronization`
-   * :doc:`saltedge`
-   * :doc:`bank_statements`
@@ -1,6 +1,6 @@
-==========================================
-Salt Edge as bank synchronization provider
-==========================================
+=========
+Salt Edge
+=========

 **Salt Edge** is a third-party provider that aggregates banking information
 from your bank accounts. It supports ~5000 institutions in more than 50
@@ -8,12 +8,15 @@ countries.

 .. image:: saltedge/saltedge-logo.png
   :align: center
+   :width: 50%
   :alt: Salt Edge Logo

 Odoo can synchronize directly with your bank to get all bank statements imported
 automatically into your database.

-Salt Edge is a free third-party provider.
+.. seealso::
+   - :doc:`../bank_synchronization`
+   - :doc:`../transactions`

 Configuration
 =============
@@ -103,9 +106,3 @@ In case you already have a connection with the same credentials present on your
 and this synchronization was created with Odoo, you will normally be able to find it by going to
 :menuselection:`Accounting --> Configuration --> Online Synchronization`. Please make sure to do an
 *Update Credentials* to reactivate the connection.
-
-.. seealso::
-
-   * :doc:`bank_synchronization`
-   * :doc:`ponto`
-   * :doc:`bank_statements`
@@ -1,13 +0,0 @@
-:nosearch:
-
-==========
-Bank feeds
-==========
-
-.. toctree::
-   :titlesonly:
-
-   feeds/bank_statements
-   feeds/bank_synchronization
-   feeds/ponto
-   feeds/saltedge
@@ -1,62 +0,0 @@
-===============
-Bank statements
-===============
-
-Importing your bank statements allows you to keep track of your bank account transactions and
-reconcile them with the ones recorded in Odoo.
-
-We recommend using :doc:`the bank synchronization feature <bank_synchronization>` for more
-efficiency. However, if you do not want to use it or if your bank is not yet supported, other
-options exist:
-
- Import the bank statement files delivered by your bank;
- Register the bank statements manually.
-
-Import bank statements files
-============================
-
-Odoo supports multiple file formats to import bank statements:
-
- SEPA recommended Cash Management format (CAMT.053);
- Comma-separated values (.CSV);
- Open Financial Exchange (.OFX);
- Quicken Interchange Format (.QIF);
- Belgium: Coded Statement of Account (.CODA).
-
-To import a file, go to the Accounting dashboard and click on :guilabel:`Import (Statements)` under
-the :guilabel:`Bank` window, or click on the drop-down menu (:guilabel:`⋮`) button and then on
-:guilabel:`Import Statement`.
-
-.. image:: bank_statements/bank-overview.png
-   :align: center
-   :alt: Import a bank statement file in Odoo Accounting
-
-Next, select the file you want to import and click on :guilabel:`Upload`.
-
-Once the file uploaded, the **import widget** helps you set formatting options and **map** the
-different columns you want to import. You also can :guilabel:`test` the bank statement file before
-importing it to your database.
-
-.. image:: bank_statements/import-bank-statement.png
-   :align: center
-   :alt: Register bank statements manually in Odoo Accounting
-
-Register bank statements manually
-=================================
-
-If needed, you can also record your bank statements manually. To do so, go to the
-:guilabel:`Accounting dashboard` and click on the :guilabel:`Create Statements` under the
-:guilabel:`Bank` window. Alternatively, you can click the drop-down menu (:guilabel:`⋮`) button, and
-then :guilabel:`New Statement`.
-
-To ease the reconciliation process, make sure to fill out the :guilabel:`Partner` field. You can
-also type in the payments’ references in the :guilabel:`Label` field. Add a new line for each
-transaction written on the original bank statement.
-
-.. image:: bank_statements/bank-statements-03.png
-   :align: center
-   :alt: Register bank statements manually in Odoo Accounting
-
-.. note::
-   The **Ending Balance** and the **Computed Balance** should have the same amount. If this is not
-   the case, make sure there are no mistakes in the transactions’ amounts.
@@ -15,8 +15,8 @@ Settings` and then under the :guilabel:`Default Accounts` section.

 .. note::
   At least two bank accounts are needed to make internal transfers. Refer to
-   :doc:`Bank and cash accounts section <../setup/bank_accounts>` to see how to add an additional
-   bank account to your database.
+   :doc:`Bank and cash accounts section <setup/bank_accounts>` to see how to add an additional bank
+   account to your database.

 Register an internal transfer from one bank to another
 ======================================================
@@ -91,8 +91,8 @@ Manage and reconcile bank statements
 ------------------------------------

 The next step is to book the bank statements to finalize the transaction by creating,
-:doc:`importing <../feeds/bank_statements>`, or :doc:`synchronizing <../feeds/bank_synchronization>`
-your :guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and click on the
+:doc:`importing <transactions>`, or :doc:`synchronizing <bank_synchronization>` your
+:guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and click on the
 :guilabel:`Reconcile` button.

 .. image:: interbank/transactions-line.png
@@ -100,7 +100,7 @@ your :guilabel:`Transactions lines`. Fill in the :guilabel:`Ending balance` and
   :alt: Transaction lines to be filled in prior to reconciliation

 .. seealso::
-   - :doc:`../reconciliation/use_cases`
+   :doc:`reconciliation/use_cases`

 In the next window, choose counterparts for the payment - in this example, the outstanding payment
 account - then click :guilabel:`Validate`.
@@ -1,10 +0,0 @@
-:nosearch:
-
-=============
-Miscellaneous
-=============
-
-.. toctree::
-   :titlesonly:
-
-   misc/interbank
@@ -125,5 +125,5 @@ line*.
 .. seealso::

   - :doc:`use_cases`
-   - :doc:`../feeds/bank_synchronization`
+   - :doc:`../bank_synchronization`
   - :doc:`../../receivables/customer_invoices/cash_discounts`
@@ -102,4 +102,4 @@ right and validate all related payments :
   :align: center

 .. seealso::
-   * :doc:`../feeds/bank_synchronization`
+   :doc:`../bank_synchronization`
@@ -4,7 +4,7 @@ Bank and cash accounts

 You can manage as many bank or cash accounts as needed on your database. Configuring them well
 allows you to have all your banking data up-to-date and ready for :doc:`reconciliation
-<../../bank/reconciliation/use_cases>` with your journal entries.
+<../reconciliation/use_cases>` with your journal entries.

 In Odoo Accounting, each bank account has a dedicated journal set to post all entries in a dedicated
 account. Both the journal and the account are automatically created and configured whenever you add
@@ -33,7 +33,7 @@ To connect your bank account to your database, go to :menuselection:`Accounting
 follow the instructions.

 .. seealso::
-   :doc:`../../bank/feeds/bank_synchronization`
+   :doc:`../bank_synchronization`

 Create a bank account
 ---------------------
@@ -83,7 +83,7 @@ You can edit the accounting information and bank account number according to you

 .. seealso::
   - :doc:`../../others/multi_currency`
-   - :doc:`../../bank/feeds/bank_statements`
+   - :doc:`../transactions`
   - :doc:`../../bank/setup/outstanding_accounts`

 Suspense account
@@ -132,5 +132,5 @@ Bank feeds
  with your database.

 .. seealso::
-   - :doc:`../../bank/feeds/bank_synchronization`
-   - :doc:`../../bank/feeds/bank_statements`
+   - :doc:`../bank_synchronization`
+   - :doc:`../transactions`
@@ -0,0 +1,94 @@
+============
+Transactions
+============
+
+Importing transactions from your bank statements allows keeping track of bank account transactions
+and reconciling them with the ones recorded in your accounting.
+
+:doc:`Bank synchronization <bank_synchronization>` automates the process. However, if you do not
+want to use it or if your bank is not yet supported, other options exist:
+
+- :ref:`Import bank transactions <transactions/import>` delivered by your bank;
+- :ref:`Register bank transactions <transactions/register>` manually.
+
+.. note::
+   :ref:`Grouping transactions by statement <transactions/statements>` is optional.
+
+.. _transactions/import:
+
+Import transactions
+===================
+
+Odoo supports multiple file formats to import transactions:
+
+- SEPA recommended Cash Management format (CAMT.053);
+- Comma-separated values (.CSV);
+- Open Financial Exchange (.OFX);
+- Quicken Interchange Format (.QIF);
+- Belgium: Coded Statement of Account (.CODA).
+
+To import a file, go to the :guilabel:`Accounting Dashboard`, and in the :guilabel:`Bank` journal,
+click on :guilabel:`Import Transactions`.
+
+.. image:: transactions/import-transactions.png
+   :alt: Import bank transactions from the bank journal
+
+Next, select the file and upload it.
+
+After setting the necessary formatting options and mapping the file columns with their related Odoo
+fields, you can run a :guilabel:`Test` and :guilabel:`Import` your bank transactions.
+
+.. seealso::
+   :doc:`/applications/general/export_import_data`
+
+.. _transactions/register:
+
+Register bank transactions manually
+===================================
+
+You can also record your bank transactions manually. To do so, go to :guilabel:`Accounting
+Dashboard`, click on the :guilabel:`Bank` journal, and then on :guilabel:`New`. Make sure to fill
+out the :guilabel:`Partner` and :guilabel:`Label` fields to ease the reconciliation process.
+
+.. _transactions/statements:
+
+Statements
+==========
+
+A **bank statement** is a document provided by a bank or financial institution that lists the
+transactions that have occurred in a particular bank account over a specified period of time.
+
+In Odoo Accounting, it is optional to group transactions by their related statement, but depending
+on your business flow, you may want to record them for control purposes.
+
+.. important::
+   If you want to compare the ending balances of your bank statements with the ending balances of
+   your financial records, *don't forget to create an opening transaction* to record the bank
+   account balance as of the date you begin synchronizing or importing transactions. This is
+   necessary to ensure the accuracy of your accounting.
+
+To access a list of statements, go to your :guilabel:`Accounting Dashboard`, click on the vertical
+ellipsis (:guilabel:`⋮`) button next to the bank or cash journal you want to check, then on
+:guilabel:`Statements`
+
+Statement creation from the kanban view
+---------------------------------------
+
+Open the bank reconciliation view by clicking on the name of the bank journal, and identify the
+transaction corresponding to the last transaction of your bank statement. Click on the
+:guilabel:`STATEMENT` button when hovering on the upper separator line.
+
+.. image:: transactions/statements-kanban.png
+   :alt: A "STATEMENT" button is visible when hovering on the line separating two transactions.
+
+Fill out the statement's details and save. The newly created statement includes the previous
+transactions following the last statement.
+
+Statement creation from the list view
+-------------------------------------
+
+Open the list of transactions by clicking on the name of the bank journal and switching to the list
+view. Select all the transactions corresponding to the bank statement, and, in the
+:guilabel:`Statement` column, select an existing statement or create a new one by typing its
+reference, clicking on :guilabel:`Create and edit...`, filling out the statement's details, and
+saving.
@@ -1,11 +0,0 @@
-:nosearch:
-
-====================
-Fiscal localizations
-====================
-
-.. toctree::
-   :titlesonly:
-
-   fiscal_localizations/overview
-   fiscal_localizations/localizations
@@ -1,27 +0,0 @@
-:nosearch:
-
-=============
-Localizations
-=============
-
-.. toctree::
-   :titlesonly:
-
-   localizations/argentina
-   localizations/australia
-   localizations/chile
-   localizations/colombia
-   localizations/colombia_ES
-   localizations/egypt
-   localizations/france
-   localizations/germany
-   localizations/india
-   localizations/indonesia
-   localizations/italy
-   localizations/italy_IT
-   localizations/luxembourg
-   localizations/mexico
-   localizations/netherlands
-   localizations/peru
-   localizations/spain
-   localizations/switzerland
@@ -1,189 +0,0 @@
-=====
-India
-=====
-
-.. _india/installation:
-
-Installation
-============
-
-:ref:`Install <general/install>` the following modules to get all the features of the Indian
-localization:
-
-.. list-table::
-   :header-rows: 1
-
-   * - Name
-     - Technical name
-     - Description
-   * - :guilabel:`Indian - Accounting`
-     - `l10n_in`
-     - Default :doc:`fiscal localization package <../overview/fiscal_localization_packages>`
-   * - :guilabel:`Indian E-invoice Integration`
-     - `l10n_in_edi`
-     - :ref:`Indian e-invoicing integration <india/e-invoicing>`
-
-.. _india/e-invoicing:
-
-Indian e-invoicing
-==================
-
-Odoo is compliant with the **Indian Good and Services Tax (GST) e-Invoice system** requirements.
-
-.. important::
-   Indian e-invoicing is available from Odoo 15.0. If needed, :doc:`upgrade
-   </administration/upgrade>` your database.
-
-.. _india/e-invoicing-api:
-
-Registration on your NIC e-Invoice web portal
---------------------------------------------
-
-You must register on the **NIC e-Invoice** web portal to get your **API credentials**. You need
-these credentials to :ref:`configure your Odoo Accounting app <india/e-invoicing-configuration>`.
-
-#. Login to the NIC e-Invoice web portal on - https://einvoice1.gst.gov.in/ by clicking on
-   :guilabel:`Login` and entering your :guilabel:`Username` and :guilabel:`Password`.
-
-   .. note::
-      If you have already registered on the NIC Eway Bill Production portal, then you can use the
-      same login credentials here.
-
-   .. image:: india/e-invoice-system-login.png
-      :align: center
-      :alt: Register Odoo ERP system on e-invoice web portal
-
-#. From your dashboard, go to :menuselection:`API Registration --> User Credentials --> Create API
-   User`.
-
-   .. image:: india/e-invoice-create-api-user.png
-      :align: center
-      :alt: Click on User Credentials and Create API User
-
-#. After that, you receive an :abbr:`OTP (one-time password)` code to your registered mobile number.
-#. Enter the OTP code and click on :guilabel:`Verify OTP`.
-
-   .. image:: india/trigger-otp.png
-      :align: center
-      :alt: Trigger an OTP to your registerd phone number
-
-#. Select :guilabel:`Through GSP` in the first field, select :guilabel:`Tera Software Limited`
-   as your GSP, and type in a :guilabel:`Username` and :guilabel:`Password` for your API.
-
-   .. image:: india/submit-api-registration-details.png
-      :align: center
-      :alt: Submit API specific Username and Password
-
-#. Click on :guilabel:`Submit`.
-
-.. _india/e-invoicing-configuration:
-
-Configuration on Odoo
---------------------
-
-To set up the e-invoice service, go to :menuselection:`Accounting --> Configuration --> Settings -->
-Indian Electronic Invoicing`, and enter the :guilabel:`Username` and :guilabel:`Password`.
-
-.. image:: india/e-invoice-setup.png
-   :align: center
-   :alt: Setup e-invoice service
-
-.. _india/e-invoicing-journals:
-
-Journals
-~~~~~~~~
-
-Your default *sales* journal should be already configured correctly. You can check it or configure
-other journals by going to :menuselection:`Accounting --> Configuration --> Journals`. Then, open
-your *sales* journal, and in the :guilabel:`Advanced Settings` tab, under :guilabel:`Electronic Data
-Interchange`, check :guilabel:`E-Invoice (IN)` and :guilabel:`Save`.
-
-.. image:: india/journal-configuration.png
-   :align: center
-   :alt: Journal configuration
-
-.. _india/e-invoicing-workflow:
-
-Workflow
--------
-
-To start invoicing from Odoo, an invoice must be created using the standard invoicing flow, that is,
-either from a sales order or the invoice menu in the Accounting application.
-
-.. _india/invoice-validation:
-
-Invoice validation
-~~~~~~~~~~~~~~~~~~
-
-Once the invoice is validated, a confirmation message is displayed at the top.
-
-Odoo automatically uploads the JSON-signed file to the government portal after a while. If you want
-to process the invoice immediately, you can click on :guilabel:`Process Now`.
-
-.. image:: india/e-invoice-process.png
-   :align: center
-   :alt: Indian e-invoicing confirmation message: "The invoice will be processed asynchronously by
-         the following E-invoicing service : E-Invoice (IN)"
-
-.. note::
-   - You can find the JSON-signed file in the attached files, in the chatter.
-   - You can check the status of EDI with web-service under the :guilabel:`EDI Document` tab or the
-     :guilabel:`Electronic invoicing` field.
-
-.. _india/invoice-pdf-report:
-
-Invoice PDF Report
-~~~~~~~~~~~~~~~~~~
-
-Once the invoice is submitted and validated, you can print the invoice PDF report. The report
-includes the :abbr:`IRN (Invoice Reference Number)`, acknowledgment number and date, and QR code.
-They certify that the invoice is a valid fiscal document.
-
-.. image:: india/invoice-report.png
-   :align: center
-   :alt: IRN and QR code
-
-.. _india/edi-cancellation:
-
-EDI Cancellation
-~~~~~~~~~~~~~~~~
-
-If you want to cancel an e-invoice, go to the :guilabel:`Other info` tab of the invoice and fill out
-the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Then, click on
-:guilabel:`Request EDI cancellation`. The status of the :guilabel:`Electronic invoicing` field
-changes to :guilabel:`To Cancel`.
-
-.. image:: india/e-invoice-cancellation.png
-   :align: center
-   :alt: cancel reason and remarks
-
-.. note::
-   If you want to abort the cancellation before processing the invoice, then click on
-   :guilabel:`Call Off EDI Cancellation`.
-
-Once you request to cancel the e-invoice, Odoo automatically submits the JSON Signed file to the
-government portal. If you want to process the invoice immediately, you can process it by clicking on
-:guilabel:`Process Now`.
-
-.. _india/verify-e-invoice:
-
-Verify the e-invoice from the GST
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-After submitting an e-invoice, you can also verify the signed invoice from the GST e-Invoice system
-website.
-
-#. Download the JSON file from the attached files.
-#. Open the e-invoice portal: https://einvoice1.gst.gov.in/ and go to :menuselection:`Search -->
-   Verify Signed Invoice`.
-#. Select the JSON file and submit it.
-
-   .. image:: india/verify-invoice.png
-      :align: center
-      :alt: select the JSON file for verify invoice
-
-#. You can check the verified signed e-invoice here.
-
-   .. image:: india/signed-invoice.png
-      :align: center
-      :alt: verified e-invoice
@@ -1,79 +0,0 @@
-=====
-Italy
-=====
-
-Allow the user to generate the EDI document for Italian invoicing.
-
-This module allows the creation of the EDI documents and the communication with the SDICoop web
-service of FatturaPA to send or receive invoices and notifications.
-
-.. warning::
-   Once this module is installed, it's no longer possible to send invoices via :ref:`PEC mails
-   <italy/pec>`.
-
-SDICoop
-=======
-
-Configuration
-------------
-
-Setup the Codice Destinatario on FatturaPA
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To receive invoices and notifications from third parties, you need to inform the FatturaPA service
-that Odoo is the allowed party to process files for you. To do so, you must setup Odoo's *Codice
-Destinatario* on the FatturaPA portal. The *Codice Destinatario* is ``K95IV18``.
-
-#. Go to https://ivaservizi.agenziaentrate.gov.it/portale/ and authenticate.
-#. Go to section :menuselection:`Fatture e Corrispettivi`.
-#. Set the user as Legal Party for the VAT number you wish to configure the electronic adress.
-#. In :menuselection:`Servizi Disponibili --> Fatturazione Elettronica --> Registrazione
-   dell’indirizzo telematico dove ricevere tutte le fatture elettroniche`, input Odoo's Codice
-   Destinatario (**K95IV18**), then confirm.
-
-Give Odoo permission to process files
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Since the files are transmitted through Odoo's server before being sent to SDICoop or received by
-your database, you need to authorize Odoo to process your files from your database.
-
-To do this, go to :menuselection:`Accounting --> Settings --> Electronic Invoicing` and click on
-*Register*.
-
-.. image:: italy/register.png
-   :align: center
-   :alt: Register button to allow Odoo to process invoices.
-
-.. Note::
-   All your files are encrypted upon reception in such a way that only you are able to decrypt them.
-
-Enable FatturaPA on the Sales journal
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Open your sales journal. Under the *Advanced Settings* tab, in the **Electronic invoicing** field,
-check *FatturaPA* and *Save*.
-
-.. image:: italy/journal.png
-   :align: center
-   :alt: FatturaPA feature in the sales journal's settings
-
-Issue invoices
--------------
-
-Send an invoice the way you would do it normally. The EDI process proceeds automatically.
-
-.. image:: italy/sending.png
-   :align: center
-   :alt: Asynchronous sending on a customer invoice
-
-You can check the current status of your customer invoice under the **Electronic invoicing** field.
-
-.. image:: italy/processing.png
-   :align: center
-   :alt: Electronic invoicing status (waiting for confirmation)
-
-
-Receive invoices
-~~~~~~~~~~~~~~~~
-
-This process is ran automatically once a day.
@@ -1,130 +0,0 @@
-==========
-Italy (IT)
-==========
-
-.. _italy/pec:
-
-PEC mail
-========
-
-Questa guida spiegherà come utilizzare la fattura elettronica in Odoo e
-come configurare correttamente i dati aziendali, i contatti e la
-contabilità. Per testare la fattura elettronica i dati devono essere
-reali e non inventati, altrimenti il sistema dell’agenzia delle entrate
-non riconoscerà l’interscambio di informazioni.
-
-
-Configurare le informazioni sulla tua Azienda
---------------------------------------------
-
-Il passo successivo è la configurazione delle informazioni necessarie al
-funzionamento della fatturazione elettronica. Si può accedere alla
-schermata dall’applicazione Impostazioni: selezionare “Utenti e aziende”
-e scegliere Aziende. Accedere quindi alle informazioni sulla Azienda per
-cui si desidera configurare la fatturazione elettronica.
-
-I dati necessari al funzionamento dello strumento di fatturazione
-elettronica sono i seguenti:
-
-  Server PEC. Le informazioni sul server utilizzato dal tuo indirizzo
-   di posta elettronica certificata sono fornite dal tuo fornitore o dal
-   Ministero. Lo stesso server deve essere configurato come server che
-   gestisce tutta la corrispondenza mail in Odoo, per saperne di più si
-   può consultare la relativa :doc:`guida </applications/general/email_communication/email_servers>`.
-
-  Indirizzo PEC dell’Azienda, tale indirizzo deve essere lo stesso
-   registrato presso l’Agenzia delle Entrate per l’utilizzo dei servizi
-   di fatturazione elettronica.
-
-  Indirizzo PEC dell’Agenzia delle Entrate. La mail sarà fornito al
-   momento della registrazione della tua PEC presso l’Agenzia delle
-   Entrate, ricorda che l’Agenzia delle Entrate potrebbe cambiare questo
-   indirizzo in seguito, previa comunicazione.
-
-  Partita IVA e Codice Fiscale. Per far sì che la Fatturazione
-   Elettronica funzioni correttamente, questi campi devono essere
-   compilati correttamente.
-
-  Regime Fiscale. Il regime fiscale a cui è sottoposta l’Azienda deve
-   essere selezionato scegliendo dalla lista precompilata fornita da
-   Odoo. Chiedi al commercialista qual è il corretto regime fiscale!
-
-  Numero di Iscrizione nel registro delle Imprese.
-
-.. image:: italy_IT/italy_IT01.png
-  :align: center
-
-
-Configurare le impostazioni per la Fatturazione Elettronica
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-  Numero di iscrizione nel registro Imprese tenuto presso la Camera di
-   Commercio.
-
-  Rappresentate Fiscale. Questa opzione è dedicata ad aziende con sede
-   al di fuori del territorio nazionale ma conducenti attività
-   commerciali in Italia rilevanti ai fini dell’IVA. È possibile
-   indicare in questo campo se l’Azienda si avvale di un Rappresentate
-   Fiscale in Italia.
-
-.. image:: italy_IT/italy_IT02.png
-  :align: center
-
-
-Configurare il profilo dei clienti
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Per un corretto utilizzo dell’applicazione, il profilo di clienti e
-fornitori, nell’applicazione contatti, deve essere configurato con le
-necessarie informazioni legali.
-
-Selezionando il nome del cliente e accedendo quindi ai suoi dati, si
-trovano i seguenti campi che devono essere compilati: Indirizzo PEC,
-Codice Fiscale e Indice PA *che deve contere i 6-7 caratteri
-contenuti nell’indice PA e necessari per la comunicazione tramite
-fattura elettronica*.
-
-.. image:: italy_IT/italy_IT03.png
-  :align: center
-
-
-Il processo di fatturazione
---------------------------
-
-Si può procedere ad emettere una fattura seguendo le indicazioni
-dell’applicazione. Il momento che determina il formale invio della
-fattura è il momento in cui viene selezionata l’opzione “Valida”. La
-fattura viene quindi inviata: lo stato della sua consegna verrà
-notificato all’utente tramite pop-up sulla parte iniziale della
-schermata della fattura.
-
-.. image:: italy_IT/italy_IT04.png
-  :align: center
-
-.. image:: italy_IT/italy_IT05.png
-  :align: center
-
-I messaggi che possono apparire sono i seguenti:
-
-#. Fattura invitata. In attesa di accettazione
-
-#. Invio fallito. Puoi modificare la fattura ed inviarla di nuovo
-
-#. La fattura è stata correttamente inviata ed accettata dal
-   destinatario.
-
-I vari stadi di spedizione e recezione della fattura sono visibili anche
-dall’elenco delle Fatture nella forma di icone, accanto alla colonna
-“Stato” dall’applicazione contabilità.
-
-*Icona Rossa*: Invio fallito
-
-*Icona Gialla*: Fattura invitata. In attesa di accettazione
-
-*Icona Verde*: Fattura inviata e accettata dal destinatario
-
-Per inviare la fattura tramite PEC e generare il file XML, basterà
-cliccare su invia. Il documento verrà poi mostrato tra gli allegati.
-
-.. image:: italy_IT/italy_IT06.png
-  :align: center
--- a/Show More
+++ b/Show More