[I18N] *: export latest terms

As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#10827

X-original-commit: a64a614c7a
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>

locale/sources/administration.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 17.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-07-23 13:30+0000\n"
+"POT-Creation-Date: 2024-08-21 11:43+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -971,6 +971,26 @@ msgstr ""
 msgid "Your scheduled actions should be `idempotent <https://stackoverflow.com/a/1077421/3332416>`_: they must not cause side-effects if they are started more often than expected."
 msgstr ""
 
+#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36
+msgid "How can I automate tasks when an IP address change occurs?"
+msgstr ""
+
+#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38
+msgid "**Odoo.sh notifies project administrators of IP address changes.** Additionally, when the IP address of a production instance changes, an HTTP `GET` request is made to the path `/_odoo.sh/ip-change` with the new IP address included as a query string parameter (`new`), along with the previous IP address as an additional parameter (`old`)."
+msgstr ""
+
+#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43
+msgid "This mechanism allows custom actions to be applied in response to the IP address change (e.g., sending an email, contacting a firewall API, configuring database objects, etc.)"
+msgstr ""
+
+#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46
+msgid "For security reasons, the `/_odoo.sh/ip-change` route is accessible only internally by the platform itself and returns a `403` response if accessed through any other means."
+msgstr ""
+
+#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49
+msgid "Here is a pseudo-implementation example:"
+msgstr ""
+
 #: ../../content/administration/odoo_sh/advanced/submodules.rst:6
 #: ../../content/administration/odoo_sh/getting_started/settings.rst:170
 msgid "Submodules"
@@ -1582,7 +1602,7 @@ msgid "**SPF and DKIM compliance**"
 msgstr ""
 
 #: ../../content/administration/odoo_sh/getting_started/branches.rst:403
-msgid "In case the domain of your users email addresses use SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize Odoo as a sending host in your domain name settings to increase the deliverability of your outgoing emails. The configuration steps are explained in the documentation about :ref:`SPF <email_communication/spf_compliant>` and :ref:`DKIM <email_communication/dkim_compliant>`."
+msgid "In case the domain of your users email addresses use SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize Odoo as a sending host in your domain name settings to increase the deliverability of your outgoing emails. The configuration steps are explained in the documentation about :ref:`SPF <email-domain-spf>` and :ref:`DKIM <email-domain-dkim>`."
 msgstr ""
 
 #: ../../content/administration/odoo_sh/getting_started/branches.rst:410
@@ -2833,14 +2853,15 @@ msgstr ""
 #: ../../content/administration/supported_versions.rst:35
 #: ../../content/administration/supported_versions.rst:41
 #: ../../content/administration/supported_versions.rst:47
-#: ../../content/administration/supported_versions.rst:48
-#: ../../content/administration/supported_versions.rst:49
-#: ../../content/administration/supported_versions.rst:77
-#: ../../content/administration/supported_versions.rst:78
-#: ../../content/administration/supported_versions.rst:79
-#: ../../content/administration/supported_versions.rst:95
-#: ../../content/administration/supported_versions.rst:96
-#: ../../content/administration/supported_versions.rst:97
+#: ../../content/administration/supported_versions.rst:53
+#: ../../content/administration/supported_versions.rst:54
+#: ../../content/administration/supported_versions.rst:55
+#: ../../content/administration/supported_versions.rst:59
+#: ../../content/administration/supported_versions.rst:60
+#: ../../content/administration/supported_versions.rst:61
+#: ../../content/administration/supported_versions.rst:65
+#: ../../content/administration/supported_versions.rst:66
+#: ../../content/administration/supported_versions.rst:67
 msgid "|green|"
 msgstr ""
 
@@ -4120,7 +4141,7 @@ msgid "In you alias config (:file:`/etc/aliases`):"
 msgstr ""
 
 #: ../../content/administration/on_premise/email_gateway.rst:30
-#: ../../content/administration/on_premise/email_gateway.rst:45
+#: ../../content/administration/on_premise/email_gateway.rst:44
 msgid "Resources"
 msgstr ""
 
@@ -4136,16 +4157,16 @@ msgstr ""
 msgid "`Postfix virtual <http://www.postfix.org/virtual.8.html>`_"
 msgstr ""
 
-#: ../../content/administration/on_premise/email_gateway.rst:38
+#: ../../content/administration/on_premise/email_gateway.rst:37
 msgid "For Exim"
 msgstr ""
 
-#: ../../content/administration/on_premise/email_gateway.rst:47
+#: ../../content/administration/on_premise/email_gateway.rst:46
 msgid "`Exim <https://www.exim.org/docs.html>`_"
 msgstr ""
 
-#: ../../content/administration/on_premise/email_gateway.rst:50
-msgid "If you don't have access/manage your email server, use :ref:`inbound messages <email_communication/inbound_messages>`."
+#: ../../content/administration/on_premise/email_gateway.rst:49
+msgid "If you do not have access/manage your email server, use :ref:`incoming mail servers <email-inbound-custom-domain-incoming-server>`."
 msgstr ""
 
 #: ../../content/administration/on_premise/geo_ip.rst:3
@@ -4904,197 +4925,133 @@ msgid "End of support"
 msgstr ""
 
 #: ../../content/administration/supported_versions.rst:34
-msgid "Odoo saas~17.2"
+msgid "Odoo saas~17.4"
 msgstr ""
 
 #: ../../content/administration/supported_versions.rst:36
 #: ../../content/administration/supported_versions.rst:37
 #: ../../content/administration/supported_versions.rst:42
 #: ../../content/administration/supported_versions.rst:43
-#: ../../content/administration/supported_versions.rst:54
-#: ../../content/administration/supported_versions.rst:55
-#: ../../content/administration/supported_versions.rst:60
-#: ../../content/administration/supported_versions.rst:61
-#: ../../content/administration/supported_versions.rst:66
-#: ../../content/administration/supported_versions.rst:67
-#: ../../content/administration/supported_versions.rst:72
-#: ../../content/administration/supported_versions.rst:73
-#: ../../content/administration/supported_versions.rst:84
-#: ../../content/administration/supported_versions.rst:85
-#: ../../content/administration/supported_versions.rst:90
-#: ../../content/administration/supported_versions.rst:91
+#: ../../content/administration/supported_versions.rst:48
+#: ../../content/administration/supported_versions.rst:49
 msgid "N/A"
 msgstr ""
 
 #: ../../content/administration/supported_versions.rst:38
-msgid "April 2024"
+msgid "July 2024"
 msgstr ""
 
 #: ../../content/administration/supported_versions.rst:40
-msgid "Odoo saas~17.1"
+msgid "Odoo saas~17.2"
 msgstr ""
 
 #: ../../content/administration/supported_versions.rst:44
-msgid "January 2024"
+msgid "April 2024"
 msgstr ""
 
 #: ../../content/administration/supported_versions.rst:46
-msgid "**Odoo 17.0**"
+msgid "Odoo saas~17.1"
 msgstr ""
 
 #: ../../content/administration/supported_versions.rst:50
-#: ../../content/administration/supported_versions.rst:105
-msgid "November 2023"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:51
-msgid "October 2026 (planned)"
+msgid "January 2024"
 msgstr ""
 
 #: ../../content/administration/supported_versions.rst:52
-msgid "Odoo saas~16.4"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:53
-#: ../../content/administration/supported_versions.rst:59
-#: ../../content/administration/supported_versions.rst:65
-#: ../../content/administration/supported_versions.rst:71
-#: ../../content/administration/supported_versions.rst:83
-#: ../../content/administration/supported_versions.rst:89
-#: ../../content/administration/supported_versions.rst:101
-#: ../../content/administration/supported_versions.rst:102
-#: ../../content/administration/supported_versions.rst:103
-#: ../../content/administration/supported_versions.rst:107
-#: ../../content/administration/supported_versions.rst:108
-#: ../../content/administration/supported_versions.rst:109
-#: ../../content/administration/supported_versions.rst:113
-#: ../../content/administration/supported_versions.rst:114
-#: ../../content/administration/supported_versions.rst:115
-msgid "|red|"
+msgid "**Odoo 17.0**"
 msgstr ""
 
 #: ../../content/administration/supported_versions.rst:56
-msgid "August 2023"
+#: ../../content/administration/supported_versions.rst:75
+msgid "November 2023"
+msgstr ""
+
+#: ../../content/administration/supported_versions.rst:57
+msgid "October 2026 (planned)"
 msgstr ""
 
 #: ../../content/administration/supported_versions.rst:58
-msgid "Odoo saas~16.3"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:62
-msgid "June 2023"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:64
-msgid "Odoo saas~16.2"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:68
-msgid "March 2023"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:70
-msgid "Odoo saas~16.1"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:74
-msgid "February 2023"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:76
 msgid "**Odoo 16.0**"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:80
-#: ../../content/administration/supported_versions.rst:111
+#: ../../content/administration/supported_versions.rst:62
+#: ../../content/administration/supported_versions.rst:81
 msgid "October 2022"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:81
+#: ../../content/administration/supported_versions.rst:63
 msgid "November 2025 (planned)"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:82
-msgid "Odoo saas~15.2"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:86
-msgid "March 2022"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:87
-msgid "January 2023"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:88
-msgid "Odoo saas~15.1"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:92
-msgid "February 2022"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:93
-msgid "July 2022"
-msgstr ""
-
-#: ../../content/administration/supported_versions.rst:94
+#: ../../content/administration/supported_versions.rst:64
 msgid "**Odoo 15.0**"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:98
+#: ../../content/administration/supported_versions.rst:68
 msgid "October 2021"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:99
+#: ../../content/administration/supported_versions.rst:69
 msgid "November 2024 (planned)"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:100
+#: ../../content/administration/supported_versions.rst:70
 msgid "**Odoo 14.0**"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:104
+#: ../../content/administration/supported_versions.rst:71
+#: ../../content/administration/supported_versions.rst:72
+#: ../../content/administration/supported_versions.rst:73
+#: ../../content/administration/supported_versions.rst:77
+#: ../../content/administration/supported_versions.rst:78
+#: ../../content/administration/supported_versions.rst:79
+#: ../../content/administration/supported_versions.rst:83
+#: ../../content/administration/supported_versions.rst:84
+#: ../../content/administration/supported_versions.rst:85
+msgid "|red|"
+msgstr ""
+
+#: ../../content/administration/supported_versions.rst:74
 msgid "October 2020"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:106
+#: ../../content/administration/supported_versions.rst:76
 msgid "**Odoo 13.0**"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:110
+#: ../../content/administration/supported_versions.rst:80
 msgid "October 2019"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:112
+#: ../../content/administration/supported_versions.rst:82
 msgid "Older versions"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:116
+#: ../../content/administration/supported_versions.rst:86
 msgid "Before 2019"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:117
+#: ../../content/administration/supported_versions.rst:87
 msgid "Before 2022"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:119
+#: ../../content/administration/supported_versions.rst:89
 msgid "Legend"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:121
+#: ../../content/administration/supported_versions.rst:91
 msgid "|green| Supported version"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:123
+#: ../../content/administration/supported_versions.rst:93
 msgid "|red| End-of-support"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:125
+#: ../../content/administration/supported_versions.rst:95
 msgid "N/A Never released for this platform"
 msgstr ""
 
-#: ../../content/administration/supported_versions.rst:128
+#: ../../content/administration/supported_versions.rst:98
 msgid "Even though we don't support older versions, you can always `upgrade from any version <https://upgrade.odoo.com/>`_."
 msgstr ""
 

locale/sources/essentials.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 17.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-07-23 13:30+0000\n"
+"POT-Creation-Date: 2024-08-21 11:43+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -903,31 +903,31 @@ msgstr ""
 msgid "Export and import data"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:5
+#: ../../content/applications/essentials/export_import_data.rst:8
 msgid "In Odoo, it is sometimes necessary to export or import data for running reports, or for data modification. This document covers the export and import of data into and out of Odoo."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:9
+#: ../../content/applications/essentials/export_import_data.rst:12
 msgid "Sometimes, users run into a 'time out' error, or a record does not process, due to its size. This can occur with large exports, or in cases where the import file is too large. To circumvent this limitation surrounding the size of the records, process exports or imports in smaller batches."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:16
+#: ../../content/applications/essentials/export_import_data.rst:19
 msgid "Export data from Odoo"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:18
+#: ../../content/applications/essentials/export_import_data.rst:21
 msgid "When working with a database, it is sometimes necessary to export data in a distinct file. Doing so can aid in reporting on activities, although, Odoo provides a precise and easy reporting tool with each available application."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:22
-msgid "With Odoo, the values can be exported from any field in any record. To do so, activate the list view (:guilabel:`≣ (four horizontal lines)` icon), on the items that need to be exported, and then select the records that should be exported. To select a record, tick the checkbox next to the corresponding record. Finally, click on :guilabel:`⚙️ Action`, and then :guilabel:`Export`."
+#: ../../content/applications/essentials/export_import_data.rst:25
+msgid "With Odoo, the values can be exported from any field in any record. To do so, activate the list view (|list|), on the items that need to be exported, then select the records that should be exported. To select a record, tick the checkbox next to the corresponding record. Finally, click on |actions|, then :guilabel:`Export`."
 msgstr ""
 
 #: ../../content/applications/essentials/export_import_data.rst:-1
 msgid "View of the different things to enable/click to export data."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:31
+#: ../../content/applications/essentials/export_import_data.rst:34
 msgid "When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over window appears, with several options for the data to export:"
 msgstr ""
 
@@ -935,51 +935,51 @@ msgstr ""
 msgid "Overview of options to consider when exporting data in Odoo.."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:38
-msgid "With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system only shows the fields that can be imported. This is helpful in the case where the existing records need to be updated. This works like a filter. Leaving the box unticked, gives many more field options because it shows all the fields, not just the ones that can be imported."
+#: ../../content/applications/essentials/export_import_data.rst:41
+msgid "With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system only shows the fields that can be imported. This is helpful in the case where the :ref:`existing records need to be updated <essentials/update-data>`. This works like a filter. Leaving the box unticked, gives many more field options because it shows all the fields, not just the ones that can be imported."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:42
+#: ../../content/applications/essentials/export_import_data.rst:46
 msgid "When exporting, there is the option to export in two formats: `.csv` and `.xls`. With `.csv`, items are separated by a comma, while `.xls` holds information about all the worksheets in a file, including both content and formatting."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:45
+#: ../../content/applications/essentials/export_import_data.rst:49
 msgid "These are the items that can be exported. Use the :guilabel:`> (right arrow)` icon to display more sub-field options. Use the :guilabel:`Search` bar to find specific fields. To use the :guilabel:`Search` option more efficiently, click on all the :guilabel:`> (right arrows)` to display all fields."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:49
+#: ../../content/applications/essentials/export_import_data.rst:53
 msgid "The :guilabel:`+ (plus sign)` icon button is present to add fields to the :guilabel:`Fields to export` list."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:51
+#: ../../content/applications/essentials/export_import_data.rst:55
 msgid "The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be used to move the fields up and down, to change the order in which they are displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-down arrow)` icon."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:54
+#: ../../content/applications/essentials/export_import_data.rst:58
 msgid "The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the :guilabel:`🗑️ (trash can)` icon to remove the field."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:56
+#: ../../content/applications/essentials/export_import_data.rst:60
 msgid "For recurring reports, it is helpful to save export presets. Select all the needed fields, and click on the template drop-down menu. Once there, click on :guilabel:`New template`, and give a unique name to the export just created. Click the :guilabel:`💾 (floppy drive)` icon to save the configuration. The next time the same list needs to be exported, select the related template that was previously saved from the drop-down menu."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:63
+#: ../../content/applications/essentials/export_import_data.rst:67
 msgid "It is helpful to know the field's external identifier. For example, :guilabel:`Related Company` in the export user interface is equal to *parent_id* (external identifier). This is helpful because then, the only data exported is what should be modified and re-imported."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:70
+#: ../../content/applications/essentials/export_import_data.rst:74
 msgid "Import data into Odoo"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:72
-msgid "Importing data into Odoo is extremely helpful during implementation, or in times where data needs to be updated in bulk. The following documentation covers how to import data into an Odoo database."
+#: ../../content/applications/essentials/export_import_data.rst:76
+msgid "Importing data into Odoo is extremely helpful during implementation, or in times where data needs to be :ref:`updated in bulk <essentials/update-data>`. The following documentation covers how to import data into an Odoo database."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:76
+#: ../../content/applications/essentials/export_import_data.rst:81
 msgid "Imports are permanent and **cannot** be undone. However, it is possible to use filters (`created on` or `last modified`) to identify records changed or created by the import."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:80
+#: ../../content/applications/essentials/export_import_data.rst:85
 msgid "Activating :ref:`developer mode <developer-mode>` changes the visible import settings in the left menu. Doing so reveals an :menuselection:`Advanced` menu. Included in this advanced menu are two options: :guilabel:`Track history during import` and :guilabel:`Allow matching with subfields`."
 msgstr ""
 
@@ -987,23 +987,23 @@ msgstr ""
 msgid "Advanced import options when developer mode is activated."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:88
+#: ../../content/applications/essentials/export_import_data.rst:93
 msgid "If the model uses openchatter, the :guilabel:`Track history during import` option sets up subscriptions and sends notifications during the import, but leads to a slower import."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:91
+#: ../../content/applications/essentials/export_import_data.rst:96
 msgid "Should the :guilabel:`Allow matching with subfields` option be selected, then all subfields within a field are used to match under the :guilabel:`Odoo Field` while importing."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:95
+#: ../../content/applications/essentials/export_import_data.rst:100
 msgid "Get started"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:97
+#: ../../content/applications/essentials/export_import_data.rst:102
 msgid "Data can be imported on any Odoo business object using either Excel (`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This includes: contacts, products, bank statements, journal entries, and orders."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:101
+#: ../../content/applications/essentials/export_import_data.rst:106
 msgid "Open the view of the object to which the data should be imported/populated, and click on :menuselection:`⚙️ (Action) --> Import records`."
 msgstr ""
 
@@ -1011,11 +1011,11 @@ msgstr ""
 msgid "Action menu revealed with the import records option highlighted."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:108
+#: ../../content/applications/essentials/export_import_data.rst:113
 msgid "After clicking :guilabel:`Import records`, Odoo reveals a separate page with templates that can be downloaded and populated with the company's own data. Such templates can be imported in one click, since the data mapping is already done. To download a template click :guilabel:`Import Template for Customers` at the center of the page."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:114
+#: ../../content/applications/essentials/export_import_data.rst:119
 msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting` options. These options do **not** appear when importing the proprietary Excel file type (`.xls`, `.xlsx`)."
 msgstr ""
 
@@ -1023,31 +1023,31 @@ msgstr ""
 msgid "Formatting options presented when a CVS file is imported in Odoo."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:122
+#: ../../content/applications/essentials/export_import_data.rst:127
 msgid "Make necessary adjustments to the *Formatting* options, and ensure all columns in the :guilabel:`Odoo field` and :guilabel:`File Column` are free of errors. Finally, click :guilabel:`Import` to import the data."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:127
+#: ../../content/applications/essentials/export_import_data.rst:132
 msgid "Adapt a template"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:129
+#: ../../content/applications/essentials/export_import_data.rst:134
 msgid "Import templates are provided in the import tool of the most common data to import (contacts, products, bank statements, etc.). Open them with any spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, etc.)."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:133
+#: ../../content/applications/essentials/export_import_data.rst:138
 msgid "Once the template is downloaded, proceed to follow these steps:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:135
+#: ../../content/applications/essentials/export_import_data.rst:140
 msgid "Add, remove, and sort columns to best fit the data structure."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:136
+#: ../../content/applications/essentials/export_import_data.rst:141
 msgid "It is strongly advised to **not** remove the :guilabel:`External ID` (ID) column (see why in the next section)."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:138
+#: ../../content/applications/essentials/export_import_data.rst:143
 msgid "Set a unique ID to every record by dragging down the ID sequencing in the :guilabel:`External ID` (ID) column."
 msgstr ""
 
@@ -1055,7 +1055,7 @@ msgstr ""
 msgid "An animation of the mouse dragging down the ID column, so each record has a unique ID."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:146
+#: ../../content/applications/essentials/export_import_data.rst:151
 msgid "When a new column is added, Odoo may not be able to map it automatically, if its label does not fit any field within Odoo. However, new columns can be mapped manually when the import is tested. Search the drop-down menu for the corresponding field."
 msgstr ""
 
@@ -1063,67 +1063,63 @@ msgstr ""
 msgid "Drop-down menu expanded in the initial import screen on Odoo."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:154
+#: ../../content/applications/essentials/export_import_data.rst:159
 msgid "Then, use this field's label in the import file to ensure future imports are successful."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:157
+#: ../../content/applications/essentials/export_import_data.rst:162
 msgid "Another useful way to find out the proper column names to import is to export a sample file using the fields that should be imported. This way, if there is not a sample import template, the names are accurate."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:162
+#: ../../content/applications/essentials/export_import_data.rst:170
 msgid "Import from another application"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:164
+#: ../../content/applications/essentials/export_import_data.rst:172
 msgid "The :guilabel:`External ID` (ID) is a unique identifier for the line item. Feel free to use one from previous software to facilitate the transition to Odoo."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:167
+#: ../../content/applications/essentials/export_import_data.rst:175
 msgid "Setting an ID is not mandatory when importing, but it helps in many cases:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:169
-msgid "Update imports: import the same file several times without creating duplicates."
-msgstr ""
-
-#: ../../content/applications/essentials/export_import_data.rst:170
-msgid ":ref:`Import relation fields <export_import_data/relation-fields>`."
-msgstr ""
-
-#: ../../content/applications/essentials/export_import_data.rst:172
-msgid "To recreate relationships between different records, the unique identifier from the original application should be used to map it to the :guilabel:`External ID` (ID) column in Odoo."
-msgstr ""
-
-#: ../../content/applications/essentials/export_import_data.rst:175
-msgid "When another record is imported that links to the first one, use **XXX/ID** (XXX/External ID) for the original unique identifier. This record can also be found using its name."
+#: ../../content/applications/essentials/export_import_data.rst:177
+msgid ":ref:`Update imports <essentials/update-data>`: import the same file several times without creating duplicates."
 msgstr ""
 
 #: ../../content/applications/essentials/export_import_data.rst:179
-msgid "It should be noted that there will be a conflict if two or more records have the same name."
+msgid ":ref:`Import relation fields <export_import_data/relation-fields>`."
 msgstr ""
 
 #: ../../content/applications/essentials/export_import_data.rst:181
-msgid "The :guilabel:`External ID` (ID) can also be used to update the original import, if modified data needs to be re-imported later, therefore, it is a good practice to specify it whenever possible."
+msgid "To recreate relationships between different records, the unique identifier from the original application should be used to map it to the :guilabel:`External ID` (ID) column in Odoo."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:185
+#: ../../content/applications/essentials/export_import_data.rst:184
+msgid "When another record is imported that links to the first one, use **XXX/ID** (XXX/External ID) for the original unique identifier. This record can also be found using its name."
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:188
+msgid "It should be noted that conflicts occur if two (or more) records have the same *External ID*."
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:191
 msgid "Field missing to map column"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:187
+#: ../../content/applications/essentials/export_import_data.rst:193
 msgid "Odoo heuristically tries to find the type of field for each column inside the imported file, based on the first ten lines of the files."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:190
+#: ../../content/applications/essentials/export_import_data.rst:196
 msgid "For example, if there is a column only containing numbers, only the fields with the *integer* type are presented as options."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:193
+#: ../../content/applications/essentials/export_import_data.rst:199
 msgid "While this behavior might be beneficial in most cases, it is also possible that it could fail, or the column may be mapped to a field that is not proposed by default."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:196
+#: ../../content/applications/essentials/export_import_data.rst:202
 msgid "If this happens, check the :guilabel:`Show fields of relation fields (advanced) option`, then a complete list of fields becomes available for each column."
 msgstr ""
 
@@ -1131,322 +1127,362 @@ msgstr ""
 msgid "Searching for the field to match the tax column."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:204
+#: ../../content/applications/essentials/export_import_data.rst:210
 msgid "Change data import format"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:207
+#: ../../content/applications/essentials/export_import_data.rst:213
 msgid "Odoo can automatically detect if a column is a date, and tries to guess the date format from a set of most commonly used date formats. While this process can work for many date formats, some date formats are not recognizable. This can cause confusion, due to day-month inversions; it is difficult to guess which part of a date format is the day, and which part is the month, in a date, such as `01-03-2016`."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:213
+#: ../../content/applications/essentials/export_import_data.rst:219
 msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting` options."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:216
+#: ../../content/applications/essentials/export_import_data.rst:222
 msgid "To view which date format Odoo has found from the file, check the :guilabel:`Date Format` that is shown when clicking on options under the file selector. If this format is incorrect, change it to the preferred format using *ISO 8601* to define the format."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:221
+#: ../../content/applications/essentials/export_import_data.rst:227
 msgid "*ISO 8601* is an international standard, covering the worldwide exchange, along with the communication of date and time-related data. For example, the date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it should be written as `1981-07-24`."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:226
+#: ../../content/applications/essentials/export_import_data.rst:232
 msgid "When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to store dates. This maintains locale date formats for display, regardless of how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-separated Values)` file, use Odoo's :guilabel:`Formatting` section to select the date format columns to import."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:232
+#: ../../content/applications/essentials/export_import_data.rst:238
 msgid "Import numbers with currency signs"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:234
+#: ../../content/applications/essentials/export_import_data.rst:240
 msgid "Odoo fully supports numbers with parenthesis to represent negative signs, as well as numbers with currency signs attached to them. Odoo also automatically detects which thousand/decimal separator is used. If a currency symbol unknown to Odoo is used, it might not be recognized as a number, and the import crashes."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:240
+#: ../../content/applications/essentials/export_import_data.rst:246
 msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, the :guilabel:`Formatting` menu appears on the left-hand column. Under these options, the :guilabel:`Thousands Separator` can be changed."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:244
+#: ../../content/applications/essentials/export_import_data.rst:250
 msgid "Examples of supported numbers (using 'thirty-two thousand' as the figure):"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:246
+#: ../../content/applications/essentials/export_import_data.rst:252
 msgid "32.000,00"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:247
+#: ../../content/applications/essentials/export_import_data.rst:253
 msgid "32000,00"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:248
+#: ../../content/applications/essentials/export_import_data.rst:254
 msgid "32,000.00"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:249
+#: ../../content/applications/essentials/export_import_data.rst:255
 msgid "-32000.00"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:250
+#: ../../content/applications/essentials/export_import_data.rst:256
 msgid "(32000.00)"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:251
+#: ../../content/applications/essentials/export_import_data.rst:257
 msgid "$ 32.000,00"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:252
+#: ../../content/applications/essentials/export_import_data.rst:258
 msgid "(32000.00 €)"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:254
+#: ../../content/applications/essentials/export_import_data.rst:260
 msgid "Example that will not work:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:256
+#: ../../content/applications/essentials/export_import_data.rst:262
 msgid "ABC 32.000,00"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:257
+#: ../../content/applications/essentials/export_import_data.rst:263
 msgid "$ (32.000,00)"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:260
+#: ../../content/applications/essentials/export_import_data.rst:266
 msgid "A :guilabel:`() (parenthesis)` around the number indicates that the number is a negative value. The currency symbol **must** be placed within the parenthesis for Odoo to recognize it as a negative currency value."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:265
+#: ../../content/applications/essentials/export_import_data.rst:271
 msgid "Import preview table not displayed correctly"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:267
+#: ../../content/applications/essentials/export_import_data.rst:273
 msgid "By default, the import preview is set on commas as field separators, and quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated Values)` file does not have these settings, modify the :guilabel:`Formatting` options (displayed under the :guilabel:`Import` :abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV (Comma-separated Values)` file)."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:273
+#: ../../content/applications/essentials/export_import_data.rst:279
 msgid "If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a separator, Odoo does **not** detect the separations. The file format options need to be modified in the spreadsheet application. See the following :ref:`Change CSV file format <export_import_data/change-csv>` section."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:281
+#: ../../content/applications/essentials/export_import_data.rst:287
 msgid "Change CSV file format in spreadsheet application"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:283
+#: ../../content/applications/essentials/export_import_data.rst:289
 msgid "When editing and saving :abbr:`CSV (Comma-separated Values)` files in spreadsheet applications, the computer's regional settings are applied for the separator and delimiter. Odoo suggests using *OpenOffice* or *LibreOffice*, as both applications allow modifications of all three options (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box --> Check the box 'Edit filter settings' --> Save`)."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:289
+#: ../../content/applications/essentials/export_import_data.rst:295
 msgid "Microsoft Excel can modify the encoding when saving (:menuselection:`'Save As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:293
+#: ../../content/applications/essentials/export_import_data.rst:299
 msgid "Difference between Database ID and External ID"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:295
+#: ../../content/applications/essentials/export_import_data.rst:301
 msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When such fields are imported, Odoo has to recreate links between the different records. To help import such fields, Odoo provides three mechanisms."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:300
+#: ../../content/applications/essentials/export_import_data.rst:306
 msgid "**Only one** mechanism should be used per field that is imported."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:302
+#: ../../content/applications/essentials/export_import_data.rst:308
 msgid "For example, to reference the country of a contact, Odoo proposes three different fields to import:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:304
+#: ../../content/applications/essentials/export_import_data.rst:310
 msgid ":guilabel:`Country`: the name or code of the country"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:305
+#: ../../content/applications/essentials/export_import_data.rst:311
 msgid ":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by the ID PostgreSQL column"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:307
+#: ../../content/applications/essentials/export_import_data.rst:313
 msgid ":guilabel:`Country/External ID`: the ID of this record referenced in another application (or the `.XML` file that imported it)"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:310
+#: ../../content/applications/essentials/export_import_data.rst:316
 msgid "For the country of Belgium, for example, use one of these three ways to import:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:312
+#: ../../content/applications/essentials/export_import_data.rst:318
 msgid ":guilabel:`Country`: `Belgium`"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:313
+#: ../../content/applications/essentials/export_import_data.rst:319
 msgid ":guilabel:`Country/Database ID`: `21`"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:314
+#: ../../content/applications/essentials/export_import_data.rst:320
 msgid ":guilabel:`Country/External ID`: `base.be`"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:316
+#: ../../content/applications/essentials/export_import_data.rst:322
 msgid "According to the company's need, use one of these three ways to reference records in relations. Here is an example when one or the other should be used, according to the need:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:319
+#: ../../content/applications/essentials/export_import_data.rst:325
 msgid "Use :guilabel:`Country`: this is the easiest way when data comes from :abbr:`CSV (Comma-separated Values)` files that have been created manually."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:321
+#: ../../content/applications/essentials/export_import_data.rst:327
 msgid "Use :guilabel:`Country/Database ID`: this should rarely be used. It is mostly used by developers as the main advantage is to never have conflicts (there may be several records with the same name, but they always have a unique Database ID)"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:324
+#: ../../content/applications/essentials/export_import_data.rst:330
 msgid "Use :guilabel:`Country/External ID`: use *External ID* when importing data from a third-party application."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:327
+#: ../../content/applications/essentials/export_import_data.rst:333
 msgid "When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` files with the :guilabel:`External ID` (ID) column defining the *External ID* of each record that is imported. Then, a reference can be made to that record with columns, like `Field/External ID`. The following two :abbr:`CSV (Comma-separated Values)` files provide an example for products and their categories."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:332
+#: ../../content/applications/essentials/export_import_data.rst:338
 msgid ":download:`CSV file for categories <export_import_data/External_id_3rd_party_application_product_categories.csv>`"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:334
+#: ../../content/applications/essentials/export_import_data.rst:340
 msgid ":download:`CSV file for Products <export_import_data/External_id_3rd_party_application_products.csv>`"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:340
+#: ../../content/applications/essentials/export_import_data.rst:346
 msgid "Import relation fields"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:342
+#: ../../content/applications/essentials/export_import_data.rst:348
 msgid "An Odoo object is always related to many other objects (e.g. a product is linked to product categories, attributes, vendors, etc.). To import those relations, the records of the related object need to be imported first, from their own list menu."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:346
+#: ../../content/applications/essentials/export_import_data.rst:352
 msgid "This can be achieved by using either the name of the related record, or its ID, depending on the circumstances. The ID is expected when two records have the same name. In such a case add `/ ID` at the end of the column title (e.g. for product attributes: `Product Attributes / Attribute / ID`)."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:351
+#: ../../content/applications/essentials/export_import_data.rst:357
 msgid "Options for multiple matches on fields"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:353
+#: ../../content/applications/essentials/export_import_data.rst:359
 msgid "If, for example, there are two product categories with the child name `Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the validation is halted, but the data may still be imported. However, Odoo recommends that the data is not imported because it will all be linked to the first `Sellable` category found in the *Product Category* list (`Misc. Products/Sellable`). Odoo, instead, recommends modifying one of the duplicate's values, or the product category hierarchy."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:360
+#: ../../content/applications/essentials/export_import_data.rst:366
 msgid "However, if the company does not wish to change the configuration of product categories, Odoo recommends making use of the *External ID* for this field, 'Category'."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:364
+#: ../../content/applications/essentials/export_import_data.rst:370
 msgid "Import many2many relationship fields"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:366
+#: ../../content/applications/essentials/export_import_data.rst:372
 msgid "The tags should be separated by a comma, without any spacing. For example, if a customer needs to be linked to both tags: `Manufacturer` and `Retailer` then 'Manufacturer,Retailer' needs to be encoded in the same column of the :abbr:`CSV (Comma-separated Values)` file."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:370
+#: ../../content/applications/essentials/export_import_data.rst:376
 msgid ":download:`CSV file for Manufacturer, Retailer <export_import_data/m2m_customers_tags.csv>`"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:373
+#: ../../content/applications/essentials/export_import_data.rst:379
 msgid "Import one2many relationships"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:375
+#: ../../content/applications/essentials/export_import_data.rst:381
 msgid "If a company wants to import a sales order with several order lines, a specific row **must** be reserved in the :abbr:`CSV (Comma-separated Values)` file for each order line. The first order line is imported on the same row as the information relative to order. Any additional lines need an additional row that does not have any information in the fields relative to the order."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:380
+#: ../../content/applications/essentials/export_import_data.rst:386
 msgid "As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some quotations that can be imported, based on demo data:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:383
+#: ../../content/applications/essentials/export_import_data.rst:389
 msgid ":download:`File for some Quotations <export_import_data/purchase.order_functional_error_line_cant_adpat.csv>`"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:386
+#: ../../content/applications/essentials/export_import_data.rst:392
 msgid "The following :abbr:`CSV (Comma-separated Values)` file shows how to import purchase orders with their respective purchase order lines:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:389
+#: ../../content/applications/essentials/export_import_data.rst:395
 msgid ":download:`Purchase orders with their respective purchase order lines <export_import_data/o2m_purchase_order_lines.csv>`"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:392
+#: ../../content/applications/essentials/export_import_data.rst:398
 msgid "The following :abbr:`CSV (Comma-separated Values)` file shows how to import customers and their respective contacts:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:395
+#: ../../content/applications/essentials/export_import_data.rst:401
 msgid ":download:`Customers and their respective contacts <export_import_data/o2m_customers_contacts.csv>`"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:399
+#: ../../content/applications/essentials/export_import_data.rst:405
 msgid "Import records several times"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:401
+#: ../../content/applications/essentials/export_import_data.rst:407
 msgid "If an imported file contains one of the columns: :guilabel:`External ID` or :guilabel:`Database ID`, records that have already been imported are modified, instead of being created. This is extremely useful as it allows users to import the same :abbr:`CSV (Comma-separated Values)` file several times, while having made some changes in between two imports."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:406
+#: ../../content/applications/essentials/export_import_data.rst:412
 msgid "Odoo takes care of creating or modifying each record, depending if it is new or not."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:408
+#: ../../content/applications/essentials/export_import_data.rst:414
 msgid "This feature allows a company to use the *Import/Export tool* in Odoo to modify a batch of records in a spreadsheet application."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:412
+#: ../../content/applications/essentials/export_import_data.rst:418
 msgid "Value not provided for a specific field"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:414
+#: ../../content/applications/essentials/export_import_data.rst:420
 msgid "If all fields are not set in the CSV file, Odoo assigns the default value for every non-defined field. But, if fields are set with empty values in the :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the field, instead of assigning the default value."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:419
+#: ../../content/applications/essentials/export_import_data.rst:425
 msgid "Export/import different tables from an SQL application to Odoo"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:421
+#: ../../content/applications/essentials/export_import_data.rst:427
 msgid "If data needs to be imported from different tables, relations need to be recreated between records belonging to different tables. For instance, if companies and people are imported, the link between each person and the company they work for needs to be recreated."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:425
+#: ../../content/applications/essentials/export_import_data.rst:431
 msgid "To manage relations between tables, use the `External ID` facilities of Odoo. The `External ID` of a record is the unique identifier of this record in another application. The `External ID` must be unique across all records of all objects. It is a good practice to prefix this `External ID` with the name of the application or table. (like, 'company_1', 'person_1' - instead of '1')"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:430
+#: ../../content/applications/essentials/export_import_data.rst:436
 msgid "As an example, suppose there is an SQL database with two tables that are to be imported: companies and people. Each person belongs to one company, so the link between a person and the company they work for must be recreated."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:434
+#: ../../content/applications/essentials/export_import_data.rst:440
 msgid "Test this example, with a :download:`sample of a PostgreSQL database <export_import_data/database_import_test.sql>`."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:437
+#: ../../content/applications/essentials/export_import_data.rst:443
 msgid "First, export all companies and their *External ID*. In PSQL, write the following command:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:443
+#: ../../content/applications/essentials/export_import_data.rst:449
 msgid "This SQL command creates the following :abbr:`CSV (Comma-separated Values)` file:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:452
+#: ../../content/applications/essentials/export_import_data.rst:458
 msgid "To create the :abbr:`CSV (Comma-separated Values)` file for people linked to companies, use the following SQL command in PSQL:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:459
+#: ../../content/applications/essentials/export_import_data.rst:465
 msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:"
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:469
+#: ../../content/applications/essentials/export_import_data.rst:475
 msgid "In this file, Fabien and Laurence are working for the Bigees company (`company_1`), and Eric is working for the Organi company. The relation between people and companies is done using the *External ID* of the companies. The *External ID* is prefixed by the name of the table to avoid a conflict of ID between people and companies (`person_1` and `company_1`, who shared the same ID 1 in the original database)."
 msgstr ""
 
-#: ../../content/applications/essentials/export_import_data.rst:475
+#: ../../content/applications/essentials/export_import_data.rst:481
 msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two :abbr:`CSV (Comma-separated Values)` files, there are four contacts and three companies (the first two contacts are linked to the first company). Keep in mind to first import the companies, and then the people."
 msgstr ""
 
+#: ../../content/applications/essentials/export_import_data.rst:489
+msgid "Update data in Odoo"
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:491
+msgid "Existing data can be updated in bulk through a data import, as long as the :ref:`External ID <essentials/external-id>` remains consistent."
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:495
+msgid "Prepare data export"
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:497
+msgid "To update data through an import, first navigate to the data to be updated, and select the |list| to activate list view. On the far-left side of the list, tick the checkbox for any record to be updated. Then, click |actions|, and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu."
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:502
+msgid "On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox labeled, :guilabel:`I want to update data (import-compatible export)`. This automatically includes the *External ID* in the export. Additionally, it limits the :guilabel:`Fields to export` list to **only** include fields that are able to be imported."
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:508
+msgid "The :guilabel:`External ID` field does **not** appear in the :guilabel:`Fields to export` list unless it is manually added, but it is still included in the export. However, if the :guilabel:`I want to update data (import-compatible export)` checkbox is ticked, it is included in the export."
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:512
+msgid "Select the required fields to be included in the export using the :ref:`options <export-data>` on the pop-up window, then click :guilabel:`Export`."
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:516
+msgid "Import updated data"
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:518
+msgid "After exporting, make any necessary changes to the data file. When the file is ready, it can be :ref:`imported <import-data>` by following the same process as a normal data import."
+msgstr ""
+
+#: ../../content/applications/essentials/export_import_data.rst:522
+msgid "When updating data, it is extremely important that the *External ID* remain consistent, as this is how the system identifies a record. If an ID is altered, or removed, the system may add a duplicate record, instead of updating the existing one."
+msgstr ""
+
 #: ../../content/applications/essentials/in_app_purchase.rst:3
 msgid "In-app purchases (IAP)"
 msgstr ""
@@ -1564,7 +1600,7 @@ msgid ":doc:`Enrich your contacts base with Partner Autocomplete <../sales/crm/o
 msgstr ""
 
 #: ../../content/applications/essentials/in_app_purchase.rst:92
-msgid ":doc:`SMS essentials <../marketing/sms_marketing/essentials/sms_essentials>`"
+msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`"
 msgstr ""
 
 #: ../../content/applications/essentials/in_app_purchase.rst:97
@@ -1608,7 +1644,7 @@ msgid "The number of credits consumed depends on the length of the SMS and the c
 msgstr ""
 
 #: ../../content/applications/essentials/in_app_purchase.rst:121
-msgid "For more information, refer to the :doc:`SMS Pricing and FAQ <../marketing/sms_marketing/pricing/pricing_and_faq>` documentation."
+msgid "For more information, refer to the :doc:`SMS Pricing and FAQ <../marketing/sms_marketing/pricing_and_faq>` documentation."
 msgstr ""
 
 #: ../../content/applications/essentials/in_app_purchase.rst:127
@@ -2101,30 +2137,94 @@ msgid "Several groups can be used at the same time. The first group that is sele
 msgstr ""
 
 #: ../../content/applications/essentials/search.rst:187
-msgid "Favorites"
+msgid "Comparison"
 msgstr ""
 
 #: ../../content/applications/essentials/search.rst:189
+msgid "Certain reporting dashboards include a :guilabel:`Comparison` section in the drop-down menus of their :guilabel:`Search...` bars. This includes the :doc:`Overall Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` report for the *Manufacturing* app, and the :doc:`Purchase <../inventory_and_mrp/purchase/advanced/analyze>` report for the *Purchase* app, among others."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:195
+msgid "The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used to compare data from two different time periods. There are two comparison options to choose from: :guilabel:`(Time Filter): Previous Period` and :guilabel:`(Time Filter): Previous Year`."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:200
+msgid "For some reports, the :guilabel:`Comparison` section **only** appears in the :guilabel:`Search...` bar drop-down menu if one (or more) time periods have been selected in the :guilabel:`Filters` column. This is because, if no time period is specified, there is nothing to compare."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:205
+msgid "Additionally, some reports only allow use of the :guilabel:`Comparison` feature when the :icon:`fa-pie-chart` :guilabel:`(pie chart)` graph type, or the :icon:`oi-view-pivot` :guilabel:`(pivot)` view, is selected. A :guilabel:`Comparison` option can be selected even if another view is enabled, but doing so does **not** change the way data is displayed on the report."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:-1
+msgid "The Search... bar for the production analysis report."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:215
+msgid "To view data using one of the two comparisons, begin by selecting a time period in the :guilabel:`Filters` column of the :guilabel:`Search...` bar drop-down menu. Then, select either :guilabel:`(Time Filter): Previous Period` or :guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` section."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:220
+msgid "With one of the :guilabel:`Comparison` options enabled, the report compares the data for the selected period, with the data for the same unit of time (month, quarter, year), one period or year prior. The way the data is displayed depends on the selected view:"
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:224
+msgid "The :icon:`fa-bar-chart` :guilabel:`(bar chart)` shows two bars, side-by-side, for each unit of time for the selected time period. The left bar represents the selected time period, while the right bar represents the previous time period."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:227
+msgid "The :icon:`fa-line-chart` :guilabel:`(line chart)` is displayed with two lines, one representing the selected time period, and the other representing the previous time period."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:229
+msgid "The :icon:`fa-pie-chart` :guilabel:`(pie chart)` appears as a large circle with a smaller circle inside. The larger circle represents the selected time period, while the smaller circle represents the previous time period."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:232
+msgid "The :icon:`oi-view-pivot` :guilabel:`(pivot table)` is displayed with each column split into two smaller columns. The right column represents the selected time period, while the left column represents the previous time period."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:237
+msgid "In the :guilabel:`Production Analysis` report of the :menuselection:`Manufacturing` app, data for the second quarter of 2024 is compared to data for the second quarter of 2023. :guilabel:`Q2` is selected in the :guilabel:`End Date` filter section of the :guilabel:`Search...` bar drop-down menu. In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` is selected."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:242
+msgid "The current year is 2024, so the larger circle shows data for the second quarter (Q2) of 2024. The smaller circle shows data for the second quarter (Q2) of 2023, which is the same time period, but one *year* prior."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:246
+msgid "If :guilabel:`End Date: Previous Period` is selected instead, the smaller circle shows data for the first quarter (Q1) of 2024, which is the same time period, but one *period* prior."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:0
+msgid "The comparison view of the Production Analysis report."
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:256
+msgid "Favorites"
+msgstr ""
+
+#: ../../content/applications/essentials/search.rst:258
 msgid "Favorites are a way to save a specific search for future use, or as the new default filter for the view."
 msgstr ""
 
-#: ../../content/applications/essentials/search.rst:192
+#: ../../content/applications/essentials/search.rst:261
 msgid "To save the current view as a favorite, click the :guilabel:`🔽 (down arrow)` icon in the search bar, then select the :guilabel:`Save current search` drop-down menu to display the following options:"
 msgstr ""
 
-#: ../../content/applications/essentials/search.rst:196
+#: ../../content/applications/essentials/search.rst:265
 msgid "Filter name: name of the favorited search."
 msgstr ""
 
-#: ../../content/applications/essentials/search.rst:197
+#: ../../content/applications/essentials/search.rst:266
 msgid ":guilabel:`Default filter`: sets the favorited search as the default filter for the view."
 msgstr ""
 
-#: ../../content/applications/essentials/search.rst:198
+#: ../../content/applications/essentials/search.rst:267
 msgid ":guilabel:`Shared`: makes the favorited search available to all users. By default, the favorited search is only available to the user who created it."
 msgstr ""
 
-#: ../../content/applications/essentials/search.rst:201
+#: ../../content/applications/essentials/search.rst:270
 msgid "Once the options are set, click :guilabel:`Save` to save the favorited search."
 msgstr ""
 
@@ -2132,10 +2232,10 @@ msgstr ""
 msgid "Saving a favorite search on the Sales Analysis report"
 msgstr ""
 
-#: ../../content/applications/essentials/search.rst:207
+#: ../../content/applications/essentials/search.rst:276
 msgid "Saved favorites can be accessed by clicking the :guilabel:`🔽 (down arrow)` icon in the search bar, then selecting the saved filter in the :guilabel:`Favorites` drop-down menu. To remove a saved favorite, click the :guilabel:`🗑️ (garbage can)` icon next to the favorited search."
 msgstr ""
 
-#: ../../content/applications/essentials/search.rst:212
+#: ../../content/applications/essentials/search.rst:281
 msgid "To view *all* favorited searches, first activate :ref:`developer-mode`, and navigate to :menuselection:`Settings app --> Technical --> User Interface: User-defined Filters`. From here, all favorited searches can be viewed, edited, archived, or deleted."
 msgstr ""

locale/sources/services.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 17.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-07-23 13:30+0000\n"
+"POT-Creation-Date: 2024-08-21 11:43+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -28,149 +28,49 @@ msgstr ""
 msgid "`Odoo Tutorials: Field Service <https://www.odoo.com/slides/field-service-49>`_"
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:3
-msgid "User default warehouse"
+#: ../../content/applications/services/field_service/creating_tasks.rst:3
+msgid "Creating field service tasks"
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:5
-msgid "Setting up a **default warehouse** can be useful for field technicians who keep a supply in their van or those who always resupply from the same warehouse. It also allows field workers to switch between warehouses from their profiles."
+#: ../../content/applications/services/field_service/creating_tasks.rst:5
+msgid "Tasks in Odoo Field Service can be created manually or automatically, including from sales orders or helpdesk tickets."
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:9
-msgid "Products in sales orders created during field interventions are always pulled from the default warehouse, keeping the inventory accurate."
+#: ../../content/applications/services/field_service/creating_tasks.rst:9
+#: ../../content/applications/services/project/tasks/task_creation.rst:9
+msgid "Manual task creation"
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:13
-msgid ":doc:`../../inventory_and_mrp/inventory`"
+#: ../../content/applications/services/field_service/creating_tasks.rst:11
+msgid "To create a new field service task:"
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:16
-#: ../../content/applications/services/field_service/worksheets.rst:15
-#: ../../content/applications/services/helpdesk/overview/help_center.rst:14
-#: ../../content/applications/services/planning.rst:29
-#: ../../content/applications/services/project/project_management.rst:19
-#: ../../content/applications/services/project/tasks/recurring_tasks.rst:13
-msgid "Configuration"
+#: ../../content/applications/services/field_service/creating_tasks.rst:13
+msgid "Open the Field service app and go to :menuselection:`Field Service --> All Tasks --> All Tasks`."
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:18
-msgid "To set up a user default warehouse, the :doc:`storage locations <../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations>` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database."
+#: ../../content/applications/services/field_service/creating_tasks.rst:14
+msgid "Click :guilabel:`New`."
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:23
-msgid "You can either set it up :ref:`for your profile <default-warehouse/my-profile>`, or :ref:`for all users <default-warehouse/all-users>`."
+#: ../../content/applications/services/field_service/creating_tasks.rst:15
+msgid "Fill in the task title, :guilabel:`Customer` and any other :ref:`optional field <task_creation/task-configuration>`, then save manually."
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:27
-msgid ":doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations`"
+#: ../../content/applications/services/field_service/creating_tasks.rst:19
+msgid "Task creation from a sales order"
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:32
-msgid "For your profile"
+#: ../../content/applications/services/field_service/creating_tasks.rst:21
+msgid "This feature allows for field service tasks to be automatically created from a sales order. When you create a quotation with the :ref:`service product <sales/invoicing/configured-service-product>` and confirm it, a task is automatically created in your Field Service project. Click the :guilabel:`Tasks` smart button to access it from the sales order."
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:34
-msgid "To set up a default warehouse for yourself, click your **profile icon** in the upper right corner of the screen, then, go to :menuselection:`My Profile --> Preferences --> Default Warehouse`. Select the default warehouse from the drop-down menu."
+#: ../../content/applications/services/field_service/creating_tasks.rst:27
+msgid "Task creation from a helpdesk ticket"
 msgstr ""
 
-#: ../../content/applications/services/field_service/default_warehouse.rst:41
-msgid "For all users"
-msgstr ""
-
-#: ../../content/applications/services/field_service/default_warehouse.rst:43
-msgid "To set up a default warehouse for a specific user, go to :menuselection:`Settings --> Users --> Manage users`, select a user, then go to the :guilabel:`Preferences` tab. Scroll down to :guilabel:`Inventory`, and select the default warehouse from the drop-down menu."
-msgstr ""
-
-#: ../../content/applications/services/field_service/default_warehouse.rst:-1
-msgid "Selection of a default warehouse on a user profile."
-msgstr ""
-
-#: ../../content/applications/services/field_service/default_warehouse.rst:51
-msgid "Use in field service tasks"
-msgstr ""
-
-#: ../../content/applications/services/field_service/default_warehouse.rst:53
-msgid "Once a default warehouse has been configured for a user, the materials used for a sales order related to a Field Service task are pulled from that specific warehouse. Open the related sales order, go to the :guilabel:`Other Info` tab, then scroll down to :guilabel:`Delivery`. The default warehouse is applied correctly."
-msgstr ""
-
-#: ../../content/applications/services/field_service/default_warehouse.rst:58
-msgid "Once the Field Service task is marked as done, the stock of the default warehouse is automatically updated."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:3
-msgid "Onsite interventions planning"
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:6
-msgid "From a sales order"
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:8
-msgid "Allowing your sales team to open onsite interventions creates a seamless experience for your customers. They can receive a quotation they first have to approve before the work even starts."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:11
-msgid "Go to :menuselection:`Field Service --> Configuration --> Products` and create or edit a product."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:13
-msgid "Under the :guilabel:`General Information` tab, select :guilabel:`Service` as :guilabel:`Product Type`."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:15
-msgid "Under the :guilabel:`Sales` tab, select :guilabel:`Timesheets on tasks` as :guilabel:`Service Invoicing Policy`."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:17
-msgid "Select :guilabel:`Create a task in an existing project` as :guilabel:`Service Tracking`."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:18
-msgid "Select your :guilabel:`Project`."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:19
-msgid "If you use them, select your :guilabel:`Worksheet Template`, and save."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:-1
-msgid "Product configuration to create tasks from sales orders in Odoo Field Service"
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:25
-msgid "From the :doc:`Sales <../../sales/sales>` app, create a quotation with the product and confirm it. A task is automatically set up under your Field Service project. It is directly accessible from the sales order."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:-1
-msgid "Field Service task on a sales order in Odoo Sales"
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:34
-msgid "From helpdesk tickets"
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:36
-msgid "The integration with the :doc:`Helpdesk <../helpdesk>` app lets your helpdesk team manage intervention requests directly. Planning field service tasks from tickets speeds up your processes."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:40
-msgid "Configure the helpdesk team"
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:42
-msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select a team and enable :guilabel:`Onsite Interventions`."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:-1
-msgid "Onsite interventions settings in Odoo Helpdesk"
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:49
-msgid "The helpdesk tickets of the team now display the :guilabel:`Plan Intervention` button. Click on it to create a new task under your field service project."
-msgstr ""
-
-#: ../../content/applications/services/field_service/onsite_interventions.rst:-1
-msgid "Plan intervention from helpdesk tickets in Odoo Helpdesk"
+#: ../../content/applications/services/field_service/creating_tasks.rst:29
+msgid "If you have the Helpdesk app installed, you can :ref:`create field service tasks from a helpdesk ticket <helpdesk/field>`."
 msgstr ""
 
 #: ../../content/applications/services/field_service/planning_itinerary.rst:3
@@ -221,6 +121,123 @@ msgstr ""
 msgid "Click your task in the left column or the map pin to display the task's details. From there, you can :guilabel:`Open` the task or click :guilabel:`Navigate to` to get an itinerary from your current location to this specific task's location."
 msgstr ""
 
+#: ../../content/applications/services/field_service/product_management.rst:3
+msgid "Product management"
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:5
+msgid "When field service workers perform tasks on-site, they commonly use products to complete their work. Odoo Field Service allows them to record these products using the **product catalog** and **default warehouse** features. Doing so keeps your inventory up-to-date in real-time and automatically adds the products to the invoice."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:11
+msgid "Product catalog"
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:13
+msgid "To activate the product catalog for Field Service, go to :menuselection:`Field Service --> Configuration --> Settings` and enable the :guilabel:`Time and Material Invoicing` feature."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:16
+msgid "To add products to a task, proceed as follows:"
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:18
+msgid "Go to Field Service and open a task."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:19
+msgid "Click the :guilabel:`Products` smart button."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:20
+msgid "Click :guilabel:`Add` on a product card to add it to your task."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:21
+msgid "If needed, adjust the number of products using the :guilabel:`-` and :guilabel:`+` buttons."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:23
+msgid "Going back to your task, the smart button now displays the amount of products you added and the price. You can return to the product catalog at any time to edit the product selection."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:27
+msgid "To create and edit products from Field Service, go to :menuselection:`Field Service --> Configuration --> Products`."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:29
+msgid "To find your products more easily, use the search bar and filter your products by :guilabel:`Product Category` and :guilabel:`Attributes`."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:33
+msgid "User default warehouse"
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:35
+msgid "Setting up a **default warehouse** can be useful for field technicians who keep a supply on the go in their van or those who always resupply from the same warehouse. It also allows field workers to switch between warehouses from their profiles."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:39
+msgid "Products in sales orders created during field interventions are always pulled from the default warehouse, keeping the inventory accurate."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:43
+msgid ":doc:`../../inventory_and_mrp/inventory`"
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:46
+#: ../../content/applications/services/field_service/worksheets.rst:15
+#: ../../content/applications/services/helpdesk/overview/help_center.rst:14
+#: ../../content/applications/services/planning.rst:29
+#: ../../content/applications/services/project/project_management.rst:19
+#: ../../content/applications/services/project/tasks/recurring_tasks.rst:13
+msgid "Configuration"
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:48
+msgid "To set up a user default warehouse, the :doc:`storage locations <../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations>` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:53
+msgid "You can either set it up :ref:`for your profile <default-warehouse/my-profile>`, or :ref:`for all users <default-warehouse/all-users>`."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:57
+msgid ":doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations`"
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:62
+msgid "For your profile"
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:64
+msgid "To set up a default warehouse for yourself, click your **profile icon** in the upper right corner of the screen, then, go to :menuselection:`My Profile --> Preferences --> Default Warehouse`. Select the default warehouse from the drop-down menu."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:71
+msgid "For all users"
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:73
+msgid "To set up a default warehouse for a specific user, go to :menuselection:`Settings --> Users --> Manage users`, select a user, then go to the :guilabel:`Preferences` tab. Scroll down to :guilabel:`Inventory`, and select the default warehouse from the drop-down menu."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:-1
+msgid "Selection of a default warehouse on a user profile."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:81
+msgid "Use in field service tasks"
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:83
+msgid "Once a default warehouse has been configured for a user, the materials used for a sales order related to a Field Service task are pulled from that specific warehouse. Open the related sales order, go to the :guilabel:`Other Info` tab, then scroll down to :guilabel:`Delivery`. The default warehouse is applied correctly."
+msgstr ""
+
+#: ../../content/applications/services/field_service/product_management.rst:88
+msgid "Once the Field Service task is marked as done, the stock of the default warehouse is automatically updated."
+msgstr ""
+
 #: ../../content/applications/services/field_service/worksheets.rst:3
 msgid "Worksheets"
 msgstr ""
@@ -1421,7 +1438,7 @@ msgid "When the necessary information has been entered, click :guilabel:`Create
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:256
-msgid ":doc:`../../../inventory_and_mrp/inventory/product_management/product_replenishment/uom`"
+msgid ":doc:`../../../inventory_and_mrp/inventory/product_management/configure/uom`"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:257
@@ -2379,7 +2396,7 @@ msgid ":doc:`/applications/services/helpdesk/advanced/close_tickets`"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:351
-msgid ":doc:`/applications/general/email_communication/email_servers`"
+msgid ":doc:`../../../general/email_communication`"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:352
@@ -3543,6 +3560,94 @@ msgstr ""
 msgid "**To stop** the recurrence, open the last task in recurrence and press the :guilabel:`Recurrent` button next to the :guilabel:`Planned date`."
 msgstr ""
 
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:3
+msgid "Sub-tasks"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:5
+msgid "When handling project tasks, you can often benefit from splitting the workload into smaller **sub-tasks**, making it easier to track progress and manage the work."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:8
+msgid "Odoo’s sub-task feature is particularly useful in some of the following cases:"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:10
+msgid "The task workload is too big to handle in one record."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:11
+msgid "There’s a clear sequence of steps to follow."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:12
+msgid "Some parts of the workload fall under the scope of different projects and/or assignees."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:14
+msgid "The original task to which sub-tasks are linked is referred to as the **parent task**. The sub-tasks of the parent task are known as **child tasks**."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:18
+msgid "Creating sub-tasks"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:20
+msgid "To create a sub-task:"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:22
+msgid "Open the Project app, then go into your desired project."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:23
+msgid "Click the task where you want to add the sub-task, then click the :guilabel:`Sub-tasks` tab."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:24
+msgid "Click :guilabel:`Add a line`, then fill in the :guilabel:`Title`."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:25
+msgid "Click the :icon:`fa-cloud-upload` (:guilabel:`save`) icon to save the task manually."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:28
+msgid "You can edit several fields of a sub-task directly from the parent task’s sub-task tab without opening the individual sub-task. By default, those are: :guilabel:`Title`, :guilabel:`Priority`, :guilabel:`Status`, and :guilabel:`Assignees`. Use the :icon:`fa-sliders` (:guilabel:`sliders`) icon to add or remove fields."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:33
+msgid "Once the new sub-task is created, the following changes occur in the parent task:"
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:35
+msgid "A **smart button** displays the total number of sub-tasks, as well as the number of closed (**done** or **canceled**) sub-tasks. Click the smart button to access the list of the sub-tasks."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:37
+msgid "The :guilabel:`Allocated time` displays the amount of time allocated to the parent task, as well as time allocated to the sub-tasks. This can be used to ensure that the time allocated to sub-tasks does not exceed time allocated to the parent task."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:40
+msgid "The :guilabel:`Timesheets` tab includes a breakdown of time spent on the parent task as well as sub-tasks."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:43
+msgid "Click :guilabel:`View` to open the sub-task you created. The sub-task form is identical to the :ref:`task form <task_creation/task-configuration>`."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:48
+msgid "A **smart button** allows to navigate back to the :guilabel:`Parent task`."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:49
+msgid "The :guilabel:`Sub-tasks` tab allows for further creation of sub-tasks."
+msgstr ""
+
+#: ../../content/applications/services/project/tasks/sub-tasks.rst:50
+msgid "Selecting a :guilabel:`Project` will trigger this sub-task to be displayed in the Kanban view of the selected project."
+msgstr ""
+
 #: ../../content/applications/services/project/tasks/task_creation.rst:3
 msgid "Task creation"
 msgstr ""
@@ -3551,10 +3656,6 @@ msgstr ""
 msgid "Tasks in Odoo Project can be created manually or automatically, including from emails or website forms."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:9
-msgid "Manual task creation"
-msgstr ""
-
 #: ../../content/applications/services/project/tasks/task_creation.rst:11
 msgid "Open the Project app and choose the desired project. Create a new task by doing one of the following:"
 msgstr ""
@@ -3571,83 +3672,83 @@ msgstr ""
 msgid "Fill in the :guilabel:`Task Title` and add one or more :guilabel:`Assignees`, then click :guilabel:`Add`."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:23
+#: ../../content/applications/services/project/tasks/task_creation.rst:25
 msgid "Task configuration"
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:25
+#: ../../content/applications/services/project/tasks/task_creation.rst:27
 msgid "Click the task to open it. The task form includes the following fields that you can fill in:"
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:27
+#: ../../content/applications/services/project/tasks/task_creation.rst:29
 msgid ":guilabel:`Task Title`: title of the task."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:28
+#: ../../content/applications/services/project/tasks/task_creation.rst:30
 msgid ":icon:`fa-star-o` (:guilabel:`Star`): click the :icon:`fa-star-o` (:guilabel:`star`) icon to mark the task as high priority. The icon will turn yellow. Click it again to remove the high priority."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:30
+#: ../../content/applications/services/project/tasks/task_creation.rst:32
 msgid ":guilabel:`Project`: the project that this task belongs to."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:31
+#: ../../content/applications/services/project/tasks/task_creation.rst:33
 msgid ":guilabel:`Assignees`: the person(s) in charge of handling the work on this task."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:32
+#: ../../content/applications/services/project/tasks/task_creation.rst:34
 msgid ":guilabel:`Tags`: custom labels allowing to categorize and filter your tasks."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:33
+#: ../../content/applications/services/project/tasks/task_creation.rst:35
 msgid ":guilabel:`Customer`: the person or company that will be billed for this task. This field only appears in tasks that belong to billable projects."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:35
+#: ../../content/applications/services/project/tasks/task_creation.rst:37
 msgid ":guilabel:`Sales Order Item`: this can be either the sales order that was used to create this task, or a sales order that was linked to this task manually. This field only appears in tasks linked to billable projects."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:38
+#: ../../content/applications/services/project/tasks/task_creation.rst:40
 msgid ":guilabel:`Allocated Time`: the amount of time that the work on this task is expected to last, tracked by timesheets."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:40
+#: ../../content/applications/services/project/tasks/task_creation.rst:42
 msgid ":guilabel:`Deadline`: the expected end date of the task. Once this field is filled in, you can also add a start date to designate the entire time frame of the tasks' duration."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:45
+#: ../../content/applications/services/project/tasks/task_creation.rst:47
 msgid "You can also create new tasks by switching to the list or Gantt view and clicking :guilabel:`New`."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:47
+#: ../../content/applications/services/project/tasks/task_creation.rst:49
 msgid "The following fields can also be edited directly from the Kanban view without opening the individual task: :icon:`fa-star-o` (**priority**), :guilabel:`Allocated hours`, :guilabel:`Assignees`, and **task status**. You can also **color code** or :guilabel:`Set a Cover image` to your task by clicking the :icon:`fa-ellipsis-v` (**vertical ellipsis**)."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:51
+#: ../../content/applications/services/project/tasks/task_creation.rst:53
 msgid "You can use the following keyboard shortcuts in the task title to configure new tasks (modify the values in the examples below according to your needs):"
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:54
+#: ../../content/applications/services/project/tasks/task_creation.rst:56
 msgid "**30h**: to allocate 30 hours to the task."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:55
+#: ../../content/applications/services/project/tasks/task_creation.rst:57
 msgid "**#tags**: to add tags to the task."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:56
+#: ../../content/applications/services/project/tasks/task_creation.rst:58
 msgid "**@user**: to assign the task to a user."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:57
+#: ../../content/applications/services/project/tasks/task_creation.rst:59
 msgid "**!**: to star the task as high priority."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:59
+#: ../../content/applications/services/project/tasks/task_creation.rst:61
 msgid "Along with using the correct format, follow this order: the task's name, followed by the allocated time, the tags, the assignee, and then the priority."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:62
+#: ../../content/applications/services/project/tasks/task_creation.rst:64
 msgid "For example, if you want to create a task named \"Prepare workshop\", allocate 5h hours to it, add the \"School\" tag, assign it to Audrey and set its priority to :guilabel:`High`, enter the following task title: Prepare workshop 5h #school @Audrey !"
 msgstr ""
 
@@ -3655,31 +3756,31 @@ msgstr ""
 msgid "Using keyboard shortcuts to create a task in Project."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:70
+#: ../../content/applications/services/project/tasks/task_creation.rst:74
 msgid "Creating tasks from an email alias"
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:72
+#: ../../content/applications/services/project/tasks/task_creation.rst:76
 msgid "This feature allows for project tasks to be automatically created once an email is delivered to a designated email address."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:75
+#: ../../content/applications/services/project/tasks/task_creation.rst:79
 msgid "To configure it, open the Project app, then click the :icon:`fa-ellipsis-v` (:guilabel:`vertical ellipsis`) icon next to the desired project's name. Select :guilabel:`Settings`, then open the :guilabel:`Settings` tab."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:79
+#: ../../content/applications/services/project/tasks/task_creation.rst:83
 msgid "Fill in the :guilabel:`Create tasks by sending an email to` field as follows:"
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:81
+#: ../../content/applications/services/project/tasks/task_creation.rst:85
 msgid "**Section of the alias before the @ symbol**: type the name of the email alias, e.g. `contact`, `help`, `jobs`."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:83
-msgid "**Domain**: in most cases, this is filled in by default with your :doc:`domain <../../../general/email_communication/email_servers>`."
+#: ../../content/applications/services/project/tasks/task_creation.rst:87
+msgid "**Domain**: in most cases, this is filled in by default with your :doc:`domain <../../../general/email_communication>`."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:85
+#: ../../content/applications/services/project/tasks/task_creation.rst:89
 msgid "**Accept Emails From**: refine the senders whose emails will create tasks in the project."
 msgstr ""
 
@@ -3687,67 +3788,67 @@ msgstr ""
 msgid "View of the email alias chosen on the dashboard view in Odoo Project"
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:90
+#: ../../content/applications/services/project/tasks/task_creation.rst:94
 msgid "Once configured, the email alias can be seen under the name of your project on the Kanban dashboard."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:92
+#: ../../content/applications/services/project/tasks/task_creation.rst:96
 msgid "When an email is sent to the alias, the email is automatically converted into a project task. The following rules apply:"
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:95
+#: ../../content/applications/services/project/tasks/task_creation.rst:99
 msgid "The email sender is displayed in the :guilabel:`Customer` field."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:96
+#: ../../content/applications/services/project/tasks/task_creation.rst:100
 msgid "The email subject is displayed in the :guilabel:`Task Title` field."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:97
+#: ../../content/applications/services/project/tasks/task_creation.rst:101
 msgid "The email body is displayed in the :guilabel:`Description` field."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:98
+#: ../../content/applications/services/project/tasks/task_creation.rst:102
 msgid "The whole content of the email is additionally displayed in the **chatter**."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:99
+#: ../../content/applications/services/project/tasks/task_creation.rst:103
 msgid "All the recipients of the email (To/Cc/Bcc) that are Odoo users are automatically added as **followers** of the task."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:103
+#: ../../content/applications/services/project/tasks/task_creation.rst:107
 msgid "Creating tasks from a website form"
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:105
+#: ../../content/applications/services/project/tasks/task_creation.rst:109
 msgid "If you have the Website app installed in your database, you can configure any form on your website to trigger the creation of tasks in a project."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:108
+#: ../../content/applications/services/project/tasks/task_creation.rst:112
 msgid "Go to the website page where you wish to add the the form and :ref:`add the Form building block <websites/website/web_design/building_blocks>`."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:110
+#: ../../content/applications/services/project/tasks/task_creation.rst:114
 msgid "In the website editor, edit the following fields:"
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:112
+#: ../../content/applications/services/project/tasks/task_creation.rst:116
 msgid ":guilabel:`Action`: select :guilabel:`Create a Task`."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:113
+#: ../../content/applications/services/project/tasks/task_creation.rst:117
 msgid ":guilabel:`Project`: choose the project that you want the new tasks to be created in."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:115
+#: ../../content/applications/services/project/tasks/task_creation.rst:119
 msgid ":ref:`Customize the form <dynamic_content/form>`."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:117
+#: ../../content/applications/services/project/tasks/task_creation.rst:121
 msgid "When the form is submitted, it automatically creates a project task. The task's content is defined by the form's corresponding fields."
 msgstr ""
 
-#: ../../content/applications/services/project/tasks/task_creation.rst:121
+#: ../../content/applications/services/project/tasks/task_creation.rst:125
 msgid ":doc:`Dynamic website content <../../../websites/website/web_design/building_blocks/dynamic_content>`"
 msgstr ""
 

locale/sources/studio.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 17.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-07-23 13:30+0000\n"
+"POT-Creation-Date: 2024-08-21 11:43+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -1794,62 +1794,80 @@ msgid "Views"
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:5
-msgid "Views are the interface that allows displaying the data contained in a model. One model can have several views, which are simply different ways to show the same data. In Studio, views are organized into four categories: :ref:`general <studio/views/general>`, :ref:`multiple records <studio/views/multiple-records>`, :ref:`timeline <studio/views/timeline>`, and :ref:`reporting <studio/views/reporting>`."
+msgid "Views are the interface that allows displaying the data contained in a :doc:`model <models_modules_apps>`. One model can have several views, which are simply different ways to show the same data. In Studio, views are organized into four categories: :ref:`general <studio/views/general>`, :ref:`multiple records <studio/views/multiple-records>`, :ref:`timeline <studio/views/timeline>`, and :ref:`reporting <studio/views/reporting>`."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:12
-msgid "To change the default view of a model, go to :menuselection:`Studio --> Views --> Dropdown menu (⋮) --> Set as Default`."
+msgid "To change the default view of a model, :ref:`access Studio <studio/access>`, go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` (:guilabel:`ellipsis`) icon next to the desired view, and click :guilabel:`Set as Default`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:16
-msgid "You can modify views by using the built-in XML editor. To do so, activate :ref:`Developer mode <developer-mode>`, go to the view you want to edit, select the :guilabel:`View` tab and then click on :guilabel:`</> XML`."
+#: ../../content/applications/studio/views.rst:15
+msgid "You can modify views using the built-in XML editor: Activate the :ref:`Developer mode <developer-mode>`, go to the view you want to edit, select the :guilabel:`View` tab, and click :guilabel:`</> XML`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:21
-msgid "If you are editing a view using the XML editor, avoid making changes directly to standard views and inherited views, as those would be reset and would not be kept in case of an update or module upgrade. Always make sure you select the right Studio inherited views. Indeed, when you modify a view in Studio by drag-and-dropping a new field, a specific Studio inherited view and its XPath, the latter which defines which part of the view is modified, are automatically generated."
+#: ../../content/applications/studio/views.rst:20
+msgid "If you are editing a view using the XML editor, avoid making changes directly to standard and inherited views, as these would be reset and lost during updates or module upgrades. Always make sure you select the right Studio inherited views: When you modify a view in Studio by dragging and dropping a new field, for example, a specific Studio inherited view and its corresponding XPath, which defines the modified part of the view, are automatically generated."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:31
+#: ../../content/applications/studio/views.rst:30
 msgid "General views"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:34
-#: ../../content/applications/studio/views.rst:97
-#: ../../content/applications/studio/views.rst:195
-#: ../../content/applications/studio/views.rst:311
+#: ../../content/applications/studio/views.rst:33
+#: ../../content/applications/studio/views.rst:104
+#: ../../content/applications/studio/views.rst:205
+#: ../../content/applications/studio/views.rst:320
 msgid "The settings described below are found under the view's :guilabel:`View` tab unless specified otherwise."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:40
+#: ../../content/applications/studio/views.rst:39
 msgid "Form"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:42
-msgid "The :guilabel:`Form` view is used when creating and editing records, such as contacts, sales orders, products, etc."
+#: ../../content/applications/studio/views.rst:41
+msgid "The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and editing records, such as contacts, sales orders, products, etc."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:45
-msgid "To structure a form, drag-and-drop the :guilabel:`Tabs and Columns` element found under the :guilabel:`+ Add` tab."
+#: ../../content/applications/studio/views.rst:44
+msgid "To structure a form, drag and drop the :guilabel:`Tabs and Columns` element found under the :guilabel:`+ Add` tab."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:47
-#: ../../content/applications/studio/views.rst:132
+#: ../../content/applications/studio/views.rst:46
+#: ../../content/applications/studio/views.rst:137
 msgid "To prevent users from creating, editing, or deleting records, untick :guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`."
 msgstr ""
 
+#: ../../content/applications/studio/views.rst:48
+msgid "To add a button, click :guilabel:`Add a button` at the top of the form, enter a :guilabel:`Label`, and select the button's action:"
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:51
+#: ../../content/applications/studio/views.rst:153
+msgid ":guilabel:`Run a Server Action`: select the :ref:`server action <reference/actions/server>` to be executed from the dropdown list;"
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:53
+#: ../../content/applications/studio/views.rst:155
+msgid ":guilabel:`Call a method`: specify an existing Python method already defined in Odoo."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:55
+msgid "To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose an :guilabel:`Icon`, and select a :ref:`related field <studio/fields/relational-fields/related-field>`."
+msgstr ""
+
 #: ../../content/applications/studio/views.rst:0
 msgid "Sales order model's Form view"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:59
+#: ../../content/applications/studio/views.rst:67
 msgid "Activity"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:61
-msgid "The :guilabel:`Activity` view is used to schedule and have an overview of activities (emails, calls, etc.) linked to records."
+#: ../../content/applications/studio/views.rst:69
+msgid "The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and have an overview of activities (emails, calls, etc.) linked to records."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:65
+#: ../../content/applications/studio/views.rst:73
 msgid "This view can only be modified within Studio by editing the XML code."
 msgstr ""
 
@@ -1857,84 +1875,89 @@ msgstr ""
 msgid "Lead/Opportunity model's Activity view"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:76
+#: ../../content/applications/studio/views.rst:83
 msgid "Search"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:78
-msgid "The :guilabel:`Search` view is added on top of other views to filter, group, and search records."
+#: ../../content/applications/studio/views.rst:85
+msgid "The :guilabel:`Search` :icon:`oi-search` view is added on top of other views to filter, group, and search records."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:80
+#: ../../content/applications/studio/views.rst:88
 msgid "To add custom :guilabel:`Filters` and structure them using :guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop them under :guilabel:`Filters`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:82
-msgid "To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and drag-and-drop it under :guilabel:`Autocompletion Fields`."
+#: ../../content/applications/studio/views.rst:90
+msgid "To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion Fields`."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:0
 msgid "Project model's Search view on the Kanban view"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:94
+#: ../../content/applications/studio/views.rst:101
 msgid "Multiple records views"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:103
+#: ../../content/applications/studio/views.rst:110
 msgid "Kanban"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:105
-msgid "The :guilabel:`Kanban` view is often used to support business flows by moving records across stages or as an alternative way to display records inside *cards*."
+#: ../../content/applications/studio/views.rst:112
+msgid "The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support business flows by moving records across stages or as an alternative way to display records inside *cards*."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:109
+#: ../../content/applications/studio/views.rst:116
 msgid "If the :guilabel:`Kanban` view exists, it is used by default to display data on mobile devices instead of the :ref:`List view <studio/views/multiple-records/list>`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:112
+#: ../../content/applications/studio/views.rst:119
 msgid "To prevent users from creating new records, untick :guilabel:`Can Create`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:113
+#: ../../content/applications/studio/views.rst:120
 msgid "To create records directly within the view, in a minimalistic form, enable :guilabel:`Quick Create`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:115
-msgid "To change the way records are grouped by default, select a new group under :guilabel:`Default Group by`."
+#: ../../content/applications/studio/views.rst:122
+#: ../../content/applications/studio/views.rst:149
+msgid "To set a default grouping for records, select a field under :guilabel:`Default Group By`."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:0
 msgid "Project model's Kanban view"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:127
+#: ../../content/applications/studio/views.rst:132
 msgid "List"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:129
-msgid "The :guilabel:`List` view is used to overview many records at once, look for records, and edit simple records."
-msgstr ""
-
 #: ../../content/applications/studio/views.rst:134
-msgid "To create and edit records directly within the view, select either :guilabel:`New record on top` or :guilabel:`New record at the bottom` under :guilabel:`Editable`."
+msgid "The :guilabel:`List` :icon:`oi-view-list` view is used to overview many records at once, look for records, and edit simple records."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:138
+#: ../../content/applications/studio/views.rst:139
+msgid "To create and edit records directly within the view, select either :guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or :guilabel:`Open form view` under :guilabel:`When Creating Record`."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:144
 msgid "This prevents users from opening records in :ref:`Form view <studio/views/general/form>` from the :guilabel:`List` view."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:141
+#: ../../content/applications/studio/views.rst:147
 msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:142
+#: ../../content/applications/studio/views.rst:148
 msgid "To change the way records are sorted by default, select a field under :guilabel:`Sort By`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:145
-msgid "To add a drag handle icon to reorder records manually, add an :ref:`Integer field <studio/fields/simple-fields/integer>` with the :guilabel:`Handle` widget."
+#: ../../content/applications/studio/views.rst:150
+msgid "To add a button, click :guilabel:`Add a button` at the top of the list, enter a :guilabel:`Label`, and select the button's action:"
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:158
+msgid "To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder records manually, add an :ref:`Integer field <studio/fields/simple-fields/integer>` with the :guilabel:`Handle` widget."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:0
@@ -1945,31 +1968,31 @@ msgstr ""
 msgid "Sales order model's List view"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:161
+#: ../../content/applications/studio/views.rst:172
 msgid "Map"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:163
-msgid "The :guilabel:`Map` view is used to display records on a map. For example, it is used in the Field Service app to plan an itinerary between different tasks."
+#: ../../content/applications/studio/views.rst:174
+msgid "The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on a map. For example, it is used in the Field Service app to plan an itinerary between different tasks."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:167
+#: ../../content/applications/studio/views.rst:178
 msgid "A :ref:`Many2One field <studio/fields/relational-fields/many2one>` linked to the *Contact* model is required to activate the view, as the contact address is used to position records on the map."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:170
+#: ../../content/applications/studio/views.rst:181
 msgid "To select which kind of contact should be used on the map, select it under :guilabel:`Contact Field`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:172
-msgid "To hide the name or the address of the record, tick :guilabel:`Hide name` or :guilabel:`Hide Address`."
+#: ../../content/applications/studio/views.rst:183
+msgid "To hide the name or the address of the record, tick :guilabel:`Hide Name` or :guilabel:`Hide Address`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:174
+#: ../../content/applications/studio/views.rst:185
 msgid "To add information from other fields, select them under :guilabel:`Additional Fields`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:175
+#: ../../content/applications/studio/views.rst:186
 msgid "To have a route suggested between the different records, tick :guilabel:`Enable Routing` and select which field should be used to sort records for the routing."
 msgstr ""
 
@@ -1977,75 +2000,75 @@ msgstr ""
 msgid "Task model's Map view"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:187
+#: ../../content/applications/studio/views.rst:197
 msgid "Timeline views"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:190
+#: ../../content/applications/studio/views.rst:200
 msgid "When you first activate one of the timeline views, you need to select which :ref:`Date <studio/fields/simple-fields/date>` or :ref:`Date & Time <studio/fields/simple-fields/date-time>` fields on your model should be used to define when the records start and stop in order to display them on the view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop Date Field` after activating the view."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:201
+#: ../../content/applications/studio/views.rst:211
 msgid "Calendar"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:203
-msgid "The :guilabel:`Calendar` view is used to overview and manage records inside a calendar."
+#: ../../content/applications/studio/views.rst:213
+msgid "The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and manage records inside a calendar."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:205
+#: ../../content/applications/studio/views.rst:216
 msgid "To create records directly within the view instead of opening the :ref:`Form view <studio/views/general/form>`, enable :guilabel:`Quick Create`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:209
+#: ../../content/applications/studio/views.rst:220
 msgid "This only works on specific models that can be *quick-created* using only a *name*. However, most models do not support quick creation and open the :guilabel:`Form` view to fill in the required fields."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:213
+#: ../../content/applications/studio/views.rst:224
 msgid "To color records on the calendar, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:217
+#: ../../content/applications/studio/views.rst:228
 msgid "As the number of colors is limited, the same color can end up being assigned to different values."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:220
+#: ../../content/applications/studio/views.rst:231
 msgid "To display events lasting the whole day at the top of the calendar, select a :ref:`Checkbox field <studio/fields/simple-fields/checkbox>` that specifies if the event lasts the whole day."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:223
+#: ../../content/applications/studio/views.rst:234
 msgid "To choose the default time scale used to display events, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Display Mode`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:227
-msgid "You can also use :guilabel:`Delay Field` to display the duration of the event in hours by selecting a :ref:`Decimal <studio/fields/simple-fields/decimal>` or :ref:`Integer <studio/fields/simple-fields/integer>` field on the model which specifies the duration of the event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken into account."
+#: ../../content/applications/studio/views.rst:238
+msgid "You can also use a :guilabel:`Delay Field` to display the duration of the event in hours by selecting a :ref:`Decimal <studio/fields/simple-fields/decimal>` or :ref:`Integer <studio/fields/simple-fields/integer>` field on the model which specifies the duration of the event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken into account."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:0
 msgid "Calendar Event model's Calendar view"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:242
+#: ../../content/applications/studio/views.rst:252
 msgid "Cohort"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:244
-msgid "The :guilabel:`Cohort` view is used to examine the life cycle of records over a time period. For example, it is used in the Subscriptions app to view the subscriptions' retention rate."
+#: ../../content/applications/studio/views.rst:254
+msgid "The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the life cycle of records over a time period. For example, it is used in the Subscriptions app to view the subscriptions' retention rate."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:247
+#: ../../content/applications/studio/views.rst:258
 msgid "To display a measure (i.e., the aggregated value of a given field) by default on the view, select a :guilabel:`Measure Field`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:249
+#: ../../content/applications/studio/views.rst:260
 msgid "To choose which time interval is used by default to group results, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Interval`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:251
+#: ../../content/applications/studio/views.rst:262
 msgid "To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` :dfn:`the percentage of records staying over a period of time, it starts at 100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of records moving out over a period of time - it starts at 0% and increases with time`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:255
+#: ../../content/applications/studio/views.rst:266
 msgid "To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` (from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is used."
 msgstr ""
 
@@ -2053,51 +2076,51 @@ msgstr ""
 msgid "Subscription model's Cohort view"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:268
+#: ../../content/applications/studio/views.rst:278
 msgid "Gantt"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:270
-msgid "The :guilabel:`Gantt` view is used to forecast and examine the overall progress of records. Records are represented by a bar under a time scale."
-msgstr ""
-
-#: ../../content/applications/studio/views.rst:273
-msgid "To prevent users from creating or editing records, untick :guilabel:`Can Create` or :guilabel:`Can Edit`."
-msgstr ""
-
-#: ../../content/applications/studio/views.rst:275
-msgid "To fill cells in gray whenever a record should not be created there (e.g., on weekends for employees), tick :guilabel:`Display Unavailability`."
-msgstr ""
-
-#: ../../content/applications/studio/views.rst:279
-msgid "The underlying model must support this feature, and support for it cannot be added using Studio. It is supported for the Project, Time Off, Planning, and Manufacturing apps."
-msgstr ""
-
-#: ../../content/applications/studio/views.rst:282
-msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`."
+#: ../../content/applications/studio/views.rst:280
+msgid "The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine the overall progress of records. Records are represented by a bar under a time scale."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:283
-msgid "To collapse multiple records in a single row, tick :guilabel:`Collapse First Level`."
+msgid "To prevent users from creating or editing records, untick :guilabel:`Can Create` or :guilabel:`Can Edit`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:284
-msgid "To choose which way records are grouped by default on rows (e.g., per employee or project), select a field under :guilabel:`Default Group by`."
+#: ../../content/applications/studio/views.rst:285
+msgid "To fill cells in gray whenever a record should not be created there (e.g., on weekends for employees), tick :guilabel:`Display Unavailability`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:286
-msgid "To define a default time scale to view records, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Scale`."
-msgstr ""
-
-#: ../../content/applications/studio/views.rst:288
-msgid "To color records on the view, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color."
+#: ../../content/applications/studio/views.rst:289
+msgid "The underlying model must support this feature, and support for it cannot be added using Studio. It is supported for the Project, Time Off, Planning, and Manufacturing apps."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:292
-msgid "As the number of colors is limited, the same color can be assigned to different values."
+msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:293
+msgid "To collapse multiple records in a single row, tick :guilabel:`Collapse First Level`."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:294
+msgid "To choose which way records are grouped by default on rows (e.g., per employee or project), select a field under :guilabel:`Default Group by`."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:296
+msgid "To define a default time scale to view records, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Scale`."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:298
+msgid "To color records on the view, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:302
+msgid "As the number of colors is limited, the same color can be assigned to different values."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:304
 msgid "To specify with which degree of precision each time scale should be divided by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or :guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or :guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month Precision`."
 msgstr ""
 
@@ -2105,31 +2128,31 @@ msgstr ""
 msgid "Planning Shift model's Gantt view"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:308
+#: ../../content/applications/studio/views.rst:317
 msgid "Reporting views"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:317
+#: ../../content/applications/studio/views.rst:326
 msgid "Pivot"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:319
-msgid "The :guilabel:`Pivot` view is used to explore and analyze the data contained in records in an interactive manner. It is especially useful to aggregate numeric data, create categories, and drill down the data by expanding and collapsing different levels of data."
+#: ../../content/applications/studio/views.rst:328
+msgid "The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and analyze the data contained in records in an interactive manner. It is especially useful to aggregate numeric data, create categories, and drill down the data by expanding and collapsing different levels of data."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:323
+#: ../../content/applications/studio/views.rst:332
 msgid "To access all records whose data is aggregated under a cell, tick :guilabel:`Access records from cell`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:325
+#: ../../content/applications/studio/views.rst:334
 msgid "To divide the data into different categories, select field(s) under :guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or :guilabel:`Row grouping - Second level`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:327
+#: ../../content/applications/studio/views.rst:336
 msgid "To add different types of data to be measured using the view, select a field under :guilabel:`Measures`."
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:329
+#: ../../content/applications/studio/views.rst:338
 msgid "To display a count of records that made up the aggregated data in a cell, tick :guilabel:`Display count`."
 msgstr ""
 
@@ -2137,50 +2160,38 @@ msgstr ""
 msgid "Purchase Report model's Pivot view"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:341
+#: ../../content/applications/studio/views.rst:349
 msgid "Graph"
 msgstr ""
 
-#: ../../content/applications/studio/views.rst:343
-msgid "The :guilabel:`Graph` view is used to showcase data from records in a bar, line, or pie chart."
-msgstr ""
-
-#: ../../content/applications/studio/views.rst:345
-msgid "To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` under :guilabel:`Type`."
-msgstr ""
-
-#: ../../content/applications/studio/views.rst:347
-msgid "To choose a default data dimension (category), select a field under :guilabel:`First dimension` and, if needed, another under :guilabel:`Second dimension`."
-msgstr ""
-
-#: ../../content/applications/studio/views.rst:349
-msgid "To select a default type of data to be measured using the view, select a field under :guilabel:`Measure`."
-msgstr ""
-
 #: ../../content/applications/studio/views.rst:351
-msgid "*For Bar and Line charts only*: To sort the different data categories by their value, select :guilabel:`Ascending` (from lowest to highest value) or :guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`."
+msgid "The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data from records in a bar, line, or pie chart."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:354
-msgid "*For Bar and Pie charts only*: To access all records whose data is aggregated under a data category on the chart, tick :guilabel:`Access records from graph`."
+msgid "To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` under :guilabel:`Type`."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:356
+msgid "To choose a default data dimension (category), select a field under :guilabel:`First dimension` and, if needed, another under :guilabel:`Second dimension`."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:358
+msgid "To select a default type of data to be measured using the view, select a field under :guilabel:`Measure`."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:360
+msgid "*For Bar and Line charts only*: To sort the different data categories by their value, select :guilabel:`Ascending` (from lowest to highest value) or :guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:363
+msgid "*For Bar and Pie charts only*: To access all records whose data is aggregated under a data category on the chart, tick :guilabel:`Access records from graph`."
+msgstr ""
+
+#: ../../content/applications/studio/views.rst:365
 msgid "*For Bar charts only*: When using two data dimensions (categories), display the two columns on top of each other by default by ticking :guilabel:`Stacked graph`."
 msgstr ""
 
 #: ../../content/applications/studio/views.rst:0
 msgid "Sales Analysis Report model's Bar chart on Graph view"
 msgstr ""
-
-#: ../../content/applications/studio/views.rst:368
-msgid "Dashboard"
-msgstr ""
-
-#: ../../content/applications/studio/views.rst:370
-msgid "The :guilabel:`Dashboard` view is used to display multiple reporting views and key performance indicators. Which elements are displayed on the view depends on the configuration of the other reporting views."
-msgstr ""
-
-#: ../../content/applications/studio/views.rst:0
-msgid "Sales Analysis Report model's Dashboard view"
-msgstr ""

locale/sources/websites.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 17.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2024-07-23 13:30+0000\n"
+"POT-Creation-Date: 2024-08-21 11:43+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -229,7 +229,7 @@ msgid "Run a modern open-source online store with Odoo eCommerce. Learn how to s
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce.rst:14
-#: ../../content/applications/websites/website.rst:14
+#: ../../content/applications/websites/website.rst:47
 msgid "Odoo offers a :ref:`free custom domain name <domain-name/register>` to all Odoo Online databases for one year. Visitors can then access your website with an address such as `www.example.com` rather than the default `example.odoo.com`."
 msgstr ""
 
@@ -238,12 +238,12 @@ msgid ":doc:`Website Documentation <website>`"
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce.rst:20
-#: ../../content/applications/websites/website.rst:19
+#: ../../content/applications/websites/website.rst:52
 msgid "`Odoo Tutorials: Website <https://www.odoo.com/slides/website-25>`_"
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce.rst:21
-#: ../../content/applications/websites/website.rst:20
+#: ../../content/applications/websites/website.rst:53
 msgid "`Odoo Tutorials: eCommerce <https://www.odoo.com/slides/ecommerce-26>`_"
 msgstr ""
 
@@ -605,72 +605,74 @@ msgid "Own shipping methods"
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:17
-msgid "You can create your own custom shipping methods and define rules to compute shipping costs. To do so, go to :menuselection:`Website --> Configuration --> Shipping Methods`, and either select an **existing** shipping method, or :guilabel:`Create` one. When creating a shipping method, you can choose between :doc:`Fixed Price </applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method>`, :doc:`Based on Rules </applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method>`, and :guilabel:`Pickup in store`."
+msgid "You can create your own custom shipping methods and define rules to compute shipping costs. To do so, go to :menuselection:`Website --> Configuration --> Shipping Methods`, and either select an **existing** shipping method, or :guilabel:`Create` one. When creating a shipping method, you can choose between :ref:`Fixed Price <inventory/shipping/fixed>`, :ref:`Based on Rules <inventory/shipping/rules>`, and :guilabel:`Pickup in store`."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:26
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:24
 msgid "Pickup in store"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:28
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:26
 msgid ":guilabel:`Pickup in store` must first be **enabled** in the settings (:menuselection:`Website --> Configuration --> Settings --> Shipping section)` by checking :guilabel:`On Site Payments & Picking`. Once enabled, you can select and :guilabel:`Customize Pickup Sites`. :guilabel:`Picking sites` can be made **website-specific**, but are by default available for *all* websites."
 msgstr ""
 
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:32
+msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration`"
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:33
+#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83
+msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing`"
+msgstr ""
+
 #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:34
-msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`"
+#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85
+msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/multipack`"
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:35
-msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`"
+msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/cancel`"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:36
-msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`"
-msgstr ""
-
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:37
-msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel`"
-msgstr ""
-
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:42
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:40
 msgid "Shipping providers"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:44
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:42
 msgid "Another solution is to use one of the integrations with an existing shipping provider. The advantage of using an integration is that delivery costs are automatically computed based on each order as well as generating shipping labels."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:51
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:49
 msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:50
 msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:53
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:51
 msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:54
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52
 #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:84
 msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/labels`"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:55
 #: ../../content/applications/websites/ecommerce/products.rst:205
 msgid "Website availability"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:59
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57
 msgid "Shipping methods can be made available on **specific** websites *only*, if desired. To do so, go to :menuselection:`Website --> Configuration --> Settings --> Shipping Methods`, and select the desired **shipping method**. In the :guilabel:`Website` field, set the website you want the shipping method to be restrained to. Leave the field **empty** for the method to be available on *all* websites."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:65
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:63
 msgid "Delivery method at checkout"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:67
+#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:65
 msgid "Customers can choose the shipping method at the end of the checkout process, at the :guilabel:`Confirm Order` step."
 msgstr ""
 
@@ -951,14 +953,6 @@ msgstr ""
 msgid "If customers are allowed to pay when picking up their order in stores or by wire transfer, the quotation is **not** be confirmed and the stock is **not** be reserved. Orders must be confirmed manually to reserve products in stock."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83
-msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`"
-msgstr ""
-
-#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85
-msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`"
-msgstr ""
-
 #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:88
 msgid "Returns and refunds"
 msgstr ""
@@ -1769,7 +1763,7 @@ msgid "Price per unit"
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/products/price_management.rst:55
-msgid "It is possible to display a :doc:`price per unit </applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom>` on the product page. To do that, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Product Reference Price` under the :guilabel:`Shop - Products` section. When enabled, ensure an amount is set in the :guilabel:`Base Unit Count` field of the **product template**, and in the :guilabel:`Sales Price`."
+msgid "It is possible to display a :doc:`price per unit <../../../inventory_and_mrp/inventory/product_management/configure/uom>` on the product page. To do that, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Product Reference Price` under the :guilabel:`Shop - Products` section. When enabled, ensure an amount is set in the :guilabel:`Base Unit Count` field of the **product template**, and in the :guilabel:`Sales Price`."
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/products/price_management.rst:-1
@@ -1789,7 +1783,7 @@ msgid "Pay attention that having the price per unit may be **mandatory** in some
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/products/price_management.rst:77
-msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`"
+msgid ":doc:`../../../inventory_and_mrp/inventory/product_management/configure/uom`"
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/products/price_management.rst:82
@@ -3006,7 +3000,7 @@ msgid "Live Chat"
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:7
-msgid "Odoo *Live Chat* allows users to communicate with website visitors in real-time. With *Live Chat*, leads can be qualified for their sales potential, support questions can be answered quickly, and issues can be directed to the appropriate team for further investigation or follow up. *Live Chat* also provides the opportunity for instant feedback from customers."
+msgid "Odoo **Live Chat** allows users to communicate with website visitors in real-time. With **Live Chat**, leads can be qualified for their sales potential, support questions can be answered quickly, and issues can be directed to the appropriate team for further investigation or follow up. **Live Chat** also provides the opportunity for instant feedback from customers."
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:13
@@ -3014,11 +3008,11 @@ msgid "Enable Live Chat"
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:15
-msgid "The *Live Chat* application can be installed multiple ways:"
+msgid "The **Live Chat** application can be installed multiple ways:"
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:17
-msgid "Go to :menuselection:`Apps application --> Live Chat` and click :guilabel:`Install`."
+msgid "Go to :menuselection:`Apps application`, search `Live Chat`, and click :guilabel:`Install`."
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:18
@@ -3034,7 +3028,7 @@ msgid "View of the settings page and the live chat feature for Odoo Live Chat."
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:30
-msgid "After the *Live Chat* application is installed, a live chat *Channel* is created by default."
+msgid "After the **Live Chat** application is installed, a live chat *Channel* is created, by default."
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:33
@@ -3078,15 +3072,15 @@ msgid "Current operators can be edited, or removed, by clicking on their respect
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:76
-msgid "Click :guilabel:`Add` to reveal an :guilabel:`Add: Operators` modal."
+msgid "Click :guilabel:`Add` to reveal an :guilabel:`Add: Operators` pop-up window."
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:78
-msgid "In the modal, scroll to find the desired users, or enter their name in the :guilabel:`Search...` bar. Then, click the checkbox next to the users to be added, and click :guilabel:`Select`."
+msgid "In the pop-up window, scroll to find the desired users, or enter their name in the search bar. Then, tick the checkbox next to the users to be added, and click :guilabel:`Select`."
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:81
-msgid "New operators can be created and added to the list directly from this modal, as well, by clicking :guilabel:`New`, and filling out the :guilabel:`Create Operators` form. When the form is complete, click :guilabel:`Save & Close`, or :guilabel:`Save & New` for multiple record creations."
+msgid "New operators can be created and added to the list directly from this pop-up window, as well, by clicking :guilabel:`New`, and filling out the :guilabel:`Create Operators` form. When the form is complete, click :guilabel:`Save & Close`, or :guilabel:`Save & New` for multiple record creations."
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:86
@@ -3102,7 +3096,7 @@ msgid "Livechat button"
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:104
-msgid "The *Livechat Button* is the icon that appears in the bottom corner of the website."
+msgid "The *Livechat Button* is the icon that appears in the bottom-right corner of the website."
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:-1
@@ -3122,7 +3116,7 @@ msgid "Color selection, for the button or header, can be made manually using a s
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:126
-msgid "Livechat window"
+msgid "Livechat Window"
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:128
@@ -3150,106 +3144,114 @@ msgid "Channel Rules tab"
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:153
-msgid "The :guilabel:`Channel Rules` tab on the live chat channel detail form determines when the live chat window opens on the website, by configuring when a :guilabel:`URL Regex` action is triggered, such as a page visit."
+msgid "To configure which website user actions open the live chat window, go to the :guilabel:`Channel Rules` tab on the live chat channel detail form."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:157
-msgid "To create a new channel rule, click :guilabel:`Add a line`. This opens the :guilabel:`Create Rules` modal."
+#: ../../content/applications/websites/livechat.rst:156
+msgid "To create a new channel rule, click :guilabel:`Add a line`. This opens the :guilabel:`Create Rules` pop-up window."
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:-1
 msgid "View of a channel's rules form for Odoo Live Chat."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:165
+#: ../../content/applications/websites/livechat.rst:164
 msgid "Create new rules"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:167
-msgid "Fill out the fields on the :guilabel:`Create Rules` modal, as instructed below. Then, click :guilabel:`Save & Close`."
+#: ../../content/applications/websites/livechat.rst:166
+msgid "Fill out the fields on the :guilabel:`Create Rules` pop-up window as instructed below, then click :guilabel:`Save & Close`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:172
+#: ../../content/applications/websites/livechat.rst:171
 msgid "Live Chat Button"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:174
-msgid "The *Live Chat Button* is the icon that appears in the bottom corner of the website. Select from one of the following display options:"
+#: ../../content/applications/websites/livechat.rst:173
+msgid "The *Livechat Button* is the icon that appears in the bottom-right corner of the website. Select from one of the following display options:"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:177
+#: ../../content/applications/websites/livechat.rst:176
 msgid ":guilabel:`Show`: displays the chat button on the page."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:178
+#: ../../content/applications/websites/livechat.rst:177
 msgid ":guilabel:`Show with notification`: displays the chat button, as well as a floating text bubble next to the button."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:180
-msgid ":guilabel:`Open automatically`: displays the button and automatically opens the chat window after a specified amount of time (designated in the :guilabel:`Open automatically timer` field, which is revealed when selecting this option)."
+#: ../../content/applications/websites/livechat.rst:179
+msgid ":guilabel:`Open automatically`: displays the button, and automatically opens the chat window after a specified amount of time (designated in the :guilabel:`Open automatically timer` field, that appears when this option is selected)."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:183
+#: ../../content/applications/websites/livechat.rst:182
 msgid ":guilabel:`Hide`: hides the chat button on the page."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:185
+#: ../../content/applications/websites/livechat.rst:184
 msgid "Chatbot"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:187
+#: ../../content/applications/websites/livechat.rst:186
 msgid "To include a :doc:`Chatbot <livechat/chatbots>` on this channel, select it from the drop-down menu. If the chatbot should only be active when no operators are active, check the box labeled :guilabel:`Enabled only if no operator`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:191
+#: ../../content/applications/websites/livechat.rst:190
 msgid "The :guilabel:`Enabled only if no operator` field is **only** visible if a chatbot is selected in the :guilabel:`Chatbot` field."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:194
+#: ../../content/applications/websites/livechat.rst:193
 msgid "URL Regex"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:196
+#: ../../content/applications/websites/livechat.rst:195
 msgid "The *URL Regex* specifies the web pages where this rule should be applied. In the :guilabel:`URL Regex` field, input the relative URL of the page where the chat button should appear."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:200
-msgid "Open automatically timer"
+#: ../../content/applications/websites/livechat.rst:199
+msgid "For example, to apply the rule to the URL, `https://mydatabse.odoo.com/shop`, enter `/shop` to the :guilabel:`URL Regex` field."
 msgstr ""
 
 #: ../../content/applications/websites/livechat.rst:202
+msgid "To apply the rule to *all* pages on the database, enter `/` in the :guilabel:`URL Regex` field."
+msgstr ""
+
+#: ../../content/applications/websites/livechat.rst:205
+msgid "Open automatically timer"
+msgstr ""
+
+#: ../../content/applications/websites/livechat.rst:207
 msgid "This field designates the amount of time (in seconds) a page should be open before the chat window opens. This field **only** appears if the :guilabel:`Live Chat Button` for this rule is set to :guilabel:`Open automatically`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:206
+#: ../../content/applications/websites/livechat.rst:211
 msgid "Country"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:208
-msgid "If this channel should only be available to site visitors in specific countries, add them to the :guilabel:`Country` field. If this field is left blank, the channel is available to all site visitors, regardless of location."
+#: ../../content/applications/websites/livechat.rst:213
+msgid "If this channel should **only** be available to site visitors in specific countries, add them to the :guilabel:`Country` field. If this field is left blank, the channel is available to all site visitors, regardless of location."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:213
+#: ../../content/applications/websites/livechat.rst:218
 msgid "In order to track the geographical location of visitors, *GeoIP* **must** be installed on the database. While this feature is installed by default on *Odoo Online* databases, *On-Premise* databases require additional :doc:`setup steps </administration/on_premise/geo_ip>`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:220
+#: ../../content/applications/websites/livechat.rst:225
 msgid "Widget tab"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:222
+#: ../../content/applications/websites/livechat.rst:227
 msgid "The :guilabel:`Widget` tab on the live chat channel detail form provides the code for a website widget. This code can be added to a website to provide access to a live chat window."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:226
+#: ../../content/applications/websites/livechat.rst:231
 msgid "The live chat widget can be added to websites created through Odoo by navigating to :menuselection:`Website app --> Configuration --> Settings`. Then, scroll to the :menuselection:`Email & Marketing` section. In the :guilabel:`Channel` field, select the channel to add to the site. Click :guilabel:`Save` to apply."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:231
+#: ../../content/applications/websites/livechat.rst:236
 msgid "To add the widget to a website created on a third-party platform, click the first :guilabel:`COPY` button on the :guilabel:`Widget` tab, and paste the code into the `<head>` tag on the site."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:234
+#: ../../content/applications/websites/livechat.rst:239
 msgid "Likewise, to send a live chat session to a customer, click the second :guilabel:`COPY` button on the :guilabel:`Widget` tab. This link can be sent directly to a customer. When they click the link, they are redirected to a new chat window."
 msgstr ""
 
@@ -3257,23 +3259,23 @@ msgstr ""
 msgid "View of the widget tab for Odoo Live Chat."
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:243
+#: ../../content/applications/websites/livechat.rst:248
 msgid ":doc:`../productivity/discuss`"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:244
+#: ../../content/applications/websites/livechat.rst:249
 msgid ":doc:`livechat/responses`"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:245
+#: ../../content/applications/websites/livechat.rst:250
 msgid ":doc:`livechat/ratings`"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:246
+#: ../../content/applications/websites/livechat.rst:251
 msgid ":doc:`livechat/chatbots`"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:247
+#: ../../content/applications/websites/livechat.rst:252
 msgid ":doc:`livechat/participate`"
 msgstr ""
 
@@ -4133,7 +4135,7 @@ msgid "Commands and canned responses"
 msgstr ""
 
 #: ../../content/applications/websites/livechat/responses.rst:5
-msgid "In the Odoo *Live Chat* application, *commands* allow the user to perform specific actions both inside the chat window, and through other Odoo applications. The *Live Chat* app also includes *canned responses*. These are customized, preconfigured substitutions that allow users to replace shortcut entries in place of longer, well-thought out responses to some of the most common questions and comments."
+msgid "In the Odoo **Live Chat** application, *commands* allow the user to perform specific actions both inside the chat window, and through other Odoo applications. The **Live Chat** app also includes *canned responses*. These are customized, preconfigured substitutions that allow users to replace shortcut entries in place of longer, well-thought out responses to some of the most common questions and comments."
 msgstr ""
 
 #: ../../content/applications/websites/livechat/responses.rst:11
@@ -4173,50 +4175,42 @@ msgid "Type `@username` to mention a user in the conversation. A notification wi
 msgstr ""
 
 #: ../../content/applications/websites/livechat/responses.rst:45
-msgid "Type `#channel` to mention a *Discuss* channel."
-msgstr ""
-
-#: ../../content/applications/websites/livechat/responses.rst:46
 msgid "Type `/command` to execute a command."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:47
+#: ../../content/applications/websites/livechat/responses.rst:46
 msgid "Type `:shortcut` to insert a :ref:`canned response <live-chat/canned-responses>`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:-1
-msgid "View of the message generated from using the /help command in Odoo Live Chat."
-msgstr ""
-
-#: ../../content/applications/websites/livechat/responses.rst:54
+#: ../../content/applications/websites/livechat/responses.rst:49
 msgid ":doc:`/applications/productivity/discuss`"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:55
+#: ../../content/applications/websites/livechat/responses.rst:50
 msgid ":doc:`/applications/productivity/discuss/team_communication`"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:58
+#: ../../content/applications/websites/livechat/responses.rst:53
 msgid "Ticket & search tickets"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:60
+#: ../../content/applications/websites/livechat/responses.rst:55
 msgid "The `/ticket` and `/search_tickets` commands allow operators to create helpdesk tickets directly from a conversation, and search through existing tickets by keyword or ticket number."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:64
-msgid "The `/ticket` and `/search_tickets` commands can **only** be used if the *Helpdesk* app has been installed, and *Live Chat* has been activated on a *Helpdesk* team. To activate *Live Chat*, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and select a team. Scroll to the :guilabel:`Channels` section, and check the box labeled, :guilabel:`Live Chat`."
+#: ../../content/applications/websites/livechat/responses.rst:59
+msgid "The `/ticket` and `/search_tickets` commands can **only** be used if the **Helpdesk** app has been installed, and *Live Chat* has been activated on a *Helpdesk* team. To activate *Live Chat*, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and select a team. Scroll to the :guilabel:`Channels` section, and check the box labeled, :guilabel:`Live Chat`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:72
+#: ../../content/applications/websites/livechat/responses.rst:67
 msgid "Create a ticket from a live chat"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:74
+#: ../../content/applications/websites/livechat/responses.rst:69
 msgid "If an operator types `/ticket` in the chat window, the conversation is used to create a *Helpdesk* ticket."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:77
+#: ../../content/applications/websites/livechat/responses.rst:72
 msgid "After entering the `/ticket` command, type a title for the ticket into the chat window, then press `Enter`."
 msgstr ""
 
@@ -4225,135 +4219,127 @@ msgstr ""
 msgid "View of the results from a helpdesk search in a Live Chat conversation."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:84
+#: ../../content/applications/websites/livechat/responses.rst:79
 msgid "The newly created ticket will be added to the *Helpdesk* team that has live chat enabled. If more than one team has live chat enabled, the ticket will automatically be assigned based on the team's priority."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:88
+#: ../../content/applications/websites/livechat/responses.rst:83
 msgid "The transcript from the conversation will be added to the new ticket, under the :guilabel:`Description` tab."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:91
-msgid "To access the new ticket, click on the link in the chat window, or go to the :menuselection:`Helpdesk app`, and click the :guilabel:`Tickets` button on the Kanban card for the appropriate team."
+#: ../../content/applications/websites/livechat/responses.rst:86
+msgid "To access the new ticket, click on the link in the chat window, or go to the :menuselection:`Helpdesk app` and click the :guilabel:`Tickets` button on the Kanban card for the appropriate team."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:96
+#: ../../content/applications/websites/livechat/responses.rst:91
 msgid "Search for a ticket from a live chat"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:98
+#: ../../content/applications/websites/livechat/responses.rst:93
 msgid "If an operator types `/search_tickets` in the chat window, they can search through *Helpdesk* tickets, either by ticket number or keyword."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:101
+#: ../../content/applications/websites/livechat/responses.rst:96
 msgid "After entering the `/search_tickets` command, type a keyword or ticket number, then press :kbd:`Enter`. If one or more related tickets are found, a list of links is generated in the conversation window."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:110
+#: ../../content/applications/websites/livechat/responses.rst:105
 msgid "Results from the search command will only be seen by the operator, not the customer."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:113
+#: ../../content/applications/websites/livechat/responses.rst:108
 msgid "History"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:115
-msgid "Typing `/history` in the chat window generates a list of the most recent pages the visitor has viewed on the website (up to fifteen pages)."
+#: ../../content/applications/websites/livechat/responses.rst:110
+msgid "If an operator types `/history` in the chat window, it generates a list of the most recent pages the visitor has viewed on the website (up to 15)."
 msgstr ""
 
 #: ../../content/applications/websites/livechat/responses.rst:-1
 msgid "View of the results from a /history command in a Live Chat conversation."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:123
+#: ../../content/applications/websites/livechat/responses.rst:118
 msgid "Lead"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:125
-msgid "By typing `/lead` in the chat window, an operator can create a *lead* in the *CRM* application."
+#: ../../content/applications/websites/livechat/responses.rst:120
+msgid "By typing `/lead` in the chat window, an operator can create a *lead* in the **CRM** application."
 msgstr ""
 
 #: ../../content/applications/websites/livechat/responses.rst:-1
 msgid "View of the results from a /lead command in a Live Chat conversation."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:132
-msgid "The `/lead` command can only be used if the *CRM* app has been installed."
+#: ../../content/applications/websites/livechat/responses.rst:127
+msgid "The `/lead` command can only be used if the **CRM** app has been installed."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:134
+#: ../../content/applications/websites/livechat/responses.rst:129
 msgid "After typing `/lead`, create a title for this new lead, then press `Enter`. A link with the lead title appears. Click the link, or navigate to the :menuselection:`CRM` app to view the :guilabel:`Pipeline`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:139
+#: ../../content/applications/websites/livechat/responses.rst:134
 msgid "The link to the new lead can only be seen and accessed by the operator, not the customer."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:141
+#: ../../content/applications/websites/livechat/responses.rst:136
 msgid "The transcript of that specific live chat conversation (where the lead was created) is added to the :guilabel:`Internal Notes` tab of the lead form."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:144
+#: ../../content/applications/websites/livechat/responses.rst:139
 msgid "On the :guilabel:`Extra Information` tab of the lead form, the :guilabel:`Source` will be listed as :guilabel:`Livechat`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:148
+#: ../../content/applications/websites/livechat/responses.rst:143
 msgid "Leave"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:150
+#: ../../content/applications/websites/livechat/responses.rst:145
 msgid "If an operator types `/leave` in the chat window, they can automatically exit the conversation. This command does not cause the customer to be removed from the conversation, nor does it automatically end the conversation."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:155
+#: ../../content/applications/websites/livechat/responses.rst:150
 msgid ":doc:`/applications/sales/crm/acquire_leads`"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:156
+#: ../../content/applications/websites/livechat/responses.rst:151
 msgid ":doc:`../../services/helpdesk`"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:161
+#: ../../content/applications/websites/livechat/responses.rst:156
 msgid "Canned responses"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:163
-msgid "*Canned responses* are customizable inputs, where a typed shortcut populates a longer response. A user enters a keyword *shortcut*, which is then automatically replaced by the expanded *substitution* response. The shortcut is the keyword or key phrase that is to be replaced. The substitution is the longer message that replaces the shortcut."
+#: ../../content/applications/websites/livechat/responses.rst:158
+msgid "*Canned responses* are customizable inputs where a *shortcut* stands in for a longer response. An operator will enter the shortcut, and it is automatically replaced by the expanded *substitution* response in the conversation."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:171
+#: ../../content/applications/websites/livechat/responses.rst:163
 msgid "Create canned responses"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:173
+#: ../../content/applications/websites/livechat/responses.rst:165
 msgid "To create a new canned response, go to :menuselection:`Live Chat app --> Configuration --> Canned Responses --> New`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:176
+#: ../../content/applications/websites/livechat/responses.rst:168
 msgid "Type a shortcut command in the :guilabel:`Shortcut` field. Next, click the :guilabel:`Substitution` field, and type the message that should replace the shortcut."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:180
-msgid "Try to connect the shortcut to the topic of the substitution. Not only does this make it easier to use the responses, it prevents the list of responses from becoming disorganized and overwhelming."
+#: ../../content/applications/websites/livechat/responses.rst:172
+msgid "Try to connect the shortcut to the topic of the substitution. The easier it is for the operators to remember, the easier it is to use the canned responses in conversations."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:184
-msgid "In the :guilabel:`Description` field, add any information that provides context for this response, such as guidelines for when it should or should not be used."
-msgstr ""
-
-#: ../../content/applications/websites/livechat/responses.rst:187
-msgid "The :guilabel:`Last Used` field keeps track of the date and time each response was most recently used. This field **cannot** be edited."
-msgstr ""
-
-#: ../../content/applications/websites/livechat/responses.rst:191
+#: ../../content/applications/websites/livechat/responses.rst:176
 msgid "Use canned responses in a live chat conversation"
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:193
+#: ../../content/applications/websites/livechat/responses.rst:178
 msgid "To use a canned response during a live chat conversation, type a colon (`:`) into the chat window, followed by the shortcut."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:197
+#: ../../content/applications/websites/livechat/responses.rst:182
 msgid "An operator is chatting with a visitor. As soon as they type `:` they would see a list of available responses. They can manually select one from the list, or continue to type. If they want to use the canned response `'I am sorry to hear that.'`, they would type `:sorry`."
 msgstr ""
 
@@ -4361,7 +4347,7 @@ msgstr ""
 msgid "View of a chat window and the use of a canned response in Odoo Live Chat."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/responses.rst:206
+#: ../../content/applications/websites/livechat/responses.rst:191
 msgid "Typing `:` into a chat window on its own will generate a list of available canned responses. Responses can be manually selected from the list, in addition to the use of shortcuts."
 msgstr ""
 
@@ -4369,12 +4355,16 @@ msgstr ""
 msgid "View of a chat window and the list of available canned responses."
 msgstr ""
 
-#: ../../content/applications/websites/website.rst:8
+#: ../../content/applications/websites/website.rst:7
 msgid "Website"
 msgstr ""
 
-#: ../../content/applications/websites/website.rst:10
-msgid "Discover the best **Open-Source Website Builder** and learn how to build beautiful websites that convert visitors into leads or revenues."
+#: ../../content/applications/websites/website.rst:9
+msgid "**Odoo Website** offers a user-friendly platform for creating and managing your website. It includes various tools and features to help you design, publish, and maintain web pages without needing advanced technical skills. You can easily customize layouts, add multimedia content, and integrate with other Odoo apps to expand your website's functionality."
+msgstr ""
+
+#: ../../content/applications/websites/website.rst:54
+msgid ":doc:`../general/integrations/unsplash`"
 msgstr ""
 
 #: ../../content/applications/websites/website/configuration/address_autocomplete.rst:3
@@ -4992,30 +4982,110 @@ msgid "Google Search Console is a free web service provided by Google that allow
 msgstr ""
 
 #: ../../content/applications/websites/website/configuration/google_search_console.rst:10
-msgid "To enable GSC, go to `Google Search Console <https://search.google.com/search-console/welcome>`_, enter your domain or URL prefix, follow the instructions, and copy the code from Google."
+msgid "To enable Google Search Console for your website, go to `Google Search Console <https://search.google.com/search-console/welcome>`_. Then, select the property type :ref:`GSC-Domain` or :ref:`GSC-URL prefix`."
 msgstr ""
 
 #: ../../content/applications/websites/website/configuration/google_search_console.rst:-1
 msgid "Google Search Console domain or URL prefix"
 msgstr ""
 
-#: ../../content/applications/websites/website/configuration/google_search_console.rst:-1
-msgid "Verify domain or URL prefix"
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:20
+msgid "Domain property"
 msgstr ""
 
-#: ../../content/applications/websites/website/configuration/google_search_console.rst:19
-msgid "Then, access your Odoo database, go to :menuselection:`Website --> Configuration --> Settings`, and enable :guilabel:`Google Search Console` in the :guilabel:`SEO` section. Paste the code in the dedicated field."
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:22
+msgid "A domain property in Search Console tracks all versions of your website, including subdomains and protocols (http/https). This comprehensive view allows you to analyze your overall website's search performance and make informed decisions to optimize its visibility. Enter the domain, e.g., `example.com` and click :guilabel:`Continue`."
 msgstr ""
 
-#: ../../content/applications/websites/website/configuration/google_search_console.rst:-1
-msgid "Website Settings pasting GSC code"
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:28
+msgid "The domain property type can only be verified via `DNS record <https://support.google.com/webmasters/answer/9008080?hl=en#domain_name_verification&zippy=%2Chtml-tag>`_."
 msgstr ""
 
-#: ../../content/applications/websites/website/configuration/google_search_console.rst:27
-msgid "To prevent Google from indexing both your custom domain name `www.example.com` and your original Odoo database URL `www.example.odoo.com`, :ref:`map your domain name with your Odoo website <domain-name/website-map>`."
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:30
+msgid "Google suggests creating at least one domain property to represent your site, as it is the most complete view of your website information."
 msgstr ""
 
-#: ../../content/applications/websites/website/configuration/google_search_console.rst:32
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:36
+msgid "URL prefix property"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:38
+msgid "This type of verification is usually simpler as you have multiple verification methods, such as using your existing Google Analytics or Tag Manager account. It also makes sense to view a section of your website separately. For example, if you work with a consultant on a specific part of your website, you might want to verify this part separately to limit access to your data. Enter the URL, e.g., `https://www.example.odoo.com` and click :guilabel:`Continue`."
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:46
+msgid "Site ownership verification"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:48
+msgid "Before using Google Search Console for your website, you must verify your site ownership. This verification process is a security measure that protects both you and Google. It ensures that only authorized users have access to sensitive data and that you have control over how your website is treated in Google Search."
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:53
+msgid "Five methods are available to do this:"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:57
+msgid ":ref:`GSC-HTML-file-upload`"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:58
+msgid "`DNS record <https://support.google.com/webmasters/answer/9008080?hl=en#domain_name_verification&zippy=%2Chtml-tag>`_"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:59
+msgid "`HTML tag <https://support.google.com/webmasters/answer/9008080?hl=en#meta_tag_verification&zippy=%2Chtml-tag>`_"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:60
+msgid "`Google Analytics tracking code <https://support.google.com/webmasters/answer/9008080?hl=en#google_analytics_verification>`_"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:61
+msgid "`Google Tag Manager container snippet <https://support.google.com/webmasters/answer/9008080?hl=en#google_tag_manager_verification>`_"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:64
+msgid "The best method for you depends on your comfort level and technical expertise. For beginners, using a file upload or HTML tag might be easiest. Those options are convenient if you already use Google Analytics or Tag Manager. You need to access your domain registrar's settings for domain verification."
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:72
+msgid "HTML file upload"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:74
+msgid "This method involves uploading an HTML file provided by Google containing the verification code you have to put in your Odoo's Website Settings. Google verifies ownership by checking for this code."
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:77
+msgid "Once you added your website URL under the URL prefix option and clicked :guilabel:`continue`, expand the HTML file section where you find a download :icon:`fa-download` button."
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:0
+msgid "HTML file download"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:83
+msgid "Download your HTML verification file and copy the verification code (e.g., `google123abc.html`)."
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:0
+msgid "Open and copy html file"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:88
+msgid "In your Odoo database, go to :menuselection:`Website --> Configuration --> Settings`, and enable :guilabel:`Google Search Console` in the :guilabel:`SEO` section. Paste the verification code (e.g., `google123abc.html`) in the dedicated field."
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:0
+msgid "Paste html code in Odoo"
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:95
+msgid "In Google Search Console, click :guilabel:`Verify`. If you perform the steps above correctly, verification should be done immediately."
+msgstr ""
+
+#: ../../content/applications/websites/website/configuration/google_search_console.rst:99
 msgid ":doc:`domain_names`"
 msgstr ""
 
@@ -6480,34 +6550,38 @@ msgid ":abbr:`GTM (Google Tag Manager)` is a tag management system that allows y
 msgstr ""
 
 #: ../../content/applications/websites/website/reporting/analytics.rst:140
-msgid "Google Tag Manager may not be compliant with local data protection regulations."
+msgid "Some GTM tags use data layers (e.g., advanced eCommerce tracking data layers) to retrieve variables and send them to Google Analytics. Data layers are currently not managed in Odoo."
 msgstr ""
 
 #: ../../content/applications/websites/website/reporting/analytics.rst:142
-msgid "To use GTM, proceed as follows:"
+msgid "Google Tag Manager may not be compliant with local data protection regulations."
 msgstr ""
 
 #: ../../content/applications/websites/website/reporting/analytics.rst:144
-msgid "Create or sign in to a Google account by going to https://tagmanager.google.com/."
+msgid "To use GTM, proceed as follows:"
 msgstr ""
 
 #: ../../content/applications/websites/website/reporting/analytics.rst:146
-msgid "In the :guilabel:`Accounts` tab, click :guilabel:`Create account`."
+msgid "Create or sign in to a Google account by going to https://tagmanager.google.com/."
 msgstr ""
 
 #: ../../content/applications/websites/website/reporting/analytics.rst:148
-msgid "Enter an :guilabel:`Account Name` and select the account's :guilabel:`Country`."
+msgid "In the :guilabel:`Accounts` tab, click :guilabel:`Create account`."
 msgstr ""
 
 #: ../../content/applications/websites/website/reporting/analytics.rst:150
+msgid "Enter an :guilabel:`Account Name` and select the account's :guilabel:`Country`."
+msgstr ""
+
+#: ../../content/applications/websites/website/reporting/analytics.rst:152
 msgid "Enter your website's URL in the :guilabel:`Container name` field and select the :guilabel:`Target platform`."
 msgstr ""
 
-#: ../../content/applications/websites/website/reporting/analytics.rst:153
+#: ../../content/applications/websites/website/reporting/analytics.rst:155
 msgid "Click :guilabel:`Create` and agree to the Terms of Service."
 msgstr ""
 
-#: ../../content/applications/websites/website/reporting/analytics.rst:155
+#: ../../content/applications/websites/website/reporting/analytics.rst:157
 msgid "Copy the `<head>` and `<body>` codes from the popup window. Then, go to your website, click :guilabel:`Edit`, go to the :guilabel:`Themes` tab, scroll down to the :guilabel:`Website Settings` section, then click :guilabel:`<head>` and :guilabel:`</body>` to paste the codes."
 msgstr ""
 
@@ -6515,7 +6589,7 @@ msgstr ""
 msgid "Install Google Tag Manager"
 msgstr ""
 
-#: ../../content/applications/websites/website/reporting/analytics.rst:164
+#: ../../content/applications/websites/website/reporting/analytics.rst:166
 msgid "The data is collected in the marketing tools used to monitor the website (e.g., Google Analytics, Plausible, Facebook Pixel), not in Odoo."
 msgstr ""