[IMP] administration: new db manager ui

closes odoo/documentation#15403

Signed-off-by: Thomas Jude Cavazos (thjud) <thjud@odoo.com>
Co-authored-by: larm-odoo <larm@odoo.com>
Co-authored-by: StraubCreative <zst@odoo.com>

content/administration/odoo_online.rst

@@ -2,204 +2,179 @@
 Odoo Online
 ===========
 
-`Odoo Online <https://www.odoo.com/trial>`_ provides private databases which are fully managed and
-hosted by Odoo. It can be used for long-term production or to test Odoo thoroughly, including
-customizations that don't require code.
+`Odoo Online <https://www.odoo.com/trial>`_ offers private databases hosted and managed by Odoo.
+Odoo Online databases can be accessed using any web browser and do not require a local installation.
+They can be used for long-term production or to thoroughly test Odoo, including customizations that
+do not require custom code.
+
+.. tip::
+   To quickly try out Odoo, shared `demo databases <https://demo.odoo.com>`_ are available for
+   testing. No registration is required; however, each database is only available for a few hours.
 
 .. note::
-   Odoo Online is incompatible with custom modules or the Odoo App Store.
+   Odoo Online is incompatible with custom modules or modules from the `Odoo Apps Store
+   <https://apps.odoo.com/apps>`_.
 
-Odoo Online databases are accessed using any web browser and do not require a local installation.
+.. _odoo-online/database-manager:
 
-To quickly try out Odoo, shared `demo <https://demo.odoo.com>`_ instances are available. No
-registration is required, but each instance only lives for a few hours.
+Database manager
+================
 
-Database management
-===================
+To manage an Odoo Online database, open to the `database manager
+<https://www.odoo.com/my/databases>`_ and sign in as the database administrator.
 
-To manage a database, go to the `database manager <https://www.odoo.com/my/databases>`_ and sign in
-as the database administrator.
-
-All the main database management options are available by clicking the database name, except the
-upgrade option, which can be accessed by clicking the **arrow in a circle** icon next to the
-database name. It is only displayed if an upgrade is available.
-
-.. image:: odoo_online/database-manager.png
-   :alt: Accessing the database management options
-
-- :ref:`odoo_online/upgrade`
-- :ref:`odoo_online/duplicate`
-- :ref:`odoo_online/rename`
-- :ref:`odoo_online/download`
-- :ref:`odoo_online/domains`
-- :ref:`odoo_online/tags`
-- :ref:`odoo_online/delete`
-- :ref:`odoo_online/contact-support`
-- :ref:`odoo_online/users`
-- :ref:`odoo_online/web-services`
-
-.. _odoo_online/upgrade:
-
-Upgrade
-=======
-
-Trigger a database upgrade.
-
-.. seealso::
-   For more information about the upgrade process, check out the :ref:`Odoo Online upgrade
-   documentation <upgrade-request-test>`.
-
-.. _odoo_online/duplicate:
-
-Duplicate
-=========
-
-Create an exact copy of the database, which can be used to perform testing without compromising
-daily operations.
-
-.. important::
-   - By checking :guilabel:`For testing purposes`, all external actions (emails, payments, delivery
-     orders, etc.) are disabled by default on the duplicated database.
-   - Duplicated databases expire automatically after 15 days.
-   - A maximum of five duplicates can be made per database. Under extraordinary circumstances,
-     contact `support <https://www.odoo.com/help>`_ to raise the limit.
-
-.. _odoo_online/rename:
-
-Rename
-======
-
-Rename the database and its URL.
-
-.. _odoo_online/download:
-
-Download
-========
-
-Download a ZIP file containing a backup of the database.
-
-.. note::
-   Databases are backed up daily as per the `Odoo Cloud Hosting SLA
-   <https://www.odoo.com/cloud-sla>`_.
-
-.. _odoo_online/domains:
+.. _odoo-online/domain-names:
 
 Domain names
-============
+------------
 
-Use a custom :doc:`domain name </applications/websites/website/configuration/domain_names>` to
-access the database via another URL.
+:doc:`Configure a custom domain name <../applications/websites/website/configuration/domain_names>`
+by selecting a database and clicking :icon:`fa-globe` :guilabel:`Domain Names`.
 
 .. tip::
-   You can :ref:`register a domain name for free <domain-name/register>`.
+   :ref:`Register a domain name for free <domain-name/register>`.
 
-.. _odoo_online/tags:
+.. _odoo-online/tags:
 
 Tags
-====
+----
 
-Add tags to easily identify and sort your databases.
+Add tags to identify and sort databases by selecting a database and clicking :icon:`fa-tags`
+:guilabel:`Tags`. In the dialog box, enter a tag, click the :icon:`fa-plus-circle`
+(:guilabel:`plus`) button, and click :guilabel:`Save`.
 
 .. tip::
-   You can search for tags in the search bar.
+   Search for tags in the :icon:`fa-search` search bar at the top right.
 
-.. _odoo_online/delete:
+.. _odoo-online/hide:
 
-Delete
-======
+Hide
+----
 
-Delete a database instantly.
+Permanently hide the database from the database manager by selecting it and clicking
+:icon:`fa-eye-slash` :guilabel:`Hide`. In the dialog box, click :guilabel:`Yes, I don't need it
+anymore`.
 
-.. danger::
-   Deleting a database means that all data is permanently lost. The deletion is instant and applies
-   to all users. It is recommended to create a backup of the database before deleting it.
+.. Note::
+   It is possible to access a hidden database through its URL.
 
-Carefully read the warning message and only proceed if the implications of deleting a database are
-fully understood.
+.. _odoo-online/manage:
 
-.. image:: odoo_online/delete.png
-   :alt: The warning message displayed before deleting a database
+Manage
+------
+
+Access all other database management options by selecting it and clicking :icon:`fa-gears`
+:guilabel:`Manage`.
+
+Switch plans
+~~~~~~~~~~~~
+
+Switch `pricing plans <https://www.odoo.com/pricing>`_ by clicking :guilabel:`Switch` under the
+desired plan.
+
+.. _odoo-online/upgrade:
+
+Upgrade
+~~~~~~~
+
+Launch a :ref:`database upgrade <upgrade-request-test>` by clicking :guilabel:`Upgrade`.
 
 .. note::
-   - Only an administrator can delete a database.
-   - The database name is immediately made available to anyone.
-   - Deleting a database if it has expired or is linked to a subscription is impossible. In that
-     case, contact `Odoo Support <https://www.odoo.com/help>`_.
+   This option is only displayed when an upgrade is available.
 
-.. _odoo_online/contact-support:
+.. _odoo-online/rename:
 
-Contact us
-==========
+Rename
+~~~~~~
 
-Access the `Odoo.com support page <https://www.odoo.com/help>`_ with the database's details already
-pre-filled.
+Rename and change the URL of a database by clicking :guilabel:`Rename`. In the dialog box, enter a
+:guilabel:`New name` and click :guilabel:`Rename`.
 
-.. _odoo_online/users:
+.. _odoo-online/duplicate:
 
-Invite / remove users
-=====================
+Duplicate
+~~~~~~~~~
 
-To invite users, fill out the new user's email address and click :guilabel:`Invite`. To add multiple
-users, click :guilabel:`Add more users`.
+Create a copy of the database by clicking :guilabel:`Duplicate`. In the dialog box, enter a
+:guilabel:`New name` and click :guilabel:`Duplicate`.
 
-.. image:: odoo_online/invite-users.png
-   :alt: Inviting a user on a database
+.. important::
+   - By default, the :guilabel:`For testing purposes` option is enabled. It disables all external
+     actions (emails, payments, delivery orders, etc.) on the duplicated database.
+   - Duplicates expire after 15 days.
+   - A maximum of five duplicates can be created per database. Under extraordinary circumstances,
+     contact `Odoo Support <https://www.odoo.com/help>`_ to extend the limit.
 
-To remove users, select them and click :guilabel:`Remove`.
+.. _odoo-online/download:
 
-.. seealso::
-   - :doc:`/applications/general/users`
-   - :doc:`odoo_accounts`
+Download a backup
+~~~~~~~~~~~~~~~~~
 
-.. _odoo_online/web-services:
+Download a ZIP file containing a database backup by clicking :guilabel:`Download Backup`.
 
-Web Services
+.. note::
+   - Databases are backed up daily as per the `Odoo Cloud Hosting SLA
+     <https://www.odoo.com/cloud-sla>`_.
+   - If the :guilabel:`Download Backup` option is disabled, it means the database is too large to be
+     downloaded using the database manager. Contact `Odoo Support <https://www.odoo.com/help>`_ to
+     request an alternative download solution.
+
+.. _odoo-online/activity-logs:
+
+View admin activity logs
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+View the logs of all actions taken by Odoo employees or the database administrator on the database
+by clicking :guilabel:`View Admin Activity Logs`.
+
+.. note::
+   Actions taken by Odoo employees are typically the result of requests submitted to Odoo support,
+   done within the context of a quick start project, or necessary to maintain the database.
+
+.. _odoo-online/transfer-ownership:
+
+Transfer ownership
+~~~~~~~~~~~~~~~~~~
+
+Create a support ticket to request a database ownership transfer by clicking :guilabel:`Transfer
+Ownership`.
+
+.. _odoo-online/delete:
+
+Delete
+~~~~~~
+
+Delete the database and close its related subscription by clicking :guilabel:`Delete`. In the dialog
+box, click :guilabel:`Delete`.
+
+.. danger::
+   All the database's data will be deleted instaneously for all users and **cannot be restored**. It
+   is recommended to :ref:`download a backup <odoo-online/download>` before deleting a database.
+
+.. note::
+   After deletion, the database's name becomes available to anyone.
+
+.. _odoo-online/web-services:
+
+Web services
 ============
 
-In order to programmatically retrieve the list of the databases displayed in the
-`database manager <https://www.odoo.com/my/databases>`_, call the method `list` of the model
-`odoo.database` via a :doc:`Web Service </developer/howtos/web_services>` call.
+To retrieve a list of all databases displayed under the `database manager
+<https://www.odoo.com/my/databases>`_ programmatically, call the `list` method of the
+`odoo.database` model via an :doc:`external JSON-2 API <../developer/reference/external_api>` call.
 
-Inspired from the examples provided in the :doc:`Web Services </developer/howtos/web_services>`
-section, this is how to retrieve this list with the library ``xmlrpc.client``::
+.. example::
+   .. code:: python
 
-   import xmlrpc.client
+      import requests
 
-   USER = 'user@domain.tld'
-   APIKEY = 'your_apikey'
+      APIKEY = "your_apikey"
 
-   root = 'https://www.odoo.com/xmlrpc/'
-   uid = xmlrpc.client.ServerProxy(root + 'common').login('openerp', USER, APIKEY)
-   sock = xmlrpc.client.ServerProxy(root + 'object')
-   databases_list = sock.execute('openerp', uid, APIKEY, 'odoo.database', 'list')
-
-And here is the equivalent example with JSON-RPC::
-
-   import json
-   import random
-   import urllib.request
-
-   USER = 'user@domain.tld'
-   APIKEY = 'your_apikey'
-
-   def json_rpc(url, method, params):
-       data = {
-           'jsonrpc': '2.0',
-           'method': method,
-           'params': params,
-           'id': random.randint(0, 1000000000),
-       }
-       req = urllib.request.Request(url=url, data=json.dumps(data).encode(), headers={
-           "Content-Type": "application/json",
-       })
-       reply = json.loads(urllib.request.urlopen(req).read().decode('UTF-8'))
-       if reply.get('error'):
-           raise Exception(reply['error'])
-       return reply['result']
-
-   def call(url, service, method, *args):
-       return json_rpc(url, 'call', {'service': service, 'method': method, 'args': args})
-
-   url = 'https://www.odoo.com/jsonrpc'
-   uid = call(url, 'common', 'login', 'openerp', USER, APIKEY)
-   databases_list = call(url, 'object', 'execute', 'openerp', uid, APIKEY, 'odoo.database', 'list')
+      requests.post(
+          "https://www.odoo.com/json/2/odoo.database/list",
+          headers={
+              "Authorization": f"bearer {APIKEY}",
+              "X-Odoo-Database": "openerp",
+          }
+          json={},
+      )

content/administration/odoo_sh/getting_started/builds.rst

@@ -1,124 +1,137 @@
-
-.. _odoosh-gettingstarted-builds:
-
 ======
 Builds
 ======
 
+In Odoo.sh, a build is a database loaded by an Odoo server (`odoo/odoo
+<https://github.com/odoo/odoo>`_ and `odoo/enterprise <https://github.com/odoo/enterprise>`_)
+running on a specific revision of your project repository in a containerized environment. Its
+purpose is to test the proper behavior of the server, the database, and the features associated with
+that revision.
+
+.. _odoo-sh/builds/overview:
+
 Overview
 ========
 
-In Odoo.sh, a build is considered as a database loaded by an Odoo server
-(`odoo/odoo <https://github.com/odoo/odoo>`_ & `odoo/enterprise
-<https://github.com/odoo/enterprise>`_) running on a specific revision of your project repository in
-a containerized environment. Its purpose is to test the well-behavior of the server, the database
-and the features with this revision.
+.. image:: builds/builds-overview.png
+   :alt: Overiew of the builds
 
-.. image:: builds/interface-builds.png
-   :align: center
+In the :guilabel:`Builds` overview, a row represents a branch, and a cell within that row represents
+a build of that branch.
 
-In this view, a row represents a branch, and a cell of a row represents a build of this branch.
+Most builds are created after pushes to your GitHub repository branches. They can also be created
+through other operations, such as importing a database on Odoo.sh or requesting a rebuild for a
+branch in your project.
 
-Most of the time, builds are created following pushes on your Github repository branches.
-They can be created as well when you do other operations,
-such as importing a database on Odoo.sh or asking a rebuild for a branch in your project.
+Builds can have three possible statuses:
 
-A build is considered successful if no errors or warnings come up during its creation.
-A successful build is highlighted in green.
+- A build is considered **successful** if no errors or warnings occur during its creation.
+  Successful builds are highlighted in **green**.
+- A build is considered **almost successful** if warnings occur, but there are no errors. Almost
+  successful builds are highlighted in **yellow**.
+- A build is considered **failed** if errors occur during its creation. Failed builds are
+  highlighted in **red**.
 
-A build is considered failed if errors come up during its creation.
-A failed build is highlighted in red.
+.. note::
+   Builds do not always create a database from scratch. For instance, when pushing a change on the
+   production branch, the created build starts the server with your new revision and tries to load
+   the current production database on it.
 
-If warnings come up during the creation, but there are no errors, the build is considered almost
-successful. It is highlighted in yellow to notify the developer warnings were raised.
-
-Builds do not always create a database from scratch. For instance, when pushing a change on the
-production branch, the build created just starts the server with your new revision and tries to load
-the current production database on it. If no errors come up, the build is considered successful, and
-otherwise failed.
+.. _odoo-sh/builds/stages:
 
 Stages
 ======
 
+.. _odoo-sh/builds/stages/production:
+
 Production
 ----------
 
-The first build of a production branch creates a database from scratch.
-If this build is successful, this database is considered as the production database of your project.
+The first build of a production branch creates a database from scratch. If this build is successful,
+this database will become the production database of your project.
 
-From then, pushes on the production branch will create new builds that attempt to load the database
-using a server running with the new revision.
+From then on, pushes to the production branch will create new builds that attempt to load the
+database using a server running the new revision.
 
-If the build is successful, or has warnings but no errors, the production database will now run with
-this build, along with the revision associated to this build.
+If the build is successful or almost successful, the production database will run with this build
+and its associated revision.
 
-If the build fails to load or update the database, then the previous successful build is re-used to
-load the database, and therefore the database will run using a server running with the previous
-successful revision.
+If the build fails to load or update the database, the previous successful build is reused to load
+the database. In that case, the database continues to run using the previous successful revision.
 
-The build used to run the production database is always the first of the builds list. If a build
-fails, it is put after the build currently running the production database.
+.. note::
+   The build used to run the production database is always the first in the builds list. If a build
+   fails, it is placed after the build currently running the production database.
+
+.. _odoo-sh/builds/stages/staging:
 
 Staging
 -------
 
-Staging builds duplicate the production database,
-and try to load this duplicate with the revisions of the staging branches.
+Staging builds duplicate the production database and attempt to load this copy using the revisions
+of the staging branches.
 
-Each time you push a new revision on a staging branch, the build created uses a new copy of the
-production database. The databases are not re-used between builds of the same branch. This ensures:
+Each time you push a new revision to a staging branch, the resulting build uses a fresh copy of the
+production database. Databases are not reused between builds of the same branch. This ensures that:
 
-* staging builds use databases that are close to what the production looks like, so you do not make
-  your tests with outdated data,
+- Staging builds use databases that closely match the current production state, so your tests are
+  not performed on outdated data.
+- You can freely experiment within a staging database. When you want to start over with a new copy
+  of the production database, you can request a rebuild.
 
-* you can play around as much as you want in the same staging database, and you can then ask for a
-  rebuild when you want to restart with a new copy of the production.
+However, this also means that if you make configuration changes in a staging database and do not
+apply them in production, those changes will not be present in the next build of the same staging
+branch.
 
-Nevertheless, this means that if you make configuration changes in staging databases and do not
-apply them in the production, they will not be passed on the next build of the same staging branch.
+.. _odoo-sh/builds/stages/development:
 
 Development
 -----------
 
-Development builds create new databases, load the demo data and run the unit tests.
+Development builds create new databases, load the demo data, and run the unit tests.
 
-A build will be considered failed and highlighted in red if tests fail during the installation,
-as they are meant to raise errors if something wrong occurs.
+A build will be considered failed if tests fail during installation, as they are designed to raise
+errors when something is wrong.
 
-If all tests pass, and there is no error, the build will be considered successful.
+If all tests pass and no errors occur, the build is considered successful.
 
-According to the list of modules to install and test, a development build can take up to 1 hour to
-be ready. This is due to the large number of tests set in the default Odoo modules suite.
+.. note::
+   Depending on the list of modules to install and test, a development build can take up to one hour
+   to be ready. This is due to the large number of tests included in the default Odoo module suite.
+
+.. _odoo-sh/builds/stages/features:
 
 Features
 ========
 
-The production branch will always appear first, and then the other branches are ordered by last
-build created. You can filter out the branches.
+The production branch always appears first. Other branches are ordered by the time of their last
+created build. The stage highlighted in purple corresponds to the stage selected in the
+:guilabel:`Branches` menu.
 
-.. image:: builds/interface-builds-branches.png
-   :align: center
+.. tip::
+   You can filter branches using the search bar.
 
-For each branch, you can access the last build's database using the *Connect* link and jump to the
-branch code using the *Github* link. For other branches than the production, you can create a new
-build which will use the latest revision of the branch using the link *rebuild*. This last link is
-not available when there is already a build in progress for the branch.
+.. image:: builds/branches-menu.png
+   :alt: The branches menu
 
-.. image:: builds/interface-builds-build.png
-   :align: center
+For each branch, you can:
 
-For each build, you can access the revision changes using the button with the Github icon. You can
-access the build's database as the administrator using the *Connect* button. Also, you can access
-the database with another user using the *Connect as* button, in the dropdown menu of the *Connect*
-button.
+- Access the latest build's database by clicking :guilabel:`Connect`.
+- Jump to the branch's code by clicking :guilabel:`Github`.
+- Create a new build by clicking :guilabel:`Rebuild`. It uses the latest revision of the branch (it
+  is not available if a build is already in progress for that branch).
 
-.. _odoosh-gettingstarted-builds-download-dump:
+For each build, you can:
 
-.. image:: builds/interface-builds-build-dropdown.png
-   :align: center
+- View the revision changes by clicking the :icon:`fa-github` (:guilabel:`GitHub`) icon.
+- Access the build's database as the administrator by clicking :guilabel:`Connect` or as another
+  user by clicking the :icon:`fa-caret-down` (:guilabel:`More Actions`) button next to
+  :guilabel:`Connect` and selecting :guilabel:`Connect as`.
+- Access the same tools as in the branches view by clicking the :icon:`fa-caret-down`
+  (:guilabel:`More Actions`) button next to :guilabel:`Connect` and selecting :guilabel:`Logs`,
+  :guilabel:`Web Shell`, :guilabel:`Editor`, :guilabel:`Outgoing e-mails` (for the staging and
+  development stages), :guilabel:`Monitoring`, and :guilabel:`Download DB dump` (for the production
+  and staging stages).
 
-.. _odoosh-gettingstarted-builds-dropdown-menu:
-
-In the dropdown menu of the build, you can access the same features than in :ref:`the branches view
-<odoo-sh/branches/tabs>`: *Logs*, *Web Shell*, *Editor*, *Outgoing e-mails*. You also
-have the possibility to *Download a dump* of the build's database.
+.. image:: builds/builds-options.png
+   :alt: A build's options

content/administration/odoo_sh/getting_started/online-editor.rst

@@ -17,7 +17,7 @@ It also gives you the possibility to open terminals, Python consoles, Odoo Shell
 
 You can access the editor of a build through
 :ref:`the branches tabs <odoo-sh/branches/tabs>`,
-:ref:`the builds dropdown menu <odoosh-gettingstarted-builds-dropdown-menu>`
+: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/applications/sales/crm/track_leads/lead_scoring.rst

@@ -2,10 +2,10 @@
 Assign leads with predictive lead scoring
 =========================================
 
-The Odoo *CRM* app can automatically assign leads/opportunities to sales teams and salespeople. A
+The Odoo **CRM** app can automatically assign leads/opportunities to sales teams and salespeople. A
 standard practice is to assign leads based on the probability of winning each lead. Companies can
-prioritize the leads that are more likely to result in successful deals by quickly assigning them
-to the appropriate salespeople.
+prioritize the leads that are more likely to result in successful deals by quickly assigning them to
+the appropriate salespeople.
 
 Odoo automatically calculates the probability of winning each lead using a method called *predictive
 lead scoring*.
@@ -13,12 +13,12 @@ lead scoring*.
 Predictive lead scoring
 =======================
 
-Predictive lead scoring is a machine-learning model that uses historical data from Odoo *CRM* to
+Predictive lead scoring is a machine-learning model that uses historical data from Odoo **CRM** to
 score open leads/opportunities.
 
 As a company processes opportunities through the CRM pipeline, Odoo collects data on which
-opportunities are won and lost. Predictive lead scoring uses this data to predict the probability
-of winning each new lead or opportunity.
+opportunities are won and lost. Predictive lead scoring uses this data to predict the probability of
+winning each new lead or opportunity.
 
 The more opportunities that are sent through the CRM pipeline, the more data Odoo collects,
 resulting in more accurate probabilities.
@@ -48,7 +48,6 @@ The probability of success of each opportunity is displayed on the opportunity f
 automatically as the opportunity progresses through the CRM pipeline.
 
 .. image:: lead_scoring/probability-opportunity-form.png
-   :align: center
    :alt: The probability of success displayed on the opportunity form.
 
 When an opportunity moves to the next stage, its probability of success automatically increases
@@ -59,18 +58,17 @@ according to the predictive lead scoring algorithm.
 Configuration
 -------------
 
-Predictive lead scoring is always active in Odoo *CRM*. However, the variables used to calculate the
-probability of success can be customized in the settings.
+Predictive lead scoring is always active in Odoo **CRM**. However, the variables used to calculate
+the probability of success can be customized in the settings.
 
 To customize the variables used by predictive lead scoring, go to :menuselection:`CRM -->
 Configuration --> Settings`. Under :guilabel:`Predictive Lead Scoring`, click on the
 :guilabel:`Update Probabilities` button.
 
 Then, click on the drop-down menu to choose which variables the predictive lead scoring feature
-will take into account.
+takes into account.
 
 .. image:: lead_scoring/update-probabilities.png
-   :align: center
    :alt: The Update Probabilities window in the Predictive Lead Scoring settings.
 
 Any number of the following variables can be activated:
@@ -90,7 +88,7 @@ Any number of the following variables can be activated:
    optional variables are selected.
 
 Next, click on the date field next to the option :guilabel:`Consider leads created as of the:` to
-select the date from which predictive lead scoring will begin its calculations.
+select the date from which predictive lead scoring begins its calculations.
 
 Lastly, click :guilabel:`Confirm` to save changes.
 
@@ -101,22 +99,21 @@ An opportunity's probability of success can be changed manually on the opportuni
 the probability number to edit it.
 
 .. important::
-   Manually changing the probability removes the automatic probability updates for that
-   opportunity. The probability will no longer update automatically as the opportunity moves
-   through each stage of the pipeline.
+   Manually changing the probability removes the automatic probability updates for that opportunity.
+   The probability no longer automatically updates as the opportunity moves through each stage of
+   the pipeline.
 
 To reactivate automatic probability, click on the gear icon next to the probability percentage.
 
 .. image:: lead_scoring/probability-gear-icon.png
-   :align: center
    :alt: The gear icon used to reactivate automatic probability on an opportunity form.
 
 Assign leads based on probability
 =================================
 
-Odoo *CRM* can assign leads/opportunities to sales teams and salespeople based on specified rules.
-Create assignment rules based on the leads' probability of success to prioritize those that are
-more likely to result in deals.
+Odoo **CRM** can assign leads/opportunities to sales teams and salespeople based on specified rules.
+Create assignment rules based on the leads' probability of success to prioritize those that are more
+likely to result in leads and opportunities.
 
 Configure rule-based assignment
 -------------------------------
@@ -125,8 +122,8 @@ To activate *rule-based assignment*, navigate to :menuselection:`CRM --> Configu
 Settings`, and activate :guilabel:`Rule-Based Assignment`.
 
 The rule-based assignment feature can be set to run :guilabel:`Manually`, meaning an Odoo user must
-manually trigger the assignment, or :guilabel:`Repeatedly`, meaning Odoo will automatically trigger
-the assignment according to the chosen time period.
+manually trigger the assignment, or :guilabel:`Repeatedly`, meaning Odoo automatically triggers the
+assignment according to the chosen time period.
 
 To configure automatic lead assignment, select :guilabel:`Repeatedly` for the :guilabel:`Running`
 section. The frequency of this automatic assignment is customized within the :guilabel:`Repeat
@@ -134,31 +131,32 @@ every` section. Enter a specific number and select a corresponding time period t
 desired interval. Time periods range from :guilabel:`Minutes` to :guilabel:`Weeks`.
 
 .. image:: lead_scoring/rule-based-assignment.png
-   :align: center
    :alt: The Rule-Based Assignment setting in CRM settings.
 
-If rule-based assignment is set to run :guilabel:`Repeatedly`, the assignment can still be
-triggered manually using the circular arrow icon in the :guilabel:`Rule-Based Assignment` settings
-(or using the :guilabel:`Assign Leads` button on the sales team configuration page).
+If :guilabel:`rule-based assignment` is set to run :guilabel:`Repeatedly`, the assignment can still
+be triggered manually using the circular arrow icon in the :guilabel:`Rule-Based Assignment`
+settings, or using the :guilabel:`Assign Leads` button on the sales team configuration page. Once a
+lead has been assigned to a salesperson via this rule, the leads are automatically converted into an
+opportunity by the system.
 
 Configure assignment rules
 --------------------------
 
-Next, configure the *assignment rules* for each sales team and/or salesperson. These rules
-determine which leads Odoo assigns to which people. To get started, navigate to :menuselection:`CRM
---> Configuration --> Sales Teams`, and select a sales team.
+Next, configure the *assignment rules* for each sales team or salesperson. These rules determine
+which leads Odoo assigns to which people. To get started, navigate to :menuselection:`CRM -->
+Configuration --> Sales Teams`, and select a sales team.
 
 On the sales team configuration form, under :guilabel:`Assignment Rules`, click on :guilabel:`Edit
 Domain` to configure the rules that Odoo uses to determine lead assignment for this sales team. The
 rules can include anything that may be relevant for this company or team, and any number of rules
 can be added.
 
-Click :guilabel:`Add Filter` to start creating assignment rules. Click on the :guilabel:`+` sign on
-the right of the assignment rule to add another line. Click on the :guilabel:`x` symbol to remove
-the line.
+Click :guilabel:`Add Filter` to start creating assignment rules. Click on the :icon:`fa-plus-circle`
+sign on the right of the assignment rule to add another line. Click on the :guilabel:`x` symbol to
+remove the line.
 
-To create an assignment rule based on an opportunity's probability of success, click on the far
-left drop-down menu of an assignment rule line, and select :guilabel:`Probability`.
+To create an assignment rule based on an opportunity's probability of success, click on the far left
+drop-down menu of an assignment rule line, and select :guilabel:`Probability`.
 
 From the middle drop-down menu, select the desired equation symbol—most likely the symbol for
 *greater than*, *less than*, *greater than or equal to*, or *less than or equal to*.
@@ -171,7 +169,6 @@ In the far right space, enter the desired number value of the probability. Final
    success of 20% or greater, create a :guilabel:`Domain` line that reads: `Probability >= 20`.
 
    .. image:: lead_scoring/probability-domain.png
-      :align: center
       :alt: Sales team domain set to probability greater than or equal to twenty percent.
 
 Separate assignment rules can also be configured for individual team members. From the sales team
@@ -184,6 +181,6 @@ sales team or salesperson from being assigned leads automatically by Odoo's rule
 feature. If :guilabel:`Skip auto assignment` is activated, the sales team or salesperson can still
 be assigned leads manually.
 
-To manually assign leads to this sales team, click on the :guilabel:`Assign Leads` button at the
-top of the sales team configuration page. This will assign any leads that are currently unassigned
-and match this team's specified domain.
+To manually assign leads to this sales team, click on the :guilabel:`Assign Leads` button at the top
+of the sales team configuration page. This assigns any leads that are currently unassigned and match
+this team's specified domain.

locale/es_419/LC_MESSAGES/finance.po

@@ -16,7 +16,7 @@ msgstr ""
 "Project-Id-Version: Odoo 17.0\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2025-11-18 10:55+0000\n"
-"PO-Revision-Date: 2025-11-22 20:00+0000\n"
+"PO-Revision-Date: 2025-11-25 20:00+0000\n"
 "Last-Translator: \"Fernanda Alvarez (mfar)\" <mfar@odoo.com>\n"
 "Language-Team: Spanish (Latin America) <https://translate.odoo.com/projects/"
 "odoo-17-doc/finance/es_419/>\n"
@@ -26,7 +26,7 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=3; plural=(n == 1) ? 0 : ((n != 0 && n % 1000000 == 0)"
 " ? 1 : 2);\n"
-"X-Generator: Weblate 5.12.2\n"
+"X-Generator: Weblate 5.14.3\n"
 
 #: ../../content/applications/finance.rst:5
 msgid "Finance"
@@ -13536,7 +13536,7 @@ msgstr ""
 
 #: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:102
 msgid "Analytic distribution on invoices or bills"
-msgstr "Distribición analícia en facturas de cliente o de proveedor"
+msgstr "Distribución analítica en las facturas de cliente o de proveedor"
 
 #: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:104
 msgid ""