[MOV] ecommerce: moving product management page

taskid-4056328

content/applications/hr/recruitment.rst

@@ -191,8 +191,8 @@ Odoo:
 - :ref:`Initial Qualification <recruitment/initial-qualification>`
 - :ref:`First Interview <recruitment/first-interview>`
 - :ref:`Second Interview <recruitment/second-interview>`
-- :ref:`Contract Proposal <recruitment/contract-proposal>`
-- :ref:`Contract Signed <recruitment/contract-signed>`
+- :doc:`Contract Proposal <recruitment/offer_job_positions>`
+- :ref:`Contract Signed <recruitment/offer_job_positions/contract-signed>`
 
 The last column, :guilabel:`Contract Signed`, is folded by default. Folded columns appear gray, and
 the applicants in it are hidden from view. To expand the folded stage and view the applicant cards
@@ -542,141 +542,18 @@ activities or emails configured. The recruiter can now :doc:`schedule a second i
 <recruitment/schedule_interviews>` with the applicant, following the same process as the first
 interview.
 
-.. _recruitment/contract-proposal:
-
-Contract proposal
------------------
-
-When the applicant has passed the interview stages and an offer is ready to be sent, they can be
-moved to the :guilabel:`Contract Proposal` stage. Drag and drop the applicant's card to the
-:guilabel:`Contract Proposal` stage, or click on the :guilabel:`Contract Proposal` stage button at
-the top-right of the individual applicant's card.
-
-The next step is to send an offer to the applicant. On the applicant's card, click the
-:guilabel:`Generate Offer` button. A :guilabel:`Generate a Simulation Link` pop-up appears. Most
-fields are pre-populated with information from the job position. If any necessary fields are blank,
-enter the relevant information in the fields.
-
-.. note::
-   Not all fields may appear on the :guilabel:`Generate a Simulation Link` pop-up. Depending on the
-   localization setting for the company and the applications installed, some fields may not appear.
-   For example if the *Fleet* application is not installed, any fields related to vehicles do not
-   appear on the pop-up window.
-
-Universal fields
-~~~~~~~~~~~~~~~~
-
-The following fields appear for all offers sent to applicants regardless of localization settings.
-
-- :guilabel:`Contract Template`: the template currently being used to populate the
-  :guilabel:`Generate a Simulation Link` pop-up window. To modify the template, click the
-  :guilabel:`Internal link` icon to the right of the drop-down arrow. Make any changes, then click
-  :guilabel:`Save & Close`. A different :guilabel:`Contract Template` can be selected using the
-  drop-down menu.
-- :guilabel:`Job Position`: the name of the :guilabel:`Job Position` being offered to the
-  applicant. The selections available in the drop-down menu correspond to the :guilabel:`Job
-  Positions` configured on the main *Recruitment* dashboard.
-- :guilabel:`Job Title`: the specific name of the position being offered to the applicant.
-- :guilabel:`Department`: the :guilabel:`Department` the job position falls under.
-- :guilabel:`Contract Start Date`: the date the contract takes effect. The default date is the
-  current date. To modify the date, click the drop-down to reveal a calendar. Use the :guilabel:`<
-  (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired
-  month, then click on the :guilabel:`day` to select the date.
-- :guilabel:`Yearly Cost`: the annual salary being offered.
-- :guilabel:`Link Expiration Date`: job offers are only valid for a specific period of time. The
-  default expiration date is 30 days. Modify the expiration date, if desired.
-
-Send offer
-~~~~~~~~~~
-
-When the information is all updated, click :guilabel:`Send By Email` to send the offer to the
-applicant.
-
-If the applicant does not have an email address listed on their applicant card, a warning appears in
-a red box at the bottom of the :guilabel:`Generate a Simulation Link` pop-up window, stating
-:guilabel:`The applicant does not have a valid email set. The Offer Link won't be able to be
-completed.` Click :guilabel:`Discard`, enter an email on the applicant's card, then click the
-:guilabel:`Generate Offer` button again.
-
-An email pop-up window loads. The default :guilabel:`Recruitment: Your Salary Package` email
-template is used, and the :guilabel:`Recipients`, :guilabel:`Subject`, and email body are
-pre-populated based on the email template.
-
-If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer
-window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email.
-The attachment loads, and is listed above the :guilabel:`Attachments` button.
-
-Once the email is ready to send, click :guilabel:`Send`.
-
-.. note::
-   To send an offer, ensure the *Sign* application is installed. This is necessary so the offer can
-   be sent to the applicant by the recruiter. The applicant does not need any software installed.
-
-.. image:: recruitment/send-offer.png
-   :align: center
-   :alt: Send an email to the applicant with a link to the offered salary.
-
-Configure your package
-~~~~~~~~~~~~~~~~~~~~~~
-
-The email template includes a :guilabel:`Configure your package` button. This link takes the
-applicant to a webpage where they can modify the proposed salary package, and enter their personal
-information.
-
-Once the applicant is hired, the personal information entered on the webpage is imported to their
-employee record, when created.
-
-If applicable, the applicant can modify their salary package. This option is not available for all
-localizations. Depending on where the company is located, this option may not be available.
-
-Once all the information is completed, the applicant accepts the offer by clicking the
-:guilabel:`Review Contract & Sign` button to accept the contract and sign it using the *Sign*
-application.
-
-.. _recruitment/contract-signed:
-
-Contract signed
----------------
-
-Once the applicant has accepted the offer and signed the contract, the next step is to move the
-applicant to the :guilabel:`Contract Signed` stage. To move the applicant to the next stage, drag
-and drop the applicant's card to the :guilabel:`Contract Signed` stage, or click the
-:guilabel:`More` button at the top of the applicant's card to reveal the :guilabel:`Contract
-Signed` stage button at the top of the individual applicant's card, and click :guilabel:`Contract
-Signed`.
-
-The :guilabel:`Contract Signed` stage is folded in the Kanban view, but the card may still be
-dragged and dropped into that stage.
-
-Once the applicant's card moves to the :guilabel:`Contract Signed` stage, a green :guilabel:`HIRED`
-banner appears in the top-right of the applicant's card.
-
-.. image:: recruitment/hired.png
-   :align: center
-   :alt: Hired banner in the top right corner of applicant card.
-
-Create employee
-~~~~~~~~~~~~~~~
-
-Once the applicant has been hired, the next step is to create an employee record of them. On the
-applicant's card, click the :guilabel:`Create Employee` button in the top-left. An employee form
-appears, and any information from the applicant's card that can be imported into the employee card
-appears in the form.
-
-Fill out the rest of the form. For detailed information on the fields, refer to the
-:doc:`employees/new_employee` documentation. When done, the employee record is saved in the
-*Employees* app.
-
 .. seealso::
    - recruitment/new_job
-   - recruitment/schedule_interviews
    - recruitment/add-new-applicants
+   - recruitment/schedule_interviews
+   - recruitment/offer_job_positions
    - recruitment/refuse_applicant
 
 .. toctree::
    :titlesonly:
 
    recruitment/new_job
-   recruitment/schedule_interviews
    recruitment/add-new-applicants
+   recruitment/schedule_interviews
+   recruitment/offer_job_positions
    recruitment/refuse_applicant

content/applications/hr/recruitment/offer_job_positions.rst

@@ -0,0 +1,160 @@
+===================
+Offer job positions
+===================
+
+Once an applicant has successfully passed the various interview stages, the recruitment team is
+ready to send an offer for employment. The next step is to send the applicant a contract.
+
+.. seealso::
+   Refer to the :doc:`recruitment <../recruitment>` documentation for details on the various stages
+   of the recruitment process.
+
+Contract proposal
+=================
+
+When an offer is ready to be sent, first open the applicant's card by navigating to the
+:menuselection:`Recruitment app`, and clicking on the desired job position card.
+
+From the resulting :guilabel:`Job Positions` Kanban view, the corresponding applicant card can be
+dragged-and-dropped to the :guilabel:`Contract Proposal` stage. Or, click into the desired
+applicant's card, and click the :guilabel:`Contract Proposal` stage, located in the status bar in
+the top-right of the applicant's form.
+
+The next step is to send an offer to the applicant. Start by selecting the desired applicant's card
+to open their applicant form.
+
+On the applicant's form, click the :guilabel:`Generate Offer` button. A :guilabel:`Generate a
+Simulation Link` pop-up window appears.
+
+Most fields are pre-populated with information from the job position. If any necessary fields are
+blank, or if any information needs to be updated, enter, or update, the relevant information in the
+corresponding fields.
+
+.. note::
+   Depending on the localization setting for the company, and which applications are installed, some
+   fields may not appear in the :guilabel:`Generate a Simulation Link` pop-up window.
+
+   For example, if the *Fleet* application is **not** installed, any fields related to vehicles do
+   **not** appear.
+
+Universal fields
+----------------
+
+The following fields appear in the :guilabel:`Generate a Simulation Link` pop-up window, regardless
+of the localization.
+
+- :guilabel:`Contract Template`: the template currently being used to populate the
+  :guilabel:`Generate a Simulation Link` pop-up window. Use the drop-down menu to select a different
+  :guilabel:`Contract Template`, if desired.
+
+  .. note::
+     To modify the template, hover over the current template name, and click the :icon:`oi-launch`
+     :guilabel:`Internal link` icon that appears to the right of the field. Make any desired
+     changes, then click :guilabel:`Save & Close`.
+
+- :guilabel:`Job Position`: the name of the :guilabel:`Job Position` being offered to the applicant.
+  The selections available in the drop-down menu correspond to the job position configured on the
+  main *Recruitment* dashboard.
+- :guilabel:`Job Title`: the selected :guilabel:`Job Position` populates this field, by default.
+  The title can be modified to suit the specific applicant's position and provide more details.
+
+  .. example::
+     An applicant is offered a marketing manager job at a shoe company, specifically for the
+     children's line.
+
+     The :guilabel:`Job Position` selected from the drop-down menu is `Marketing Manager`, and the
+     :guilabel:`Job Title` is modified for their specific responsibilities, `Marketing Manager:
+     Children's Shoes`.
+
+- :guilabel:`Department`: the department the job position falls under.
+- :guilabel:`Contract Start Date`: the date the contract takes effect. The default date is the
+  current date. To modify the date, click on the displayed date to reveal a calendar popover window.
+  Navigate to the desired month, then click the day to select the date.
+- :guilabel:`Yearly Cost`: the annual salary being offered.
+- :guilabel:`Link Expiration Date`: the number of days the job offer is valid. The default
+  expiration date is `30` days. Modify the expiration date, if desired.
+
+Send offer
+----------
+
+Once the :guilabel:`Generate a Simulation Link` pop-up window is complete, click :guilabel:`Send By
+Email` to reveal an email pop-up window.
+
+.. important::
+   If the applicant does not have an email address listed on their applicant card, a warning appears
+   in a red box at the bottom of the :guilabel:`Generate a Simulation Link` pop-up window, stating:
+   :guilabel:`The applicant does not have a valid email set. The Offer Link won't be able to be
+   completed.` Click :guilabel:`Discard`, then enter an email on the applicant's card. Once an email
+   is entered, click the :guilabel:`Generate Offer` button, and the email pop-up window loads again.
+
+The default :guilabel:`Recruitment: Your Salary Package` email template is used (set in the
+:guilabel:`Load template` field), and the :guilabel:`Recipients`, :guilabel:`Subject`, and email
+body are pre-populated based on the email template.
+
+If any attachments need to be added, click the :icon:`fa-paperclip` :guilabel:`Attachments` button,
+and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to
+attach it to the email. The attachment loads, and is listed above the :icon:`fa-paperclip`
+:guilabel:`Attachments` button.
+
+Once the email is ready to send, click :guilabel:`Send`. The email pop-up window closes, and an
+:guilabel:`Offers` smart button appears at the top of the applicant's card.
+
+.. note::
+   To send an offer, ensure the *Sign* application is installed. This is necessary, so the offer can
+   be sent to the applicant by the recruiter, and they can actually sign the offer. The applicant
+   does **not** need any software installed to sign the offer.
+
+.. image:: offer_job_positions/send-offer.png
+   :align: center
+   :alt: Send an email to the applicant with a link to the offered salary.
+
+Configure your package
+----------------------
+
+If applicable, the applicant can modify their salary package. This option is not available for all
+localizations. Depending on where the company is located, this option may not be available.
+
+The email template includes a :guilabel:`Configure your package` button. This link takes the
+applicant to a webpage, where they can modify the proposed salary package, and enter their personal
+information.
+
+Once the applicant is hired, the personal information entered on the webpage is imported to their
+employee record, when created.
+
+Once all the information is completed, the applicant can then accept the offer by clicking the
+:guilabel:`Review Contract & Sign` button to accept the contract, and sign it using the *Sign*
+application.
+
+.. _recruitment/offer_job_positions/contract-signed:
+
+Contract signed
+===============
+
+Once the applicant has accepted the offer and signed the contract, the next step is to move the
+applicant to the :guilabel:`Contract Signed` stage. This stage is folded in the Kanban view, by
+default.
+
+To move the applicant to that stage, drag-and-drop the applicant's card to the :guilabel:`Contract
+Signed` stage. If the stage is not visible, click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)`
+button to the right of :guilabel:`Contract Proposal` on the applicant's form, and click
+:guilabel:`Contract Signed` from the resulting drop-down menu.
+
+Once the applicant is moved to the :guilabel:`Contract Signed` stage, a green :guilabel:`HIRED`
+banner appears in the top-right of the applicant's card and form.
+
+.. image:: offer_job_positions/hired.png
+   :align: center
+   :alt: Hired banner in the top right corner of applicant card.
+
+Create employee
+===============
+
+Once the applicant has been hired, the next step is to create their employee record. Click the
+:guilabel:`Create Employee` button in the top-left corner of the hired applicant's form.
+
+An employee form appears, with information from the applicant's card, and the employee contract.
+
+Fill out the rest of the employee form. For detailed information on the fields, refer to the
+:doc:`../employees/new_employee` documentation.
+
+Once completed, the employee record is saved in the *Employees* app.

content/applications/hr/referrals.rst

@@ -22,6 +22,8 @@ the :ref:`reporting <referrals/reporting>` and configurations menus. For more in
 and access rights, refer to these documents: :doc:`../general/users` and
 :doc:`../general/users/access_rights`.
 
+.. _referrals/onboarding:
+
 Onboarding
 ==========
 
@@ -168,76 +170,6 @@ any changes, and revert to the original content.
    original image. To revert to the original image, the *Referrals* application must be *uninstalled
    then reinstalled.*
 
-Referral points
-===============
-
-The referral program is based on earning points that are then exchanged for rewards. On the main
-*Referrals* application dashboard, the top displays a summary of the user's current points. The left
-side of the summary displays the total points earned, and the right side displays the points that
-are available to spend.
-
-To see the various referrals and the points earned for each, click on one of the buttons directly
-beneath the avatars. The options are :guilabel:`Referrals`, :guilabel:`Ongoing`, and
-:guilabel:`Successful`.
-
-The current number of referrals who are still active in the recruitment pipeline, and have not yet
-been hired or refused, appear above the :guilabel:`Ongoing` button. The number of referrals who have
-been hired appear above the :guilabel:`Successful` button. The total number of referrals (both the
-ongoing and successful referrals combined) appear above the :guilabel:`Referrals` button.
-
-.. note::
-   To view the referrals associated with each of the categories, :guilabel:`Referrals`,
-   :guilabel:`Ongoing`, and :guilabel:`Successful`, click on the corresponding button. All the
-   referrals for that specific category are displayed.
-
-My referrals
-------------
-
-To see all the referrals (both ongoing and successful) click the :guilabel:`Referrals` button. A
-:guilabel:`My Referral` window loads. This screen displays all the referrals, with each referral in
-its own referral card.
-
-A successful referral displays a green :guilabel:`Hired` banner in the top-right corner of the card.
-Referrals that are in process display a purple :guilabel:`In Progress` banner in the top-right
-corner.
-
-Each referral card lists the name of the applicant, the subject/application title (as it appears on
-the applicant card in the *Recruitment* app), the name of the job position, the person responsible
-for filling the role (recruiter), and the points earned. For referrals that have been hired, the
-selected avatar also appears on the card.
-
-.. image:: referrals/referrals.png
-   :align: center
-   :alt: Two referral cards, one hired and one in-progress.
-
-Points
-~~~~~~
-
-The points that can be earned for a referral are the same across all job positions. Each stage of
-the recruitment process has corresponding points assigned to it. The stages listed correspond to the
-stages configured in the *Recruitment* application.
-
-On each individual referral card, beneath the points earned is a bar chart that displays how many
-points have been earned out of the total possible points that can be earned if the applicant is
-hired.
-
-Beneath the bar chart is a list of the various recruitment stages and the points earned when the
-referral moves to that stage. If a stage has been achieved and the points have been earned, a green
-check mark appears next to the stage.
-
-.. example::
-   The pre-configured point structure for referrals is as follows:
-
-   - :guilabel:`Initial Qualification`: 1 point
-   - :guilabel:`First Interview`: 20 points
-   - :guilabel:`Second Interview`: 9 points
-   - :guilabel:`Contract Proposal`: 5 points
-   - :guilabel:`Contract Signed`: 50 points
-
-   The total points earned for a referral that is hired is 85 points. Modifications of the points
-   earned for each stage are done in the *Recruitment* application. Refer to the
-   :ref:`Recruitment <recruitment/modify-stages>` documentation to modify the points for each stage.
-
 .. _referrals/levels:
 
 Levels
@@ -356,11 +288,13 @@ spreadsheet from the drop-down menu, or select :guilabel:`New Spreadsheet`. Clic
 
 .. seealso::
    - :doc:`referrals/share_jobs`
+   - :doc:`referrals/points`
    - :doc:`referrals/rewards`
    - :doc:`referrals/alerts`
 
 .. toctree::
 
    referrals/share_jobs
+   referrals/points
    referrals/rewards
    referrals/alerts

content/applications/hr/referrals/points.rst

@@ -0,0 +1,72 @@
+===============
+Referral points
+===============
+
+The *Referrals* application allows employees to earn points that are then exchanged for
+:doc:`rewards <rewards>`.
+
+Current referral points can be viewed on the main *Referrals* app dashboard, which appears when the
+application is opened, after the :ref:`onboarding <referrals/onboarding>` slides have been viewed or
+skipped.
+
+At the top, a summary of the user's current points is displayed. The left side of the summary
+displays the :guilabel:`Total` points earned, and the right side displays the points that are
+available :guilabel:`To Spend`.
+
+To view the various referral stages, and their respective earned points, click one of the referral
+statuses beneath the avatar. The options are: :guilabel:`Referrals`, :guilabel:`Ongoing`, and
+:guilabel:`Successful`.
+
+The current number of referrals that are still active in the recruitment pipeline, but have not yet
+been hired or refused, appear above :guilabel:`Ongoing`. The number of referrals that have been
+hired, appear above :guilabel:`Successful`. The total number of referrals, both the ongoing and
+successful referrals combined, appears above :guilabel:`Referrals`.
+
+My referrals
+============
+
+To see all the referrals, both ongoing and successful, click :guilabel:`Referrals`. The
+:guilabel:`My Referral` screen page displays all the referrals, with each individual referral housed
+in its own referral card.
+
+A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` badge in the top-right
+corner of the card, along with a vertical green stripe on the left-side of the card. Referrals that
+are in process have a purple :guilabel:`In Progress` badge in the top-right corner.
+
+Each referral card lists the name of the applicant, the subject/application title as it appears on
+the applicant card in the *Recruitment* app, the name of the job position, the person responsible
+for filling the role (i.e. the recruiter), and the points earned.
+
+For referrals that have been hired, the selected avatar also appears on the card.
+
+.. image:: points/referrals.png
+   :align: center
+   :alt: Two referral cards, one hired and one in-progress.
+
+Points
+------
+
+The points that can be earned for a referral are the same across all job positions. Each stage of
+the recruitment process has corresponding points assigned to it. The stages listed correspond to the
+stages configured in the *Recruitment* application.
+
+On each individual referral card, beneath the points earned, is a progress bar that displays how
+many points have been earned out of the total possible points that can be earned, if the applicant
+is hired.
+
+Beneath the bar chart is a list of the various recruitment stages, and the points earned when the
+referral moves to that stage. If a stage has been achieved, and the points have been earned, a green
+:icon:`fa-check` :guilabel:`(checkmark)` appears next to the stage.
+
+.. note::
+   The preconfigured point structure for referrals is as follows:
+
+   - :guilabel:`Initial Qualification`: 1 point
+   - :guilabel:`First Interview`: 20 points
+   - :guilabel:`Second Interview`: 9 points
+   - :guilabel:`Contract Proposal`: 5 points
+   - :guilabel:`Contract Signed`: 50 points
+
+   The default total points earned for a referral that is hired is 85 points. Modifications of the
+   points earned for each stage are made in the *Recruitment* application. Refer to the
+   :ref:`Recruitment <recruitment/modify-stages>` documentation to modify the points for each stage.

content/applications/hr/time_off.rst

@@ -8,7 +8,7 @@ Odoo's *Time Off* application serves as a centralized hub for all time-off-relat
 application manages requests, balances, allocations, approvals, and reports.
 
 Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see an overview of their
-requests and time off balances. Managers can :ref:`allocate time off <time_off/allocate>` to
+requests and time off balances. Managers can :doc:`allocate time off <time_off/allocations>` to
 individuals, teams, or the whole company, and :ref:`approve time off requests
 <time_off/manage-time-off>`.
 
@@ -429,124 +429,6 @@ Enter the following information on that new line:
    :align: center
    :alt: The Mandatory Days section with three configured days.
 
-.. _time_off/allocate:
-
-Allocate time off
-=================
-
-Once time off types and accrual plans have been configured, the next step is to allocate, or give,
-time off to employees. This section is only visible to users who have either :guilabel:`Time Off
-Officer` or :guilabel:`Administrator` access rights for the *Time Off* application.
-
-To create a new allocation, navigate to :menuselection:`Time Off app --> Management -->
-Allocations`.
-
-This presents a list of all current allocations, including their respective statuses.
-
-Click :guilabel:`New` to allocate time off, and a blank allocation form appears.
-
-After entering a name for the allocation on the first blank field of the form, enter the following
-information:
-
-- :guilabel:`Time Off Type`: using the drop-down menu, select the type of time off that is being
-  allocated to the employees.
-- :guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual
-  Allocation`. If the allocation is **not** based on an accrual plan, select :guilabel:`Regular
-  Allocation`.
-- :guilabel:`Accrual Plan`: if :guilabel:`Accrual Allocation` is selected for the
-  :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears. Using the drop-down menu,
-  select the accrual plan with which the allocation is associated. An accrual plan **must** be
-  selected for an :guilabel:`Accrual Allocation`.
-- :guilabel:`Validity Period/Start Date`: if :guilabel:`Regular Allocation` is selected for the
-  :guilabel:`Allocation Type`, this field is labeled :guilabel:`Validity Period`. If
-  :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this field is
-  labeled :guilabel:`Start Date`.
-
-  The current date populates the first date field by default. To select another date, click on the
-  pre-populated date to reveal a popover calendar window. Navigate to the desired start date for the
-  allocation, and click on the date to select it.
-
-  If the allocation expires, select the expiration date in the next date field. If the time off does
-  *not* expire, leave the second date field blank. `No Limit` appears in the field if no date is
-  selected.
-
-  If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this second
-  field is labeled :guilabel:`Run until`.
-- :guilabel:`Allocation`: enter the amount of time that is being allocated to the employees. This
-  field displays the time in either :guilabel:`Hours` or :guilabel:`Days`, depending on how the
-  selected :ref:`Time Off Type <time_off/time-off-types>` is configured (in hours or days).
-- :guilabel:`Mode`: using the drop-down menu, select how the allocation is assigned. This selection
-  determines who receives the time off allocation. The options are :guilabel:`By Employee`,
-  :guilabel:`By Company`, :guilabel:`By Department`, or :guilabel:`By Employee Tag`.
-
-  Depending on what is selected for the :guilabel:`Mode`, this following field is labeled either:
-  :guilabel:`Employees`, :guilabel:`Company`, :guilabel:`Department`, or :guilabel:`Employee Tag`.
-
-  Using the drop-down menu, indicate the specific employees, company, department, or employee tags
-  who are receiving this time off.
-
-  Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`.
-
-  Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`.
-- :guilabel:`Add a reason...`: if any description or note is necessary to explain the time off
-  allocation, enter it in this field at the bottom of the form.
-
-.. image:: time_off/new-allocation.png
-   :align: center
-   :alt: A new allocation form with all the fields filled out for the annual two week vacation
-         granted to all employees.
-
-.. _time_off/request-allocation:
-
-Request allocation
-==================
-
-If an employee has used all their time off, or is going to run out of time off, they can request an
-allocation for additional time. Allocations can be requested in one of two ways, either from the
-:ref:`Dashboard <time_off/dashboard>` or the :ref:`My Allocations <time_off/my-allocations>` view.
-
-To create a new allocation request, click either the :guilabel:`New Allocation Request` button on
-the main *Time Off* dashboard, or the :guilabel:`New` button in the :guilabel:`My Allocations` list
-view. Both buttons open a new allocation request form.
-
-.. note::
-   Both :guilabel:`New` buttons open a :guilabel:`New Allocation` request form, but when requested
-   from the :guilabel:`Dashboard`, the form appears in a modal. When requested from the
-   :guilabel:`My Allocations` list view, the screen navigates to a new allocation request page,
-   instead.
-
-Enter the following information on the :guilabel:`New Allocation` request form:
-
-- :guilabel:`Time Off Type`: select the type of time off being requested for the allocation from the
-  drop-down menu. After a selection is made, the title updates with the time off type.
-- :guilabel:`Validity Period`: this field **only** appears if requesting an allocation with a time
-  off type that has the :guilabel:`Take Time Off in` field :ref:`configured
-  <time_off/time-off-officer>` to either :guilabel:`Day` or :guilabel:`Half Day`. This field does
-  **not** appear if the :guilabel:`Take Time Off in` field is set to :guilabel:`Hours`.
-
-  Using the calendar selector, select a start and end date the allocation is valid for. By default,
-  the current date populates the first field, and :guilabel:`No Limit` populates the second field.
-
-  Adjust both of these dates, if desired.
-- :guilabel:`Allocation`: enter the amount of time being requested in this field. The format is
-  presented in either days or hours, depending on how the time off type is configured. Once this
-  field is populated, the name of the allocation request is updated to include the amount of time
-  being requested.
-- :guilabel:`Add a reason...`: enter a description for the allocation request. This should include
-  any details that managers and approvers may need in order to approve the request.
-
-If the request was created from the :guilabel:`Dashboard`, click the :guilabel:`Save & Close` button
-to save the information and submit the request.
-
-If the form was completed from the :guilabel:`My Allocations` list view, the information is
-automatically saved as it is entered. However, the form can be saved manually at any time by
-clicking the *save manually* button, represented by a :guilabel:`(cloud upload)` icon.
-
-.. image:: time_off/allocation-request.png
-   :align: center
-   :alt: An allocation request form filled out for an employee requesting an additional week of
-         sick time.
-
 Overview
 ========
 
@@ -664,6 +546,7 @@ detailed information on the reports, and their various options, refer to the :do
 <../essentials/reporting>` documentation.
 
 .. seealso::
+   - :doc:`time_off/allocations`
    - :doc:`time_off/request_time_off`
    - :doc:`time_off/my_time`
    - :doc:`time_off/management`
@@ -671,6 +554,7 @@ detailed information on the reports, and their various options, refer to the :do
 .. toctree::
    :titlesonly:
 
+   time_off/allocations
    time_off/request_time_off
    time_off/my_time
    time_off/management

content/applications/hr/time_off/allocations.rst

@@ -0,0 +1,118 @@
+===========
+Allocations
+===========
+
+Once :ref:`time off types <time_off/time-off-types>` and :ref:`accrual plans
+<time_off/accrual-plans>` have been configured, the next step is to *allocate*, or give, time off to
+employees.
+
+The *Allocations* section of the *Time Off* app is **only** visible to users who have either
+:guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for the *Time Off*
+application. For more information on access rights, refer to the :doc:`access rights
+<../../general/users/access_rights/>` documentation.
+
+Allocate time off
+=================
+
+To create a new allocation, navigate to :menuselection:`Time Off app --> Management -->
+Allocations`.
+
+This presents a list of all current allocations, including their respective statuses.
+
+Click :guilabel:`New` to allocate time off, and a blank allocation form appears.
+
+After entering a name for the allocation on the first blank field of the form, enter the following
+information:
+
+- :guilabel:`Time Off Type`: using the drop-down menu, select the type of time off that is being
+  allocated to the employees.
+- :guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual
+  Allocation`. If the allocation is **not** based on an :ref:`accrual plan
+  <time_off/accrual-plans>`, select :guilabel:`Regular Allocation`.
+- :guilabel:`Accrual Plan`: if :guilabel:`Accrual Allocation` is selected for the
+  :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears. Using the drop-down menu,
+  select the accrual plan with which the allocation is associated. An accrual plan **must** be
+  selected for an :guilabel:`Accrual Allocation`.
+- :guilabel:`Validity Period/Start Date`: if :guilabel:`Regular Allocation` is selected for the
+  :guilabel:`Allocation Type`, this field is labeled :guilabel:`Validity Period`. If
+  :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this field is
+  labeled :guilabel:`Start Date`.
+
+  The current date populates the first date field, by default. To select another date, click on the
+  pre-populated date to reveal a popover calendar window. Navigate to the desired start date for the
+  allocation, and click on the date to select it.
+
+  If the allocation expires, select the expiration date in the next date field. If the time off does
+  *not* expire, leave the second date field blank. :guilabel:`No Limit` appears in the field if no
+  date is selected.
+
+  If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this second
+  field is labeled :guilabel:`Run until`.
+- :guilabel:`Allocation`: enter the amount of time that is being allocated to the employees. This
+  field displays the time in either :guilabel:`Hours` or :guilabel:`Days`, depending on how the
+  selected :ref:`Time Off Type <time_off/time-off-types>` is configured.
+- :guilabel:`Mode`: using the drop-down menu, select how the allocation is assigned. This selection
+  determines who receives the time off allocation. The options are :guilabel:`By Employee`,
+  :guilabel:`By Company`, :guilabel:`By Department`, or :guilabel:`By Employee Tag`.
+
+  Depending on what is selected for the :guilabel:`Mode`, the following field is labeled either:
+  :guilabel:`Employees`, :guilabel:`Company`, :guilabel:`Department`, or :guilabel:`Employee Tag`.
+
+  Using the drop-down menu, indicate the specific employees, company, department, or employee tags
+  receiving this time off.
+
+  Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`.
+
+  Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`.
+- :guilabel:`Add a reason...`: if any description or note is necessary to explain the time off
+  allocation, enter it in this field at the bottom of the form.
+
+.. image:: allocations/new-allocation.png
+   :align: center
+   :alt: A new allocation form with all the fields filled out for the annual two week vacation
+         granted to all employees.
+
+.. _time_off/request-allocation:
+
+Request allocation
+==================
+
+If an employee has used all their time off, or will run out of time off, they can request an
+allocation for additional time. Allocations can be requested in one of two ways, either from the
+:ref:`Dashboard <time_off/dashboard>` or the :ref:`My Allocations <time_off/my-allocations>` view.
+
+To create a new allocation request, click either the :guilabel:`New Allocation Request` button on
+the main *Time Off* dashboard, or the :guilabel:`New` button in the :guilabel:`My Allocations` list
+view. Both buttons open a new allocation request form.
+
+.. note::
+   Both options open a new allocation request form, but when requested from the
+   :guilabel:`Dashboard`, the form appears in a pop-up window. When requested from the
+   :guilabel:`My Allocations` list view, the screen navigates to a new allocation request page,
+   instead.
+
+Enter the following information on the new allocation request form:
+
+- :guilabel:`Time Off Type`: select the type of time off being requested for the allocation from the
+  drop-down menu. After a selection is made, the title updates with the time off type.
+- :guilabel:`Validity Period`: using the calendar selector, select a start and end date the
+  allocation is valid for. By default, the current date populates the first field, and :guilabel:`No
+  Limit` populates the second field. Adjust both of these dates, if desired.
+- :guilabel:`Allocation`: enter the amount of time being requested in this field. The format is
+  presented in either :guilabel:`Days` or :guilabel:`Hours`, depending on how the :guilabel:`Time
+  Off Type` is configured. Once this field is populated, the name of the allocation request is
+  updated to include the amount of time being requested.
+- :guilabel:`Add a reason...`: enter a description for the allocation request. This should include
+  any details that approvers may need to approve the request.
+
+If the request was created from the :guilabel:`Dashboard`, click the :guilabel:`Save & Close` button
+on the :guilabel:`New Allocation` pop-up window to save the information and submit the request.
+
+If the form was completed from the :guilabel:`My Allocations` list view, the information is
+automatically saved as it is entered. However, the form can be saved manually at any time by
+clicking the :icon:`fa-cloud-upload` :guilabel:`(cloud upload)` icon.
+
+.. image:: allocations/allocation-request.png
+   :align: center
+   :alt: An allocation request form filled out for an employee requesting an additional week of
+         sick time.

content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst

@@ -26,7 +26,13 @@ To begin, go to the `Bpost website <https://parcel.bpost.be/en/home/business>`_
 into, the company's Bpost business account. When creating the Bpost account, have the company's VAT
 number and mobile phone number ready.
 
-Follow the website's steps to complete registration, and sign up for shipping services.
+Follow the website's steps to complete registration, and sign up for shipping services. Doing so
+submits a request to enter a contractual business relationship between the company and Bpost.
+
+.. important::
+   Odoo **cannot** be integrated with `non-business Bpost
+   <https://bpost.freshdesk.com/support/solutions/articles/174847-account-id-and-passphrase>`_
+   accounts.
 
 After completing the setup, get the Bpost account ID and passphrase, by navigating to the
 :guilabel:`Shipping Manager` menu item.

content/applications/inventory_and_mrp/manufacturing/workflows.rst

@@ -15,3 +15,5 @@ Workflows
    workflows/unbuild_orders
    workflows/byproducts
    workflows/allocation
+   workflows/continuous_improvement
+   workflows/oee

content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst

@@ -0,0 +1,248 @@
+==============================
+Continuous product improvement
+==============================
+
+.. |MO| replace:: :abbr:`MO (Manufacturing Order)`
+.. |MOs| replace:: :abbr:`MOs (Manufacturing Orders)`
+.. |BoM| replace:: :abbr:`BoM (Bill of Materials)`
+.. |ECO| replace:: :abbr:`ECO (Engineering Change Order)`
+.. |QCP| replace:: :abbr:`QCP (Quality Control Point)`
+.. |PLM| replace:: :abbr:`PLM (Product Lifecycle Management)`
+.. |BoMs| replace:: :abbr:`BoMs (Bills of Materials)`
+
+*Continuous improvement* is a general philosophy intended to help individuals and organizations
+constantly improve themselves and the work they produce.
+
+There are a variety of different methodologies that fall under the umbrella of continuous
+improvement. These include kaizen, six sigma, and lean, among others. While the specific steps of
+each method differ, their goal remains the same: implement a process by which improvement is a
+perpetual goal, rather than a one-time accomplishment.
+
+The sections below contain details about how Odoo can be used to implement four general steps common
+to many of the most popular continuous improvement strategies, with links to documentation about
+configuring the necessary features. The final section details how a specific company might configure
+these Odoo implementations within their organization.
+
+#. :ref:`manufacturing/workflows/ci-identify`
+#. :ref:`manufacturing/workflows/ci-suggest`
+#. :ref:`manufacturing/workflows/ci-implement`
+#. :ref:`manufacturing/workflows/ci-review`
+
+.. important::
+   Continuous improvement is not a one-size-fits-all methodology. While most strategies include
+   between four and six steps, proper implementation requires developing a system tailored to the
+   specific needs of each company.
+
+   This is not a limitation, but rather a benefit, as it makes the methodology flexible enough to
+   adapt to almost any use case. Odoo, in particular, adapts well to this flexibility, as it can be
+   configured to meet the needs of almost any workflow.
+
+   As such, it is important to remember the content below only provides *examples* of how Odoo
+   *might* be used. They should be viewed as more of a starting point, rather than a concrete
+   outline that every organization must follow.
+
+.. _manufacturing/workflows/ci-identify:
+
+Identify problems
+=================
+
+Before improvement can begin, it is necessary to determine where improvement is necessary. This is
+where identifying problems comes into play. Two of the best Odoo apps for identifying problems with
+products or processes are *Helpdesk* and *Quality*.
+
+Helpdesk
+--------
+
+The *Helpdesk* app is useful for receiving feedback from outside of the organization, like from
+clients or customers. This is accomplished by implementing one (or more) of the methods for
+:doc:`receiving tickets <../../../services/helpdesk/overview/receiving_tickets>`, including email
+aliases, live chat conversations, and website forms.
+
+Using these methods, customers can submit feedback about problems, which is then reviewed by a
+member of a :doc:`helpdesk team <../../../services/helpdesk>`. Depending on the outcome of the
+review, the team member may decide to take further action to ensure the issue is addressed. This can
+include creating a :doc:`quality alert <../../quality/quality_management/quality_alerts>`.
+
+Quality
+-------
+
+The *Quality* app is useful for receiving feedback from *within* the organization, like from
+employees.
+
+One method for accomplishing this is to set up a :doc:`quality control point
+<../../quality/quality_management/quality_control_points>` (QCP). A |QCP| is used to automatically
+create quality checks at regular intervals, prompting employees to inspect, and confirm, the quality
+of a product.
+
+If an issue is found, an employee can then create a :doc:`quality alert
+<../../quality/quality_management/quality_alerts>` to notify a quality team. Quality alerts can also
+be created independent of a |QCP|, in the event that an employee discovers an issue without being
+prompted to check for one. This is a great way for customer support employees to notify a quality
+team of an issue brought to their attention by a customer ticket.
+
+.. _manufacturing/workflows/ci-suggest:
+
+Suggest improvements
+====================
+
+Once a problem is identified, the next step is to put forward ideas for how to address the problem.
+As with identifying problems, the *Quality app* is also useful for suggesting improvements. In
+addition, the *PLM* (*Product Lifecycle Management*) app can be used for this purpose, as well.
+
+Quality
+-------
+
+When creating a :doc:`quality alert <../../quality/quality_management/quality_alerts>` to bring an
+issue to the attention of a quality team, the :guilabel:`Corrective Actions` and
+:guilabel:`Preventive Actions` tabs can be used to provide feedback about how the issue can be
+addressed.
+
+The :guilabel:`Corrective Actions` tab is used to suggest a method for fixing items affected by the
+issue. For example, `Screw the bolts on tighter, so the seat stays in place`.
+
+The :guilabel:`Preventive Actions` tab is used to suggest a method for preventing the issue from
+occurring in the future. For example, `Do not tighten the screws too much, or they will be
+stripped`.
+
+The quality team that reviews the alert sees these suggested actions, and can take them into account
+when deciding how to address the issue.
+
+PLM
+---
+
+The |PLM| app is used to manage the lifecycle of a product from its introduction through each
+successive version. As such, it is useful for testing ideas for product improvements.
+
+Using :doc:`engineering change orders <../../plm/manage_changes/engineering_change_orders>`, product
+management teams can create new iterations of product |BoMs|, adding or removing specific components
+or operations, as needed. The products created using these |BoMs| are put through a review process
+to confirm the effectiveness of the changes.
+
+.. _manufacturing/workflows/ci-implement:
+
+Implement strategies
+====================
+
+Implementing strategies involves putting the proposed solutions from the suggest improvements step
+into action. The |PLM| app continues to be useful during this step, as it can be configured to make
+|BoM| updates. The *Field Service* app can also be used by certain companies to make improvements to
+products that have already been sold to customers.
+
+PLM
+---
+
+Once |BoM| changes have gone through the proper review process, they can be approved, and the
+updated |BoM| put into use. This is accomplished by configuring one of the |ECO| review stages to
+:ref:`apply the changes <plm/eco/apply-changes>` made to the |BoM|, at which point the updated |BoM|
+becomes available for new |MOs|.
+
+Product |BoMs| can continue to be updated, as needed. The :doc:`version control
+<../../plm/manage_changes/version_control>` features of the |PLM| app allow for easy management of
+all versions of a given |BoM|.
+
+Field Service
+-------------
+
+The |PLM| app is a great way to make changes to product |BoMs|. However, these changes only affect
+products produced using the new |BoM|. If a defective product has already been sold to a customer,
+it may be necessary to repair (or update) that product.
+
+In such a case, the *Field Service* app can be used to schedule :doc:`onsite interventions
+<../../../services/field_service/onsite_interventions>`. These interventions allow service
+technicians (or other employees) to be sent to a customer's location to address an issue with a
+product.
+
+.. _manufacturing/workflows/ci-review:
+
+Review actions
+==============
+
+Reviewing actions is where the "continuous" part of continuous improvement comes into play, as it
+allows an organization to evaluate the decisions made in the previous steps. As such, this step is,
+essentially, returning to the beginning of the process, so that additional problems can be
+identified and addressed.
+
+This means that the *Helpdesk* and *Quality* apps should be used again to receive customer and
+employee feedback. Another app that may be useful at this stage is the *Surveys* app.
+
+Surveys
+-------
+
+After implementing changes to a product or process, it may be wise to solicit customers for their
+feedback directly, rather than waiting to hear from them of their own volition. This may bring to
+light feedback that customers may have otherwise neglected to share.
+
+One of the best ways to accomplish this is through the :doc:`Surveys <../../../marketing/surveys>`
+app. Creating a survey, and sending it to customers who receive an updated product, increases the
+likelihood of receiving relevant feedback about the product.
+
+.. admonition:: Example workflow: coat rack product improvement
+   :class: alert alert-success
+
+   *Wood Hut* is a manufacturer of fine wood products. They are committed to manufacturing products
+   of the highest-possible quality, and are always looking for ways to improve the products they
+   sell, along with the processes used to create them.
+
+   Wood Hut uses the Odoo platform to manage every element of their production, fulfillment, and
+   customer satisfaction processes. They have developed a custom product improvement workflow that
+   incorporates the Helpdesk, Quality, PLM, and Manufacturing apps.
+
+   One of Wood Hut's most popular products is their *coat rack*. It's made entirely of oak, and
+   customers describe it as "sleek and elegant." However, recent customer feedback about the coat
+   rack has brought attention to quality issues that necessitate revising the current manufacturing
+   process.
+
+   The product revision workflow begins when the customer service team receives a ticket in the
+   Helpdesk app from a customer having problems with the coat rack she purchased. The customer,
+   Abigail Peterson, has found that her coat rack falls over when more than five coats are hanging
+   from it. This is a major issue, as the coat rack has enough dowels for six coats.
+
+   .. image:: continuous_improvement/helpdesk-ticket.png
+      :align: center
+      :alt: A Helpdesk ticket about an issue with the coat rack product.
+
+   Marc, the customer service employee assigned to the helpdesk ticket, opens the Quality app, and
+   creates a new quality alert. He tags the *Production Quality Team* and assigns Julie Andreson as
+   the quality employee responsible for the alert.
+
+   Julie reviews the alert, and consults with her team about the best course of action. They decide
+   that it is necessary to revise the product's |BoM| to prevent the issue from occurring in the
+   future, which Julie notes in the :guilabel:`Corrective Actions` tab of the quality alert.
+
+   .. image:: continuous_improvement/quality-alert.png
+      :align: center
+      :alt: A quality alert created about the issue with the coat rack product.
+
+   Then, Julie messages product engineer, Joe Kazan in the chatter of the quality alert to bring it
+   to his attention. Joe opens the |PLM| app and creates a new |ECO|, noting the problem with the
+   coat rack, and suggesting that a change to the product's |BoM| may be necessary.
+
+   .. image:: continuous_improvement/eco.png
+      :align: center
+      :alt: An ECO created to update the coat rack product's BoM.
+
+   Joe clicks :guilabel:`Start Revision`, and then the :guilabel:`Revision` smart button to open
+   version two of the coat rack's |BoM|. This |BoM| was created alongside the |ECO|, and remains
+   archived until it is approved.
+
+   After some testing, Joe discovers that adding a metal *support rod* to the coat rack strengthens
+   it, allowing the rack to hold six or more coats without falling over. He updates the |BoM| to
+   include the support rod as one of the components, and adds an extra operation to make sure it is
+   installed during the manufacturing process. Finally, he leaves a message in the chatter of the
+   |ECO|, letting his manager, Jose, know that it is ready for review.
+
+   .. image:: continuous_improvement/bom.png
+      :align: center
+      :alt: The coat rack BoM, updated to add an extra component and operation.
+
+   Jose reviews the changes, and confirms they are an effective method for addressing the problem
+   with the coat rack. He moves the |ECO| to the *Approved* stage, which makes version two of the
+   coat rack |BoM| the current version.
+
+   Now, each time an |MO| is created to produce a coat rack, the updated |BoM| is automatically
+   selected. Wood Hut begins producing the improved coat rack, and customer feedback confirms that
+   the new version has addressed the problem with its predecessor.
+
+   Using the Odoo platform, Wood Hut has implemented an end-to-end product improvement process.
+   Since the essential elements of this process (customer feedback, quality control, etc.) are
+   always functioning, it can be reused to continuously update products and processes.

content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst

@@ -0,0 +1,169 @@
+===============================
+Overall equipment effectiveness
+===============================
+
+.. |MO| replace:: :abbr:`MO (manufacturing order)`
+.. |OEE| replace:: :abbr:`OEE (overall equipment effectiveness)`
+.. |BoM| replace:: :abbr:`BoM (Bill of Materials)`
+
+In Odoo's *Manufacturing* app, *overall equipment effectiveness* (OEE) represents the amount of time
+a work center is fully productive. |OEE| is displayed as a percentage of the total time a work
+center is active.
+
+Fully productive time is considered to be time when the work center is operational **and**
+processing work orders that have not exceeded their *expected duration*.
+
+|OEE| helps manufacturing teams understand the efficiency of work centers, and the causes of
+manufacturing downtime.
+
+.. important::
+   Since |OEE| tracks work center productivity, using it requires enabling the work centers feature
+   in the settings of the Manufacturing app.
+
+   To do so, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick
+   the checkbox next to :guilabel:`Work Orders`, under the :guilabel:`Operations` heading. Then,
+   click :guilabel:`Save`.
+
+Efficiency standards
+====================
+
+For |OEE| to accurately reflect the percentage of fully productive time for a work center, the work
+center **must** be properly configured with the correct productivity metrics. These include the work
+center's *time efficiency*, *capacity*, and *OEE target*.
+
+Time efficiency
+---------------
+
+Time efficiency represents the efficiency of a work center when processing work orders, and is
+represented as a percentage. A time efficiency value of 100% signifies that the work center
+processes work orders at the speed of the expected duration, as listed on a product's |BoM|. A value
+less than or greater than 100% signifies that the work center processes work orders slower or faster
+than an operation's expected duration, respectively.
+
+To set the time efficiency for a work center, navigate to :menuselection:`Manufacturing app -->
+Configuration --> Work Centers`, and select a work center. On the :guilabel:`General Information`
+tab, enter a numerical value in the :guilabel:`Time Efficiency` field.
+
+.. example::
+   Manufacturing a *chair* product requires two operations: *cut* and *assemble*. The product's
+   |BoM| lists an expected duration of 30 minutes for each operation.
+
+   The cut operation is carried out at the *cut station* work center, which has a time efficiency
+   value of 50%. This means it takes twice as long to complete the operation, for a total time of
+   one hour.
+
+   The assemble operation is carried out at the *assembly line* work center, which has a time
+   efficiency value of 200%. This means it takes half as long to complete the operation, for a total
+   time of 15 minutes.
+
+Capacity
+--------
+
+Capacity represents how many units of a product can be produced in parallel at a work center. The
+duration of work orders for multiple units increases or decreases, based on how many units the work
+center can handle.
+
+To set the capacity for a work center, navigate to :menuselection:`Manufacturing app -->
+Configuration --> Work Centers`, and select a work center. On the :guilabel:`General Information`
+tab, enter a numerical value in the :guilabel:`Capacity` field.
+
+.. example::
+   A *drill station* work center has a capacity of one unit. An |MO| is confirmed for 10 units of a
+   *chair*, a product manufactured using the drill station.
+
+   Since there are ten times as many units to produce than the work center can handle at once, the
+   operation time is ten times the duration listed on the product's |BoM|.
+
+|OEE| target
+------------
+
+The |OEE| target is the goal for how much of a work center's operating time should be fully
+productive time. It is displayed as a percentage, and should only be set as high as `100%`.
+
+To set the |OEE| target for a work center, navigate to :menuselection:`Manufacturing app -->
+Configuration --> Settings --> Work Centers`, and select a work center. On the :guilabel:`General
+Information` tab, enter a numerical value of `100.00` or less in the :guilabel:`OEE Target` field.
+
+Calculating |OEE|
+=================
+
+|OEE| is represented as a percentage value between zero and 100. The value signifies the amount of
+time that a work center was fully productive. The remainder signifies the amount of time that the
+work center was operating at less than full efficiency. This can occur for a number of reasons,
+including *reduced speed*, *material availability*, and *equipment failure*.
+
+Fully productive time
+---------------------
+
+For a work center to be considered fully productive, it must be able to receive work orders, have
+the components necessary to process work orders, and be operating within the expected duration of
+the work order it is processing.
+
+.. example::
+   An *assembly line* work center is not blocked, and receives a work order to assemble a *bicycle*.
+   The required components are available, so production begins as soon as they are picked and
+   delivered to the work center. The work order has an expected duration of 30 minutes, and is
+   completed in 27 minutes. All of this time is considered fully productive time.
+
+Reduced speed
+-------------
+
+When a work center is operating at reduced speed, it means that it is processing a work order that
+has exceeded its expected duration. While the work center may be operational, this is not considered
+fully productive time.
+
+.. example::
+   A *cutting station* work center receives a work order to cut boards for a *table*. The expected
+   duration of the work order is 15 minutes. The work order ends up taking 18 minutes to complete.
+   The work center is considered to have been operating at reduced speed during the three minutes
+   that exceeded the expected duration.
+
+Material availability
+---------------------
+
+Material availability refers to situations where a work center is able to accept a work order, but
+the required components are not available. This can occur because the components are not in stock,
+or are reserved for a different order.
+
+.. example::
+   Manufacturing of a *bench* requires 20 units of *wood*. A manufacturing order (MO) is confirmed
+   for 10 units of the bench, but there is not enough wood in stock to begin manufacturing. The time
+   it takes to acquire the wood is recorded as material availability downtime.
+
+Equipment failure
+-----------------
+
+Equipment failure signifies any period of time when a work center is unusable due to maintenance
+issues with its equipment. This can be due to equipment breaking down, or when a work center is shut
+down for scheduled maintenance. In these cases, a work center can be blocked using a
+:doc:`maintenance request <../../maintenance/maintenance_requests>`.
+
+.. example::
+   The drill at a *drill station* work center breaks down, causing the work center to be unusable. A
+   maintenance request is created to fix the drill, and the work center is blocked from receiving
+   work orders. It takes two hours to fix the drill, and make the work center available again. This
+   two-hour period is recorded as equipment failure downtime.
+
+|OEE| reporting
+===============
+
+To view |OEE| reporting metrics for every work center, navigate to :menuselection:`Manufacturing app
+--> Reporting --> Overall Equipment Effectiveness`. This page shows the metrics for each work center
+with |OEE| data.
+
+Alternatively, to see |OEE| reporting metrics for a single work center, navigate to
+:menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center. At
+the top of the work center's form, click the :icon:`fa-pie-chart` :guilabel:`OEE` smart button.
+
+By default, the main |OEE| reporting page shows data in a bar chart, while the page for a specific
+work center shows it in a pie chart. To select a different chart type on either page, click the
+:icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or
+:icon:`fa-pie-chart` :guilabel:`(pie chart)` button above the displayed chart.
+
+It is also possible to see |OEE| data in a pivot view, or a list displaying each time entry, by
+clicking the :icon:`oi-view-pivot` :guilabel:`(pivot view)` or :icon:`oi-view-list` :guilabel:`(list
+view)` buttons at the top-right corner of the page.
+
+.. image:: oee/oee-report.png
+   :align: center
+   :alt: The dashboard of the OEE report.

content/applications/productivity/documents.rst

@@ -8,9 +8,8 @@ You can upload any file (max 64MB per file on Odoo Online) and organize them in
 
 .. seealso::
    - `Odoo Documents: product page <https://www.odoo.com/app/documents>`_
-   - `Odoo Tutorials: Documents basics [video]
-     <https://www.odoo.com/slides/slide/documents-basics-674>`_
-   - `Odoo Tutorials: Using Documents with your Accounting App [video] <https://www.odoo.com/slides/slide/using-documents-with-your-accounting-app-675?fullscreen=1#>`_
+   - `Odoo Tutorials: Documents basics [video] <https://www.odoo.com/slides/slide/documents-basics-6841?fullscreen=1>`_
+   - `Odoo Tutorials: Using Documents with your Accounting App [video] <https://www.odoo.com/slides/slide/accounting-integration-and-workflow-actions-6853?fullscreen=1>`_
 
 Configuration
 =============
@@ -18,9 +17,9 @@ Configuration
 By going to :menuselection:`Documents --> Configuration --> Settings`, you can enable the
 centralization of files attached to a specific area of your activity. For example, by ticking
 :guilabel:`Human Resources`, your HR documents are automatically available in the HR workspace,
-while documents related to Payroll are automatically available in the Payroll sub-workspace . You
+while documents related to Payroll are automatically available in the Payroll sub-workspace. You
 can change the default workspace using the dropdown menu and edit its properties by clicking the
-:guilabel:`➔` (:guilabel:`Internal link`) icon.
+:icon:`fa-arrow-right` (:guilabel:`Internal link`) icon.
 
 .. image:: documents/files-centralization.png
    :alt: Enable the centralization of files attached to a specific area of your activity.
@@ -48,7 +47,7 @@ own by going to :menuselection:`Documents --> Configuration --> Workspaces` and
 
 - :guilabel:`Name`
 - :guilabel:`Parent Workspace`: if you want to create a sub-workspace, select its :guilabel:`Parent
-  Workspace`
+  Workspace`.
 
 Three tabs are available: :ref:`Tags <documents/tags>`,
 :ref:`Access Rights <documents/access-rights>`, and :ref:`Description <documents/description>`.
@@ -68,8 +67,8 @@ and :guilabel:`Name` your tags.
    - The tags of a parent workspace apply to the child workspaces automatically;
    - Tags can be created and modified by going to :menuselection:`Documents --> Configuration -->
      Tags`;
-   - Tags can also be created or edited by clicking the :icon:`fa-cog` (:guilabel:`cog`) icon on
-     the left menu;
+   - Tags can also be created or edited by clicking the :icon:`fa-gear` (:guilabel:`gear`) icon on
+     the left panel;
    - An :ref:`email alias <documents/upload>` can be used to automatically send received documents
      to a specific workspace based on the tag assigned.
 
@@ -78,10 +77,9 @@ and :guilabel:`Name` your tags.
 Access rights
 -------------
 
-To manage your workspace access rights, go to :menuselection:`Documents --> Configuration -->
-Workspaces`, open the workspace you want to edit, and go to the :guilabel:`Access Rights` tab.
-You can add :guilabel:`Write Groups` that can view, create, and edit the workspace's documents.
-You can also add :guilabel:`Read Groups` that can only view the workspace's documents.
+To manage your workspace access rights, go to the :guilabel:`Access Rights` tab. You can add
+:guilabel:`Write Groups` that can view, create, and edit the workspace's documents. You can also add
+:guilabel:`Read Groups` that only view the workspace's documents.
 
 .. tip::
    Enable :guilabel:`Own Documents Only` to limit :guilabel:`Read Groups` and
@@ -92,16 +90,11 @@ You can also add :guilabel:`Read Groups` that can only view the workspace's docu
 Description
 -----------
 
-You can add descriptive information to your workspace by going to :menuselection:`Documents -->
-Configuration --> Workspaces`, opening the workspace you want to describe and going to the
-:guilabel:`Description` tab.
+You can add descriptive information to your workspace by going to the :guilabel:`Description` tab.
 
 .. note::
-   Workspaces can also be created and edited by clicking the :icon:`fa-cog` (:guilabel:`cog`) icon
-   on the left menu.
-
-   .. image:: documents/sub-workspaces-creation.png
-      :alt: Create sub-workspaces from the left menu
+   Workspaces can also be created and edited by clicking the :icon:`fa-gear` (:guilabel:`gear`) icon
+   on the left panel.
 
 .. _documents/management:
 
@@ -109,14 +102,21 @@ Documents management
 ====================
 
 When selecting or opening a document, the right panel displays different options, including, for
-example: :icon:`fa-download` (:guilabel:`Download`), :icon:`fa-share-alt` (:guilabel:`Share this
-selection`), :icon:`fa-retweet` (:guilabel:`Replace`), :icon:`fa-unlock` (:guilabel:`Lock`),
-:icon:`fa-scissors` (:ref:`Split <documents/split>`), :icon:`fa-comments` (:guilabel:`Open chatter`),
-and :icon:`fa-trash` (:guilabel:`Move to trash`).
+example:
 
-.. image:: documents/right-panel-options.png
-   :align: center
-   :alt: right panel options
+- :icon:`fa-download` (:guilabel:`Download`);
+- :icon:`fa-share-alt` (:guilabel:`Share this selection`): a share URL is copied to your clipboard;
+- :icon:`fa-retweet` (:guilabel:`Replace`): select a new file to replace the existing one. Scroll
+  down to the bottom of the right panel to see the :guilabel:`History` and :guilabel:`restore`,
+  :guilabel:`download`, or :guilabel:`delete` the document;
+- :icon:`fa-unlock` (:guilabel:`Lock`);
+- :icon:`fa-scissors` (:ref:`Split <documents/split>`).
+
+You can also :icon:`fa-comments` :guilabel:`Open chatter` or delete the document by clicking the
+:icon:`fa-trash` (:guilabel:`Move to trash`) icon.
+
+.. note::
+   Items moved to the trash are permanently deleted after 30 days.
 
 To modify the name of your file, click on :guilabel:`Name`. A :guilabel:`Contact` or an
 :guilabel:`Owner` can be assigned. The related :guilabel:`Workspace` can be modified and it is
@@ -158,38 +158,33 @@ pages, click the :icon:`fa-scissors` (:guilabel:`scissors`) icon.
 Additional features
 -------------------
 
-Select a workspace and click the arrow next to the :guilabel:`Upload` button to access additional
-features:
+Select a workspace and click the :icon:`fa-caret-down` (:guilabel:`down arrow`) next to the
+:guilabel:`Upload` button to access additional features:
 
 Request
 ~~~~~~~
 
-You can create "missing documents" and organize them as documents, to remind users to download them.
+You can request files and organize them as documents to remind users to download them.
 
-Select the workspace where the file should be stored, click the arrow next to the :guilabel:`Upload`
-button, and select the :guilabel:`Request` option. Add the :guilabel:`Document Name`, choose the
-person you need it from in the :guilabel:`Request To` field, fill in the :guilabel:`Due Date In`,
-confirm the :guilabel:`Workspace` the document should belong to, and add :guilabel:`Tags` and a
-:guilabel:`Note` if needed. Then, click :guilabel:`Request`. A placeholder for the missing document
-is created in the workspace.
+Select the workspace where the file should be stored, click the :icon:`fa-caret-down`
+(:guilabel:`down arrow`) next to the :guilabel:`Upload` button, then :guilabel:`Request`. Add the
+:guilabel:`Document Name` and select the person you need it from in the :guilabel:`Request To`
+field. You can also fill in the :guilabel:`Due Date In`, confirm the :guilabel:`Workspace` the
+document should belong to, and add :guilabel:`Tags` and a :guilabel:`Message`. Then, click
+:guilabel:`Request`. A placeholder for the missing document is created in the workspace.
 
-.. image:: documents/missing-doc.png
-   :alt: Placeholder for missing document
-
-To upload the document, click the :icon:`fa-upload` (:guilabel:`Upload file`) icon in the document
-preview. By default, the requestor is set as the document's :guilabel:`Owner`.
+When your document is available, click the placeholder to upload it.
 
 You can see all missing documents by going to the **Activity** view and the :guilabel:`Requested
 Document` column.
 
 .. tip::
-   - From the :guilabel:`Activity` view, you can send a **reminder email** to users from whom you
-     are expecting a document. Go to the :guilabel:`Requested Document` column, click on the
-     :icon:`fa-ellipsis-v` (:guilabel:`vertical ellipsis`) icon and :guilabel:`Document Request: Reminder`.
-
-   - Click on a date to see the details of a specific request. You can update it by clicking on the
-     :icon:`fa-pencil` (:guilabel:`pen`) icon, :guilabel:`Preview` the content of the reminder
-     email, or :guilabel:`Send Now` to send a reminder email.
+   From the :guilabel:`Activity` view, you can send a **reminder email** to users from whom you are
+   expecting a document. Go to the :guilabel:`Requested Document` column and click the
+   :icon:`fa-ellipsis-v` (:guilabel:`ellipsis`) icon, and :guilabel:`Document Request: Reminder`.
+   Click on a date to see the details of a specific request. You can update it by clicking on the
+   :icon:`fa-pencil` (:guilabel:`pen`) icon, :guilabel:`Preview` the content of the reminder email,
+   or :guilabel:`Send Now` to send a reminder email.
 
       .. image:: documents/reminder-email.png
          :alt: send a reminder email from the Activity view
@@ -199,8 +194,8 @@ Document` column.
 Add a link
 ~~~~~~~~~~
 
-To add a link to your documents dashboard, click on :guilabel:`Add a Link`, enter the
-:guilabel:`URL`, and :guilabel:`Name` it.
+To add a link to your documents dashboard, click :guilabel:`Add a Link`, enter the :guilabel:`URL`,
+and :guilabel:`Name` it.
 
 Share
 ~~~~~
@@ -210,8 +205,8 @@ You can make a document or a workspace accessible to anyone by sharing a URL.
 Share a document
 ****************
 
-To generate a **share link** to a document, select the document, click the arrow next to the
-:guilabel:`Upload` button, and click :guilabel:`Share`.
+To generate a **share link** to a document, select the document, click the :icon:`fa-caret-down`
+(:guilabel:`down arrow`) next to the :guilabel:`Upload` button, and click :guilabel:`Share`.
 
 In the pop-up, you can :guilabel:`Name` the share link, set a validity date by filling in the
 :guilabel:`Valid Until` field, and if you own more than one site, select the :guilabel:`Website` you
@@ -231,8 +226,8 @@ You can share a link to a workspace and allow users to :guilabel:`Download` its
 
 To do so, go to the left column of your dashboard. In the :guilabel:`Workspace` section, select the
 workspace to share, and possibly one or several tags that will be automatically added to the
-uploaded documents. Then, click the arrow next to the :guilabel:`Upload` button and
-:guilabel:`Share`.
+uploaded documents. Then, click the :icon:`fa-caret-down` (:guilabel:`down arrow`) next to the
+:guilabel:`Upload` button and :guilabel:`Share`.
 
 In the pop-up, a share :guilabel:`URL` you can :guilabel:`Copy` is displayed. You can
 :guilabel:`Name` your share link, set a validity date by filling in the :guilabel:`Valid Until`
@@ -245,7 +240,7 @@ Upload <documents/upload>` files to it.
 
 .. Note::
    - The links added to your workspace using the :ref:`Add a Link <documents/add-a-link>` option
-     cannot be shared and are, therefore, excluded.
+     cannot be shared and are, therefore, excluded;
    - When tags are applied to a shared workspace, users can exclusively access the documents
      associated with those tags.
 
@@ -273,6 +268,8 @@ The documents sent to this email alias are uploaded to the workspace using the c
 
 .. tip::
    Go to :menuselection:`Configuration --> Share & Emails` to see and manage your share links.
+   Select a line and click :guilabel:`Delete` to disable the URL. People who have received this
+   link will no longer be able to access the document(s) or workspace.
 
 New spreadsheet
 ~~~~~~~~~~~~~~~
@@ -287,15 +284,15 @@ Workflow actions
 
 Workflow actions help manage documents and overall business operations. These are automated actions
 that can be created and customized for each workspace. With a single click you can, for example,
-create, move, sign, and add tags to a document, and process bills.
+create, move, sign, add tags to a document, and process bills.
 
-These workflow actions appear on the right panel when a document meets the set criteria.
+When a document meets the set criteria, these workflow actions appear on the right panel.
 
 Create workflow actions
 -----------------------
 
-To create workflow actions, go to :menuselection:`Documents --> Configuration --> Actions` and click
-:guilabel:`New`.
+To update an existing workflow action or create a new one, go to :menuselection:`Documents -->
+Configuration --> Actions` and click :guilabel:`New`.
 
 .. note::
    An action applies to all **sub-workspaces** under the :guilabel:`Related Workspace` you selected.
@@ -303,16 +300,15 @@ To create workflow actions, go to :menuselection:`Documents --> Configuration --
 Set the conditions
 ------------------
 
-You can :guilabel:`Create` a new :guilabel:`Action` or edit an existing one. You can define the
-:guilabel:`Action Name` and then set the conditions that trigger the appearance of the action button
-(:guilabel:`▶`) on the right-side panel when selecting a file.
+Define the :guilabel:`Action Name` and then set the conditions that trigger the appearance of the
+:icon:`fa-play` (:guilabel:`play`) icon on the right-side panel when selecting a file.
 
 There are three basic types of conditions you can set:
 
 #. :guilabel:`Tags`: you can use the :guilabel:`Contains` and :guilabel:`Does not contain`
-   conditions, meaning the files *must have* or *must not have* the tags set here.
+   conditions, meaning the files *must have* or *must not have* the tags set here;
 
-#. :guilabel:`Contact`: the files must be associated with the contact set here.
+#. :guilabel:`Contact`: the files must be associated with the contact set here;
 
 #. :guilabel:`Owner`: the files must be associated with the owner set here.
 
@@ -332,7 +328,7 @@ Advanced condition type: domain
 
 The :ref:`developer mode <developer-mode>` needs to be activated to access the :guilabel:`Domain`
 condition from the :guilabel:`Actions` tab. Once done, select the :guilabel:`Domain` condition type
-and click :guilabel:`Add condition`.
+and click :guilabel:`New Rule`.
 
 To create a rule, you typically select a :guilabel:`field`, an :guilabel:`operator`, and a
 :guilabel:`value`. For example, if you want to add a workflow action to all the PDF files inside a
@@ -352,30 +348,29 @@ Configure the actions
 
 Select the :guilabel:`Actions` tab to set up your action. You can simultaneously:
 
-- **Set Contact**: add a contact to the file, or replace an existing contact with a new one.
-- **Set Owner**: add an owner to the file, or replace an existing owner with a new one.
-- **Move to Workspace**: move the file to any workspace.
+- **Move to Workspace**: move the file to any workspace;
 - **Create**: create one of the following items attached to the file in your database:
 
-   - **Link to record**: link the document to a record (i.e. link to a vehicle in Fleet);
-   - **Product template**: create a product you can edit directly;
-   - **Task**: create a Project task you can edit directly;
-   - **Signature PDF template**: create a new Sign template to send out;
-   - **PDF to sign**: create a PDF to sign;
-   - **Applicant**: create a new HR application you can edit directly;
-   - **Vendor bill**: create a vendor bill using OCR and AI to scrape information from the file
-     content;
-   - **Customer invoice**: create a customer invoice using OCR and AI to scrape information from
-     the file;
-   - **Vendor credit note**: create a vendor credit note using OCR and AI to scrape information
-     from the file;
-   - **Credit note**: create a customer credit note using OCR and AI to scrape information from
-     the file;
-   - **Miscellaneous Operations**: create a record in :guilabel:`Miscellaneous Operations`
-     in Accounting;
-   - **Bank Statement**: create a Bank Statement in Finance;
-   - **Expense**: create an expense automatically based on a file's content.
+  - **Link to record**: create a link between a document and a record from a specific model;
+  - **Product template**: create a product you can edit directly;
+  - **Task**: create a Project task you can edit directly;
+  - **Signature PDF template**: create a new Sign template to send out;
+  - **PDF to sign**: create a Sign template to sign directly;
+  - **Applicant**: create a new HR application you can edit directly;
+  - **Vendor bill**: create a vendor bill using OCR and AI to scrape information from the file
+    content;
+  - **Customer invoice**: create an invoice using OCR and AI to scrape information from the file;
+  - **Vendor credit note**: create a vendor credit note using OCR and AI to scrape information
+    from the file;
+  - **Credit note**: create a customer credit note using OCR and AI to scrape information from the
+    file;
+  - **Miscellaneous Operations**: create an entry in the Miscellaneous Operations journal;
+  - **Bank Statement**: import a bank statement;
+  - **Purchase Receipt**: create a vendor receipt;
+  - **Expense**: create an HR expense.
 
+- **Set Contact**: add a contact to the file, or replace an existing contact with a new one;
+- **Set Owner**: add an owner to the file, or replace an existing owner with a new one;
 - **Set Tags**: add, remove, and replace any number of tags;
 - **Activities - Mark all as Done**: mark all activities linked to the file as done;
 - **Activities - Schedule Activity**: create a new activity linked to the file as configured in

content/applications/sales/crm/acquire_leads/send_quotes.rst

@@ -94,9 +94,41 @@ catalog. Then, select a product from the drop-down menu, or create a new one by
 After selecting a product, update the :guilabel:`Quantity`, if necessary. Confirm the information in
 the remaining fields.
 
-To remove a line from the quotation, click the :guilabel:`🗑️ (trash can)` icon.
+To remove a line from the quotation, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon.
 
-Repeat the steps above until the quotation is complete.
+To organize products into sections click :guilabel:`Add a section` and type a name for the section.
+Then, click the :icon:`oi-draggable` :guilabel:`(drag)` icon to the left of the name and drag to
+move the section to the appropriate location. Move each product using the same method to finish
+organizing the quotation order lines.
+
+.. image:: send_quotes/product-sections.png
+   :align: center
+   :alt: Categories are used to create separate sections on the order lines of a quote.
+
+Product catalog
+~~~~~~~~~~~~~~~
+
+To quickly add numerous products to the quotation, click the :guilabel:`Catalog` button to open the
+product catalog.
+
+All products in the database are listed as cards and can be sorted in the left panel by
+:guilabel:`Product Category` and :guilabel:`Attributes`.
+
+.. image:: send_quotes/product-catalog.png
+   :align: center
+   :alt: The product catalog displays all products as cards.
+
+To add a product, click the :icon:`fa-shopping-cart` :guilabel:`Add` button on the product card.
+Set the quantity of the item using the :icon:`fa-plus` :guilabel:`(add)` or :icon:`fa-minus`
+:guilabel:`(subtract)` buttons, or type the quantity in the number field between the two buttons.
+To remove an item, click the :icon:`fa-trash` :guilabel:`Remove` button on the product card.
+
+.. image:: send_quotes/set-quantity.png
+   :align: center
+   :alt: The purple add and subtract buttons are used to set the quantity of an item.
+
+Once all product quantities are set, click the :guilabel:`Back to Quotation` button to return to the
+quotation. The items selected in the product catalog now appear in the :guilabel:`Order Lines` tab.
 
 Preview and send quotation
 ==========================

content/applications/sales/point_of_sale/payment_methods/terminals.rst

@@ -25,6 +25,7 @@ Then, follow the corresponding documentation to configure your device:
 - :doc:`SIX configuration <terminals/six>`
 - :doc:`Stripe configuration <terminals/stripe>`
 - :doc:`Vantiv configuration <terminals/vantiv>`
+- :doc:`Viva Wallet configuration <terminals/viva_wallet>`
 - :doc:`Worldline configuration <terminals/worldline>`
 
 Once the terminal is configured, you can :doc:`create the corresponding payment method and add it to
@@ -38,4 +39,5 @@ the POS <../payment_methods>`.
    terminals/six
    terminals/stripe
    terminals/vantiv
+   terminals/viva_wallet
    terminals/worldline

content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst

@@ -0,0 +1,134 @@
+===========
+Viva Wallet
+===========
+
+Connecting a **Viva Wallet** :doc:`payment terminal <../terminals>`  allows you to offer a fluid
+payment flow to your customers and ease the work of your cashiers.
+
+.. note::
+   Viva Wallet lets you turn your phone into a mobile card reader: `Tap On Phone
+   <https://www.vivawallet.com/gb_en/blog-tap-on-phone-gb>`_.
+
+Configuration
+=============
+
+Start by creating your Viva Wallet account on `Viva Wallet's website <https://www.vivawallet.com>`_.
+
+Locate your Viva Wallet credentials
+-----------------------------------
+
+When configuring Viva Wallet in Point of Sale, you need to use specific credentials that are
+available in your Viva Wallet account. These credentials include your :ref:`Merchant ID
+<viva_wallet/id-key>`, :ref:`API key <viva_wallet/id-key>`, :ref:`POS API credentials
+<viva_wallet/pos-api>`, and :ref:`Terminal ID <viva_wallet/identifier>` number.
+
+.. _viva_wallet/id-key:
+
+Merchant ID and API key
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Locate your `Merchant ID and API key following the Viva documentation
+<https://developer.vivawallet.com/getting-started/find-your-account-credentials/merchant-id-and-api-key/>`_.
+Then, save the keys and paste them into the Odoo :guilabel:`Merchant ID` and :guilabel:`API Key`
+fields :ref:`when creating the payment method <viva_wallet/method-creation>`.
+
+.. image:: viva_wallet/access-cred.png
+   :alt: merchant ID and API key fields
+
+.. note::
+   These credentials are used for APIs that authenticate with Basic Auth.
+
+.. _viva_wallet/pos-api:
+
+POS API credentials
+~~~~~~~~~~~~~~~~~~~
+
+Locate and generate your `POS API credentials following the Viva documentation
+<https://developer.vivawallet.com/getting-started/find-your-account-credentials/pos-api-credentials/>`_.
+Then, save the keys and paste them in the Odoo :guilabel:`Client secret` and :guilabel:`Client ID`
+fields :ref:`when creating the payment method <viva_wallet/method-creation>`.
+
+.. warning::
+   These credentials are only displayed once. Ensure you keep a copy to secure them.
+
+.. image:: viva_wallet/api-cred.png
+   :alt: Client secret and client ID fields
+
+.. note::
+   These credentials are used for Android and iOS POS Activation requests, as well as the Cloud
+   Terminal API.
+
+.. _viva_wallet/identifier:
+
+Terminal ID
+~~~~~~~~~~~
+
+Your terminal ID number is used to identify your terminal. To find it:
+
+#. Go to your Viva Wallet account and select the relevant account.
+#. Go to :menuselection:`Sales --> Physical payments --> Card terminals` in the navigation menu.
+
+The terminal ID number is located under the :guilabel:`Terminal ID (TID)` column. Save it to paste
+it into the :guilabel:`Terminal ID` field :ref:`when creating the payment method
+<viva_wallet/method-creation>`.
+
+.. image:: viva_wallet/terminal-id.png
+   :alt: Viva terminal ID
+
+.. _viva_wallet/method-creation:
+
+Configure the payment method
+----------------------------
+
+#. :doc:`Activate the POS Viva Wallet module <../../../../general/apps_modules>` to enable the
+   payment terminal.
+#. :doc:`Create the related payment method <../../payment_methods>` by going to
+   :menuselection:`Point of Sale --> Configuration --> Payment Methods` and clicking
+   :guilabel:`New`.
+#. Set the journal type as :guilabel:`Bank`.
+#. Select :guilabel:`Viva Wallet` in the :guilabel:`Use a Payment Terminal` field.
+#. Fill in the mandatory fields with your:
+
+   - :ref:`Merchant ID and API key <viva_wallet/ID-key>`
+   - :ref:`Client ID and Client secret <viva_wallet/pos-api>`
+   - :ref:`Terminal ID <viva_wallet/identifier>`
+
+#. Save the form and copy the generated webhook URL from the :guilabel:`Viva Wallet Webhook
+   Endpoint` field. This URL is necessary :ref:`when configuring the webhook <viva_wallet/webhook>`.
+
+.. image:: viva_wallet/create-method-viva-wallet.png
+   :alt: payment method creation form
+   :scale: 75%
+
+.. _viva_wallet/webhook:
+
+Configure the webhook
+---------------------
+
+Webhooks allow you to receive real-time notifications whenever a transaction occurs within your Viva
+Wallet account. Set them up for `payment transactions following the Viva documentation
+<https://developer.vivawallet.com/webhooks-for-payments/transaction-payment-created/>`_.
+
+.. seealso::
+   `Setting up webhooks <https://developer.viva.com/webhooks-for-payments/#setting-up-webhooks>`_
+
+Link the payment method to a POS
+--------------------------------
+
+You can select the payment method in your POS settings once the payment method is created. To do so,
+go to the :ref:`POS' settings <configuration/settings>` and add the payment method under the
+:guilabel:`Payment methods` field of the :guilabel:`Payment` section.
+
+Pay with a payment terminal
+===========================
+
+When processing a payment, select the related payment method. Check the amount and click on
+:guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment
+Successful`.
+
+.. note::
+   - | In case of connection issues between Odoo and the payment terminal, force the payment by
+       clicking on :guilabel:`Force Done`, which allows you to validate the order.
+     | This option is only available after receiving an error message informing you that the
+       connection failed.
+   - To cancel the payment request, click :guilabel:`cancel`.

content/applications/sales/sales/products_prices/prices/pricing.rst

@@ -482,4 +482,4 @@ rule on a fresh form.
 
 .. seealso::
    - :doc:`/applications/sales/sales/products_prices/prices/currencies`
-   - :doc:`/applications/websites/ecommerce/managing_products/price_management`
+   - :doc:`/applications/websites/ecommerce/products/price_management`

content/applications/sales/sales/products_prices/products/variants.rst

@@ -28,7 +28,7 @@ within the Odoo *Sales* application.
    other similar records in Odoo.
 
 .. seealso::
-   :doc:`/applications/websites/ecommerce/managing_products/variants`
+   :doc:`/applications/websites/ecommerce/products/variants`
 
 Configuration
 =============

content/applications/sales/subscriptions/scheduled_actions.rst

@@ -107,10 +107,14 @@ Odoo uses the information in the :guilabel:`Recurring Plan` field to update the
 accordingly.
 
 .. warning::
-   If there is no payment provider set up, Odoo does **not** create an invoice, and the customer is
-   not charged. Instead, the subscription is processed as a free recurring product, and is reflected
-   as such in the *chatter* of the subscription sales order. When this occurs, the following message
-   appears: `Automatic renewal succeeded. Free subscription. Next invoice:[date]. No email sent.`
+   If the product invoicing policy is set to *Based on Delivered Quantities (Manual)*, and the
+   delivered quantity is `0`, Odoo does **not** create an invoice, and the customer is not charged.
+
+   Instead, the subscription is processed as a free recurring product, and is reflected as such in
+   the *chatter* of the subscription sales order.
+
+   When this occurs, the following message appears: `Automatic renewal succeeded. Free subscription.
+   Next invoice:[date]. No email sent.`
 
 Once the invoice for the subscription sales order is created, the invoice can be viewed by clicking
 the :guilabel:`Invoices` smart button that appears at the top of the subscription sales order.
@@ -125,8 +129,8 @@ the :guilabel:`Payment Token` field, under the :guilabel:`Subscription` section.
    :align: center
    :alt: The Payment Token field under the Other Info tab on a subscription sales order form.
 
-If there is no :guilabel:`Payment Token` (i.e. payment provider is `Bank Transfer`), the invoice is
-created and sent to the customer. The payment **must** be registered manually in this case.
+If there is no :guilabel:`Payment Token`, the invoice is created, and sent to the customer. The
+payment **must** be registered manually in this case.
 
 Closing invoices
 ----------------

content/applications/studio.rst

@@ -13,19 +13,27 @@ Studio
    studio/models_modules_apps
    studio/automated_actions
    studio/pdf_reports
+   studio/approval_rules
 
 Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you
-can, on any app, add or modify:
+can, in any app, add or modify:
 
 - :doc:`Fields <studio/fields>`
 - :doc:`Views <studio/views>`
 - :doc:`Models <studio/models_modules_apps>`
 - :doc:`Automated actions <studio/automated_actions>`
 - :doc:`PDF reports <studio/pdf_reports>`
-- Approval rules
+- :doc:`Approval rules <studio/approval_rules>`
 - Security rules
 
-Or you can :doc:`build an app from scratch <studio/models_modules_apps>`.
+You can also :doc:`build an app from scratch <studio/models_modules_apps>`.
+
+.. _studio/access:
+
+To access Studio, navigate to the app and model you want to modify, then click the **Toggle Studio**
+button, or vice versa.
+
+To close Studio, click :guilabel:`Close` in the upper right corner.
 
 .. seealso::
-   - `Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_
+   `Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_

content/applications/studio/approval_rules.rst

@@ -0,0 +1,79 @@
+==============
+Approval rules
+==============
+
+Studio approval rules are used to automate approval processes for actions. They allow you to define
+the criteria for when an approval is required before an action can be performed using a button.
+
+Configuration
+=============
+
+To add approval rules, proceed as follows:
+
+#. :ref:`Open Studio <studio/access>` and switch to the required :doc:`view <views>`.
+#. Select the button for which you want to add approval rules.
+#. In the :guilabel:`Properties` tab on the left, enable the :guilabel:`Set approval rules`
+   feature.
+#. Specify the :guilabel:`Allowed Group` to limit the approval permission to a specific user
+   group.
+#. Select the :guilabel:`Responsible` user to create an activity for a specific user when approval
+   is requested from them.
+#. Select the :guilabel:`Users to notify` via internal note.
+#. Add a :guilabel:`Description` to be displayed in the :ref:`Approval dialog <approval-rules/use>`.
+
+Optionally, you can also add conditions for the approval rule to be applied by clicking the
+:icon:`fa-filter` (:guilabel:`filter`) icon next to the :guilabel:`Allowed Group` field.
+
+To add another rule, click :guilabel:`Add an approval rule`. When there are multiple approval rules,
+you can:
+
+- enable :guilabel:`Exclusive Approval` to require approvers to be different users;
+- change the :guilabel:`Notification Order` of the approval rule so that the :guilabel:`Responsible`
+  and :guilabel:`Users to notify` are only notified when the previous rule has been approved, and
+  their approval is required. If the approval rules have the same :guilabel:`Notification Order`,
+  all users are notified at the same time when the first approval is requested.
+
+Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the :guilabel:`Allowed Group` field to
+delete the approval rule.
+
+.. tip::
+   You can create :ref:`user groups <access-rights/groups>` specifically for approvals.
+
+.. _approval-rules/use:
+
+Use
+===
+
+Once approval rules have been defined for a button:
+
+- A **user avatar** icon is displayed next to the button's label for each approval rule that has
+  been defined.
+
+   .. image:: approval_rules/approvals-button.png
+      :alt: Confirm button with approval for purchase orders
+
+- When an unauthorized user clicks the button, an error message is displayed in the top-right corner
+  and an activity is created for the user specified in the :guilabel:`Responsible` field.
+- Only users from the group defined in the :guilabel:`Allowed Group` field are authorized to approve
+  or reject the action.
+
+Authorized users can:
+
+- approve and perform the action by clicking the button;
+- approve the action and allow another user to perform it by clicking the **user avatar** icon next
+  to the button's label, then clicking the :icon:`fa-check` (:guilabel:`Approve`) button in the
+  dialog that opens;
+- reject the action by clicking the **user avatar** icon next to the button's label, then clicking
+  the :icon:`fa-times` (:guilabel:`Reject`) button in the dialog that opens.
+
+.. image:: approval_rules/approvals-awaiting.png
+   :alt: Approval dialog
+
+.. tip::
+   - The user who approved/rejected the action can revoke their decision by clicking the **user
+     avatar** icon next to the button's label, then clicking the :icon:`fa-undo`
+     (:guilabel:`Revoke`) button.
+   - Approvals are tracked in the record's chatter. An approval entry is also created every time
+     a Studio approval-related action is performed. To access the approval entries, :doc:`activate
+     the developer mode </applications/general/developer_mode>` and go to :menuselection:`Settings
+     --> Technical --> Studio Approval Entries`.

content/applications/websites/ecommerce.rst

@@ -23,6 +23,6 @@ products and increase your average cart sizes.
 .. toctree::
    :titlesonly:
 
-   ecommerce/managing_products
+   ecommerce/products
    ecommerce/checkout_payment_shipping
    ecommerce/ecommerce_management

content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst

@@ -25,11 +25,11 @@ the :guilabel:`Shop - Checkout Process` section, look for :guilabel:`Add to Cart
 the options.
 
 .. note::
-   If a product has :doc:`optional products <../managing_products/cross_upselling>`, the **dialog
+   If a product has :doc:`optional products <../products/cross_upselling>`, the **dialog
    box** will always appear.
 
 .. seealso::
-   :doc:`../managing_products/catalog`
+   :doc:`../products/catalog`
 
 .. _cart/prevent-sale:
 

content/applications/websites/ecommerce/managing_products.rst

@@ -1,14 +0,0 @@
-:nosearch:
-
-========
-Products
-========
-
-.. toctree::
-   :titlesonly:
-
-   managing_products/products
-   managing_products/catalog
-   managing_products/variants
-   managing_products/price_management
-   managing_products/cross_upselling

content/applications/websites/ecommerce/products.rst

@@ -1,6 +1,8 @@
-==================
-Product management
-==================
+:show-content:
+
+========
+Products
+========
 
 Odoo allows you to create, import, and manage your products' pages all within the **Website** app.
 
@@ -17,9 +19,9 @@ To add a product to your catalog, you can either do it in:
   :ref:`Import records <import-data>`.
 
 .. seealso::
-   - :doc:`../managing_products/catalog`
-   - :doc:`../../../sales/sales/products_prices/products/import`
-   - :doc:`Product-related documentation <../../../sales/sales>`
+   - :doc:`products/catalog`
+   - :doc:`../../sales/sales/products_prices/products/import`
+   - :doc:`Product-related documentation <../../sales/sales>`
 
 Publish
 -------
@@ -78,7 +80,7 @@ In the **website builder** window, click :guilabel:`Customize` to enable additio
    - To allow **wishlists**, the option must be enabled in :menuselection:`Website --> Configuration
      --> Settings --> Shop - Products`;
    - To access the :guilabel:`Variants` options, the :doc:`Product Variants
-     <../../../sales/sales/products_prices/products/variants>` option must first be enabled under
+     <../../sales/sales/products_prices/products/variants>` option must first be enabled under
      :menuselection:`Website --> Configuration --> Settings --> Shop - Products`.
 
 Layout
@@ -191,13 +193,13 @@ The **eCommerce-related** fields to translate are:
 
 .. note::
    Having untranslated content on a web page may be detrimental to the user experience and
-   :doc:`SEO <../../../websites/website/pages/seo>`.
+   :doc:`SEO <../../websites/website/pages/seo>`.
 .. note::
    To check the language(s) of your website, go to :menuselection:`Website --> Configuration -->
    Settings --> Website Info section`.
 
 .. seealso::
-   - :doc:`../../../websites/website/pages/seo`
+   - :doc:`../../websites/website/pages/seo`
 
 Website availability
 --------------------
@@ -244,7 +246,7 @@ If you are selling non-prepackaged kits (i.e., the kits are made of individual p
 recommend you read the related documentation to keep track of your stock.
 
 .. seealso::
-   :doc:`../../../inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping`
+   :doc:`../../inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping`
 
 Product comparison
 ==================
@@ -260,9 +262,17 @@ On the product page, scroll down to the :guilabel:`Specifications` section and c
 summary.
 
 .. note::
-   The :guilabel:`Product Comparison Tool` can only be used if :doc:`attributes <variants>` are set
-   on the **product's template**.
+   The :guilabel:`Product Comparison Tool` can only be used if :doc:`attributes <products/variants>`
+   are set on the **product's template**.
 
 .. image:: products/products-compare.png
    :align: center
    :alt: Product comparison window
+
+.. toctree::
+   :titlesonly:
+
+   products/catalog
+   products/variants
+   products/price_management
+   products/cross_upselling

content/applications/websites/ecommerce/products/catalog.rst

@@ -35,7 +35,7 @@ category, the option :guilabel:`Collapsable Category Recursive` appears and allo
    :alt: Categories options for your eCommerce website
 
 .. seealso::
-   :doc:`products`
+   :doc:`../products`
 
 .. _ecommerce-browsing:
 

content/applications/websites/ecommerce/products/variants.rst

@@ -11,7 +11,7 @@ To use product variants, enable them under :menuselection:`Website --> Configura
 in the :guilabel:`Shop - Products` section.
 
 .. seealso::
-   - :doc:`../managing_products/products`
+   - :doc:`../products`
    - :doc:`../../../sales/sales/products_prices/products/variants`
    - :doc:`../../../sales/sales/products_prices/products/import`
 

content/applications/websites/website/configuration/multi_website.rst

@@ -11,7 +11,7 @@ target audience.
 Each website can be designed and configured independently with its own :doc:`domain name
 <domain_names>`, :doc:`theme <../web_design/themes>`, :doc:`pages <../pages>`, :doc:`menus
 <../pages/menus>`, :doc:`languages <translate>`, :doc:`products
-<../../ecommerce/managing_products/products>`, assigned sales team, etc. They can also
+<../../ecommerce/products>`, assigned sales team, etc. They can also
 :ref:`share content and pages <multi-website/website_content>`.
 
 .. tip::

locale/ar/LC_MESSAGES/essentials.po

@@ -696,10 +696,13 @@ msgid ""
 "contact is a repository of vital business information, facilitating "
 "communication and business transactions."
 msgstr ""
+"يتم تثبيت تطبيق *جهات الاتصال* على جميع قواعد بيانات Odoo. يتم إنشاء جهات "
+"الاتصال للعملاء الذين تتعامل معهم الشركة من خلال Odoo. جهة الاتصال هي مستودع"
+" للمعلومات التجارية الحيوية، مما يسهل الاتصالات والمعاملات التجارية. "
 
 #: ../../content/applications/essentials/contacts.rst:10
 msgid "Contact form"
-msgstr ""
+msgstr "استمارة التواصل "
 
 #: ../../content/applications/essentials/contacts.rst:12
 msgid ""
@@ -707,10 +710,12 @@ msgid ""
 "click :guilabel:`Create`. A new form appears where various contact "
 "information can be added."
 msgstr ""
+"لإنشاء جهة اتصال جديدة، انتقل إلى :menuselection:`تطبيق جهات الاتصال`، وانقر"
+" على :guilabel:`إنشاء`. يظهر نموذج جديد حيث يمكن إضافة معلومات اتصال مختلفة."
 
 #: ../../content/applications/essentials/contacts.rst:16
 msgid "Contact type"
-msgstr ""
+msgstr "نوع جهة الاتصال  "
 
 #: ../../content/applications/essentials/contacts.rst:18
 msgid ""
@@ -718,6 +723,9 @@ msgid ""
 "contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, "
 "depending on the type of contact that is being added."
 msgstr ""
+"يسمح Odoo بكل من جهات الاتصال :guilabel:`Individual` و :guilabel:`Company`. "
+"حدد إما :guilabel:`فرد` أو :guilabel:`شركة`، حسب نوع جهة الاتصال التي تتم "
+"إضافتها. "
 
 #: ../../content/applications/essentials/contacts.rst:22
 msgid "Name"
@@ -729,6 +737,8 @@ msgid ""
 ":guilabel:`Company`. This is how the name appears throughout the database. "
 "This field is **mandatory**."
 msgstr ""
+"أولاً، قم بملء اسم :guilabel:`فرد` أو :guilabel:`شركة`. هذه هي الطريقة التي "
+"يظهر بها الاسم في جميع أنحاء قاعدة البيانات. هذا الحقل **إلزامي**. "
 
 #: ../../content/applications/essentials/contacts.rst:28
 msgid ""
@@ -736,6 +746,9 @@ msgid ""
 "linked to it. After selecting :guilabel:`Individual`, a new "
 ":guilabel:`Company Name...` field appears below the first name field."
 msgstr ""
+":guilabel:يمكن أن تحتوي جهات الاتصال `الفردية' على جهة اتصال "
+":guilabel:`شركة` مرتبطة بها. بعد تحديد :guilabel:`فرد`، يظهر حقل جديد "
+":guilabel:`اسم الشركة...` أسفل حقل الاسم الأول. "
 
 #: ../../content/applications/essentials/contacts.rst:33
 msgid "Address"
@@ -755,32 +768,40 @@ msgid ""
 ":guilabel:`Delivery Address`, :guilabel:`Other Address`, and "
 ":guilabel:`Private Address`."
 msgstr ""
+"إذا تم تحديد الخيار :guilabel:`Individual`، فيمكن اختيار *نوع العنوان* من "
+"القائمة المنسدلة. تتضمن خيارات هذه القائمة المنسدلة ما يلي: :guilabel:`جهة "
+"الاتصال`، :guilabel:`عنوان الفاتورة`، :guilabel:`عنوان التسليم`، "
+":guilabel:`عنوان آخر`، و :guilabel:`عنوان خاص`. "
 
 #: ../../content/applications/essentials/contacts.rst:44
 msgid "Additional fields"
-msgstr ""
+msgstr "الحقول الإضافية "
 
 #: ../../content/applications/essentials/contacts.rst:46
 msgid ""
 "Additional details are included on the initial form. The following fields "
 "are available:"
-msgstr ""
+msgstr "يتم تضمين تفاصيل إضافية في النموذج الأولي. الحقول التالية متاحة: "
 
 #: ../../content/applications/essentials/contacts.rst:48
 msgid ":guilabel:`VAT`: Value Added Tax number."
-msgstr ""
+msgstr ":guilabel:`VAT`: رقم ضريبة القيمة المضافة. "
 
 #: ../../content/applications/essentials/contacts.rst:49
 msgid ""
 ":guilabel:`Citizen Identification`: citizen or government identification "
 "number (only available on :guilabel:`Individual`)."
 msgstr ""
+":guilabel:`تعريف المواطن`: رقم هوية المواطن أو الحكومة (متاح فقط على "
+":guilabel:`فردي`). "
 
 #: ../../content/applications/essentials/contacts.rst:51
 msgid ""
 ":guilabel:`Job Position`: list the job position of the "
 ":guilabel:`Individual` (only available on :guilabel:`Individual`)."
 msgstr ""
+":guilabel:`Job Position`: قم بإدراج المنصب الوظيفي لـ :guilabel:`فرد` (متاح "
+"فقط على :guilabel:`فرد`). "
 
 #: ../../content/applications/essentials/contacts.rst:53
 msgid ""
@@ -788,6 +809,9 @@ msgid ""
 "an SMS, or WhatsApp message by hovering over the field on the saved form, "
 "and clicking the desired option."
 msgstr ""
+":guilabel:`Phone`: قائمة رقم الهاتف (مع رمز البلد). قم بإجراء مكالمة أو "
+"إرسال رسالة نصية قصيرة أو رسالة عبر تطبيق WhatsApp من خلال تمرير الماوس فوق "
+"الحقل الموجود في النموذج المحفوظ، والنقر فوق الخيار المطلوب. "
 
 #: ../../content/applications/essentials/contacts.rst:55
 msgid ""
@@ -795,16 +819,21 @@ msgid ""
 "call, send an SMS, or WhatsApp message by hovering over the field on the "
 "saved form, and clicking on the desired option."
 msgstr ""
+":guilabel:`Mobile`: قائمة رقم الهاتف المحمول (مع رمز البلد). قم بإجراء "
+"مكالمة أو إرسال رسالة نصية قصيرة أو رسالة عبر تطبيق WhatsApp من خلال تمرير "
+"الماوس فوق الحقل الموجود في النموذج المحفوظ، والنقر فوق الخيار المطلوب. "
 
 #: ../../content/applications/essentials/contacts.rst:57
 msgid ":guilabel:`Email`: enter the email address with the domain."
-msgstr ""
+msgstr ":guilabel:`Email`: أدخل عنوان البريد الإلكتروني مع المجال. "
 
 #: ../../content/applications/essentials/contacts.rst:58
 msgid ""
 ":guilabel:`Website`: enter the full website address, starting with `http` or"
 " `https`."
 msgstr ""
+":guilabel:`موقع الويب`: أدخل عنوان موقع الويب بالكامل، بدءًا من `http` أو "
+"`https`. "
 
 #: ../../content/applications/essentials/contacts.rst:59
 msgid ""
@@ -812,6 +841,9 @@ msgid ""
 ":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new"
 " one directly from this field."
 msgstr ""
+":guilabel:`Title`: حدد :guilabel:`Doctor`، :guilabel:`Madam`، "
+":guilabel:`Miss`، :guilabel:`Mister`، :guilabel:`Professor`، أو قم بإنشاء "
+"واحدة جديدة مباشرة من هذا الحقل. "
 
 #: ../../content/applications/essentials/contacts.rst:61
 msgid ""
@@ -820,10 +852,14 @@ msgid ""
 "the new tag in the field, and click :guilabel:`Create` from the resulting "
 "drop-down menu."
 msgstr ""
+":guilabel:`العلامات`: أدخل العلامات التي تم تكوينها مسبقًا عن طريق كتابتها "
+"في الحقل، أو النقر فوق القائمة المنسدلة، واختيار واحدة. لإنشاء علامة جديدة، "
+"اكتب العلامة الجديدة في الحقل، ثم انقر فوق :guilabel:`Create` من القائمة "
+"المنسدلة الناتجة. "
 
 #: ../../content/applications/essentials/contacts.rst:66
 msgid "Contacts & Addresses tab"
-msgstr ""
+msgstr "علامة تبويب جهات الاتصال والعناوين  "
 
 #: ../../content/applications/essentials/contacts.rst:68
 msgid ""
@@ -832,6 +868,10 @@ msgid ""
 "associated with a :guilabel:`Company` and related addresses. For example, a "
 "specific contact person for the company can be listed here."
 msgstr ""
+"يوجد في الجزء السفلي من نموذج الاتصال عدة علامات تبويب. في علامة التبويب "
+":guilabel:`جهات الاتصال والعناوين`، يمكن إضافة جهات الاتصال المرتبطة بـ "
+":guilabel:`الشركة` والعناوين ذات الصلة. على سبيل المثال، يمكن إدراج جهة "
+"اتصال محددة للشركة هنا. "
 
 #: ../../content/applications/essentials/contacts.rst:72
 msgid ""
@@ -840,10 +880,14 @@ msgid ""
 ":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create "
 "Contact` pop-up form, in which additional addresses can be configured."
 msgstr ""
+"يمكن إضافة عناوين متعددة على كل من جهات الاتصال :guilabel:`Individual` و "
+":guilabel:`Company`. للقيام بذلك، انقر فوق :guilabel:`إضافة` في علامة "
+"التبويب :guilabel:`جهات الاتصال والعناوين`. يؤدي القيام بذلك إلى ظهور نموذج "
+"منبثق :guilabel:`Create Contact`، حيث يمكن تكوين عناوين إضافية. "
 
 #: ../../content/applications/essentials/contacts.rst-1
 msgid "Add a contact/address to the contact form."
-msgstr ""
+msgstr "أضف جهة اتصال/عنوانًا إلى نموذج الاتصال. "
 
 #: ../../content/applications/essentials/contacts.rst:80
 msgid ""
@@ -851,6 +895,9 @@ msgid ""
 " :guilabel:`Other Address` field at the top to reveal a drop-down menu of "
 "address-related options."
 msgstr ""
+"في النموذج المنبثق :guilabel:`Create Contact`، ابدأ بالنقر فوق الحقل "
+"الافتراضي :guilabel:`عنوان آخر` في الجزء العلوي للكشف عن قائمة منسدلة "
+"بالخيارات المتعلقة بالعنوان. "
 
 #: ../../content/applications/essentials/contacts.rst:83
 msgid "Select any of the following options:"
@@ -894,12 +941,17 @@ msgid ""
 "Once an option is selected, enter the corresponding contact information that"
 " should be used for the specified address type."
 msgstr ""
+"بمجرد تحديد أحد الخيارات، أدخل معلومات الاتصال المقابلة التي يجب استخدامها "
+"لنوع العنوان المحدد. "
 
 #: ../../content/applications/essentials/contacts.rst:98
 msgid ""
 "Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, "
 "along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below."
 msgstr ""
+"أضف :guilabel:`اسم جهة الاتصال`، :guilabel:`العنوان`، :guilabel:`البريد "
+"الإلكتروني`، بالإضافة إلى أرقام :guilabel:`الهاتف` و/أو :guilabel:`الجوال` "
+"أدناه. "
 
 #: ../../content/applications/essentials/contacts.rst:101
 msgid ""
@@ -907,12 +959,16 @@ msgid ""
 "address type has been selected. This is similar to the "
 ":guilabel:`Individual` contact."
 msgstr ""
+"قم بتعيين :guilabel:`Job Position`، الذي يظهر إذا تم تحديد نوع عنوان "
+":guilabel:`Contact`. وهذا مشابه لجهة الاتصال :guilabel:`الفردية`. "
 
 #: ../../content/applications/essentials/contacts.rst:104
 msgid ""
 "To add a note, click on the text field next to :guilabel:`Notes`, and write "
 "anything that is applicable to the customer or contact."
 msgstr ""
+"لإضافة ملاحظة، انقر فوق حقل النص بجوار :guilabel:`Notes`، واكتب أي شيء ينطبق"
+" على العميل أو جهة الاتصال. "
 
 #: ../../content/applications/essentials/contacts.rst:107
 msgid ""
@@ -920,16 +976,21 @@ msgid ""
 ":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save "
 "the address, and immediately input another one."
 msgstr ""
+"ثم انقر فوق :guilabel:`حفظ وإغلاق` لحفظ العنوان، وأغلق نافذة "
+":guilabel:`إنشاء جهة اتصال`. أو انقر فوق :guilabel:`Save & New` لحفظ "
+"العنوان، وإدخال عنوان آخر على الفور. "
 
 #: ../../content/applications/essentials/contacts.rst:111
 msgid "Sales & Purchase tab"
-msgstr ""
+msgstr "علامة تبويب المبيعات والمشتريات "
 
 #: ../../content/applications/essentials/contacts.rst:113
 msgid ""
 "Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the "
 "*Sales*, *Purchase*, **or** *Point of Sale* applications are installed."
 msgstr ""
+"بعد ذلك، هي علامة التبويب :guilabel: `المبيعات والمشتريات`، والتي تظهر فقط "
+"عند تثبيت تطبيقات *Sales* أو *Purchase* أو **أو** *Point of Sale*. "
 
 #: ../../content/applications/essentials/contacts.rst:116
 msgid ""
@@ -937,6 +998,8 @@ msgid ""
 "Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down "
 "menu."
 msgstr ""
+"يمكن تعيين :guilabel:`المركز المالي` في علامة التبويب :guilabel:`المبيعات "
+"والمشتريات`. حدد :guilabel:`الوضع المالي` من القائمة المنسدلة. "
 
 #: ../../content/applications/essentials/contacts.rst:120
 msgid "Sales section"

locale/ar/LC_MESSAGES/hr.po

@@ -4609,7 +4609,7 @@ msgstr ""
 #: ../../content/applications/hr/fleet/new_vehicle.rst:158
 #: ../../content/applications/hr/fleet/service.rst:173
 msgid "Contacts & Addresses tab"
-msgstr ""
+msgstr "علامة تبويب جهات الاتصال والعناوين  "
 
 #: ../../content/applications/hr/fleet/new_vehicle.rst:160
 msgid ""
@@ -4710,7 +4710,7 @@ msgstr ""
 #: ../../content/applications/hr/fleet/new_vehicle.rst:210
 #: ../../content/applications/hr/fleet/service.rst:224
 msgid "Sales & Purchase tab"
-msgstr ""
+msgstr "علامة تبويب المبيعات والمشتريات "
 
 #: ../../content/applications/hr/fleet/new_vehicle.rst:212
 msgid ""

locale/ar/LC_MESSAGES/inventory_and_mrp.po

@@ -27721,7 +27721,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor.rst:5
 msgid "Shop Floor"
-msgstr "طابق المحل "
+msgstr "شاشة التصنيع "
 
 #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:3
 msgid "Shop Floor overview"
@@ -32929,7 +32929,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/plm/management.rst:3
 msgid "Project management"
-msgstr ""
+msgstr "إدارة المشاريع "
 
 #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:3
 msgid "Approvals"

locale/ar/LC_MESSAGES/productivity.po

@@ -8102,7 +8102,7 @@ msgstr ""
 
 #: ../../content/applications/productivity/to_do.rst:61
 msgid "Scheduling activities"
-msgstr ""
+msgstr "جدولة الأنشطة "
 
 #: ../../content/applications/productivity/to_do.rst:63
 msgid ""

locale/ar/LC_MESSAGES/sales.po

@@ -40,18 +40,24 @@ msgid ""
 "the pipeline and manage your day-to-day activities with meetings and next "
 "activities."
 msgstr ""
+"يساعدك **تطبيق إدارة علاقات العملاء لدى أودو** على تنظيم أنشطة المبيعات "
+"الخاصة بك: تتبع العملاء المهتمين وإغلاق الفرص والحصول على توقعات دقيقة. حافظ"
+" على تنظيم الفرص من خلال مخطط سير العمل وأدر أنشطتك اليومية من خلال "
+"الاجتماعات والأنشطة التالية. "
 
 #: ../../content/applications/sales/crm.rst:15
 msgid "`Odoo Tutorials: CRM <https://www.odoo.com/slides/crm-16>`_"
 msgstr ""
+"`دروس أودو التعليمية: إدارة علاقات العملاء "
+"<https://www.odoo.com/slides/crm-16>`_ "
 
 #: ../../content/applications/sales/crm/acquire_leads.rst:5
 msgid "Acquire leads"
-msgstr ""
+msgstr "استقطاب العملاء المهتمين "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:3
 msgid "Convert leads into opportunities"
-msgstr ""
+msgstr "تحويل العملاء المهتمين إلى فرص "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:5
 msgid ""
@@ -105,10 +111,13 @@ msgid ""
 "Configuration --> Settings` and check the box labeled, :guilabel:`Leads`. "
 "Then, click :guilabel:`Save`."
 msgstr ""
+"لتفعيل إعداد *العملاء المهتمين*، اذهب إلى :menuselection:`تطبيق إدارة علاقات"
+" العملاء --> التهيئة --> الإعدادات` وقم بتحديد المربع المسمى "
+":guilabel:`العملاء المهتمين`. ثم اضغط على :guilabel:`حفظ`. "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst-1
 msgid "Leads setting on CRM configuration page."
-msgstr ""
+msgstr "إعداد العملاء المهتمين في صفحة تهيئة تطبيق إدارة علاقات العملاء. "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:18
 msgid ""
@@ -119,7 +128,7 @@ msgstr ""
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst-1
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst-1
 msgid "Leads menu on CRM application."
-msgstr ""
+msgstr "قائمة العملاء المهتمين في تطبيق إدارة علاقات العملاء. "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:25
 msgid ""
@@ -133,7 +142,7 @@ msgstr ""
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:36
 msgid "Convert a lead into an opportunity"
-msgstr ""
+msgstr "تحويل العميل المهتم إلى فرصة "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:38
 msgid ""
@@ -161,7 +170,7 @@ msgstr ""
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst-1
 msgid "Create opportunity button on a lead record."
-msgstr ""
+msgstr "زر إنشاء فرصة على سجل العميل المهتم. "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:56
 msgid ""
@@ -187,6 +196,10 @@ msgid ""
 "the resulting record is referred to as an opportunity, regardless of which "
 "record was created first."
 msgstr ""
+"عند الدمج، يمنح Odoo الأولوية للعميل المتوقع/الفرصة التي تم إنشاؤها في "
+"النظام أولاً، ويدمج المعلومات في العميل المحتمل/الفرصة التي تم إنشاؤها لأول "
+"مرة. ومع ذلك، إذا تم دمج عميل متوقع وفرصة، تتم الإشارة إلى السجل الناتج على "
+"أنه فرصة، بغض النظر عن السجل الذي تم إنشاؤه أولاً. "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:69
 msgid ""
@@ -202,15 +215,17 @@ msgid ""
 "If the lead has already been assigned to a salesperson or a team, these "
 "fields automatically populate with that information."
 msgstr ""
+"إذا تم بالفعل تعيين العميل المتوقع إلى مندوب مبيعات أو فريق، فسيتم تعبئة هذه"
+" الحقول تلقائيًا بهذه المعلومات. "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst-1
 msgid "Create opportunity pop-up."
-msgstr ""
+msgstr "إنشاء نافذة منبثقة للفرصة. "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:81
 msgid ""
 "Under the :guilabel:`Customer` heading, choose from the following options:"
-msgstr ""
+msgstr "ضمن عنوان :guilabel:`Customer`، اختر من بين الخيارات التالية: "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:83
 msgid ""
@@ -235,7 +250,7 @@ msgstr ""
 msgid ""
 "Lastly, when all configurations are complete, click :guilabel:`Create "
 "Opportunity`."
-msgstr ""
+msgstr "وأخيرًا، عند اكتمال كافة التكوينات، انقر فوق :guilabel:`إنشاء فرصة`. "
 
 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:92
 msgid ""
@@ -270,7 +285,7 @@ msgstr ""
 
 #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:17
 msgid "Configure email aliases"
-msgstr ""
+msgstr "تهيئة ألقاب البريد الإلكتروني "
 
 #: ../../content/applications/sales/crm/acquire_leads/email_manual.rst:19
 msgid ""
@@ -476,7 +491,7 @@ msgstr ""
 
 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:3
 msgid "Lead mining"
-msgstr ""
+msgstr "استقطاب العملاء المهتمين "
 
 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:8
 msgid ""
@@ -496,10 +511,12 @@ msgstr ""
 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1
 msgid "Activate lead mining in Odoo CRM settings."
 msgstr ""
+"قم بتفعيل خاصية استقطاب العملاء المهتمين في تطبيق إدارة علاقات العملاء لدى "
+"أودو. "
 
 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:23
 msgid "Generate leads"
-msgstr ""
+msgstr "إنشاء العملاء المهتمين "
 
 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:25
 msgid ""
@@ -518,7 +535,7 @@ msgstr ""
 
 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1
 msgid "The Generate Leads button to use the lead mining feature."
-msgstr ""
+msgstr "زر إنشاء العملاء المهتمين لاستخدام خاصية استقطاب العملاء المهتمين. "
 
 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:37
 msgid ""
@@ -531,6 +548,8 @@ msgid ""
 "The pop-up window with the selection criteria in order to generate leads in "
 "Odoo."
 msgstr ""
+"النافذة المنبثقة التي تحتوي على فئات الخيارات التي يتم على أساسها إنشاء "
+"العملاء المهتمين في أودو. "
 
 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:44
 msgid ""
@@ -675,7 +694,7 @@ msgstr ""
 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst-1
 msgid "Buy credits in the Odoo IAP settings."
-msgstr ""
+msgstr "قم بشراء الرصيد في إعدادات عمليات الشراء داخل التطبيق في أودو. "
 
 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:112
 msgid ""
@@ -956,7 +975,7 @@ msgstr ""
 
 #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:9
 msgid "Create a new quotation"
-msgstr ""
+msgstr "إنشاء عرض سعر جديد "
 
 #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:11
 msgid ""
@@ -1336,7 +1355,7 @@ msgstr ""
 
 #: ../../content/applications/sales/crm/optimize.rst:5
 msgid "Optimize your Day-to-Day work"
-msgstr ""
+msgstr "قم بتحسين أعمالك اليومية "
 
 #: ../../content/applications/sales/crm/optimize/gamification.rst:3
 msgid "CRM Gamification"
@@ -1479,7 +1498,7 @@ msgstr ""
 
 #: ../../content/applications/sales/crm/optimize/gamification.rst:87
 msgid "Create a challenge"
-msgstr ""
+msgstr "إنشاء تحدي "
 
 #: ../../content/applications/sales/crm/optimize/gamification.rst:89
 msgid ""
@@ -1621,7 +1640,7 @@ msgstr ""
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:3
 msgid "Lead enrichment"
-msgstr ""
+msgstr "إثراء العملاء المهتمين "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:5
 msgid ""
@@ -1630,6 +1649,10 @@ msgid ""
 " requires credits to use, and is available for existing leads in an Odoo "
 "database."
 msgstr ""
+"*إثراء العملاء المهتمين* هي عبارة عن خدمة توفر معلومات العمل الخاصة بجهة "
+"اتصال مرتبطة بالعميل المهتم. إثراء العملاء المهتمين هي عملية شراء داخل "
+"التطبيق (IAP) تتطلب أرصدة لاستخدامها، وهي متاحة للعملاء المهتمين الحاليين في"
+" قاعدة بيانات أودو. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:9
 msgid ""
@@ -1640,6 +1663,12 @@ msgid ""
 ":guilabel:`Estimated revenue`, :guilabel:`Phone` number, "
 ":guilabel:`Timezone`, and :guilabel:`Technologies Used`."
 msgstr ""
+"يمكن أن تتضمن المعلومات المقدمة من خلال إثراء العملاء المهتمين معلومات عامة "
+"عن الشركة (كاسم الشركة بالكامل وشعارها)، وحسابات وسائل التواصل الاجتماعي، "
+":guilabel:`نوع الشركة`، :guilabel:`معلومات التأسيس`، :guilabel:`معلومات "
+"القطاعات`، عدد :guilabel:`الموظفين`، :guilabel:`الإيرادات المقدرة`، "
+":guilabel:`رقم الهاتف`، :guilabel:`المنطقة الزمنية`، و :guilabel:`التقنيات "
+"المستخدمة`. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:16
 #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:78
@@ -1649,6 +1678,11 @@ msgid ""
 "credits for the database. This includes demo/training databases, educational"
 " databases, and one-app-free databases."
 msgstr ""
+"يحصل مستخدمو إصدار أودو للمؤسسات الذين لديهم اشتراك سارٍ على رصيد مجاني "
+"لاختبار خصائص :abbr:`IAP (عمليات الشراء داخل التطبيق)` قبل اتخاذ قرار بشراء "
+"شراء المزيد من الأرصدة لقاعدة البيانات. يتضمن ذلك قواعد البيانات "
+"التجريبية/التدريبية، وقواعد البيانات التعليمية، وقواعد البيانات المجانية ذات"
+" التطبيق الواحد. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:21
 msgid ""
@@ -1658,10 +1692,16 @@ msgid ""
 ":guilabel:`CRM` section activate the :guilabel:`Leads` option and click "
 ":guilabel:`Save`."
 msgstr ""
+"**يجب** أن يتم تفعيل خاصية *العملاء المهتمين* في صفحة إعدادات *إدارة علاقات "
+"العملاء* حتى تتمكن من استخدام خاصية إثراء العملاء المهتمين. للوصول إلى "
+"إعدادات *إدارة علاقات العملاء*، قم بالذهاب إلى :menuselection:`تطبيق إدارة "
+"علاقات العملاء --> التهيئة --> الإعدادات`. تحت قسم :guilabel:`إدارة علاقات "
+"العملاء`، قم بتفعيل خيار :guilabel:`العملاء المهتمين` ثم اضغط على "
+":guilabel:`حفظ`. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:27
 msgid "Lead enrichment set up"
-msgstr ""
+msgstr "إعدادات إثراء العملاء المهتمين "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:29
 msgid ""
@@ -1672,16 +1712,24 @@ msgid ""
 "demand only` or :guilabel:`Enrich all leads automatically`. Click the "
 ":guilabel:`Save` button to activate the changes."
 msgstr ""
+"لإعداد خاصية إثراء العملاء المهتمين في تطبيق *إدارة علاقات العملاء*، اذهب "
+"إلى :menuselection:`تطبيق إدارة علاقات العملاء --> التهيئة --> الإعدادات`. "
+"بعد ذلك، ضمن قسم :guilabel:`إنشاء العملاء المهتمين`، قم بتحديد مربع الاختيار"
+" بجوار :guilabel:`إثراء العملاء المهتمين`، وحدد إما :guilabel:`إثراء العملاء"
+" المهتمين عند الطلب فقط` أو :guilabel:`إثراء كافة العملاء المهتمين "
+"تلقائياً`. قم بالضغط على :guilabel:`حفظ` لتفعيل التغييرات. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst-1
 msgid ""
 "CRM lead generation settings page, with lead enrichment activation highlighted, and enrich\n"
 "leads on demand only chosen."
 msgstr ""
+"صفحة إعدادات إنشاء عملاء مهتمين لإدارة علاقات العملاء، مع التركيز على تفعيل خاصية إثراء العملاء المهتمين وتحديد\n"
+"خيار إثراء العملاء المهتمين عند الطلب فقط. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:41
 msgid "Enrich leads"
-msgstr ""
+msgstr "إثراء العملاء المهتمين "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:43
 msgid ""
@@ -1689,10 +1737,13 @@ msgid ""
 "customer set on the lead. There are two different ways that a lead can be "
 "enriched: *automatically* or *manually*."
 msgstr ""
+"يعتمد إثراء العملاء المهتمين على نطاق عنوان البريد الإلكتروني الخاص بالعميل "
+"الذي تم تعيينه للعميل المهتم. توجد طريقتان مختلفتان يمكن من خلالهما إثراء "
+"العميل المهتم: *تلقائياً* أو *يدوياً*. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:47
 msgid "Automatically enrich leads"
-msgstr ""
+msgstr "إثراء العملاء المهتمين تلقائياً "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:49
 msgid ""
@@ -1702,6 +1753,11 @@ msgid ""
 "sixty minutes, and enrichment occurs on leads, after a remote database is "
 "contacted."
 msgstr ""
+"أثناء الإعداد، إذا تم تحديد خيار :guilabel:`إثراء كافة  العملاء المهتمين "
+"تلقائياً` في صفحة :guilabel:`إعدادات` *إدارة علاقات العملاء*، فلن يضطر "
+"المستخدم إلى اتخاذ أي إجراء لإثراء العميل المهتم. يتم تشغيل الإجراء المجدول "
+"تلقائياً، كل 60 دقيقة، ويتم إثراء العملاء المهتمين بعد الاتصال بقاعدة بيانات"
+" عن بُعد. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:55
 msgid ""
@@ -1713,20 +1769,29 @@ msgid ""
 "necessary adjustments. In the :guilabel:`Execute Every` field, enter a value"
 " greater than, or equal to, five minutes."
 msgstr ""
+"للوصول إلى cron الذي يتم تشغيله لإثراء العملاء المهتميت تلقائياً، قم بتفعيل "
+":ref:`وضع المطوِّر <developer-mode>`، ثم انتقل إلى :menuselection:`تطبيق "
+"الإعدادات --> القائمة الفنية --> قسم الأتمتة --> الإجراءات المجدولة`. في "
+"شريط :guilabel:`البحث...`، قم بكتابة `إدارة علاقات العملاء`. اضغط على "
+"النتيجة المسماة :guilabel:`إدارة علاقات العملاء: إثراء العملاء المهتمين "
+"(IAP)`، وأجرِ أي تعديلات لازمة. في حقل :guilabel:`تنفيذ كل`، أدخل قيمة أكبر "
+"من أو تساوي خمس دقائق. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:62
 msgid ""
 "The following is an example of lead enrichment data that has been "
 "autocompleted successfully:"
 msgstr ""
+"فيما يلي مثال على بيانات إثراء العملاء المهتمين التي تم إكمالها تلقائياً "
+"بنجاح: "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:0
 msgid "Chatter showing lead enrichment data."
-msgstr ""
+msgstr "نافذة الدردشة تُظهِر بيانات عملية إثراء العملاء المهتمين. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:69
 msgid "Manually enrich leads"
-msgstr ""
+msgstr "إثراء العملاء المهتمين يدوياً "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:71
 msgid ""
@@ -1736,6 +1801,11 @@ msgid ""
 "enriched. This is achieved by clicking the :guilabel:`Enrich` button in the "
 "top menu of the lead."
 msgstr ""
+"إذا تم تحديد خيار :guilabel:`إثراء العملاء المهتمين عند الطلب فقط` في صفحة "
+":guilabel:`إعدادات` *إدارة علاقات العملاء*، عند تفعيل خيار :guilabel:`إثراء "
+"العملاء المهتمين`، فإن كل عميل مهتم يرغب المستخدم في إثرائه **يجب** أن يتم "
+"إثراؤه يدوياً. يتم تحقيق ذلك عن طريق الضغط على زر :guilabel:`إثراء` الموجود "
+"في القائمة العلوية للعميل المهتم. "
 
 #: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:76
 msgid ""
@@ -4947,6 +5017,8 @@ msgid ""
 "opportunity is logged in the chatter, and the information fields, for "
 "reference."
 msgstr ""
+"عند دمج الفرص، لا يتم فقدان أي معلومات. يتم تسجيل البيانات من الفرصة الأخرى "
+"في الدردشة وحقول المعلومات للرجوع إليها. "
 
 #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:15
 msgid "Identify similar leads and opportunities"
@@ -5012,6 +5084,9 @@ msgid ""
 "their related information. To merge those selected leads/opportunities, "
 "click :guilabel:`Merge`."
 msgstr ""
+"أسفل هذه الحقول، يتم إدراج العملاء المتوقعين/الفرص المراد دمجها، بالإضافة "
+"إلى المعلومات ذات الصلة بهم. لدمج هؤلاء العملاء المتوقعين/الفرص المحددة، "
+"انقر فوق :guilabel:`Merge`. "
 
 #: ../../content/applications/sales/crm/pipeline/merge_similar.rst-1
 msgid ""
@@ -19503,7 +19578,7 @@ msgstr ""
 
 #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1
 msgid "Add a contact/address to the contact form."
-msgstr ""
+msgstr "أضف جهة اتصال/عنوانًا إلى نموذج الاتصال. "
 
 #: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:38
 msgid ""

locale/ar/LC_MESSAGES/services.po

@@ -4498,13 +4498,15 @@ msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:230
 msgid ":ref:`Reporting views <reporting/views>`"
-msgstr ""
+msgstr ":ref:`نوافذ عرض التقارير <reporting/views>` "
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:231
 msgid ""
 ":doc:`Allow customers to close their tickets "
 "</applications/services/helpdesk/advanced/close_tickets>`"
 msgstr ""
+":doc:`السماح للعملاء بإغلاق تذاكرهم الخاصة بأنفسهم "
+"</applications/services/helpdesk/advanced/close_tickets>` "
 
 #: ../../content/applications/services/planning.rst:5
 msgid "Planning"
@@ -5146,6 +5148,8 @@ msgid ""
 "assign activities to coworkers, and keep track of each project's "
 "profitability."
 msgstr ""
+"تطبيق المشاريع لدى أودو هو أداة لإدارة مشاريعك الجارية، مثل جدولة المهام، "
+"وإسناد الأنشطة إلى زملاء العمل، وتتبع ربحية كل مشروع. "
 
 #: ../../content/applications/services/project.rst:14
 #: ../../content/applications/services/timesheets.rst:11
@@ -5153,10 +5157,12 @@ msgid ""
 "`Odoo Tutorials: Project and Timesheets "
 "<https://www.odoo.com/slides/project-and-timesheets-21>`_"
 msgstr ""
+"`دروس أودو التعليمية: المشاريع والجداول الزمنية "
+"<https://www.odoo.com/slides/project-and-timesheets-21>`_ "
 
 #: ../../content/applications/services/project/project_management.rst:3
 msgid "Project management"
-msgstr ""
+msgstr "إدارة المشاريع "
 
 #: ../../content/applications/services/project/project_management.rst:5
 msgid ""
@@ -5164,6 +5170,9 @@ msgid ""
 "projects are broken down into tasks, which are categorized on a whiteboard "
 "according to what production phase they are in."
 msgstr ""
+"يستخدم تطبيق المشاريع لدى أودو نظام **كانبان** لإدارة المشاريع. هذا يعني أن "
+"كافة المشاريع مقسمة إلى مهام أصغر، والتي يتم تصنيفها على السبورة البيضاء "
+"وفقاً لمرحلة الإنتاج التي تمر بها. "
 
 #: ../../content/applications/services/project/project_management.rst:8
 msgid "Did you know?"
@@ -5174,12 +5183,16 @@ msgid ""
 "The word **Kanban** comes from Japanese and refers to the \"visual board\" "
 "management method."
 msgstr ""
+"كلمة **كانبان** تأتي من اللغة اليابانية وتشير إلى طريقة إدارة \"اللوحة "
+"المرئية\". "
 
 #: ../../content/applications/services/project/project_management.rst:13
 msgid ""
 "`Odoo Tutorials: Kanban Project Management "
 "<https://www.odoo.com/slides/slide/kanban-project-management-1664>`_"
 msgstr ""
+"`دروس أودو التعليمية: إدارة المشاريع على نافذة عرض كانبان "
+"<https://www.odoo.com/slides/slide/kanban-project-management-1664>`_ "
 
 #: ../../content/applications/services/project/project_management.rst:19
 msgid ""
@@ -5187,20 +5200,24 @@ msgid ""
 "project. Enter a :guilabel:`Name` for your project and click "
 ":guilabel:`Create Project`."
 msgstr ""
+"افتح تطبيق **المشاريع** ثم اضغط على :guilabel:`إنشاء` لبدء مشروع جديد. قم "
+"بإدخال :guilabel:`اسم` لمشروعك ثم اضغط على :guilabel:`إنشاء مشروع`. "
 
 #: ../../content/applications/services/project/project_management.rst:22
 msgid ""
 "You can customize your existing **projects** from the dashboard by clicking "
 "the drop-down toggle button (:guilabel:`⋮`) on your project's **card**."
 msgstr ""
+"يمكنك تخصيص **مشاريعك** الموجودة بالفعل من لوحة البيانات عن طريق الضغط على "
+"زر التبديل المنسدل (:guilabel:`⋮`) الموجود على **بطاقة** مشروعك. "
 
 #: ../../content/applications/services/project/project_management.rst-1
 msgid "Project card"
-msgstr ""
+msgstr "بطاقة المشروع "
 
 #: ../../content/applications/services/project/project_management.rst:29
 msgid "This enables a new menu divided into four parts:"
-msgstr ""
+msgstr "يؤدي ذلك إلى تمكين قائمة جديدة مقسمة إلى أربعة أجزاء: "
 
 #: ../../content/applications/services/project/project_management.rst:31
 msgid ""
@@ -5210,80 +5227,96 @@ msgid ""
 "such as :guilabel:`Documents`. All uploaded files can be found under this "
 "menu, as well as in the **Documents** app, under :guilabel:`Projects`;"
 msgstr ""
+":guilabel:`نافذة العرض`: ألقِ نظرة عامة على مكونات مشروعك، مثل "
+":guilabel:`المهام`، و :guilabel:`مؤشرات التقدم الرئيسية`، و "
+":guilabel:`تحديثات المشروع`. بناءً على التطبيقات التي قمت بتنشيطها، قد تتوفر"
+" المزيد من الخيارات، مثل :guilabel:`المستندات`. ستجد كافة الملفات التي تم "
+"تحميلها ضمن هذه القائمة، وكذلك في تطبيق **المستندات**، ضمن "
+":guilabel:`المشاريع`؛ "
 
 #: ../../content/applications/services/project/project_management.rst:35
 msgid ""
 ":guilabel:`Reporting`: analyze your project's progress and profitability "
 "through graphics and statistics;"
 msgstr ""
+":guilabel:`التقارير`: قم بتحليل مستوى تقدم مشروعك وربحيته من خلال الرسومات "
+"والإحصائيات؛ "
 
 #: ../../content/applications/services/project/project_management.rst:37
 msgid ""
 "**Color**: make a line of color appear on the left side of the card so that "
 "your project is more recognizable;"
 msgstr ""
+"**اللون**: اجعل خطاً من الألوان يظهر على الجانب الأيسر من البطاقة حتى يسهل "
+"التعرف على مشروعك؛ "
 
 #: ../../content/applications/services/project/project_management.rst:39
 msgid ":guilabel:`Settings`: you can change the following:"
-msgstr ""
+msgstr ":guilabel:`الإعدادات`: يمكنك تغيير التالي: "
 
 #: ../../content/applications/services/project/project_management.rst:41
 msgid "the :guilabel:`Name` of the project;"
-msgstr ""
+msgstr ":guilabel:`اسم` المشروع؛ "
 
 #: ../../content/applications/services/project/project_management.rst:42
 msgid "the :guilabel:`Name of the tasks` found under that project;"
-msgstr ""
+msgstr ":guilabel:`أسماء المهام` موجودة أسفل ذلك المشروع؛ "
 
 #: ../../content/applications/services/project/project_management.rst:43
 msgid "the :guilabel:`Customer` for whom the project is intended;"
-msgstr ""
+msgstr ":guilabel:`العميل` الشخص الذي يتم إنجاز المشؤوع من أجله؛ "
 
 #: ../../content/applications/services/project/project_management.rst:44
 msgid "the :guilabel:`Tags` used for filtering;"
-msgstr ""
+msgstr ":guilabel:`علامات التصنيف` المستخدَمة للتصفية؛ "
 
 #: ../../content/applications/services/project/project_management.rst:45
 msgid "the :guilabel:`Company` responsible for the project;"
-msgstr ""
+msgstr ":guilabel:`الشركة` مسؤولة عن تنفيذ المشروع؛ "
 
 #: ../../content/applications/services/project/project_management.rst:46
 msgid "the employee designated as :guilabel:`Project Manager`;"
-msgstr ""
+msgstr "الموظف المعيّن كـ :guilabel:`مدير المشروع`؛ "
 
 #: ../../content/applications/services/project/project_management.rst:47
 msgid "the :guilabel:`Planned Date` of the project;"
-msgstr ""
+msgstr ":guilabel:`التاريخ المخطط له` لإنجاز المشروع؛ "
 
 #: ../../content/applications/services/project/project_management.rst:48
 msgid "the total :guilabel:`Allocated Hours` for that project."
-msgstr ""
+msgstr "إجمالي :guilabel:`الساعات المخصصة` لذلك المشروع. "
 
 #: ../../content/applications/services/project/project_management.rst:50
 msgid ""
 "Additionally, you can mark the project as :guilabel:`Favorite`, allowing you"
 " to find it using the :guilabel:`My Favorites` filter on the Kanban view;"
 msgstr ""
+"إضافة إلى ذلك، يمكنك وضع علامة على المشروع على أنه :guilabel:`مفضل`، مما "
+"يتيح لك العثور عليه باستخدام فلتر :guilabel:`المفضلة` في نافذة عرض كانبان؛ "
 
 #: ../../content/applications/services/project/project_management.rst-1
 msgid "Project settings"
-msgstr ""
+msgstr "إعدادات المشروع "
 
 #: ../../content/applications/services/project/project_management.rst:58
 msgid ""
 "`Odoo Tutorials: Customize projects "
 "<https://www.odoo.com/slides/slide/customize-projects-3615?fullscreen=1>`_"
 msgstr ""
+"`دروس أودو التعليمية : تخصيص المشاريع "
+"<https://www.odoo.com/slides/slide/customize-projects-3615?fullscreen=1>`_ "
 
 #: ../../content/applications/services/project/project_management.rst:61
 msgid ""
 "Further settings are available under the :guilabel:`Settings` tab. Most of "
 "them are *only* available depending on the activated apps."
 msgstr ""
+"تتوفر المزيد من الإعدادات تحت علامة تبويب :guilabel:`الإعدادات`. معظمها متاح"
+" *فقط* بناءً على التطبيقات التي تم تفعيلها. "
 
 #: ../../content/applications/services/project/project_management.rst:65
 msgid "Scheduling activities"
-msgstr ""
+msgstr "جدولة الأنشطة "
 
 #: ../../content/applications/services/project/project_management.rst:67
 msgid ""
@@ -5296,12 +5329,22 @@ msgid ""
 "According to the :guilabel:`Activity Type`, you may have **additional "
 "options** available."
 msgstr ""
+"يمكنك جدولة **الأنشطة** لكل مشروع (مثل :guilabel:`مكالمة`، "
+":guilabel:`اجتماع`، وما إلى ذلك)، من خلال الضغط على أيقونة **الساعة** "
+"الموجودة في المشروع. يؤدي القيام بذلك إلى فتح قائمة بالأنشطة التي تمت "
+"جدولتها بالفعل ويتيح لك التخطيط للأنشطة **الجديدة** عن طريق الضغط على "
+":guilabel:`+ جدولة نشاط`. قم بتحديد :guilabel:`نوع النشاط` من النافذة "
+"المنبثقة ثم أدخِل :guilabel:`ملخص` هذا النشاط و :guilabel:`تاريخ الاستحقاق`،"
+" وقم بإسناده إلى موظف. وفقاً لـ :guilabel:`نوع النشاط`، قد تكون لديك "
+"**خيارات إضافية** متاحة. "
 
 #: ../../content/applications/services/project/project_management.rst:75
 msgid ""
 "If an activity is **already** scheduled, the icon may change to a **phone**,"
 " **group of people**, or other."
 msgstr ""
+"إذا تمت جدولة النشاط **بالفعل**، فقد تتغير الأيقونة إلى **هاتف** أو **مجموعة"
+" من الأشخاص** أو غير ذلك. "
 
 #: ../../content/applications/services/project/tasks.rst:5
 msgid "Tasks"
@@ -5309,7 +5352,7 @@ msgstr "المهام"
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:3
 msgid "Create Project's Tasks from an Email Alias"
-msgstr ""
+msgstr "قم بإنشاء مهام المشروع من لقب البريد الإلكتروني "
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:5
 msgid ""
@@ -5319,16 +5362,21 @@ msgid ""
 "structured work. It automatically creates a task in the first stage of a "
 "project."
 msgstr ""
+"عندما يكون لديك بالفعل عنوان بريد إلكتروني ييتذكره العملاء بسهولة، فليس من "
+"الجيد تغييره. عوضاً عن ذلك، قم بربط هذا العنوان بمشروعك وتحويل تلك المحادثات"
+" إلى عمل منظم. يقوم تلقائياً بإنشاء مهمة في المرحلة الأولى من المشروع. "
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:11
 msgid "Set up an incoming email server"
-msgstr ""
+msgstr "إعداد خادم البريد الوارد "
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:14
 msgid ""
 "On the *Settings* application, enable *External Email Servers* and define "
 "the incoming email alias you would like to use."
 msgstr ""
+"في تطبيق *الإعدادات*، قم بتمكين *خوادم البريد الإلكتروني الخارجية* وحدد لقب "
+"البريد الإلكتروني الوارد الذي ترغب في استخدامه. "
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:15
 msgid ""
@@ -5340,7 +5388,7 @@ msgstr ""
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:18
 msgid "Configure the email alias in your project"
-msgstr ""
+msgstr "قم بتهيئة لقب البريد الإلكتروني في مشروعك "
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:22
 msgid ""
@@ -5349,34 +5397,44 @@ msgid ""
 "*Emails* tab, define the wanted email alias and choose the policy to receive"
 " a message."
 msgstr ""
+"الآن بعد أن قمت بإعداد خادم البريد الإلكتروني الوارد، اذهب إلى "
+":menuselection:`المشروع --> التهيئة --> المشاريع --> تحرير`. ضمن علامة تبويب"
+" *رسائل البريد الإلكتروني*، قم بتحدبد لقب البريد الإلكتروني المطلوب واختر "
+"السياسة لتلقي الرسالة. "
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:23
 msgid "In addition, you can now directly set it when creating a new project."
-msgstr ""
+msgstr "إضافة إلى ذلك، يمكنك الآن ضبطه مباشرة عند إنشاء مشروع جديد. "
 
 #: ../../content/applications/services/project/tasks/email_alias.rst-1
 msgid ""
 "In the settings of your project, define the emails alias under the tab email"
 " in Odoo Project"
 msgstr ""
+"في إعدادات مشروعك، قم بتحديد اللقب لرسائل البريد الإلكتروني تحت علامة تبويب "
+"البريد الإلكتروني، في تطبيق المشاريع لدى أودو "
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:30
 msgid ""
 "All the recipients of the email (To/Cc/Bcc) are automatically added as "
 "followers of the task."
 msgstr ""
+"تتم إضافة كافة مستلمي البريد الإلكتروني (المُرسَل إليه/نسخة/نسخة مخفية) "
+"تلقائياً كمتابعين للمهمة. "
 
 #: ../../content/applications/services/project/tasks/email_alias.rst:32
 msgid "The email can be seen under the name of your project on the dashboard."
-msgstr ""
+msgstr "يمكن رؤية البريد الإلكتروني تحت اسم مشروعك في لوحة البيانات. "
 
 #: ../../content/applications/services/project/tasks/email_alias.rst-1
 msgid "View of the email alias chosen on the dashboard view in Odoo Project"
 msgstr ""
+"عرض لقب البريد الإلكتروني الذي تم اختياره في نافذة عرض لوحة البيانات في "
+"تطبيق المشاريع لدى أودو "
 
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:3
 msgid "Recurring tasks"
-msgstr ""
+msgstr "المهام المتكررة "
 
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:5
 msgid ""
@@ -5384,12 +5442,17 @@ msgid ""
 "times: for example, weekly meetings or status reports. The **recurring "
 "tasks** feature allows you to automate the creation of those tasks."
 msgstr ""
+"عند التعامل مع مشروع ما، غالباً ما تحتاج إلى تنفيذ نفس المهمة عدة مرات: على "
+"سبيل المثال، الاجتماعات الأسبوعية أو تقارير الحالة. تتيح لك خاصية **المهام "
+"المتكررة** إمكانية إنشاء تلك المهام تلقائياً. "
 
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:10
 msgid ""
 "`Odoo Tutorials: Recurring tasks "
 "<https://www.odoo.com/slides/slide/recurring-tasks-1946>`_"
 msgstr ""
+"`دروس أودو التعليمية: المهام المتكررة "
+"<https://www.odoo.com/slides/slide/recurring-tasks-1946>`_ "
 
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:15
 msgid ""
@@ -5400,7 +5463,7 @@ msgstr ""
 
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:19
 msgid "Set up task recurrence"
-msgstr ""
+msgstr "قم بإعداد وتيرة تكرار المهمة "
 
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:21
 msgid ""
@@ -5427,6 +5490,8 @@ msgid ""
 ":guilabel:`Stage`: first stage of the project dashboard (:guilabel:`New` or "
 "equivalent);"
 msgstr ""
+":guilabel:`المرحلة`: المرحلة الأولى من لوحة بيانات المشروع "
+"(:guilabel:`جديدة` أو ما يعادلها)؛ "
 
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:31
 msgid ""
@@ -5434,6 +5499,9 @@ msgid ""
 ":guilabel:`Assignees`, :guilabel:`Customer`, :guilabel:`Tags`: copied from "
 "the original task;"
 msgstr ""
+":guilabel:`الاسم`، :guilabel:`الوصف`، :guilabel:`المشروع`، "
+":guilabel:`الأفراد المسند إليهم`، :guilabel:`العميل`، :guilabel:`علامات "
+"التصنيف`: يتم نسخها من المهمة الأصلية؛ "
 
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:33
 msgid ""
@@ -5446,11 +5514,11 @@ msgstr ""
 msgid ""
 "A **smart button** on the task displays the total number of existing "
 "recurrences."
-msgstr ""
+msgstr "يعرض **الزر الذكي** الموجود في المهمة إجمالي عدد التكرارات الموجودة. "
 
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:39
 msgid "Edit or stop task recurrence"
-msgstr ""
+msgstr "تحرير أو إيقاف تكرار المهمة "
 
 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:41
 msgid ""
@@ -5471,7 +5539,7 @@ msgstr "الجداول الزمنية "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst:3
 msgid "Create Timesheets upon Time Off Validation"
-msgstr ""
+msgstr "قم بإنشاء جداول زمنية عند تصديق الإجازات "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst:5
 msgid ""
@@ -5480,18 +5548,27 @@ msgid ""
 "does not leave place for forgetfulness and questions after hours that have "
 "not been timesheeted by the employee."
 msgstr ""
+"يقوم أودو تلقائياً بإعداد الجداول الزمنية للمشروع/المهام بناءً على طلبات "
+"الإجازة. يتيح لك ذلك إمكانية التحكم الشامل بشكل أفضل فيما يتعلق بالتحقق من "
+"صحة الجداول الزمنية، لأنه لا يترك مجالاً للنسيان والأسئلة بعد ساعات العمل "
+"التي لم تتم جدولتها من قِبَل الموظف. "
 
 #: ../../content/applications/services/timesheets/overview/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."
 msgstr ""
+"قم بتفعيل :ref: `وضع المطوِّر <developer-mode>` ثم اذهب إلى *الجداول "
+"الزمنية* وقم بتغيير *المشروع* و*المهمة* التي تم تعيينها افتراضياً، إذا أردت."
+" "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst-1
 msgid ""
 "View of Timesheets setting enabling the feature record time off in Odoo "
 "Timesheets"
 msgstr ""
+"عرض إعداد الجداول الزمنية لتفعيل خاصية تسجيل الإجازة في تطبيق الجداول "
+"الزمنية لدى أودو "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst:16
 msgid ""
@@ -5499,12 +5576,16 @@ msgid ""
 " or create the needed type, and decide if you would like the requests to be "
 "validated or not."
 msgstr ""
+"اذهب إلى :menuselection:`الإجازات --> التهيئة --> أنواع الإجازات`. قم بتحديد"
+" أو إنشاء النوع المطلوب، وقرر ما إذا كنت ترغب في تصديق الطلبات أم لا. "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst-1
 msgid ""
 "View of a time off types form emphasizing the time off requests and timesheets section in\n"
 "Odoo Time Off"
 msgstr ""
+"عرض لاستمارة أنواع الإجازات مع التركيز على قسم طلبات الإجازات والجداول الزمنية في \n"
+"تطبيق الإجازات لدى أودو "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst:26
 msgid ""
@@ -5513,16 +5594,21 @@ msgid ""
 "automatically allocated on *Timesheets*, under the respective project and "
 "task."
 msgstr ""
+"الآن، بمجرد قيام الموظف بطلب إجازة ويتم تصديق الطلب (أو قد لا يتم تصديقه، "
+"بناءً على الإعداد المحدد)، يتم تخصيص الوقت تلقائياً في *الجداول الزمنية*، "
+"تحت المشروع والمهمة المعينين. "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst:27
 msgid ""
 "On the example below, the user requested *Paid Time off* from July 13th to "
 "15th."
 msgstr ""
+"في المثال أدناه، قام المستخدم بطلب *إجازة مدفوعة الأجر* من تاريخ 13 إلى 15 "
+"يوليو. "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst-1
 msgid "View of the time off request form in Odoo Time Off"
-msgstr ""
+msgstr "عرض استمارة طلب الإجازة في تطبيق الإجازات لدى أودو "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst:33
 msgid ""
@@ -5531,12 +5617,17 @@ msgid ""
 "time is automatically allocated after the responsible person for validating "
 "does it so."
 msgstr ""
+"مع الأخذ بعين الاعتبار أن عملية التصديق غير مطلوبة، يتم عرض الإجازة التي تم "
+"طلبها تلقائياً في *الجداول الزمنية*. إذا كان لابد من تصديق طلب الإجازة، "
+"فسيتم تخصيص الوقت تلقائياً بعد قيام الشخص المسؤول عن التصديق بذلك. "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst-1
 msgid ""
 "Video of timesheets emphasizing the requested time off from the employee in "
 "Odoo Timesheets"
 msgstr ""
+"مقطع فيديو للجداول الزمنية يركز على الإجازة التي تم طلبها بواسطة الموظف في "
+"تطبيق الجداول الزمنية لدى أودو "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst:41
 msgid ""
@@ -5544,7 +5635,10 @@ msgid ""
 "all the aggregated data on that cell (day), and see details regarding the "
 "project/task."
 msgstr ""
+"اضغط على العدسة المكبرة، مع تحريك الفأرة فوق الخلية المعنية، للوصول إلى كافة"
+" البيانات المجمعة في تلك الخلية (اليوم)، والاطلاع على التفاصيل المتعلقة "
+"بالمشروع/المهمة. "
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst-1
 msgid "View of the details of a project/task in Odoo Timeheets"
-msgstr ""
+msgstr "عرض تفاصيل المشروع/المهمة في تطبيق الجداول الزمنية لدى أودو "

locale/ar/LC_MESSAGES/settings.po

@@ -5,6 +5,7 @@
 # 
 # Translators:
 # Wil Odoo, 2023
+# Malaz Abuidris <msea@odoo.com>, 2024
 # 
 #, fuzzy
 msgid ""
@@ -13,7 +14,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-05-18 07:12+0200\n"
 "PO-Revision-Date: 2023-11-08 08:57+0000\n"
-"Last-Translator: Wil Odoo, 2023\n"
+"Last-Translator: Malaz Abuidris <msea@odoo.com>, 2024\n"
 "Language-Team: Arabic (https://app.transifex.com/odoo/teams/41243/ar/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -27,7 +28,7 @@ msgstr "الإعدادات"
 
 #: ../../content/applications/settings/users_and_features.rst:6
 msgid "Users and Features"
-msgstr ""
+msgstr "المستخدمين والخصائص "
 
 #: ../../content/applications/settings/users_and_features.rst:8
 msgid ""
@@ -35,6 +36,8 @@ msgid ""
 "This includes the Apps you install as well as the number of users currently "
 "in use."
 msgstr ""
+"بصفتك مدير قاعدة البيانات، أنت مسؤول عن استخدامها. يشمل ذلك التطبيقات التي "
+"تقوم بثبيتها بالإضافة إلى عدد المستخدمين النشطين في الوقت الحالي. "
 
 #: ../../content/applications/settings/users_and_features.rst:12
 msgid ""
@@ -44,6 +47,12 @@ msgid ""
 "subscription amount significantly (or switch you from a free account to a "
 "paying one on our online platform)."
 msgstr ""
+"أودو هو العديد من الأشياء (برنامج لتخطيط موارد المؤسسات، نظام إدارة محتوى، "
+"تطبيق لإدارة علاقات العملاء، واجهة خلفية للتجارة الإلكترونية، إلخ..)، ولكنه "
+"*ليس* هاتفاً ذكياً. عليك توخي الحذر عند إضافة/إزالة الخصائص (خصوصاً "
+"التطبيقات) في قاعدة بياناتك، حيث قد يؤثر ذلك على تكلفة اشتراكك بشكل كبير (أو"
+" قد يؤدي إلى انتقالك من الحساب المجاني إلى الحساب المدفوع على منصتنا عبر "
+"الإنترنت). "
 
 #: ../../content/applications/settings/users_and_features.rst:18
 msgid ""
@@ -52,6 +61,9 @@ msgid ""
 "to test them on a duplicate of your database first. That way, if something "
 "goes wrong, your day-to-day business is not impacted."
 msgstr ""
+"تحتوي هذه الصفحة على معلومات حول كيفية إدارة مثيلات أودو الخاصة بك. قبل "
+"القيام بتلك العمليات، نوصي **بشدة** اختبارها أولاً على نسخة من قاعدة "
+"البيانات. بهذه الطريقة، إذا حدث خطأ ما، لن يتأثر عملك الجاري بذلك الخطأ. "
 
 #: ../../content/applications/settings/users_and_features.rst:23
 msgid ""
@@ -59,6 +71,9 @@ msgid ""
 " <duplicate_online>` and :ref:`on premise <duplicate_premise>` "
 "installations."
 msgstr ""
+"ستجد الدلائل التي توضح كيفية إنشاء نسخة مطابقة لقاعدة البيانات لكل من إصداري"
+" أودو :ref:`أونلاين <duplicate_online>` و :ref:`الاستضافة الذاتية "
+"<duplicate_premise>`. "
 
 #: ../../content/applications/settings/users_and_features.rst:27
 msgid ""
@@ -66,35 +81,42 @@ msgid ""
 "issue while carrying out these procedures, please contact us through our "
 "`support form <https://www.odoo.com/help>`__."
 msgstr ""
+"إذا كانت لديك أسئلة حول محتوى هذه الصفحة أو إذا واجهتك مشكلة أثناء تنفيذ هذه"
+" الإجراءات، فلا تتردد في التواصل معنا عن طريق `استمارة الدعم "
+"<https://www.odoo.com/help>`__. "
 
 #: ../../content/applications/settings/users_and_features.rst:33
 msgid "Deactivating Users"
-msgstr ""
+msgstr "تعطيل المستخدمين "
 
 #: ../../content/applications/settings/users_and_features.rst:35
 msgid ""
 "Make sure you have sufficient **administrative rights** if you want to "
 "change the status of any of your users."
 msgstr ""
+"تأكد من أنك تملك **صلاحيات الوصول الإدارية** الكافية إذا كنت ترغب في تغيير "
+"حالة أي من المستخدمين لديك. "
 
 #: ../../content/applications/settings/users_and_features.rst:38
 msgid ""
 "In your Odoo instance, click on **Settings**. You will have a section "
 "showing you the active users on your database. Click on **Manage Users.**"
 msgstr ""
+"في مثيل أودو الخاص بك،قم بالضغط على **الإعدادات**. سيكون لديك قسم يُظهِر "
+"المستخدمين النشطين في قاعدة بياناتك. اضغط على **إدارة المستخدمين.** "
 
 #: ../../content/applications/settings/users_and_features.rst:42
 #: ../../content/applications/settings/users_and_features.rst:79
 msgid "|settings|"
-msgstr ""
+msgstr "|settings|"
 
 #: ../../content/applications/settings/users_and_features.rst:42
 msgid "|browse_users|"
-msgstr ""
+msgstr "|browse_users|"
 
 #: ../../content/applications/settings/users_and_features.rst:45
 msgid "You'll then see the list of your users."
-msgstr ""
+msgstr "سترى عندها قائمة بمستخدميك. "
 
 #: ../../content/applications/settings/users_and_features.rst:50
 msgid ""
@@ -102,6 +124,9 @@ msgid ""
 "from the *Portal Users* which are free). If you remove this filter, you'll "
 "get all your users (the ones you pay for and the portal ones)"
 msgstr ""
+"يُظهر فلتر *المستخدمين الداخليين* المحدد مسبقًا المستخدمين المدفوعين "
+"(يختلفون عن *مستخدمي البوابة* المجانيين). إذا قمت بإزالة هذا الفلتر، فستحصل "
+"على كافة المستخدمين (المستخدمين المدفوعين ومستخدمي البوابة) "
 
 #: ../../content/applications/settings/users_and_features.rst:55
 msgid ""
@@ -109,18 +134,21 @@ msgid ""
 "you are on the userform, click on the Action drop down menu, and then click "
 "on Archive."
 msgstr ""
+"في قائمة المستخدمين الخاصة بك،قم بالضغط على المستخدم الذي ترغب في تعطيله. "
+"بمجرد دخولك إلى استمارة المستخدم، قم بالضغط على  القائمة المنسدلة \"إجراء\"،"
+" ثم اضغط على \"أرشفة\". "
 
 #: ../../content/applications/settings/users_and_features.rst:63
 msgid "The user is now deactivated."
-msgstr ""
+msgstr "تم تعطيل المستخدم. "
 
 #: ../../content/applications/settings/users_and_features.rst:65
 msgid "**Never** deactivate the main user (*admin*)"
-msgstr ""
+msgstr "لا تقم **مطلقًا** بتعطيل المستخدم الرئيسي (*admin*) "
 
 #: ../../content/applications/settings/users_and_features.rst:68
 msgid "Uninstalling Apps"
-msgstr ""
+msgstr "إلغاء تثبيت التطبيقات "
 
 #: ../../content/applications/settings/users_and_features.rst:70
 msgid ""
@@ -128,6 +156,9 @@ msgid ""
 "<duplicate_online>` of your database before making any changes (*especially*"
 " installing/uninstalling apps)."
 msgstr ""
+"تأكد أولاً من اختبار ما أنت على وشك القيام به على :ref:`نسخة مطابقة لقاعدة "
+"البيانات <duplicate_online>` قبل إجراء أي تغييرات (*خاصة* تثبيت/إلغاء تثبيت "
+"التطبيقات). "
 
 #: ../../content/applications/settings/users_and_features.rst:74
 msgid ""
@@ -135,10 +166,13 @@ msgid ""
 "to see how many applications you have installed. Click on **Browse Apps** to"
 " access the list of your installed applications."
 msgstr ""
+"في مثيل أودو الخاص بك، قم بالضغط على **الإعدادات**؛ ستتمكن في هذا التطبيق من"
+" معرفة عدد التطبيقات التي قمت بتثبيتها. اضغط على **تصفح التطبيقات** للوصول "
+"إلى قائمة التطبيقات المثبتة لديك. "
 
 #: ../../content/applications/settings/users_and_features.rst:79
 msgid "|browse_apps|"
-msgstr ""
+msgstr "|browse_apps|"
 
 #: ../../content/applications/settings/users_and_features.rst:82
 msgid ""
@@ -146,6 +180,9 @@ msgid ""
 "applications. Click on the application you want to uninstall. Then, on the "
 "form of the application, click on **Uninstall**."
 msgstr ""
+"في لوحة بيانات تطبيقاتك، سترى كافة أيقونات تطبيقاتك. قم بالضغط على التطبيق "
+"الذي ترغب في إلغاء تثبيته، ثم اضفط على **إلغاء التثبيت** في استمارة التطبيق."
+" "
 
 #: ../../content/applications/settings/users_and_features.rst:89
 msgid ""
@@ -156,19 +193,25 @@ msgid ""
 "permanently disappear). If you are sure you still want to uninstall it, then"
 " click **Confirm**."
 msgstr ""
+"تحتوي بعض التطبيقات على تطبيقات معتمدة عليها، مثل الفوترة والمتجر الإلكتروني"
+" وما إلى ذلك. لذلك، سيعرض النظام رسالة تحذيرية لإعلامك بما هو على وشك أن تتم"
+" إزالته. إذا قمت بإلغاء تثبيت تطبيقك، فسيتم إلغاء تثبيت كافة التطبيقات "
+"المعتمدة عليه أيضاً (وستختفي البيانات الموجودة فيه نهائياً). إذا كنت متأكداً"
+" من أنك لا تزال ترغب في إلغاء تثبيته، فانقر فوق **تأكيد**. "
 
 #: ../../content/applications/settings/users_and_features.rst:96
 msgid ""
 "Last, after having checked the warning message (if any), click **Confirm**."
 msgstr ""
+"أخيراً، بعد التحقق من رسالة التحذير (إن وجدت)، اضغط على زر **تأكيد**. "
 
 #: ../../content/applications/settings/users_and_features.rst:101
 msgid "You have finished uninstalling your application."
-msgstr ""
+msgstr "لقد انتهيت من إلغاء تثبيت التطبيق الخاص بك."
 
 #: ../../content/applications/settings/users_and_features.rst:104
 msgid "Good to know"
-msgstr ""
+msgstr "من الجيد معرفته "
 
 #: ../../content/applications/settings/users_and_features.rst:106
 msgid ""
@@ -179,6 +222,11 @@ msgid ""
 "*do not know how you work* and therefore cannot validate these kinds of "
 "operations."
 msgstr ""
+"**إلغاء تثبيت التطبيقات وإدارة المستخدمين وما إلى ذلك أمر متروك لك**: لا "
+"يمكن لأي شخص آخر معرفة ما إذا كان سير أعمالك معطلاً أفضل منك. إذا أردنا "
+"إلغاء تثبيت التطبيقات لك، فلن نتمكن أبدًا من معرفة ما إذا كانت البيانات ذات "
+"الصلة قد تمت إزالتها أو ما إذا كان أحد تدفقات أعمالك معطلاً لأننا *لا نعرف "
+"كيف تعمل* وبالتالي لا يمكننا التحقق من صحة هذه الأنواع من العمليات. "
 
 #: ../../content/applications/settings/users_and_features.rst:112
 msgid ""
@@ -189,6 +237,11 @@ msgid ""
 "need or use the Website itself, it is needed for the Online Quotes feature "
 "to work properly."
 msgstr ""
+"**تحتوي تطبيقات Odoo على تبعيات**: هذا يعني أنك قد تحتاج إلى تثبيت وحدات لا "
+"تستخدمها بشكل نشط للوصول إلى بعض ميزات Odoo التي قد تحتاجها. على سبيل "
+"المثال، يلزم وجود تطبيق Website Builder لتتمكن من عرض أسعاره لعميلك في صفحة "
+"ويب. على الرغم من أنك قد لا تحتاج إلى موقع الويب نفسه أو تستخدمه، إلا أنه "
+"ضروري لكي تعمل ميزة عروض الأسعار عبر الإنترنت بشكل صحيح. "
 
 #: ../../content/applications/settings/users_and_features.rst:119
 msgid ""
@@ -196,3 +249,7 @@ msgid ""
 "database): that way you can know what other apps may be required, etc. This "
 "will avoid surprises when uninstalling or when receiving your invoices."
 msgstr ""
+"**اختبر دائمًا تثبيت/إزالة التطبيق على نسخة مكررة** (أو على قاعدة بيانات "
+"تجريبية مجانية): وبهذه الطريقة يمكنك معرفة التطبيقات الأخرى التي قد تكون "
+"مطلوبة، وما إلى ذلك. سيؤدي هذا إلى تجنب المفاجآت عند إلغاء التثبيت أو عند "
+"استلام فواتيرك. "

locale/de/LC_MESSAGES/administration.po

@@ -9813,7 +9813,7 @@ msgstr ""
 
 #: ../../content/administration/upgrade.rst:220
 msgid "Can you export your data?"
-msgstr ""
+msgstr "Können Sie Ihre Daten exportieren?"
 
 #: ../../content/administration/upgrade.rst:224
 msgid ""