[FIX] *: make several untranslatable parts translatable

Some parts of the documention were currently not translatable: - the custom `Card` directives - the strings in the layout HTML pages - the placeholder text in the search box - the "Edit on GitHub" text on each page This commit makes sure that all of these are translatable now. X-original-commit: 1fbe71f76d Part-of: odoo/documentation#15909 Signed-off-by: Tiffany Chang (tic) <tic@odoo.com> Signed-off-by: Dylan Kiss (dyki) <dyki@odoo.com>
2026-03-27 14:10:23 +07:00 · 2025-12-28 19:35:34 +00:00
parent 0e032e24e7
commit 11ed2ccbb7
15 changed files with 3536 additions and 2423 deletions
--- a/.weblate.json
+++ b/.weblate.json
@@ -61,6 +61,11 @@
                "filemask": "locale/*/LC_MESSAGES/services.po",
                "new_base": "locale/sources/services.pot"
            },
+            {
+                "name": "sphinx",
+                "filemask": "locale/*/LC_MESSAGES/sphinx.po",
+                "new_base": "locale/sources/sphinx.pot"
+            },
            {
                "name": "studio",
                "filemask": "locale/*/LC_MESSAGES/studio.po",
--- a/extensions/cards/init.py
+++ b/extensions/cards/init.py
@@ -2,7 +2,9 @@ from pathlib import Path

 from docutils import nodes
 from docutils.parsers.rst import directives
+from sphinx import addnodes
 from sphinx.util.docutils import SphinxDirective
+from sphinx.util.nodes import set_source_info


 class Cards(SphinxDirective):
@@ -67,21 +69,24 @@ class Card(SphinxDirective):
        div_card_body = Div(classes=['card-body', 'pb-0'])
        div_card += div_card_body

-        h4_title = H4(classes=['card-title', 'text-primary', 'mb-1'])
-        h4_title += nodes.Text(self.arguments[0])
+        title_nodes, _ = self.state.inline_text(self.arguments[0], self.lineno)
+        h4_title = H4('', *title_nodes, classes=['card-title', 'text-primary', 'mb-1'])
+        set_source_info(self, h4_title)
        div_card_body += h4_title

-        p_card_text = nodes.paragraph(classes=['card-text', 'text-dark', 'fw-normal'])
-        p_card_text += nodes.Text('\n'.join(self.content))
+        text_nodes, _ = self.state.inline_text('\n'.join(self.content), self.lineno)
+        p_card_text = nodes.paragraph('', *text_nodes, classes=['card-text', 'text-dark', 'fw-normal'])
+        set_source_info(self, p_card_text)
        div_card_body += p_card_text

        div_card_footer = Div(classes=['card-footer', 'border-0'])
        div_card += div_card_footer

        if 'tag' in self.options:
-            span_badge = Span(classes=['badge', 'rounded-pill', 'bg-dark', 'mt-auto', 'mb-2'])
+            tag_nodes, _ = self.state.inline_text(self.options['tag'], self.lineno)
+            span_badge = Span('', *tag_nodes, classes=['badge', 'rounded-pill', 'bg-dark', 'mt-auto', 'mb-2'])
+            set_source_info(self, span_badge)
            div_card_footer += span_badge
-            span_badge += nodes.Text(self.options['tag'])

        return [a_col]

@@ -94,16 +99,34 @@ class A(nodes.General, nodes.Element):
    custom_tag_name = 'a'


-class Span(nodes.General, nodes.Element):
+class TranslatableMixin(addnodes.translatable):
+    """
+    Mixin to make a node translatable.
+    """
+    def preserve_original_messages(self):
+        # Store the original text (msgid) if not already saved.
+        if 'rawtext' not in self:
+            self['original_message'] = self.astext()
+
+    def apply_translated_message(self, original_message, translated_message):
+        # Replace the node's children (content) with the translated text.
+        self.children = [nodes.Text(translated_message)]
+
+    def extract_original_messages(self):
+        # Retrieve the preserved msgid.
+        return [self['original_message']]
+
+
+class Span(nodes.General, nodes.Element, TranslatableMixin):
    custom_tag_name = 'span'


-class H4(nodes.General, nodes.Element):
+class H4(nodes.General, nodes.Element, TranslatableMixin):
    custom_tag_name = 'h4'


 def visit_node(translator, node):
-    custom_attr = {k: v for k, v in node.attributes.items() if k not in node.known_attributes}
+    custom_attr = {k: v for k, v in node.attributes.items() if k not in node.known_attributes and k != 'original_message'}
    translator.body.append(translator.starttag(node, node.custom_tag_name, **custom_attr).rstrip())


--- a/extensions/odoo_theme/layout.html
+++ b/extensions/odoo_theme/layout.html
@@ -119,7 +119,7 @@
                    {%- if github_link and pagename != 'search' and not pagename.startswith('legal') %}
                        <a href="{{ github_link(mode='edit') }}"
                           class="o_git_link d-none d-lg-inline-block">
-                            <i class="i-edit"></i> Edit on GitHub
+                            <i class="i-edit"></i> {%- trans %}Edit on GitHub{%- endtrans %}
                        </a>
                    {%- endif %}
                </article>
--- a/extensions/odoo_theme/layout_templates/searchbox.html
+++ b/extensions/odoo_theme/layout_templates/searchbox.html
@@ -1,7 +1,7 @@
 {# NOTE: the 'searchbox' id is used to hook the "Hide Search Matches" button #}
 <div id="searchbox" class="o_search_wrapper d-flex flex-grow-1" role="search">
    <form class="o_search" action="{{ pathto('search') }}" method="get">
-        <input type="text" name="q" id="q" class="form-control rounded-pill" placeholder="What are you looking for?">
+        <input type="text" name="q" id="q" class="form-control rounded-pill" placeholder="{{ _('What are you looking for?') }}">
        <input type="hidden" name="area" value="default">
        <input type="hidden" name="check_keywords" value="yes">
        <button type="submit" class="btn"><i class="i-search"></i></button>
--- a/locale/sources/administration.pot
+++ b/locale/sources/administration.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo master\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-12-20 18:30+0000\n"
+"POT-Creation-Date: 2026-01-07 14:06+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"
@@ -685,8 +685,6 @@ msgstr ""
 #: ../../content/administration/odoo_sh/advanced/submodules.rst:9
 #: ../../content/administration/odoo_sh/first_module.rst:6
 #: ../../content/administration/odoo_sh/getting_started/builds.rst:14
-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9
-#: ../../content/administration/odoo_sh/getting_started/status.rst:6
 msgid "Overview"
 msgstr ""

@@ -1009,8 +1007,8 @@ msgstr ""

 #: ../../content/administration/odoo_sh/advanced/submodules.rst:82
 #: ../../content/administration/odoo_sh/advanced/submodules.rst:94
-#: ../../content/administration/odoo_sh/first_module.rst:362
-#: ../../content/administration/odoo_sh/first_module.rst:501
+#: ../../content/administration/odoo_sh/first_module.rst:359
+#: ../../content/administration/odoo_sh/first_module.rst:498
 msgid "Replace"
 msgstr ""

@@ -1229,7 +1227,7 @@ msgid "Stage the changes to be committed"
 msgstr ""

 #: ../../content/administration/odoo_sh/first_module.rst:161
-#: ../../content/administration/odoo_sh/first_module.rst:397
+#: ../../content/administration/odoo_sh/first_module.rst:394
 msgid "Commit your changes"
 msgstr ""

@@ -1242,312 +1240,312 @@ msgid "From an Odoo.sh editor terminal:"
 msgstr ""

 #: ../../content/administration/odoo_sh/first_module.rst:175
-msgid "The above command is explained in the section :ref:`Commit & Push your changes <odoosh-gettingstarted-online-editor-push>` of the :ref:`Online Editor <odoosh-gettingstarted-online-editor>` chapter. It includes the explanation regarding the fact you will be prompted to type your username and password, and what to do if you use the two-factor authentication."
+msgid "The above command is explained in the section :ref:`Commit and push changes <odoo-sh/editor/commit>` of the :doc:`Online editor page <getting_started/online_editor>`. It includes the explanation regarding the fact you will be prompted to type your username and password, and what to do if you use the two-factor authentication."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:183
-#: ../../content/administration/odoo_sh/first_module.rst:385
-#: ../../content/administration/odoo_sh/first_module.rst:411
+#: ../../content/administration/odoo_sh/first_module.rst:180
+#: ../../content/administration/odoo_sh/first_module.rst:382
+#: ../../content/administration/odoo_sh/first_module.rst:408
 msgid "Or, from your computer terminal:"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:189
+#: ../../content/administration/odoo_sh/first_module.rst:186
 msgid "You need to specify *-u origin feature-1* for the first push only. From that point, to push your future changes from your computer, you can simply use"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:197
+#: ../../content/administration/odoo_sh/first_module.rst:194
 msgid "Test your module"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:199
+#: ../../content/administration/odoo_sh/first_module.rst:196
 msgid "Your branch should appear in your development branches in your project."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:204
+#: ../../content/administration/odoo_sh/first_module.rst:201
 msgid "In the branches view of your project, you can click on your branch name in the left navigation panel to access its history."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:210
+#: ../../content/administration/odoo_sh/first_module.rst:207
 msgid "You can see here the changes you just pushed, including the comment you set. Once the database ready, you can access it by clicking the *Connect* button."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:216
+#: ../../content/administration/odoo_sh/first_module.rst:213
 msgid "If your Odoo.sh project is configured to install your module automatically, you will directly see it amongst the database apps. Otherwise, it will be available in the apps to install."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:220
+#: ../../content/administration/odoo_sh/first_module.rst:217
 msgid "You can then play around with your module, create new records and test your features and buttons."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:223
+#: ../../content/administration/odoo_sh/first_module.rst:220
 msgid "Test with the production data"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:225
+#: ../../content/administration/odoo_sh/first_module.rst:222
 msgid "You need to have a production database for this step. You can create it if you do not have it yet."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:227
+#: ../../content/administration/odoo_sh/first_module.rst:224
 msgid "Once you tested your module in a development build with the demo data and believe it is ready, you can test it with the production data using a staging branch."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:230
+#: ../../content/administration/odoo_sh/first_module.rst:227
 msgid "You can either:"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:232
+#: ../../content/administration/odoo_sh/first_module.rst:229
 msgid "Make your development branch a staging branch, by drag and dropping it onto the *staging* section title."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:238
+#: ../../content/administration/odoo_sh/first_module.rst:235
 msgid "Merge it in an existing staging branch, by drag and dropping it onto the given staging branch."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:243
-#: ../../content/administration/odoo_sh/first_module.rst:289
+#: ../../content/administration/odoo_sh/first_module.rst:240
+#: ../../content/administration/odoo_sh/first_module.rst:286
 msgid "You can also use the :code:`git merge` command to merge your branches."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:245
+#: ../../content/administration/odoo_sh/first_module.rst:242
 msgid "This will create a new staging build, which will duplicate the production database and make it run using a server updated with your latest changes of your branch."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:251
-#: ../../content/administration/odoo_sh/first_module.rst:297
+#: ../../content/administration/odoo_sh/first_module.rst:248
+#: ../../content/administration/odoo_sh/first_module.rst:294
 msgid "Once the database ready, you can access it using the *Connect* button."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:256
-#: ../../content/administration/odoo_sh/first_module.rst:300
+#: ../../content/administration/odoo_sh/first_module.rst:253
+#: ../../content/administration/odoo_sh/first_module.rst:297
 msgid "Install your module"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:258
+#: ../../content/administration/odoo_sh/first_module.rst:255
 msgid "Your module will not be installed automatically, you have to install it from the apps menu. Indeed, the purpose of the staging build is to test the behavior of your changes as it would be on your production, and on your production you would not like your module to be installed automatically, but on demand."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:263
+#: ../../content/administration/odoo_sh/first_module.rst:260
 msgid "Your module may not appear directly in your apps to install either, you need to update your apps list first:"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:266
+#: ../../content/administration/odoo_sh/first_module.rst:263
 msgid "Activate the :ref:`developer mode <developer-mode>`"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:267
+#: ../../content/administration/odoo_sh/first_module.rst:264
 msgid "in the apps menu, click the *Update Apps List* button,"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:268
+#: ../../content/administration/odoo_sh/first_module.rst:265
 msgid "in the dialog that appears, click the *Update* button."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:273
+#: ../../content/administration/odoo_sh/first_module.rst:270
 msgid "Your module will then appear in the list of available apps."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:279
+#: ../../content/administration/odoo_sh/first_module.rst:276
 msgid "Deploy in production"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:281
+#: ../../content/administration/odoo_sh/first_module.rst:278
 msgid "Once you tested your module in a staging branch with your production data, and believe it is ready for production, you can merge your branch in the production branch."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:284
+#: ../../content/administration/odoo_sh/first_module.rst:281
 msgid "Drag and drop your staging branch on the production branch."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:291
+#: ../../content/administration/odoo_sh/first_module.rst:288
 msgid "This will merge the latest changes of your staging branch in the production branch, and update your production server with these latest changes."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:302
+#: ../../content/administration/odoo_sh/first_module.rst:299
 msgid "Your module will not be installed automatically, you have to install it manually as explained in the :ref:`above section about installing your module in staging databases <odoosh-gettingstarted-firstmodule-productiondata-install>`."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:310
+#: ../../content/administration/odoo_sh/first_module.rst:307
 msgid "Add a change"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:312
+#: ../../content/administration/odoo_sh/first_module.rst:309
 msgid "This section explains how to add a change in your module by adding a new field in a model and deploy it."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:317
+#: ../../content/administration/odoo_sh/first_module.rst:314
 msgid "From the Odoo.sh editor,"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:316
+#: ../../content/administration/odoo_sh/first_module.rst:313
 msgid "browse to your module folder *~/src/user/my_module*,"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:317
+#: ../../content/administration/odoo_sh/first_module.rst:314
 msgid "then, open the file *models/models.py*."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:323
+#: ../../content/administration/odoo_sh/first_module.rst:320
 msgid "Or, from your computer,"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:320
+#: ../../content/administration/odoo_sh/first_module.rst:317
 msgid "use the file browser of your choice to browse to your module folder *~/src/odoo-addons/my_module*,"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:322
+#: ../../content/administration/odoo_sh/first_module.rst:319
 msgid "then, open the file *models/models.py* using the editor of your choice, such as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:325
+#: ../../content/administration/odoo_sh/first_module.rst:322
 msgid "Then, after the description field"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:331
+#: ../../content/administration/odoo_sh/first_module.rst:328
 msgid "Add a datetime field"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:337
+#: ../../content/administration/odoo_sh/first_module.rst:334
 msgid "Then, open the file *views/views.xml*."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:339
-#: ../../content/administration/odoo_sh/first_module.rst:475
+#: ../../content/administration/odoo_sh/first_module.rst:336
+#: ../../content/administration/odoo_sh/first_module.rst:472
 msgid "After"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:345
-#: ../../content/administration/odoo_sh/first_module.rst:452
-#: ../../content/administration/odoo_sh/first_module.rst:469
-#: ../../content/administration/odoo_sh/first_module.rst:481
+#: ../../content/administration/odoo_sh/first_module.rst:342
+#: ../../content/administration/odoo_sh/first_module.rst:449
+#: ../../content/administration/odoo_sh/first_module.rst:466
+#: ../../content/administration/odoo_sh/first_module.rst:478
 msgid "Add"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:351
+#: ../../content/administration/odoo_sh/first_module.rst:348
 msgid "These changes alter the database structure by adding a column in a table, and modify a view stored in database."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:354
+#: ../../content/administration/odoo_sh/first_module.rst:351
 msgid "In order to be applied in existing databases, such as your production database, these changes requires the module to be updated."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:357
+#: ../../content/administration/odoo_sh/first_module.rst:354
 msgid "If you would like the update to be performed automatically by the Odoo.sh platform when you push your changes, increase your module version in its manifest."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:360
+#: ../../content/administration/odoo_sh/first_module.rst:357
 msgid "Open the module manifest *__manifest__.py*."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:368
-#: ../../content/administration/odoo_sh/first_module.rst:507
+#: ../../content/administration/odoo_sh/first_module.rst:365
+#: ../../content/administration/odoo_sh/first_module.rst:504
 msgid "with"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:374
+#: ../../content/administration/odoo_sh/first_module.rst:371
 msgid "The platform will detect the change of version and trigger the update of the module upon the new revision deployment."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:377
+#: ../../content/administration/odoo_sh/first_module.rst:374
 msgid "Browse to your Git folder."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:379
+#: ../../content/administration/odoo_sh/first_module.rst:376
 msgid "Then, from an Odoo.sh terminal:"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:391
+#: ../../content/administration/odoo_sh/first_module.rst:388
 msgid "Then, stage your changes to be committed"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:403
+#: ../../content/administration/odoo_sh/first_module.rst:400
 msgid "Push your changes:"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:405
+#: ../../content/administration/odoo_sh/first_module.rst:402
 msgid "From an Odoo.sh terminal:"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:417
+#: ../../content/administration/odoo_sh/first_module.rst:414
 msgid "The platform will then create a new build for the branch *feature-1*."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:422
+#: ../../content/administration/odoo_sh/first_module.rst:419
 msgid "Once you tested your changes, you can merge your changes in the production branch, for instance by drag-and-dropping the branch on the production branch in the Odoo.sh interface. As you increased the module version in the manifest, the platform will update the module automatically and your new field will be directly available. Otherwise you can manually update the module within the apps list."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:428
+#: ../../content/administration/odoo_sh/first_module.rst:425
 msgid "Use an external Python library"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:430
+#: ../../content/administration/odoo_sh/first_module.rst:427
 msgid "If you would like to use an external Python library which is not installed by default, you can define a *requirements.txt* file listing the external libraries your modules depends on."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:434
+#: ../../content/administration/odoo_sh/first_module.rst:431
 msgid "It is not possible to install or upgrade system packages on an Odoo.sh database (e.g., apt packages). However, under specific conditions, packages can be considered for installation. This also applies to **Python modules** requiring system packages for their compilation, and **third-party Odoo modules**."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:438
+#: ../../content/administration/odoo_sh/first_module.rst:435
 msgid "**PostgreSQL extensions** are not supported on Odoo.sh."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:439
+#: ../../content/administration/odoo_sh/first_module.rst:436
 msgid "For more information, consult our `FAQ <https://www.odoo.sh/faq#install_dependencies>`_."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:441
+#: ../../content/administration/odoo_sh/first_module.rst:438
 msgid "The platform will use this file to automatically install the Python libraries your project needs."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:443
+#: ../../content/administration/odoo_sh/first_module.rst:440
 msgid "The feature is explained in this section by using the `Unidecode library <https://pypi.python.org/pypi/Unidecode>`_ in your module."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:446
+#: ../../content/administration/odoo_sh/first_module.rst:443
 msgid "Create a file *requirements.txt* in the root folder of your repository"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:448
+#: ../../content/administration/odoo_sh/first_module.rst:445
 msgid "From the Odoo.sh editor, create and open the file ~/src/user/requirements.txt."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:450
+#: ../../content/administration/odoo_sh/first_module.rst:447
 msgid "Or, from your computer, create and open the file ~/src/odoo-addons/requirements.txt."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:458
+#: ../../content/administration/odoo_sh/first_module.rst:455
 msgid "Then use the library in your module, for instance to remove accents from characters in the name field of your model."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:461
+#: ../../content/administration/odoo_sh/first_module.rst:458
 msgid "Open the file *models/models.py*."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:463
+#: ../../content/administration/odoo_sh/first_module.rst:460
 msgid "Before"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:497
+#: ../../content/administration/odoo_sh/first_module.rst:494
 msgid "Adding a Python dependency requires a module version increase for the platform to install it."
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:499
+#: ../../content/administration/odoo_sh/first_module.rst:496
 msgid "Edit the module manifest *__manifest__.py*"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:513
+#: ../../content/administration/odoo_sh/first_module.rst:510
 msgid "Stage and commit your changes:"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:521
+#: ../../content/administration/odoo_sh/first_module.rst:518
 msgid "Then, push your changes:"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:523
+#: ../../content/administration/odoo_sh/first_module.rst:520
 msgid "In an Odoo.sh terminal:"
 msgstr ""

-#: ../../content/administration/odoo_sh/first_module.rst:529
+#: ../../content/administration/odoo_sh/first_module.rst:526
 msgid "In your computer terminal:"
 msgstr ""

@@ -1987,7 +1985,7 @@ msgid "You can open multiple tabs and drag and drop them to arrange the layout a
 msgstr ""

 #: ../../content/administration/odoo_sh/getting_started/branches.rst:292
-msgid ":doc:`Online editor documentation <online-editor>`."
+msgid ":doc:`Online editor documentation <online_editor>`."
 msgstr ""

 #: ../../content/administration/odoo_sh/getting_started/branches.rst:297
@@ -3080,164 +3078,200 @@ msgstr ""
 msgid "Refer to the :doc:`database registration documentation <../../on_premise>` for step-by-step instructions."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6
-msgid "Online Editor"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:3
+msgid "Online editor"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11
-msgid "The online editor allows you to edit the source code of your builds from a web browser. It also gives you the possibility to open terminals, Python consoles, Odoo Shell consoles and `Notebooks <https://jupyterlab.readthedocs.io/en/stable/user/notebook.html>`_."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:5
+msgid "The :guilabel:`Online Editor` view allows editing the source code of your builds from a web browser. It also gives you the possibility to open terminals, Python consoles, Odoo shell consoles, and `Jupyter Notebooks <https://jupyterlab.readthedocs.io/en/stable/user/notebook.html>`_."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18
-msgid "You can access the editor of a build through :ref:`the branches tabs <odoo-sh/branches/tabs>`, :ref:`the builds dropdown menu <odoo-sh/builds/stages/features>` or by adding */odoo-sh/editor* to your build domain name (e.g. *https://odoo-addons-master-1.dev.odoo.com/odoo-sh/editor*)."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:None
+msgid "Overview of the online editor"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25
-msgid "Edit the source code"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:12
+msgid "You can access the editor of a build through :ref:`the branches tab <odoo-sh/branches/tabs>`, :ref:`the builds dropdown menu <odoo-sh/builds/stages/features>`, or by adding `/odoo-sh/editor` to the build's URL (e.g., `https://odoo-addons-master-1.dev.odoo.com/odoo-sh/editor`)."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27
-msgid "The working directory is composed of the following folders:"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:19
+msgid "Editing the source code"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49
-msgid "You can edit the source code (files under */src*) in development and staging builds."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:21
+msgid "The working directory is composed of the following:"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52
-msgid "Your changes won't be propagated to a new build, you must commit them in your source code if you want to make them persist."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:43
+msgid "You can edit the source code (files under `/src`) of development and staging builds. For production builds, the source code is read-only, because applying local changes on a production server is not a good practice."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56
-msgid "For production builds, the source code is read-only, because applying local changes on a production server is not a good practice."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:48
+msgid "Your changes won't be propagated to new builds. It is necessary to :ref:`commit them to the source code <odoo-sh/editor/commit>` if you want them to persist."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59
-msgid "The source code of your Github repository is located under */src/user*,"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:50
+msgid "The source code of your GitHub repository is located under `/src/user`."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60
-msgid "The source code of Odoo is located under"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:51
+msgid "The source code of Odoo is located under:"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62
-msgid "*/src/odoo* (`odoo/odoo <https://github.com/odoo/odoo>`_),"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:53
+msgid "`/src/odoo` (`<https://github.com/odoo/odoo>`_)"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63
-msgid "*/src/enterprise* (`odoo/enterprise <https://github.com/odoo/enterprise>`_),"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:54
+msgid "`/src/enterprise` (`<https://github.com/odoo/enterprise>`_)"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64
-msgid "*/src/themes* (`odoo/design-themes <https://github.com/odoo/design-themes>`_)."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:55
+msgid "`/src/themes` (`<https://github.com/odoo/design-themes>`_)"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66
-msgid "To open a file in the editor, just double-click on it in the file browser panel on the left."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:57
+msgid "To open a file in the editor, double-click it in the file browser panel. You can then edit the file. To save your changes, go to :menuselection:`File --> Save` or use the :kbd:`Ctrl+S` keyboard shortcut."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71
-msgid "You can then begin to make your changes. You can save your changes with the menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` shortcut."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:61
+msgid "If you save a Python file in your Odoo server's addons path, Odoo will detect it and reload automatically, meaning your changes are immediately visible."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77
-msgid "If you save a Python file which is under your Odoo server addons path, Odoo will detect it and reload automatically so your changes are reflected immediately, without having to restart the server manually."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:None
+msgid "Change to a Python file being immediately visible"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84
-msgid "However, if the change is a data stored in database, such as the label of a field, or a view, you have to update the according module to apply the change. You can update the module of the currently opened file by using the menu :menuselection:`Odoo --> Update current module`. Note that the file considered as currently opened is the file focused in the text editor, not the file highlighted in the file browser."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:67
+msgid "However, if your changes are stored in the database, such as a field's label or a view, it is necessary to update the related module to apply the changes. To update the module of the currently1 open file, go to :menuselection:`Odoo --> Update current module`."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93
-msgid "You can also open a terminal and execute the command:"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:None
+msgid "Using the editor to update the current module"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102
-msgid "Commit & Push your changes"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:75
+msgid "You can also execute the following command in a terminal to update a module:"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104
-msgid "You have the possibility to commit and push your changes to your Github repository."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:84
+msgid "Committing and pushing changes"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106
-msgid "Open a terminal (:menuselection:`File --> New --> Terminal`),"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:86
+msgid "To commit and push changes to your GitHub repository:"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107
-msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`,"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:88
+msgid "Open a terminal by going to :menuselection:`File --> New --> Terminal`."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108
-msgid "Stage your changes using :code:`git add`,"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:89
+msgid "Change the directory to `~/src/user`."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109
-msgid "Commit your changes using :code:`git commit`,"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:95
+msgid "State your identity."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110
-msgid "Push your changes using :code:`git push https HEAD:<branch>`."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:101
+msgid "Stage your changes."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112
-msgid "In this last command,"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:107
+msgid "Commit your changes."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114
-msgid "*https* is the name of your *HTTPS* Github remote repository (e.g. https://github.com/username/repository.git),"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:113
+msgid "Push your changes."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116
-msgid "HEAD is the reference to the latest revision you committed,"
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:119
+msgid "In this command:"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117
-msgid "<branch> must be replaced by the name of the branch to which you want to push the changes, most-likely the current branch if you work in a development build."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:121
+msgid "`https` is the name of your *HTTPS* GitHub remote repository (e.g., `https://github.com/username/repository.git`)."
 msgstr ""

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

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137
-msgid "The Git source folder *~/src/user* is not checked out on a branch but rather on a detached revision: This is because builds work on specific revisions rather than branches. In other words, this means you can have multiple builds on the same branch, but on different revisions."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:124
+msgid "`<branch>` must be replaced by the name of the branch to which you want to push the changes, most likely the current branch if you work on a development build."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141
-msgid "Once your changes are pushed, according to your :ref:`branch push behavior <odoo-sh/branches/tabs/settings>`, a new build may be created. You can continue to work in the editor you pushed from, as it will have the same revision as the new build that was created, but always make sure to be in an editor of a build using the latest revision of your branch."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:127
+msgid "You will be prompted to input your GitHub username and password. After inputting your credentials, press enter."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:None
+msgid "The commands to commit and push changes"
+msgstr ""
+
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:134
+msgid "If you activate two-factor authentication for your GitHub account, you can create a `personal access token <https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token>`_ and use it as a password. `Granting the repo permission <https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/repository-access-and-collaboration/inviting-collaborators-to-a-personal-repository>`_ suffices."
+msgstr ""
+
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:140
+msgid "It is not possible to authenticate yourself using SSH, as your private SSH key is not hosted in your build containers for security reasons, nor forwarded through an SSH agent, as you access the editor through a web browser."
+msgstr ""
+
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:143
+msgid "The source folder `~/src/user` is not checked out on a branch but rather on a detached revision. This is because builds work on specific revisions rather than branches, meaning you can have multiple builds on the same branch, but on different revisions."
+msgstr ""
+
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:147
+msgid "Once your changes are pushed, according to your :ref:`branch push behavior <odoo-sh/branches/tabs/settings>`, a new build may be created. You can continue to work in the editor you pushed from, as it will have the same revision as the new build that was created. However, always make sure to be in the editor of a build using the latest revision of your branch."
+msgstr ""
+
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:155
 msgid "Consoles"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150
-msgid "You can open Python consoles, which are `IPython interactive shells <https://ipython.readthedocs.io/en/stable/interactive/tutorial.html>`_. One of the most interesting addition to use a Python console rather than a IPython shell within a terminal is the `rich display <https://ipython.readthedocs.io/en/stable/config/integrating.html#rich-display>`_ capabilities. Thanks to this, you will be able to display objects in HTML."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:157
+msgid "You can open Python consoles, which are `IPython interactive shells <https://ipython.readthedocs.io/en/stable/interactive/tutorial.html>`_. Using these Python consoles (rather than IPython shells within a terminal) allows you to utilize their `rich display capabilities <https://ipython.readthedocs.io/en/stable/config/integrating.html#rich-display>`_ to display objects in HTML."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158
-msgid "You can for instance display cells of a CSV file using `pandas <https://pandas.pydata.org/pandas-docs/stable/tutorials.html>`_."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:164
+msgid "The :code:`Pretty` class displays lists in a legible way."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164
-msgid "You can also open an Odoo Shell console to play around with the Odoo registry and model methods of your database. You can also directly read or write on your records."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:0
+msgid "Pretty class example"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169
-msgid "In an Odoo Console, transactions are automatically committed. This means, for instance, that changes in records are applied effectively in the database. If you change the name of a user, the name of the user is changed in your database as well. You therefore should use Odoo consoles carefully on production databases."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:170
+msgid "Using `pandas <https://pandas.pydata.org/pandas-docs/stable/getting_started/tutorials.html>`_ you can display:"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174
-msgid "You can use *env* to invoke models of your database registry, e.g. :code:`env['res.users']`."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:173
+msgid "Cells of a CSV file"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184
-msgid "The class :code:`Pretty` gives you the possibility to easily display lists and dicts in a pretty way, using the `rich display <https://ipython.readthedocs.io/en/stable/config/integrating.html#rich-display>`_ mentioned above."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:0
+msgid "pandas CSV example"
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192
-msgid "You can also use `pandas <https://pandas.pydata.org/pandas-docs/stable/tutorials.html>`_ to display graphs."
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:178
+msgid "Graphs"
+msgstr ""
+
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:0
+msgid "pandas graph example"
+msgstr ""
+
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:183
+msgid "You can open Odoo shell consoles to experiment with the Odoo registry and model methods of your database. You can also read or write directly on your records."
+msgstr ""
+
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:187
+msgid "In an Odoo shell console, transactions are automatically committed. This means that changes made to records are applied to the database. For example, if you change a user's name, it will be updated in your database as well. Therefore, use Odoo shell consoles carefully on production databases."
+msgstr ""
+
+#: ../../content/administration/odoo_sh/getting_started/online_editor.rst:192
+msgid "You can use `env` to invoke models of your database registry, e.g., :code:`env['res.users']`."
 msgstr ""

 #: ../../content/administration/odoo_sh/getting_started/settings.rst:5
@@ -3428,7 +3462,6 @@ msgstr ""
 #: ../../content/administration/odoo_sh/getting_started/settings.rst:95
 #: ../../content/administration/odoo_sh/getting_started/settings.rst:145
 #: ../../content/administration/odoo_sh/getting_started/settings.rst:195
-#: ../../content/administration/odoo_sh/getting_started/status.rst:3
 msgid "Status"
 msgstr ""

@@ -3671,10 +3704,6 @@ msgstr ""
 msgid "For any other issue, contact `Odoo Support <https://www.odoo.com/help>`_."
 msgstr ""

-#: ../../content/administration/odoo_sh/getting_started/status.rst:8
-msgid "The status page shows statistics regarding the servers your project uses. It includes the servers availability."
-msgstr ""
-
 #: ../../content/administration/on_premise.rst:8
 msgid "Register a database"
 msgstr ""
--- a/locale/sources/finance.pot
+++ b/locale/sources/finance.pot
--- a/locale/sources/general.pot
+++ b/locale/sources/general.pot
--- a/locale/sources/hr.pot
+++ b/locale/sources/hr.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo master\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-12-20 18:30+0000\n"
+"POT-Creation-Date: 2026-01-07 14:06+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"
@@ -1167,7 +1167,6 @@ msgid "To view the specific details for an employee's skill types, expand the :g
 msgstr ""

 #: ../../content/applications/hr/appraisals/skills_evolution.rst:43
-#: ../../content/applications/hr/attendances.rst:239
 msgid ":guilabel:`Employee`: the name of the employee."
 msgstr ""

@@ -1309,58 +1308,58 @@ msgid "Attendances"
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:7
-msgid "Odoo's **Attendances** application functions as a time clock. Employees are able to check in and out of work using a :ref:`dedicated device in kiosk mode <attendances/kiosk-mode-entry>`, while users are also able to check in and out of work :ref:`directly from the database <attendances/check-in>`. Managers can see who is available at any given time, create reports to see everyone's hours, and gain insights on which employees are working overtime, or checking out of work earlier than expected."
+msgid "Odoo's **Attendances** application functions as a time clock. Employees are able to check in and out of work using a :ref:`dedicated device in kiosk mode <attendances/kiosk-mode-entry>`, while users are also able to check in and out of work :ref:`directly from the database <attendances/check-in>`. Managers can see who is available at any given time, create reports to see everyone's hours, and gain insights on which employees are working overtime or checking out of work earlier than expected."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:17
+#: ../../content/applications/hr/attendances.rst:16
 msgid "Access rights"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:19
+#: ../../content/applications/hr/attendances.rst:18
 msgid "Understanding access rights is essential to navigating the **Attendances** application."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:21
+#: ../../content/applications/hr/attendances.rst:20
 msgid "Every user in the database is able to check in and out directly from the database, without needing access to the **Attendances** app. Additionally, all users can access their own attendance records from their employee form in the **Employees** app."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:25
-msgid "Access to both the **Attendances** application, and the various features within the application is determined by access rights."
+#: ../../content/applications/hr/attendances.rst:24
+msgid "Access to both the **Attendances** application and the various features within the application is determined by access rights."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:28
+#: ../../content/applications/hr/attendances.rst:27
 msgid "To see what access rights a user has, navigate to the :menuselection:`Settings app --> Users & Companies --> Users`, and click on an individual user. The :guilabel:`Access Rights` tab is visible by default. Scroll down to the :guilabel:`HUMAN RESOURCES` section to view the settings. For the :guilabel:`Attendances` field, the options are either to leave the field blank or select :guilabel:`Administrator`."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:34
+#: ../../content/applications/hr/attendances.rst:33
 msgid "If the :guilabel:`Administrator` option is selected, the user has full access to the entire **Attendances** application, with no restrictions. They can view all employee attendance records, enter *Kiosk Mode* from the application, access all reporting metrics, and make modifications to the settings. If left blank, the user does **not** have access to the **Attendances** application."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:40
+#: ../../content/applications/hr/attendances.rst:39
 msgid "If a user does **not** have :guilabel:`Administrator` rights for the **Attendances** app, they are **not** able to open the app, even though it appears on the main database dashboard. An :guilabel:`Access Error` pop-up message appears, stating:"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:44
+#: ../../content/applications/hr/attendances.rst:43
 msgid "`You do not have enough rights to access the fields \"attendance_manager_id\" on Employee (hr.employee). Please contact your system administrator.`"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:47
+#: ../../content/applications/hr/attendances.rst:46
 msgid "Users who cannot access the **Attendances** app can still :doc:`check in and check out <../hr/attendances/check_in_check_out>` of work within the database, using the :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-circle` :guilabel:`(green circle)` that are always available at the top of the database."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:55
+#: ../../content/applications/hr/attendances.rst:54
 msgid "Approvers"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:57
+#: ../../content/applications/hr/attendances.rst:56
 msgid "An approver is a user assigned to review and manage an employee's attendance records. An approver is typically a manager, though that is not required. Approvers without administrative rights can access and modify attendance records **only** for the employees they are assigned to. This is the only exception where non-admin users can view records in the **Attendances** app."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:62
-msgid "To view who the attendances approver for an employee is, navigate to the :menuselection:`Employees application` and click on the specific employee. Click on the :guilabel:`Work Information` tab, scroll to the :guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. The person selected is able to view that employees' attendance records, both on the **Attendances** application dashboard as well as in the attendance reports, and make modifications to their records."
+#: ../../content/applications/hr/attendances.rst:61
+msgid "To view who the attendance approver for an employee is, navigate to the :menuselection:`Employees application` and click on the specific employee. Click on the :guilabel:`Work Information` tab, scroll to the :guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. The person selected is able to view that employee's attendance records, both on the **Attendances** application dashboard as well as in the attendance reports, and make modifications to their records."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:69
+#: ../../content/applications/hr/attendances.rst:68
 #: ../../content/applications/hr/attendances/kiosks.rst:22
 #: ../../content/applications/hr/frontdesk.rst:15
 #: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:840
@@ -1372,79 +1371,83 @@ msgstr ""
 msgid "Configuration"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:71
+#: ../../content/applications/hr/attendances.rst:70
 msgid "Few configurations are needed in the **Attendances** app. Determining how employees check in and out, defining how the kiosks function, and determining how extra hours are computed are all set in the Configuration menu. Navigate to the :menuselection:`Attendances application --> Configuration` to access the configuration menu."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:77
-msgid "Any configuration item with an :icon:`fa-building-o` :guilabel:`(building)` icon is a company-specific configuration. Items without an :icon:`fa-building-o` :guilabel:`(building)` icon apply to all companies within the database."
+#: ../../content/applications/hr/attendances.rst:76
+msgid "Any configuration item with a :icon:`fa-building-o` :guilabel:`(building)` icon is a company-specific configuration. Items without an :icon:`fa-building-o` :guilabel:`(building)` icon apply to all companies within the database."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:84
+#: ../../content/applications/hr/attendances.rst:83
 msgid "Modes"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:86
-msgid ":guilabel:`Attendances from Backend` :icon:`fa-building-o`: activate this feature to allow users to check in and out directly from the Odoo database. If this is not activated, users must use a kiosk to check in and out of work."
+#: ../../content/applications/hr/attendances.rst:85
+msgid ":guilabel:`Attendances from Backend` :icon:`fa-building-o`: Activate this feature to allow users to check in and out directly from the Odoo database. If this is not activated, users must use a kiosk to check in and out of work."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:89
-msgid ":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: activate this feature to automatically check out employees according to their working schedule, after a buffer of time has passed."
+#: ../../content/applications/hr/attendances.rst:88
+msgid ":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: Activate this feature to automatically check out employees according to their working schedule, after a buffer of time has passed."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:91
-msgid ":guilabel:`Tolerance`: this field appears only when the :guilabel:`Automatic Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of time, in hours, that must elapse after an employee's working hours have ended, before they are automatically checked out."
+#: ../../content/applications/hr/attendances.rst:90
+msgid ":guilabel:`Tolerance`: This field appears only when the :guilabel:`Automatic Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of time, in hours, that must elapse after an employee's working hours have ended, before they are automatically checked out."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:96
-msgid "With the :guilabel:`Automatic Check-Out` option enabled, and the :guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at 9:00 AM, and forgets to check-out at 5:00 PM. At 7:00 PM, they are automaticlaly checked out."
+#: ../../content/applications/hr/attendances.rst:95
+msgid "With the :guilabel:`Automatic Check-Out` option enabled, and the :guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at 9:00 AM and forgets to check out at 5:00 PM. At 7:00 PM, they are automatically checked out."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:100
-msgid ":guilabel:`Absence Management` :icon:`fa-building-o`: activate this feature to log any absences that are not associated with a time off request, such as vacation time or sick time, on the attendances report."
+#: ../../content/applications/hr/attendances.rst:99
+msgid ":guilabel:`Absence Management` :icon:`fa-building-o`: Activate this feature to log any absences that are not associated with a time off request, such as vacation time or sick time, on the :doc:`attendance report <attendances/attendance_reporting>`."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:105
+#: ../../content/applications/hr/attendances.rst:104
 msgid "Extra Hours"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:107
+#: ../../content/applications/hr/attendances.rst:106
 msgid "This section specifies how extra time (sometimes referred to as *overtime*) is calculated, including when extra time is counted and what time is not logged."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:110
-msgid ":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in minutes, that is **not** counted towards an employee's overtime. When an employee checks out, and the extra time logged is below the specified minutes, the extra time is **not** counted as overtime for the employee."
+#: ../../content/applications/hr/attendances.rst:109
+msgid ":guilabel:`Tolerance Time In Favor Of Company`: Enter the amount of time, in minutes, that is **not** counted towards an employee's overtime. When an employee checks out, and the extra time logged is below the specified minutes, the extra time is **not** counted as overtime for the employee. When an employee checks out, and the extra time logged is more than the specified minutes, the extra time **is** counted as overtime for the employee."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:114
-msgid ":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, in minutes, that an employee is given, that does **not** adversely affect their attendance if they log less time than their working hours. When an employee checks out, and the total time logged for the day is less than their specified working hours and less than this specified grace period, they are **not** penalized for their reduced hours."
+#: ../../content/applications/hr/attendances.rst:116
+msgid "A company sets the :guilabel:`Tolerance Time In Favor Of Company` to `15` minutes, and the working hours for the entire company are set from 9:00 AM to 5:00 PM."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:121
-msgid "A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and the working hours for the entire company are set from 9:00 AM to 5:00 PM."
+#: ../../content/applications/hr/attendances.rst:119
+msgid "An employee checks in at 9:00 AM. If the employee checks out at 5:14 PM, the extra 14 minutes are **not** counted towards their overtime. If the employee checks out at 5:17 PM, they earn 17 minutes of overtime."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:124
-msgid "If an employee checks in at 9:00 AM, and checks out at 5:14 PM, the extra 14 minutes are **not** counted towards their overtime."
+#: ../../content/applications/hr/attendances.rst:123
+msgid ":guilabel:`Tolerance Time In Favor Of Employee`: Enter the amount of time, in minutes, that an employee is given, which does **not** adversely affect their attendance if they log less time than their working hours. When an employee checks out, and the total time logged for the day is less than their specified working hours and less than this specified grace period, they are **not** penalized for their reduced hours. When an employee checks out, and the total time logged for the day is less than their specified working hours and more than this specified grace period, they **are** penalized for their reduced hours."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:127
-msgid "If an employee checks in at 9:05 AM, and checks out at 4:55 PM, even though they logged a total of 10 minutes less than their full working hours, they are **not** penalized for this discrepancy."
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:131
-msgid ":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: tick either the radio button next to :guilabel:`Automatically Approved` to have all extra time automatically approved, or :guilabel:`Approved by Manager` if all extra time should be reviewed and approved by a manager."
+#: ../../content/applications/hr/attendances.rst:132
+msgid "A company sets the :guilabel:`Tolerance Time In Favor Of Employee` fields to `15` minutes, and the working hours for the entire company are set from 9:00 AM to 5:00 PM."
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:135
-msgid ":guilabel:`Display Extra Hours`: activate this box to display the extra hours logged by an employee when they check out with a kiosk, or when a user checks out in the database."
+msgid "An employee checks in at 9:05 AM. If the employee checks out at 4:55 PM, even though they logged a total of 10 minutes less than their full working hours, they are **not** penalized for this discrepancy, and they are logged as working a full eight-hour day. If the employee checks out at 4:40 PM, they **are** penalized, and they are logged as only working 7 hours and 35 minutes."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:139
+#: ../../content/applications/hr/attendances.rst:141
+msgid ":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: Click on either the radio button next to :guilabel:`Automatically Approved` to have all extra time automatically approved, or :guilabel:`Approved by Manager` if all extra time should be reviewed and approved by a manager."
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:145
+msgid ":guilabel:`Display Extra Hours`: Activate this box to display the extra hours logged by an employee when they check out with a kiosk, or when a user checks out in the database."
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:149
 msgid "Approved extra hours can be :ref:`deducted from an approved time off request <time_off/deduct-extra-hours>`."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:143
+#: ../../content/applications/hr/attendances.rst:153
 #: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:11
 #: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:231
 #: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:428
@@ -1454,11 +1457,11 @@ msgstr ""
 msgid "Overview"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:145
-msgid "When entering the **Attendances** application, the :guilabel:`Overview` dashboard is presented, containing all the user's check in and check out information. If the user has the required :ref:`access rights <attendances/access-rights>` or is an :ref:`approver <attendances/approvers>` for specific employees, those employeess' check-in and check-out information also appears on the :guilabel:`Overview` dashboard."
+#: ../../content/applications/hr/attendances.rst:155
+msgid "When entering the **Attendances** application, the :guilabel:`Overview` dashboard is presented, containing all the user's check in and check out information. If the user has the required :ref:`access rights <attendances/access-rights>` or is an :ref:`approver <attendances/approvers>` for specific employees, those employees' check-in and check-out information also appears on the :guilabel:`Overview` dashboard."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:151
+#: ../../content/applications/hr/attendances.rst:161
 msgid "The **Attendance** dashboard allows switching between :icon:`fa-tasks` :guilabel:`(Gantt)` and :icon:`oi-view-list` :guilabel:`(List)` views, and selecting a period to analyze. The current period is automatically highlighted in yellow for real-time attendance records, while the :icon:`fa-crosshairs` :guilabel:`(Focus Today)` button instantly returns the dashboard to the present date."
 msgstr ""

@@ -1467,241 +1470,245 @@ msgid "The overview dashboard presenting the information for the week, with the
 "highlighted."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:162
+#: ../../content/applications/hr/attendances.rst:172
 msgid "Any entries that have errors appear in red, indicating they need to be resolved by a user with the proper :ref:`access rights <attendances/access-rights>` and/or are :ref:`approvers <attendances/approvers>` for the employees with the errors."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:169
+#: ../../content/applications/hr/attendances.rst:179
 msgid "Filters and groups"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:171
-msgid "Sometimes, attendance officers and managers need to view specific records, such as all automatic checkouts to determine which employees chronically forget to check-out, or by department, to determine which team is working the most overtime."
+#: ../../content/applications/hr/attendances.rst:181
+msgid "Sometimes, attendance officers and managers need to view specific records, such as all automatic checkouts, to determine which employees chronically forget to check out, or by department, to determine which team is working the most overtime."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:175
-msgid "For these cases, use the search bar to select a :icon:`fa-filter` :guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine these both to present the desired information."
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:179
-msgid ":doc:`../essentials/search`"
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:182
-msgid "High-value filters"
+#: ../../content/applications/hr/attendances.rst:185
+msgid "For these cases, use the search bar to select a :icon:`fa-filter` :guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine both to present the desired information."
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:189
-msgid "Filter"
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:190
-msgid "Common use case"
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:191
-msgid "At Work"
+msgid ":doc:`../essentials/search`"
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:192
+msgid "High-value filters"
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:199
+msgid "Filter"
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:200
+msgid "Common use case"
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:201
+msgid "At Work"
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:202
 msgid "Verify employees still on-site before shutting down the building for the night, or to perform a head count."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:194
+#: ../../content/applications/hr/attendances.rst:204
 #: ../../content/applications/hr/lunch/orders.rst:86
 msgid "Errors"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:195
+#: ../../content/applications/hr/attendances.rst:205
 msgid "View all errors to correct them prior to payroll processing."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:196
+#: ../../content/applications/hr/attendances.rst:206
 msgid "Automatically Checked-Out"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:197
+#: ../../content/applications/hr/attendances.rst:207
 msgid "Perform an audit to determine employees who chronically forget to check-out of work."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:198
+#: ../../content/applications/hr/attendances.rst:208
 msgid "Date"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:199
+#: ../../content/applications/hr/attendances.rst:209
 msgid "Limit results to a specific pay-period or audit window."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:200
+#: ../../content/applications/hr/attendances.rst:210
 msgid "Active/Archived Employees"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:201
+#: ../../content/applications/hr/attendances.rst:211
 msgid "Switch between current staff and former employees when auditing historical data."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:204
+#: ../../content/applications/hr/attendances.rst:214
 msgid "Insightful groupings"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:211
+#: ../../content/applications/hr/attendances.rst:221
 msgid "Group by"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:212
+#: ../../content/applications/hr/attendances.rst:222
 msgid "When it helps"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:213
+#: ../../content/applications/hr/attendances.rst:223
 #: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:977
 msgid "Employee"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:214
+#: ../../content/applications/hr/attendances.rst:224
 msgid "Review individual attendance records during a 1:1 meeting."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:215
+#: ../../content/applications/hr/attendances.rst:225
 msgid "Department"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:216
+#: ../../content/applications/hr/attendances.rst:226
 msgid "Compare staffing levels and working hours to determine over-working and under-working teams."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:217
+#: ../../content/applications/hr/attendances.rst:227
 msgid "Manager"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:218
+#: ../../content/applications/hr/attendances.rst:228
 msgid "Determine where attendance follow-up questions can be directed to for an employee."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:219
+#: ../../content/applications/hr/attendances.rst:229
 msgid "Method"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:220
+#: ../../content/applications/hr/attendances.rst:230
 msgid "Spot trends in attendance methods to potentially resolve hardware issues."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:221
+#: ../../content/applications/hr/attendances.rst:231
 msgid "Date (Day/Week/Month)"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:222
+#: ../../content/applications/hr/attendances.rst:232
 msgid "Identify absenteeism spikes or seasonal patterns."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:227
+#: ../../content/applications/hr/attendances.rst:237
 msgid "Attendance log details"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:229
-msgid "Odoo records both the time and location for every check-in and check-out, with fields varying by the method used. These detailed attendance logs can confirm where an employee was on any given work day. This can be useful for companies with hybrid working schedules, who may need to perform audits to ensure proper compliance."
+#: ../../content/applications/hr/attendances.rst:239
+msgid "Odoo records both the time and location for every check-in and check-out, with fields varying by the method used. These detailed attendance logs can confirm where an employee was on any given workday. This can be useful for companies with hybrid working schedules, who may need to perform audits to ensure proper compliance."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:234
+#: ../../content/applications/hr/attendances.rst:244
 msgid "The detailed attendance log contains the following information:"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:237
+#: ../../content/applications/hr/attendances.rst:247
 msgid "Main details"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:240
-msgid ":guilabel:`Check In`: the date and time the employee checked in."
+#: ../../content/applications/hr/attendances.rst:249
+msgid ":guilabel:`Employee`: The name of the employee."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:241
-msgid ":guilabel:`Check Out`: the date and time the employee checked out. This **only** appears if the employee has checked out."
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:243
-msgid ":guilabel:`Worked Time`: the total amount of time the employee logged for the day, across multiple check-ins and outs. In an hour and minute format (HH:MM)."
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:245
-msgid ":guilabel:`Worked Extra Hours`: unpaid overtime hours worked beyond the expected working schedule (shows **only** when present for the employee)."
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:247
-msgid ":guilabel:`Extra Hours`: approved overtime (the :guilabel:`Worked Time` minus the approved :guilabel:`Worked Extra Hours`."
+#: ../../content/applications/hr/attendances.rst:250
+msgid ":guilabel:`Check In`: The date and time the employee checked in."
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:251
-msgid "Check in/check out details"
+msgid ":guilabel:`Check Out`: The date and time the employee checked out. This **only** appears if the employee has checked out."
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:253
-msgid "The following information appears for both the :guilabel:`Check In` and :guilabel:`Check Out` sections."
+msgid ":guilabel:`Worked Time`: The total amount of time the employee logged for the day, across multiple check-ins and outs, in an hour and minute format (HH:MM)."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:256
-msgid ":guilabel:`Mode`: attendance submission method. Can be :ref:`Systray <attendances/check-in>`, :ref:`Kiosk <attendances/kiosk-mode-entry>`, or :guilabel:`Manual` entry."
+#: ../../content/applications/hr/attendances.rst:255
+msgid ":guilabel:`Worked Extra Hours`: Unpaid overtime hours worked beyond the expected working schedule (shows **only** when present for the employee)."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:258
-msgid ":guilabel:`IP Address`: the device's IP address used to log in or out."
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:259
-msgid ":guilabel:`Browser`: the web browser the employee used to log in or out."
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:260
-msgid ":guilabel:`Localisation`: the city and country associated with the computer's IP address."
+#: ../../content/applications/hr/attendances.rst:257
+msgid ":guilabel:`Extra Hours`: Approved overtime (the :guilabel:`Worked Time` minus the approved :guilabel:`Worked Extra Hours`."
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:261
-msgid ":guilabel:`GPS Coordinates`: the specific coordinates when the user logged in or out. To view the specific coordinates on a map, click the :icon:`oi-arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS Coordinates`. This opens a map in a new browser tab, with the specific location pointed out."
+msgid "Check in/check out details"
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:263
+msgid "The following information appears for both the :guilabel:`Check In` and :guilabel:`Check Out` sections."
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:266
+msgid ":guilabel:`Mode`: Attendance submission method. Can be :ref:`Systray <attendances/check-in>`, :ref:`Kiosk <attendances/kiosk-mode-entry>`, or :guilabel:`Manual` entry."
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:268
+msgid ":guilabel:`IP Address`: The device's IP address used to log in or out."
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:269
+msgid ":guilabel:`Browser`: The web browser the employee used to log in or out."
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:270
+msgid ":guilabel:`Localisation`: The city and country associated with the computer's IP address."
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:271
+msgid ":guilabel:`GPS Coordinates`: The specific coordinates when the user logged in or out. To view the specific coordinates on a map, click the :icon:`oi-arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS Coordinates`. This opens a map in a new browser tab, with the specific location pointed out."
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:None
 msgid "The detailed information for an attendance entry."
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:270
+#: ../../content/applications/hr/attendances.rst:280
 msgid "Attendance errors"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:272
-msgid "Entries that contain an error appear on the overview dashboard in red. In the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red background. If in the :icon:`oi-view-list` :guilabel:`(List)` view, the entry text appears in red."
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:276
-msgid "An error occurs when an employee has checked in but not checked out within 24 hours, or when a single check-in period exceeds 16 hours."
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:279
-msgid "To fix the error, the attendance entry must be modified or deleted. Click on the entry to reveal a pop-up containing the details for that particular entry. To modify the :guilabel:`Check In` and/or :guilabel:`Check Out` information, click on the :guilabel:`Check In` or :guilabel:`Check Out` field and a calendar selector appears. Click on the desired date, then use the time selector beneath the calendar to select the specific time for the entry. When the information is correct, click :guilabel:`Apply.`"
+#: ../../content/applications/hr/attendances.rst:282
+msgid "Entries that contain an error appear on the overview dashboard in red. In the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red background; in the :icon:`oi-view-list` :guilabel:`(List)` view, the entry text appears in red."
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:286
-msgid "When all the information on the pop-up is correct, click :guilabel:`Save & Close`. When the entry no longer has an error, the entry appears in gray instead of red."
+msgid "An error occurs when an employee has checked in but not checked out within 24 hours, or when a single check-in period exceeds 16 hours."
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:289
-msgid "To delete an entry, click the red :guilabel:`Delete` button on the pop-up window instead of making modifications to the entry."
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:293
-msgid ":doc:`attendances/check_in_check_out`"
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:294
-msgid ":doc:`attendances/kiosks`"
-msgstr ""
-
-#: ../../content/applications/hr/attendances.rst:295
-msgid ":doc:`attendances/management`"
+msgid "To fix the error, the attendance entry must be modified or deleted. Click on the entry to reveal a pop-up containing the details for that particular entry. To modify the :guilabel:`Check In` and/or :guilabel:`Check Out` information, click on the :guilabel:`Check In` or :guilabel:`Check Out` field, and a calendar selector appears. Click on the desired date, then use the time selector beneath the calendar to select the specific time for the entry. When the information is correct, click :guilabel:`Apply.`"
 msgstr ""

 #: ../../content/applications/hr/attendances.rst:296
+msgid "When all the information on the pop-up is correct, click :guilabel:`Save & Close`. When the entry no longer has an error, the entry appears in gray instead of red."
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:299
+msgid "To delete an entry, click the red :guilabel:`Delete` button on the pop-up window instead of making modifications to the entry."
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:303
+msgid ":doc:`attendances/check_in_check_out`"
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:304
+msgid ":doc:`attendances/kiosks`"
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:305
+msgid ":doc:`attendances/management`"
+msgstr ""
+
+#: ../../content/applications/hr/attendances.rst:306
 msgid ":doc:`attendances/hardware`"
 msgstr ""

-#: ../../content/applications/hr/attendances.rst:297
+#: ../../content/applications/hr/attendances.rst:307
 msgid ":doc:`attendances/attendance_reporting`"
 msgstr ""

@@ -1931,6 +1938,7 @@ msgid "It is recommended to place kiosks on a secure stand, or mount them secure
 msgstr ""

 #: ../../content/applications/hr/attendances/hardware.rst:35
+#: ../../content/applications/hr/employees.rst:35
 #: ../../content/applications/hr/employees/badges.rst:3
 msgid "Badges"
 msgstr ""
@@ -2414,6 +2422,75 @@ msgstr ""
 msgid "Odoo **Employees** centralizes :doc:`personnel files <employees/new_employee>`, employment :doc:`contracts <payroll/contracts>`, and :doc:`departmental hierarchies <employees/departments>` in one system. Properly configuring its settings ensures the dashboard shows each employee's real-time attendance and work location—data that drives payroll accuracy, capacity planning, and compliance reporting."
 msgstr ""

+#: ../../content/applications/hr/employees.rst:15
+#: ../../content/applications/hr/employees/new_employee.rst:3
+msgid "New employees"
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:15
+msgid "Set up new employee records."
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:20
+#: ../../content/applications/hr/employees/departments.rst:3
+msgid "Departments"
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:20
+msgid "Create and manage the departments employees are a part of."
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:25
+#: ../../content/applications/hr/payroll/contracts.rst:3
+#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77
+#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52
+msgid "Contracts"
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:25
+msgid "Manage and create employee contracts."
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:30
+#: ../../content/applications/hr/employees/certifications.rst:3
+msgid "Certifications"
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:30
+msgid "Certify employees as subject matter experts with certifications."
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:35
+msgid "Grant badges to employees for performance and achievements."
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:40
+#: ../../content/applications/hr/employees/equipment.rst:3
+msgid "Equipment"
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:40
+msgid "Manage and track employee equipment."
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:45
+#: ../../content/applications/hr/employees/offboarding.rst:3
+msgid "Offboarding"
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:45
+msgid "Take care of employee records when collaboration ends."
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:50
+#: ../../content/applications/hr/employees/retention_report.rst:3
+msgid "Employee retention report"
+msgstr ""
+
+#: ../../content/applications/hr/employees.rst:50
+msgid "Gain insight to the retention rate for a company."
+msgstr ""
+
 #: ../../content/applications/hr/employees.rst:58
 #: ../../content/applications/hr/fleet/new_vehicle.rst:16
 #: ../../content/applications/hr/lunch.rst:19
@@ -2582,10 +2659,6 @@ msgstr ""
 msgid "The 'Reward Employee' field populated."
 msgstr ""

-#: ../../content/applications/hr/employees/certifications.rst:3
-msgid "Certifications"
-msgstr ""
-
 #: ../../content/applications/hr/employees/certifications.rst:5
 msgid "When jobs require specific knowledge, it is necessary to track employee certifications to ensure the necessary knowledge and certifications are in place."
 msgstr ""
@@ -2750,10 +2823,6 @@ msgstr ""
 msgid "This :guilabel:`ADD` button **only** appears on employee profiles that already have a certification."
 msgstr ""

-#: ../../content/applications/hr/employees/departments.rst:3
-msgid "Departments"
-msgstr ""
-
 #: ../../content/applications/hr/employees/departments.rst:5
 msgid "All employees in the **Employees** app fall under specific departments within a company."
 msgstr ""
@@ -2924,10 +2993,6 @@ msgstr ""
 msgid "The departments presented in a hierarchy view."
 msgstr ""

-#: ../../content/applications/hr/employees/equipment.rst:3
-msgid "Equipment"
-msgstr ""
-
 #: ../../content/applications/hr/employees/equipment.rst:5
 msgid "Many employees are given various items to use while they work, such as laptops, phones, and printers. Most companies track their equipment, to see who is using what, as well as having a record of important information regarding the equipment, such as serial numbers, warranty information, and maintenance history."
 msgstr ""
@@ -3028,10 +3093,6 @@ msgstr ""
 msgid "A duplicate equipment form with all the information filled out except the serial number."
 msgstr ""

-#: ../../content/applications/hr/employees/new_employee.rst:3
-msgid "New employees"
-msgstr ""
-
 #: ../../content/applications/hr/employees/new_employee.rst:5
 msgid "When a new employee is hired, the first step is to create a new employee record. This record is a centralized place where all important information about the employee is stored, including :ref:`general information <employees/general-info>`, :ref:`job history and skills <employees/resume>`, :ref:`various work information <employees/work-info-tab>`, :ref:`personal details <employees/private-info>`, :ref:`payroll-related information <employees/payroll>`, and various :ref:`settings <employees/hr-settings>` that affect integrations with other apps in the database."
 msgstr ""
@@ -3787,10 +3848,6 @@ msgstr ""
 msgid ":guilabel:`Badge ID`: click :guilabel:`Generate` at the end of the :guilabel:`Badge ID` line to create a badge number. Once generated, the badge number populates the :guilabel:`Badge ID` field, and :guilabel:`Generate` changes to :guilabel:`Print Badge`. Click :guilabel:`Print Badge` to create a PDF file of the employee's badge. The badge can be printed and used to log into a :abbr:`POS (point of sale)` system or :ref:`check-in <attendances/kiosk-mode-entry>` on an **Attendances** app kiosk."
 msgstr ""

-#: ../../content/applications/hr/employees/offboarding.rst:3
-msgid "Offboarding"
-msgstr ""
-
 #: ../../content/applications/hr/employees/offboarding.rst:5
 msgid "When an employee leaves the company, it is important to have an :ref:`offboarding plan <employees/offboarding>` to ensure all necessary steps are followed, such as returning equipment, revoking access to business systems, filling out HR forms, having an exit interview, and more. Depending on the company, there could be several different offboarding plans, configured for specific departments or divisions, that have different requirements and steps from the main offboarding plan."
 msgstr ""
@@ -4306,10 +4363,6 @@ msgstr ""
 msgid "All onboarding tasks scheduled in the chatter."
 msgstr ""

-#: ../../content/applications/hr/employees/retention_report.rst:3
-msgid "Employee retention report"
-msgstr ""
-
 #: ../../content/applications/hr/employees/retention_report.rst:5
 msgid "It is possible to determine the retention rate for a company by modifying an existing report."
 msgstr ""
@@ -7324,12 +7377,6 @@ msgstr ""
 msgid ":doc:`Commissions <../../sales/sales/commissions>`"
 msgstr ""

-#: ../../content/applications/hr/payroll/contracts.rst:3
-#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77
-#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52
-msgid "Contracts"
-msgstr ""
-
 #: ../../content/applications/hr/payroll/contracts.rst:5
 msgid "Every employee in Odoo is required to have a running contract in order to be paid. A contract outlines the terms of an employee's position, compensation, working hours, and any other relevant terms."
 msgstr ""
--- a/locale/sources/inventory_and_mrp.pot
+++ b/locale/sources/inventory_and_mrp.pot
@@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo master\n"
+"Project-Id-Version: Odoo saas-19.1\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-12-20 18:30+0000\n"
+"POT-Creation-Date: 2026-01-07 09:06+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"
@@ -4602,6 +4602,7 @@ msgid "Applies to both contained products and the container"
 msgstr ""

 #: ../../content/applications/inventory_and_mrp/inventory/product_management/configure.rst:96
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:143
 msgid "Custom routes"
 msgstr ""

@@ -5397,6 +5398,7 @@ msgid "Replenishment"
 msgstr ""

 #: ../../content/applications/inventory_and_mrp/inventory/product_management/configure/type.rst:230
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:23
 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.rst:3
 msgid "Reordering rules"
 msgstr ""
@@ -7170,10 +7172,63 @@ msgstr ""
 msgid "To organize and store products efficiently, use:"
 msgstr ""

+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:94
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:3
+msgid "Putaway rules"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:94
+msgid "Guide products to specific storage locations based on predefined rules"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:99
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:3
+msgid "Storage categories"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:99
+msgid "Set item or weight limits to prevent overstocking at the location and ensure proper organization"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:105
+msgid "Consignment"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:105
+msgid "Keep track of products owned by third parties"
+msgstr ""
+
 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:113
 msgid "Tailor the outgoing shipment process to fit the business needs. Picking methods and removal strategies control how products are reserved for orders, while dropshipping determines how they move. Configuring these options in Odoo ensures visibility into product movement and confirms that items reach customers efficiently."
 msgstr ""

+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:120
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:3
+msgid "Dropshipping"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:120
+msgid "Coordinate with vendors to deliver orders directly to customers, bypassing internal stock"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:125
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods.rst:5
+msgid "Picking methods"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:125
+msgid "Optimize picking operations using piece, batch, cluster, or wave picking techniques"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:130
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:6
+msgid "Removal strategies"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:130
+msgid "Use FIFO, LIFO, or FEFO strategies to automate the selection of products for delivery"
+msgstr ""
+
 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:136
 msgid "Customization"
 msgstr ""
@@ -7182,6 +7237,10 @@ msgstr ""
 msgid "Odoo's flexible framework enables businesses to tailor workflows to match specific operational needs."
 msgstr ""

+#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:143
+msgid "Define tailored receiving or delivery workflows to meet specific business needs"
+msgstr ""
+
 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:3
 msgid "Three-step delivery"
 msgstr ""
@@ -7309,10 +7368,6 @@ msgstr ""
 msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location and moves to the :guilabel:`Partners/Customers` location. Then, the status of the document will change to :guilabel:`Done`."
 msgstr ""

-#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:3
-msgid "Dropshipping"
-msgstr ""
-
 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/dropshipping.rst:7
 msgid "Dropshipping is an order fulfillment strategy that allows sellers to have items shipped directly from suppliers to customers. Normally, a seller purchases a product from a supplier, stores it in their inventory, and ships it to the end customer once an order is placed. With dropshipping, the supplier is responsible for storing and shipping the item. This benefits the seller by reducing inventory costs, including the price of operating warehouses."
 msgstr ""
@@ -7513,10 +7568,6 @@ msgstr ""
 msgid "View the :guilabel:`Stock On Hand` dashboard by navigating to :menuselection:`Inventory --> Reporting --> Inventory Report`. From this report, the :guilabel:`Locations` of all stock on-hand are displayed, in addition to the quantities per location. For consignment products, the :guilabel:`Owner` column will be populated with the owner of those products, or the original vendor who supplied the products in the first place."
 msgstr ""

-#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:3
-msgid "Putaway rules"
-msgstr ""
-
 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/putaway.rst:5
 msgid "Putaway is the process of routing products to appropriate storage locations upon shipment arrival."
 msgstr ""
@@ -8439,10 +8490,6 @@ msgstr ""
 msgid "Default warehouse location on employee form."
 msgstr ""

-#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:3
-msgid "Storage categories"
-msgstr ""
-
 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst:5
 msgid "A *storage category* is used with :doc:`putaway rules <putaway>` to assign a storage location to incoming products while accounting for the capacity of that location."
 msgstr ""
@@ -9051,10 +9098,6 @@ msgstr ""
 msgid "View of the transfers' statuses when the route is completed."
 msgstr ""

-#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods.rst:5
-msgid "Picking methods"
-msgstr ""
-
 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/picking_methods/batch.rst:3
 msgid "Batch picking"
 msgstr ""
@@ -9695,10 +9738,6 @@ msgstr ""
 msgid "The Automatic batches feature with the wave grouping option for product category selected."
 msgstr ""

-#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:6
-msgid "Removal strategies"
-msgstr ""
-
 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies.rst:8
 msgid "For companies with warehouses, *removal strategies* determine **which** products are taken from the warehouse, and **when**. For example, for perishable products, prioritizing the picking of goods with the nearest expiration date helps minimize food spoilage."
 msgstr ""
@@ -12431,7 +12470,7 @@ msgid "Tracking and cancellation"
 msgstr ""

 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/envia_shipping.rst:258
-msgid "Shipments registered with Envia can be tracked using the :guilabel:`Tracking` smart button from the delivery order or using the tracking link from the :doc:`customer portal <../../../../general/users/portal>`."
+msgid "Shipments registered with Envia can be tracked using the :guilabel:`Tracking` smart button from the delivery order or using the tracking link from the :doc:`customer portal <../../../../general/users/user_portals>`."
 msgstr ""

 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/envia_shipping.rst:None
@@ -16675,6 +16714,54 @@ msgstr ""
 msgid "Each replenishment mechanism triggers the creation or suggestion of a purchase order (PO) or manufacturing order (MO), with the best choice depending on the business process."
 msgstr ""

+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:23
+msgid "Automatically suggest or generate POs or MOs when stock falls below a minimum level."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:23
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:30
+msgid "Recommended"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:30
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/just_in_time.rst:3
+msgid "Just in time logic"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:30
+msgid "Avoid overstocking by placing order precisely to meet deadlines."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:37
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:81
+msgid "MTO"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:37
+msgid "Automatically generate POs or MOs when sales orders are confirmed."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:37
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:48
+msgid "Beginner-friendly"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:43
+msgid "MPS"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:43
+msgid "Manage long-term replenishment based on inputted sales forecasts, via a dashboard."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:48
+msgid "Suggest quantities"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:48
+msgid "Suggest quantities to order based on a past sales."
+msgstr ""
+
 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment.rst:55
 msgid "Replenishment strategies"
 msgstr ""
@@ -16760,10 +16847,6 @@ msgstr ""
 msgid ":doc:`../../manufacturing/workflows/use_mps`"
 msgstr ""

-#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/just_in_time.rst:3
-msgid "Just in time logic"
-msgstr ""
-
 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/just_in_time.rst:8
 msgid "*Just-in-time logic* in Odoo minimizes storage costs by placing orders precisely to meet deadlines. This is achieved using the :ref:`forecasted date <inventory/warehouses_storage/forecasted-date>`, which determines when replenishment is necessary to avoid overstocking. For example, for a product with a 5-day total lead time and a sales order delivery date in 10 days, Odoo waits 5 days to place the order, ensuring it arrives just in time for delivery."
 msgstr ""
@@ -18309,10 +18392,6 @@ msgstr ""
 msgid "Tick the :guilabel:`X: Supply Product from Y` checkbox, which is intended to be used with the |MTO| route or a reordering rule to replenish stock by moving the product from one warehouse to another. Proceed to the dedicated sections below to continue the process."
 msgstr ""

-#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:81
-msgid "MTO"
-msgstr ""
-
 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/resupply_warehouses.rst:83
 msgid "To replenish products using the make-to-order method, go to the product form and ensure the :ref:`MTO route is unarchived <inventory/warehouses_storage/unarchive-mto>`, so it appears in the :guilabel:`Routes` section of the :guilabel:`Inventory` tab."
 msgstr ""
@@ -23518,6 +23597,33 @@ msgstr ""
 msgid "In Odoo, companies can configure their subcontracting workflows based on a variety of different factors, including how components are sourced, and what happens to finished products once they are manufactured."
 msgstr ""

+#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:35
+#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:3
+msgid "Basic subcontracting"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:35
+msgid "Subcontract products without supplying the subcontractor with components."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:40
+#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:3
+msgid "Resupply subcontractor"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:40
+msgid "Ship components to a subcontractor each time a PO for a subcontracted product is confirmed."
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:45
+#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:3
+msgid "Dropship to subcontractor"
+msgstr ""
+
+#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:45
+msgid "Dropship components to a subcontractor each time a PO for a subcontracted product is confirmed."
+msgstr ""
+
 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:54
 msgid "To enable subcontracting in Odoo, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to the :guilabel:`Subcontracting` setting, under the :guilabel:`Operations` heading. Then, click :guilabel:`Save`."
 msgstr ""
@@ -24035,10 +24141,6 @@ msgstr ""
 msgid "Mike's Bikes ships the components to Bike Friends on the scheduled date of May 23rd, and they arrive on the deadline of May 25th. This gives Bike Friends enough time to manufacture the unicycle, and ship it back to Mike's Bikes by the expected arrival date of May 30th."
 msgstr ""

-#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:3
-msgid "Basic subcontracting"
-msgstr ""
-
 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_basic.rst:10
 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:12
 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:10
@@ -24284,10 +24386,6 @@ msgstr ""
 msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` on the order to confirm that the product has been shipped."
 msgstr ""

-#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:3
-msgid "Dropship to subcontractor"
-msgstr ""
-
 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_dropship.rst:15
 msgid "In Odoo, the *Dropship Subcontractor on Order* route is used to purchase the necessary components for a subcontracted product from the vendor, and have them delivered directly to the subcontractor, each time a purchase order (PO) for that product is confirmed."
 msgstr ""
@@ -24539,10 +24637,6 @@ msgstr ""
 msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` to confirm that the product has been shipped to the customer."
 msgstr ""

-#: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:3
-msgid "Resupply subcontractor"
-msgstr ""
-
 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:13
 msgid "In Odoo, the *Resupply Subcontractor on Order* route is used to deliver the necessary components for a subcontracted product to the subcontractor, each time a purchase order (PO) for that product is confirmed."
 msgstr ""
@@ -27067,7 +27161,7 @@ msgid "(required) :ref:`installing <general/install>` the **Purchase** app"
 msgstr ""

 #: ../../content/applications/inventory_and_mrp/purchase/advanced/edi.rst:44
-msgid "(optional) adding vendors (the sellers in this workflow) as :doc:`portal users <../../../general/users/portal>`."
+msgid "(optional) adding vendors (the sellers in this workflow) as :doc:`portal users <../../../general/users/user_portals>`."
 msgstr ""

 #: ../../content/applications/inventory_and_mrp/purchase/advanced/edi.rst:48
--- a/locale/sources/marketing.pot
+++ b/locale/sources/marketing.pot
@@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo master\n"
+"Project-Id-Version: Odoo saas-19.1\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-12-20 18:30+0000\n"
+"POT-Creation-Date: 2026-01-07 09:06+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"
@@ -36,6 +36,41 @@ msgstr ""
 msgid "`Magic Sheet - Email Marketing strategy [PDF] <https://drive.google.com/drive/folders/1TqZfYCF-56yhUSDVyfFjkmB23RWaRBP7>`_"
 msgstr ""

+#: ../../content/applications/marketing/email_marketing.rst:19
+#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:3
+#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:15
+msgid "Mailing lists"
+msgstr ""
+
+#: ../../content/applications/marketing/email_marketing.rst:19
+msgid "Silo contacts into specific mailing lists."
+msgstr ""
+
+#: ../../content/applications/marketing/email_marketing.rst:24
+msgid "Manage unsubscriptions (Blacklist)"
+msgstr ""
+
+#: ../../content/applications/marketing/email_marketing.rst:24
+msgid "Allow recipients to unsubscribe and blacklist from future mailings."
+msgstr ""
+
+#: ../../content/applications/marketing/email_marketing.rst:29
+#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:3
+msgid "Lost leads reactivation email"
+msgstr ""
+
+#: ../../content/applications/marketing/email_marketing.rst:29
+msgid "Target lost leads with Email Marketing."
+msgstr ""
+
+#: ../../content/applications/marketing/email_marketing.rst:34
+msgid "Analyze Metrics"
+msgstr ""
+
+#: ../../content/applications/marketing/email_marketing.rst:34
+msgid "Analyzing campaign metrics."
+msgstr ""
+
 #: ../../content/applications/marketing/email_marketing.rst:40
 msgid "Email marketing dashboard"
 msgstr ""
@@ -1242,10 +1277,6 @@ msgstr ""
 msgid ":doc:`Manage unsubscriptions <unsubscriptions>`"
 msgstr ""

-#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:3
-msgid "Lost leads reactivation email"
-msgstr ""
-
 #: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:5
 msgid "In Odoo, lost leads are removed from the active *CRM* pipeline, but can still be targeted with the *Email Marketing* application for strategic campaign purposes, such as lost leads reactivation."
 msgstr ""
@@ -1697,11 +1728,6 @@ msgstr ""
 msgid ":doc:`../marketing_automation`"
 msgstr ""

-#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:3
-#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:15
-msgid "Mailing lists"
-msgstr ""
-
 #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:5
 msgid "Mailing lists in Odoo are used for both pre and post sales communications in the *Email Marketing* application. They provide sales teams with qualified lead lists, focus group participants, or current customers that fulfill specific criteria."
 msgstr ""
@@ -2120,6 +2146,84 @@ msgstr ""
 msgid "`Odoo Tutorials: Events <https://www.odoo.com/slides/surveys-63>`_"
 msgstr ""

+#: ../../content/applications/marketing/events.rst:16
+#: ../../content/applications/marketing/events.rst:179
+#: ../../content/applications/marketing/events/create_events.rst:3
+msgid "Create events"
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:16
+msgid "Discover how to create events with Odoo."
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:21
+#: ../../content/applications/marketing/events.rst:192
+#: ../../content/applications/marketing/events/sell_tickets.rst:3
+msgid "Sell event tickets"
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:21
+msgid "Learn how to create, configure, and sell event tickets."
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:26
+#: ../../content/applications/marketing/events.rst:204
+msgid "Track and manage talks"
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:26
+msgid "See how to create, track, and manage event tracks with Odoo."
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:31
+#: ../../content/applications/marketing/events.rst:213
+#: ../../content/applications/marketing/events/event_templates.rst:3
+msgid "Event templates"
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:31
+msgid "Expedite the event-creation process with event templates."
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:36
+#: ../../content/applications/marketing/events.rst:231
+#: ../../content/applications/marketing/events/event_tracks.rst:3
+msgid "Event tracks"
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:36
+msgid "Learn how to create, track, and manage event tracks with Odoo."
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:41
+#: ../../content/applications/marketing/events.rst:222
+#: ../../content/applications/marketing/events/event_booths.rst:3
+msgid "Event booths"
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:41
+msgid "Create, manage, and sell event booths."
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:46
+#: ../../content/applications/marketing/events/registration_desk.rst:3
+msgid "Registration Desk"
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:46
+msgid "Instantly grant access to event attendees with Odoo's Registration Desk feature."
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:51
+#: ../../content/applications/marketing/events.rst:249
+#: ../../content/applications/marketing/events/revenues_report.rst:3
+msgid "Revenues report"
+msgstr ""
+
+#: ../../content/applications/marketing/events.rst:51
+msgid "Analyze the financial success of events with Odoo."
+msgstr ""
+
 #: ../../content/applications/marketing/events.rst:57
 msgid "Events dashboard"
 msgstr ""
@@ -2256,11 +2360,6 @@ msgstr ""
 msgid "The :guilabel:`Barcode Nomenclature` field, beneath the :guilabel:`Use Event Barcode` setting, is set to :guilabel:`Default Nomenclature`, by default, but can be changed at any time."
 msgstr ""

-#: ../../content/applications/marketing/events.rst:179
-#: ../../content/applications/marketing/events/create_events.rst:3
-msgid "Create events"
-msgstr ""
-
 #: ../../content/applications/marketing/events.rst:181
 msgid "With Odoo **Events**, events can be manually created from scratch or built off of pre-made templates."
 msgstr ""
@@ -2273,11 +2372,6 @@ msgstr ""
 msgid ":doc:`events/create_events`"
 msgstr ""

-#: ../../content/applications/marketing/events.rst:192
-#: ../../content/applications/marketing/events/sell_tickets.rst:3
-msgid "Sell event tickets"
-msgstr ""
-
 #: ../../content/applications/marketing/events.rst:194
 msgid "Create custom ticket tiers (with various price points) for potential event attendees to choose from, directly on the event template form, under the *Tickets* tab."
 msgstr ""
@@ -2290,10 +2384,6 @@ msgstr ""
 msgid ":doc:`events/sell_tickets`"
 msgstr ""

-#: ../../content/applications/marketing/events.rst:204
-msgid "Track and manage talks"
-msgstr ""
-
 #: ../../content/applications/marketing/events.rst:206
 msgid "Discover how to access various event tracks (talks, presentations, etc.), view entire agendas, and learn how attendees can propose talks for the event."
 msgstr ""
@@ -2302,11 +2392,6 @@ msgstr ""
 msgid ":doc:`events/track_manage_talks`"
 msgstr ""

-#: ../../content/applications/marketing/events.rst:213
-#: ../../content/applications/marketing/events/event_templates.rst:3
-msgid "Event templates"
-msgstr ""
-
 #: ../../content/applications/marketing/events.rst:215
 msgid "Learn the process to customize and configure event templates, which can be used to expedite the event-creation process."
 msgstr ""
@@ -2315,11 +2400,6 @@ msgstr ""
 msgid ":doc:`events/event_templates`"
 msgstr ""

-#: ../../content/applications/marketing/events.rst:222
-#: ../../content/applications/marketing/events/event_booths.rst:3
-msgid "Event booths"
-msgstr ""
-
 #: ../../content/applications/marketing/events.rst:224
 msgid "Explore the various ways to create, manage, and sell event booths with the Odoo **Events** application."
 msgstr ""
@@ -2328,11 +2408,6 @@ msgstr ""
 msgid ":doc:`events/event_booths`"
 msgstr ""

-#: ../../content/applications/marketing/events.rst:231
-#: ../../content/applications/marketing/events/event_tracks.rst:3
-msgid "Event tracks"
-msgstr ""
-
 #: ../../content/applications/marketing/events.rst:233
 msgid "Find out how to create, manage, and schedule different experiences (aka *Tracks*) for events with Odoo."
 msgstr ""
@@ -2353,11 +2428,6 @@ msgstr ""
 msgid ":doc:`events/registration_desk`"
 msgstr ""

-#: ../../content/applications/marketing/events.rst:249
-#: ../../content/applications/marketing/events/revenues_report.rst:3
-msgid "Revenues report"
-msgstr ""
-
 #: ../../content/applications/marketing/events.rst:251
 msgid "Gain invaluable insight into event-related revenues with customizable reports and metrics."
 msgstr ""
@@ -3790,10 +3860,6 @@ msgstr ""
 msgid "The track-related event submenu options on an event website built with Odoo Events."
 msgstr ""

-#: ../../content/applications/marketing/events/registration_desk.rst:3
-msgid "Registration Desk"
-msgstr ""
-
 #: ../../content/applications/marketing/events/registration_desk.rst:5
 msgid "Use the *Registration Desk* feature in Odoo **Events** to grant access to registered event attendees as they arrive, and store attendee-related data in the reporting metrics."
 msgstr ""
@@ -4490,6 +4556,41 @@ msgstr ""
 msgid "`Magic Sheet - Marketing Automation [PDF] <https://drive.google.com/drive/folders/1MMMGcYIG1tm160jC2JaXVc_D5b6x3cJd>`_"
 msgstr ""

+#: ../../content/applications/marketing/marketing_automation.rst:25
+#: ../../content/applications/marketing/marketing_automation/target_audience.rst:3
+msgid "Audience targeting"
+msgstr ""
+
+#: ../../content/applications/marketing/marketing_automation.rst:25
+msgid "Configure the target audience for a campaign."
+msgstr ""
+
+#: ../../content/applications/marketing/marketing_automation.rst:30
+msgid "Workflow activities"
+msgstr ""
+
+#: ../../content/applications/marketing/marketing_automation.rst:30
+msgid "Define the activities that occur within a campaign."
+msgstr ""
+
+#: ../../content/applications/marketing/marketing_automation.rst:35
+#: ../../content/applications/marketing/marketing_automation/testing_running.rst:3
+msgid "Testing/running campaigns"
+msgstr ""
+
+#: ../../content/applications/marketing/marketing_automation.rst:35
+msgid "Launch a test or run a campaign."
+msgstr ""
+
+#: ../../content/applications/marketing/marketing_automation.rst:40
+#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:3
+msgid "Campaign metrics"
+msgstr ""
+
+#: ../../content/applications/marketing/marketing_automation.rst:40
+msgid "Review the metrics of a campaign."
+msgstr ""
+
 #: ../../content/applications/marketing/marketing_automation.rst:48
 msgid "To begin, make sure the **Marketing Automation** application is :ref:`installed <general/install>`."
 msgstr ""
@@ -4918,10 +5019,6 @@ msgstr ""
 msgid ":doc:`../../email_marketing`"
 msgstr ""

-#: ../../content/applications/marketing/marketing_automation/target_audience.rst:3
-msgid "Audience targeting"
-msgstr ""
-
 #: ../../content/applications/marketing/marketing_automation/target_audience.rst:5
 msgid "The :guilabel:`Target` and :guilabel:`Filter` fields on the campaign form, also referred to as the *domain*, contain the parameters used to define the target audience for the campaign's reach (i.e., the unique contact records in the database, and imported list, etc.)."
 msgstr ""
@@ -5042,10 +5139,6 @@ msgstr ""
 msgid ":doc:`understanding_metrics`"
 msgstr ""

-#: ../../content/applications/marketing/marketing_automation/testing_running.rst:3
-msgid "Testing/running campaigns"
-msgstr ""
-
 #: ../../content/applications/marketing/marketing_automation/testing_running.rst:5
 msgid "The Odoo *Marketing Automation* app allows users to test marketing campaigns (and mailings) before officially running them to check for errors and correct any mistakes before it reaches its target audience."
 msgstr ""
@@ -5215,10 +5308,6 @@ msgstr ""
 msgid ":doc:`target_audience`"
 msgstr ""

-#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:3
-msgid "Campaign metrics"
-msgstr ""
-
 #: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:5
 msgid "*Campaign metrics* are detailed statistics and analytics within a marketing campaign, measuring its success and effectiveness. Triggered marketing activities populate relevant activity blocks with real-time metrics, in the campaign detail form."
 msgstr ""
@@ -5800,6 +5889,57 @@ msgstr ""
 msgid "Odoo's *SMS Marketing* application can also help boost conversion rates around valuable actions, such as event registrations, free trials, purchases, etc., since text and mobile-based marketing channels typically yield higher :abbr:`CTOR (click-to-open rate)` and :abbr:`CTR (click-through rate)` outcomes."
 msgstr ""

+#: ../../content/applications/marketing/sms_marketing.rst:21
+#: ../../content/applications/marketing/sms_marketing/create_sms.rst:3
+msgid "Create SMS messages"
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:21
+msgid "Explore how to create, configure, send, and schedule SMS messages."
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:26
+#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:3
+msgid "SMS analysis"
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:26
+msgid "Examine detailed reporting metrics related to every aspect of sent SMS messages."
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:31
+msgid "SMS marketing campaigns"
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:31
+msgid "Discover how to create and customize SMS marketing campaigns for any occasion with Odoo."
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:36
+#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:3
+msgid "Mailing lists and blacklists"
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:36
+msgid "Set up custom mailing lists and blacklists to ensure all SMS messages reach the right recipients."
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:42
+msgid "Pricing and FAQ"
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:42
+msgid "Find out more about Odoo's SMS pricing, and check out some of the most frequently asked questions."
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:48
+msgid "Twilio"
+msgstr ""
+
+#: ../../content/applications/marketing/sms_marketing.rst:48
+msgid "In some countries with stricter regulations, the out-of-the-box solution proposed by Odoo may not work. In this case, you can use our Twilio integration to send SMS worldwide."
+msgstr ""
+
 #: ../../content/applications/marketing/sms_marketing.rst:55
 msgid "SMS marketing dashboard"
 msgstr ""
@@ -5832,10 +5972,6 @@ msgstr ""
 msgid "Lastly, the :icon:`fa-area-chart` :guilabel:`Graph` view visualizes that same SMS-related data in series of graphs and charts. Odoo also provides various ways to sort and group the data for more detailed analysis."
 msgstr ""

-#: ../../content/applications/marketing/sms_marketing/create_sms.rst:3
-msgid "Create SMS messages"
-msgstr ""
-
 #: ../../content/applications/marketing/sms_marketing/create_sms.rst:5
 msgid "To start, click :guilabel:`Create` on the main :guilabel:`SMS Marketing` dashboard, and Odoo reveals a blank SMS template form, which can be configured in a number of different ways."
 msgstr ""
@@ -5964,10 +6100,6 @@ msgstr ""
 msgid ":guilabel:`Test`: allows for an :abbr:`SMS (Short Message Service)` to be sent to one or multiple numbers for test purposes. Remember to use a comma between phone numbers if multiple numbers are used as recipients."
 msgstr ""

-#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:3
-msgid "Mailing lists and blacklists"
-msgstr ""
-
 #: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:5
 msgid "Creating or importing mailing lists in Odoo is very useful when curating content to specific groups of people that already share similar demographics or interests. Mailing lists are also a great way to get started if a company is migrating from another system, and already has a established audience."
 msgstr ""
@@ -6463,10 +6595,6 @@ msgstr ""
 msgid "Yes, but it is not possible out-of-the-box. Odoo experts can help customize a database to allow for the use of a personal SMS provider. Please check our success packs `here <https://www.odoo.com/pricing-packs>`_."
 msgstr ""

-#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:3
-msgid "SMS analysis"
-msgstr ""
-
 #: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:5
 msgid "On the :guilabel:`Reporting` page (accessible via the :menuselection:`Reporting` option in the header menu), there are options to apply different combinations of :guilabel:`Filters` and :guilabel:`Measures` to view metrics in a number of different layouts (e.g. :guilabel:`Graph`, :guilabel:`List`, and :guilabel:`Cohort` views.)"
 msgstr ""
@@ -6751,6 +6879,23 @@ msgstr ""
 msgid "Odoo's *Social Marketing* application helps content marketers create and schedule posts, manage various social media accounts, analyze content effectiveness, and engage directly with social media followers in one, centralized location."
 msgstr ""

+#: ../../content/applications/marketing/social_marketing.rst:16
+#: ../../content/applications/marketing/social_marketing/social_posts.rst:3
+msgid "Social posts"
+msgstr ""
+
+#: ../../content/applications/marketing/social_marketing.rst:16
+msgid "Discover everything there is to know about how to create and customize social media posts using Odoo."
+msgstr ""
+
+#: ../../content/applications/marketing/social_marketing.rst:22
+msgid "Social campaigns"
+msgstr ""
+
+#: ../../content/applications/marketing/social_marketing.rst:22
+msgid "Learn about all the different campaign and marketing tools this application has to offer."
+msgstr ""
+
 #: ../../content/applications/marketing/social_marketing.rst:28
 msgid "Social media accounts"
 msgstr ""
@@ -7045,10 +7190,6 @@ msgstr ""
 msgid "The Odoo *Social Marketing* app is integrated with other Odoo applications, such as *Sales*, *Invoicing*, *CRM*, and *Website*."
 msgstr ""

-#: ../../content/applications/marketing/social_marketing/social_posts.rst:3
-msgid "Social posts"
-msgstr ""
-
 #: ../../content/applications/marketing/social_marketing/social_posts.rst:5
 msgid "The Odoo *Social Marketing* application provides various ways to create posts for any type of social media outlet."
 msgstr ""
@@ -7517,6 +7658,57 @@ msgstr ""
 msgid "`Odoo Tutorials: Surveys <https://www.odoo.com/slides/surveys-62>`_"
 msgstr ""

+#: ../../content/applications/marketing/surveys.rst:20
+#: ../../content/applications/marketing/surveys.rst:216
+#: ../../content/applications/marketing/surveys/create.rst:3
+msgid "Create surveys"
+msgstr ""
+
+#: ../../content/applications/marketing/surveys.rst:20
+msgid "Discover how to create surveys with Odoo."
+msgstr ""
+
+#: ../../content/applications/marketing/surveys.rst:25
+#: ../../content/applications/marketing/surveys.rst:225
+#: ../../content/applications/marketing/surveys/scoring.rst:3
+msgid "Scoring surveys"
+msgstr ""
+
+#: ../../content/applications/marketing/surveys.rst:25
+msgid "Learn how to create and analyze survey scores with Odoo."
+msgstr ""
+
+#: ../../content/applications/marketing/surveys.rst:30
+#: ../../content/applications/marketing/surveys.rst:234
+#: ../../content/applications/marketing/surveys/questions.rst:3
+#: ../../content/applications/marketing/surveys/questions.rst:64
+msgid "Create questions"
+msgstr ""
+
+#: ../../content/applications/marketing/surveys.rst:30
+msgid "See how to create, configure, and customize all types of survey questions with Odoo."
+msgstr ""
+
+#: ../../content/applications/marketing/surveys.rst:35
+#: ../../content/applications/marketing/surveys.rst:243
+#: ../../content/applications/marketing/surveys/live_session.rst:3
+msgid "Live Session surveys"
+msgstr ""
+
+#: ../../content/applications/marketing/surveys.rst:35
+msgid "Find out everything there is to know about Odoo's unique Live Session surveys."
+msgstr ""
+
+#: ../../content/applications/marketing/surveys.rst:40
+#: ../../content/applications/marketing/surveys.rst:253
+#: ../../content/applications/marketing/surveys/analysis.rst:3
+msgid "Survey analysis"
+msgstr ""
+
+#: ../../content/applications/marketing/surveys.rst:40
+msgid "Explore the various ways to analyze surveys using Odoo's in-depth reporting pages."
+msgstr ""
+
 #: ../../content/applications/marketing/surveys.rst:46
 msgid "Dashboard"
 msgstr ""
@@ -7751,11 +7943,6 @@ msgstr ""
 msgid "A new survey cannot be created in this view, as it is solely for the purpose of creating and viewing scheduled activities."
 msgstr ""

-#: ../../content/applications/marketing/surveys.rst:216
-#: ../../content/applications/marketing/surveys/create.rst:3
-msgid "Create surveys"
-msgstr ""
-
 #: ../../content/applications/marketing/surveys.rst:218
 msgid "Learn about all the different options and configurations that can be utilized when creating a survey in Odoo."
 msgstr ""
@@ -7764,11 +7951,6 @@ msgstr ""
 msgid ":doc:`surveys/create`"
 msgstr ""

-#: ../../content/applications/marketing/surveys.rst:225
-#: ../../content/applications/marketing/surveys/scoring.rst:3
-msgid "Scoring surveys"
-msgstr ""
-
 #: ../../content/applications/marketing/surveys.rst:227
 msgid "Discover how to measure a survey participant's performance, or overall satisfaction, with Odoo's detailed (and fully customizable) survey scoring options."
 msgstr ""
@@ -7777,12 +7959,6 @@ msgstr ""
 msgid ":doc:`surveys/scoring`"
 msgstr ""

-#: ../../content/applications/marketing/surveys.rst:234
-#: ../../content/applications/marketing/surveys/questions.rst:3
-#: ../../content/applications/marketing/surveys/questions.rst:64
-msgid "Create questions"
-msgstr ""
-
 #: ../../content/applications/marketing/surveys.rst:236
 msgid "With Odoo *Surveys*, there are many question types and options to choose from, providing the ability to create any kind of unique survey, questionnarire, and/or certification."
 msgstr ""
@@ -7791,11 +7967,6 @@ msgstr ""
 msgid ":doc:`surveys/questions`"
 msgstr ""

-#: ../../content/applications/marketing/surveys.rst:243
-#: ../../content/applications/marketing/surveys/live_session.rst:3
-msgid "Live Session surveys"
-msgstr ""
-
 #: ../../content/applications/marketing/surveys.rst:245
 msgid "The *Live Session* survey option available in Odoo can enhance in-person demonstrations and presentations, where participants' real-time responses can be used to dictate where the conversation goes next."
 msgstr ""
@@ -7804,11 +7975,6 @@ msgstr ""
 msgid ":doc:`surveys/live_session`"
 msgstr ""

-#: ../../content/applications/marketing/surveys.rst:253
-#: ../../content/applications/marketing/surveys/analysis.rst:3
-msgid "Survey analysis"
-msgstr ""
-
 #: ../../content/applications/marketing/surveys.rst:255
 msgid "Once the surveys start to come in, it is time to analyze the responses from your participants. Fortuantely, the in-depth reporting pages and options available in Odoo *Surveys* provide countless ways to examine everything related to surveys, and their submitted responses."
 msgstr ""
--- a/locale/sources/productivity.pot
+++ b/locale/sources/productivity.pot
@@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo master\n"
+"Project-Id-Version: Odoo saas-19.1\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-12-20 18:30+0000\n"
+"POT-Creation-Date: 2026-01-07 09:06+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"
@@ -5263,7 +5263,7 @@ msgid "Each folder and file URL includes the access rights assigned to it. When
 msgstr ""

 #: ../../content/applications/productivity/documents.rst:411
-msgid ":doc:`Portal users </applications/general/users/portal>` can access folders and files they have permission to view or edit through the customer portal by clicking the :guilabel:`Documents` card."
+msgid ":doc:`Portal users </applications/general/users/user_portals>` can access folders and files they have permission to view or edit through the customer portal by clicking the :guilabel:`Documents` card."
 msgstr ""

 #: ../../content/applications/productivity/documents.rst:416
@@ -15127,6 +15127,24 @@ msgstr ""
 msgid "Users can make and receive calls, track communication history, and automate call routing based on predefined rules. Features like call recording and analytics provide insights into call volume and response times, helping teams track communication efficiency."
 msgstr ""

+#: ../../content/applications/productivity/voip.rst:21
+#: ../../content/applications/productivity/voip/voip_widget.rst:3
+msgid "VoIP actions"
+msgstr ""
+
+#: ../../content/applications/productivity/voip.rst:21
+msgid "Get oriented with the features of the VoIP widget, like what actions can be taken during a call."
+msgstr ""
+
+#: ../../content/applications/productivity/voip.rst:28
+#: ../../content/applications/productivity/voip/devices_integrations.rst:3
+msgid "Devices and integrations"
+msgstr ""
+
+#: ../../content/applications/productivity/voip.rst:28
+msgid "Learn about accessing the VoIP widget from different devices (like phones) and apps (like Linphone)."
+msgstr ""
+
 #: ../../content/applications/productivity/voip.rst:36
 msgid "VoIP terms"
 msgstr ""
@@ -15191,6 +15209,23 @@ msgstr ""
 msgid "Odoo **cannot** verify that every alternate provider is compatible with Odoo's systems. However, if the above requirements are met, then no issues should be found."
 msgstr ""

+#: ../../content/applications/productivity/voip.rst:85
+#: ../../content/applications/productivity/voip/axivox.rst:5
+msgid "Axivox configuration"
+msgstr ""
+
+#: ../../content/applications/productivity/voip.rst:85
+msgid "Learn how to set up Axivox in Odoo. This includes adding users to Axivox, setting up call queues, and more."
+msgstr ""
+
+#: ../../content/applications/productivity/voip.rst:92
+msgid "OnSIP configuration"
+msgstr ""
+
+#: ../../content/applications/productivity/voip.rst:92
+msgid "Learn how to set up OnSIP in Odoo. This includes entering OnSIP credentials into Odoo and handling troubleshooting."
+msgstr ""
+
 #: ../../content/applications/productivity/voip.rst:100
 msgid "VoIP workflows"
 msgstr ""
@@ -15199,8 +15234,20 @@ msgstr ""
 msgid "Here are a few commonly used workflows for Odoo |VOIP|. This technology is especially popular with sales teams and support teams, but can be useful for other teams as well."
 msgstr ""

-#: ../../content/applications/productivity/voip/axivox.rst:5
-msgid "Axivox configuration"
+#: ../../content/applications/productivity/voip.rst:106
+msgid "Sales teams and VoIP"
+msgstr ""
+
+#: ../../content/applications/productivity/voip.rst:106
+msgid "Learn how to use VoIP for a sales team. This includes making sales calls, handling follow-ups, and sending a sales quotation while on a call."
+msgstr ""
+
+#: ../../content/applications/productivity/voip.rst:113
+msgid "Support queues and VoIP"
+msgstr ""
+
+#: ../../content/applications/productivity/voip.rst:113
+msgid "Learn how to use VoIP for a support team. This includes joining a call queue as an agent and handling support tickets that require calls."
 msgstr ""

 #: ../../content/applications/productivity/voip/axivox/axivox_config.rst:3
@@ -17424,10 +17471,6 @@ msgstr ""
 msgid "When the desired changes are complete, click :guilabel:`Apply changes` in the upper-right corner of the screen."
 msgstr ""

-#: ../../content/applications/productivity/voip/devices_integrations.rst:3
-msgid "Devices and integrations"
-msgstr ""
-
 #: ../../content/applications/productivity/voip/devices_integrations.rst:5
 msgid ":abbr:`VoIP (Voice over Internet Protocol)` can be used on many different devices, such as a computer, tablet, mobile phone, and many more. This is helpful in that it reduces costs, and employees can work from anywhere in the world, so long as they have a broadband internet connection."
 msgstr ""
@@ -18251,10 +18294,6 @@ msgstr ""
 msgid "Once the support agent calls their *agent disconnection code*, they'll hear a short message letting them know they are logged out of the queue. From here, the agent will no longer receive support calls until they log back in."
 msgstr ""

-#: ../../content/applications/productivity/voip/voip_widget.rst:3
-msgid "VoIP actions"
-msgstr ""
-
 #: ../../content/applications/productivity/voip/voip_widget.rst:7
 msgid "The |VOIP| widget is an add-on made available to Odoo users by installing the |VOIP| module. Instead of managing mobile devices for every salesperson, fumbling through call transfers for upset customers, or needing a meeting room to handle a conference call, utilize the |VOIP| widget to tackle any of these business needs."
 msgstr ""
--- a/locale/sources/sales.pot
+++ b/locale/sources/sales.pot
--- a/locale/sources/services.pot
+++ b/locale/sources/services.pot
@@ -6,9 +6,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Odoo master\n"
+"Project-Id-Version: Odoo saas-19.1\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-12-20 18:30+0000\n"
+"POT-Creation-Date: 2026-01-07 09:06+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"
@@ -194,6 +194,7 @@ msgstr ""
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:13
 #: ../../content/applications/services/timesheets/billing_rates.rst:19
 #: ../../content/applications/services/timesheets/billing_rates.rst:54
+#: ../../content/applications/services/timesheets/time_off.rst:12
 msgid "Configuration"
 msgstr ""

@@ -848,7 +849,7 @@ msgid "Create field service task from a ticket"
 msgstr ""

 #: ../../content/applications/services/helpdesk/advanced/after_sales.rst:240
-msgid "On-site interventions can be planned from a ticket and managed through the **Field Service** application. Customers with :doc:`portal access <../../../general/users/portal>` are able to track the progress of a **Field Service** task the same as they would a **Helpdesk** ticket."
+msgid "On-site interventions can be planned from a ticket and managed through the **Field Service** application. Customers with :doc:`portal access <../../../general/users/user_portals>` are able to track the progress of a **Field Service** task the same as they would a **Helpdesk** ticket."
 msgstr ""

 #: ../../content/applications/services/helpdesk/advanced/after_sales.rst:245
@@ -1044,7 +1045,7 @@ msgid "Customers are able to view their tickets by clicking the :guilabel:`View
 msgstr ""

 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:109
-msgid "Customers with access to the :doc:`portal <../../../general/users/portal>` are able to view their tickets under :menuselection:`My Account --> Tickets`."
+msgid "Customers with access to the :doc:`portal <../../../general/users/user_portals>` are able to view their tickets under :menuselection:`My Account --> Tickets`."
 msgstr ""

 #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:3
@@ -3326,7 +3327,7 @@ msgid ":guilabel:`All internal users`: All internal users can access the project
 msgstr ""

 #: ../../content/applications/services/project/project_management.rst:77
-msgid ":guilabel:`Invited portal users and all internal users (public)`: All internal users can access the project and all of its tasks. When following a project, :doc:`portal users </applications/general/users/portal>` only have access to the specific tasks they are following. This option is selected by default."
+msgid ":guilabel:`Invited portal users and all internal users (public)`: All internal users can access the project and all of its tasks. When following a project, :doc:`portal users </applications/general/users/user_portals>` only have access to the specific tasks they are following. This option is selected by default."
 msgstr ""

 #: ../../content/applications/services/project/project_management.rst:83
@@ -3605,23 +3606,23 @@ msgstr ""
 msgid "Once all the tasks linked to the milestone are completed (marked as :doc:`Done or Cancelled <../tasks/task_stages_statuses>`), the milestone will be automatically marked as :guilabel:`Reached` in the :menuselection:`Project --> Settings --> Milestones`. You can also check the :guilabel:`Reached` box manually whenever the milestone is reached. Manual checking of the box will not impact the tasks linked to the milestone."
 msgstr ""

-#: ../../content/applications/services/project/project_management/project_milestones.rst:49
+#: ../../content/applications/services/project/project_management/project_milestones.rst:51
 msgid "Using milestones"
 msgstr ""

-#: ../../content/applications/services/project/project_management/project_milestones.rst:51
+#: ../../content/applications/services/project/project_management/project_milestones.rst:53
 msgid "Odoo offers several ways to oversee the project’s milestones and their relationship to ongoing tasks."
 msgstr ""

-#: ../../content/applications/services/project/project_management/project_milestones.rst:54
+#: ../../content/applications/services/project/project_management/project_milestones.rst:56
 msgid "In the **Gantt view**, a milestone is shown as a vertical line marked with a diamond shape, displayed on the day of the milestone’s deadline. The line is color-coded in blue to indicate that the milestone has not yet reached its deadline, or it has been marked as reached (in which case, a check mark is displayed on the milestone). A milestone is color-coded in red if it has not been reached by its deadline."
 msgstr ""

-#: ../../content/applications/services/project/project_management/project_milestones.rst:60
+#: ../../content/applications/services/project/project_management/project_milestones.rst:62
 msgid "If a milestone’s deadline falls on the same day as the project’s deadline, it is displayed with a vertical line marked with a circle, and the same color coding principles as above apply."
 msgstr ""

-#: ../../content/applications/services/project/project_management/project_milestones.rst:63
+#: ../../content/applications/services/project/project_management/project_milestones.rst:65
 msgid "Aside from the Gantt view, you can also create, edit, and mark milestones as reached from :ref:`the project dashboard <project/project-dashboard/milestones>`."
 msgstr ""

@@ -4094,42 +4095,42 @@ msgid ":guilabel:`Allocated Time`: the amount of time that the work on this task
 msgstr ""

 #: ../../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."
+msgid ":guilabel:`Deadline`: the expected end date of the task. Click the :guilabel:`Deadline` field to select the task's end date in the dropdown calendar. To define the task's duration, including its start and end dates (and optionally specific times), click the :icon:`fa-calendar-plus-o` (:guilabel:`fa-calendar-plus-o`) icon in the dropdown calendar, select the dates and times, then click  :guilabel:`Apply` to save."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:47
+#: ../../content/applications/services/project/tasks/task_creation.rst:50
 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:49
+#: ../../content/applications/services/project/tasks/task_creation.rst:52
 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:53
+#: ../../content/applications/services/project/tasks/task_creation.rst:56
 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:56
+#: ../../content/applications/services/project/tasks/task_creation.rst:59
 msgid "**30h**: to allocate 30 hours to the task."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:57
+#: ../../content/applications/services/project/tasks/task_creation.rst:60
 msgid "**#tags**: to add tags to the task."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:58
+#: ../../content/applications/services/project/tasks/task_creation.rst:61
 msgid "**@user**: to assign the task to a user."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:59
+#: ../../content/applications/services/project/tasks/task_creation.rst:62
 msgid "**!**: to star the task as high priority."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:61
+#: ../../content/applications/services/project/tasks/task_creation.rst:64
 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:64
+#: ../../content/applications/services/project/tasks/task_creation.rst:67
 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 ""

@@ -4137,31 +4138,31 @@ msgstr ""
 msgid "Using keyboard shortcuts to create a task in Project."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:74
+#: ../../content/applications/services/project/tasks/task_creation.rst:77
 msgid "Creating tasks from an email alias"
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:76
+#: ../../content/applications/services/project/tasks/task_creation.rst:79
 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:79
+#: ../../content/applications/services/project/tasks/task_creation.rst:82
 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:83
+#: ../../content/applications/services/project/tasks/task_creation.rst:86
 msgid "Fill in the :guilabel:`Create tasks by sending an email to` field as follows:"
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:85
+#: ../../content/applications/services/project/tasks/task_creation.rst:88
 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:87
+#: ../../content/applications/services/project/tasks/task_creation.rst:90
 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:89
+#: ../../content/applications/services/project/tasks/task_creation.rst:92
 msgid "**Accept Emails From**: refine the senders whose emails will create tasks in the project."
 msgstr ""

@@ -4169,67 +4170,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:94
+#: ../../content/applications/services/project/tasks/task_creation.rst:97
 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:96
+#: ../../content/applications/services/project/tasks/task_creation.rst:99
 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:99
+#: ../../content/applications/services/project/tasks/task_creation.rst:102
 msgid "The email sender is displayed in the :guilabel:`Customer` field."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:100
+#: ../../content/applications/services/project/tasks/task_creation.rst:103
 msgid "The email subject is displayed in the :guilabel:`Task Title` field."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:101
+#: ../../content/applications/services/project/tasks/task_creation.rst:104
 msgid "The email body is displayed in the :guilabel:`Description` field."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:102
+#: ../../content/applications/services/project/tasks/task_creation.rst:105
 msgid "The whole content of the email is additionally displayed in the **chatter**."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:103
+#: ../../content/applications/services/project/tasks/task_creation.rst:106
 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:107
+#: ../../content/applications/services/project/tasks/task_creation.rst:110
 msgid "Creating tasks from a website form"
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:109
+#: ../../content/applications/services/project/tasks/task_creation.rst:112
 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:112
+#: ../../content/applications/services/project/tasks/task_creation.rst:115
 msgid "Go to the website page where you wish to add the form and :doc:`add the Form building block </applications/websites/website/web_design/building_blocks>`."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:114
+#: ../../content/applications/services/project/tasks/task_creation.rst:117
 msgid "In the website editor, edit the following fields:"
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:116
+#: ../../content/applications/services/project/tasks/task_creation.rst:119
 msgid ":guilabel:`Action`: select :guilabel:`Create a Task`."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:117
+#: ../../content/applications/services/project/tasks/task_creation.rst:120
 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:119
+#: ../../content/applications/services/project/tasks/task_creation.rst:122
 msgid ":ref:`Customize the form <website/building_blocks/form>`."
 msgstr ""

-#: ../../content/applications/services/project/tasks/task_creation.rst:121
+#: ../../content/applications/services/project/tasks/task_creation.rst:124
 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:125
+#: ../../content/applications/services/project/tasks/task_creation.rst:128
 msgid ":ref:`Website forms <website/building_blocks/form>`"
 msgstr ""

@@ -4486,54 +4487,57 @@ msgid "To create or edit existing tips, navigate to :menuselection:`Timesheets -
 msgstr ""

 #: ../../content/applications/services/timesheets/time_off.rst:3
-msgid "Create Timesheets upon Time Off Validation"
+msgid "Time off entries"
 msgstr ""

 #: ../../content/applications/services/timesheets/time_off.rst:5
-msgid "Odoo automatically timesheets on project/tasks upon time off requests. This allows for better overall control over the validation of timesheets, as it does not leave place for forgetfulness and questions after hours that have not been timesheeted by the employee."
+msgid "Odoo automatically generates timesheet entries on projects and tasks once a time off request is approved. This streamlines timesheet validation by ensuring approved time off is accurately reflected in timesheets."
 msgstr ""

-#: ../../content/applications/services/timesheets/time_off.rst:9
-msgid "Activate the :ref:`developer mode <developer-mode>`, go to *Timesheets*, and change the *Project* and *Task* set by default, if you like."
+#: ../../content/applications/services/timesheets/time_off.rst:14
+msgid "First, activate the :ref:`developer mode <developer-mode>`, then open the **Timesheets** app, and navigate to :menuselection:`Configuration --> Settings`. Scroll to the :guilabel:`Time Off` section and enable the :guilabel:`Time Off` checkbox. Enabling this option creates timesheet entries for validated time off requests and public holidays."
 msgstr ""

-#: ../../content/applications/services/timesheets/time_off.rst:None
-msgid "View of Timesheets setting enabling the feature record time off in Odoo Timesheets"
+#: ../../content/applications/services/timesheets/time_off.rst:19
+msgid "Once enabled, two fields appear: :guilabel:`Project` and :guilabel:`Task`. The default selection for :guilabel:`Project` is :guilabel:`Internal`, and the default selection for :guilabel:`Task` is :guilabel:`Time Off`. These inform Odoo where to log the time off requests, which project, and task. These can be modified, if desired, using the drop-down menu."
 msgstr ""

-#: ../../content/applications/services/timesheets/time_off.rst:16
-msgid "Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select or create the needed type, and decide if you would like the requests to be validated or not."
+#: ../../content/applications/services/timesheets/time_off.rst:25
+msgid "The available options presented vary based on the installed applications."
 msgstr ""

-#: ../../content/applications/services/timesheets/time_off.rst:None
-msgid "View of a time off types form emphasizing the time off requests and timesheets section in\n"
-"Odoo Time Off"
+#: ../../content/applications/services/timesheets/time_off.rst:28
+msgid "Time off categories without validation requirements create timesheet records instantly. Requests requiring validation creates timesheet entries *after* the time off request is approved."
 msgstr ""

-#: ../../content/applications/services/timesheets/time_off.rst:26
-msgid "Now, once the employee has requested his time off and the request has been validated (or not, depending on the setting chosen), the time is automatically allocated on *Timesheets*, under the respective project and task."
+#: ../../content/applications/services/timesheets/time_off.rst:31
+msgid "To check if a time off type requires approval, check the :guilabel:`Approvals` section of the :ref:`time off type form <time_off/time-off-requests>`."
 msgstr ""

-#: ../../content/applications/services/timesheets/time_off.rst:27
-msgid "On the example below, the user requested *Paid Time off* from July 13th to 15th."
+#: ../../content/applications/services/timesheets/time_off.rst:35
+msgid "Workflow"
 msgstr ""

-#: ../../content/applications/services/timesheets/time_off.rst:None
-msgid "View of the time off request form in Odoo Time Off"
-msgstr ""
-
-#: ../../content/applications/services/timesheets/time_off.rst:33
-msgid "Considering that validation is not required, the requested time off is automatically displayed in *Timesheets*. If validation is necessary, the time is automatically allocated after the responsible person for validating does it so."
-msgstr ""
-
-#: ../../content/applications/services/timesheets/time_off.rst:None
-msgid "Video of timesheets emphasizing the requested time off from the employee in Odoo Timesheets"
+#: ../../content/applications/services/timesheets/time_off.rst:37
+msgid "Once the employee has :doc:`requested time off <../../hr/time_off/request_time_off>`, and the request has been validated, if necessary, the time is automatically logged on the **Timesheets** app, under the respective project and task."
 msgstr ""

 #: ../../content/applications/services/timesheets/time_off.rst:41
-msgid "Click on the magnifying glass, hovering over the concerned cell, to access all the aggregated data on that cell (day), and see details regarding the project/task."
+msgid "To view the logged entry, open the **Timesheets** app and navigate to the relevant time period. The time off appears in the corresponding field, according to the :ref:`configuration <timesheets/config>`."
 msgstr ""

-#: ../../content/applications/services/timesheets/time_off.rst:None
-msgid "View of the details of a project/task in Odoo Timeheets"
+#: ../../content/applications/services/timesheets/time_off.rst:45
+msgid "To view the timesheet entry details, click the :icon:`fa-search` :guilabel:`(magnifying glass)` icon that appears when hovering over the entry, and the detailed timesheet information appears."
+msgstr ""
+
+#: ../../content/applications/services/timesheets/time_off.rst:49
+msgid "An employee is attending internal training the week of December 15-19, 2025, and logs their time in the **Timesheets** app under the `Internal` project, with a task of `Training`. On December 19, 2025, the employee is home sick, and requests the day off in the **Time Off** app."
+msgstr ""
+
+#: ../../content/applications/services/timesheets/time_off.rst:53
+msgid "The *time off type* they request is *Sick Time off*, which is configured to **not** require validation. The employee's time off request is automatically approved, and is logged in the **Timesheets** app, under the `Internal` project, and the `Time Off` task."
+msgstr ""
+
+#: ../../content/applications/services/timesheets/time_off.rst:0
+msgid "A timecard reflecting training hours and sick time off."
 msgstr ""
--- a/locale/sources/sphinx.pot
+++ b/locale/sources/sphinx.pot
@@ -0,0 +1,235 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) Odoo S.A.
+# This file is distributed under the same license as the Odoo package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Odoo 19.0\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2026-01-06 19: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"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../extensions/odoo_theme/layout.html:122
+msgid "Edit on GitHub"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/footer.html:3
+msgid "Get Help"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/footer.html:5
+msgid "Contact Support"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/footer.html:6
+msgid "Ask the Odoo Community"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/header.html:10
+msgid "Try Odoo for FREE"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:3
+msgid "Odoo Documentation"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:8
+msgid "User Docs"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:9
+msgid "Discover our guide to help you use and configure the platform, by applications."
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:10
+msgid "Top Apps"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:14
+msgid "Accounting"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:19
+msgid "Inventory"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:24
+msgid "Manufacturing"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:29
+msgid "Point of Sale"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:35
+msgid "Install and Maintain"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:36
+msgid "Learn how to install, deploy and upgrade Odoo on premise or on Odoo.sh."
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:37
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:66
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:93
+msgid "Top Links"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:41
+msgid "Installing Odoo"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:46
+msgid "Bugfix updates"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:51
+msgid "Upgrading Odoo"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:56
+msgid "Odoo.sh: The Odoo Cloud Platform"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:64
+msgid "Developer"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:65
+msgid "Learn to develop in Odoo with the developer tutorials and framework references."
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:70
+msgid "Tutorials"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:75
+msgid "How-to guides"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:80
+msgid "Reference"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:85
+msgid "External API"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:91
+msgid "Contributing"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:92
+msgid "You want to contribute to Odoo but don't know where to start? The tutorials and guidelines are there to help you make Odoo even better."
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:97
+msgid "Coding guidelines"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:102
+msgid "Documentation"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:107
+msgid "Content guidelines"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:4
+msgid "Legal"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:10
+#: ../../extensions/odoo_theme/layout_templates/legal.html:17
+msgid "Licenses"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:25
+msgid "Terms and Conditions"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:34
+msgid "Odoo Enterprise Agreement"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:36
+msgid "Applies to self-hosting, Odoo.SH and Odoo Cloud."
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:40
+#: ../../extensions/odoo_theme/layout_templates/legal.html:42
+#: ../../extensions/odoo_theme/layout_templates/legal.html:59
+#: ../../extensions/odoo_theme/layout_templates/legal.html:61
+#: ../../extensions/odoo_theme/layout_templates/legal.html:78
+#: ../../extensions/odoo_theme/layout_templates/legal.html:80
+msgid "Read"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:43
+#: ../../extensions/odoo_theme/layout_templates/legal.html:62
+#: ../../extensions/odoo_theme/layout_templates/legal.html:81
+msgid "English"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:54
+msgid "Odoo Partnership Agreement"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:73
+msgid "Terms Of Sale"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:90
+msgid "See also"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:93
+msgid "Archive of older agreements"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:99
+msgid "Other legal references"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:105
+msgid "Odoo Cloud Service Level Agreement (SLA)"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:110
+msgid "Odoo Cloud Acceptable Use Policy"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:115
+msgid "Odoo SA’s Privacy Policy"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:120
+msgid "Odoo SA’s GDPR Compliance Guide"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:126
+msgid "Contributor License Agreement"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/legal.html:133
+msgid "German Tax Accounting Standards: Odoo’s guide to GoBD Compliance"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/page_toc.html:2
+msgid "On this page"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/searchbox.html:4
+msgid "What are you looking for?"
+msgstr ""
+
+#: ../../extensions/odoo_theme/search.html:10
+msgid "Please activate JavaScript to enable the search functionality."
+msgstr ""
--- a/locale/sources/websites.pot
+++ b/locale/sources/websites.pot