[I18N] *: export saas-16.1 translations

closes odoo/documentation#6983

X-original-commit: b9a9da8808
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux 2023-12-18 20:35:46 +00:00
parent 9bd0998096
commit 2d4fb6f390
11 changed files with 17135 additions and 11482 deletions

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-16.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-09-14 05:10+0000\n"
"POT-Creation-Date: 2023-12-19 13:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -2392,7 +2392,7 @@ msgid "Alert blocks (admonitions)"
msgstr ""
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:470
msgid "Seealso"
msgid "See also"
msgstr ""
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:476

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-16.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-10-27 12:38+0000\n"
"POT-Creation-Date: 2023-12-19 13:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -2705,7 +2705,7 @@ msgid "In-App Purchase (IAP)"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:5
msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows you to send SMS Text Messages or to send Invoices by post directly from my database."
msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows you to send SMS Text Messages or to send Invoices by post directly from your database."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:11
@ -2713,11 +2713,11 @@ msgid "Buying Credits"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:13
msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult my current balance or to recharge my account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`."
msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult your current balance or to recharge your account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:21
msgid "If I am on Odoo Online and have the Enterprise version, I benefit from free credits to test our IAP features."
msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free credits to test our IAP features."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:25
@ -2737,7 +2737,7 @@ msgid "IAP Portal"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:42
msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low."
msgid "The IAP Portal is a platform regrouping your IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, you can view your current balance, recharge your credits and set a reminder when your balance falls below a threshold."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:50
@ -2745,31 +2745,7 @@ msgid "Get notified when credits are low"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:52
msgid "To be notified when its time to recharge my credits, Ill go to my IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and mark the Receive threshold warning option. Then, Ill provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:62
msgid "IAP services available"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:64
msgid "Different services are available depending on the hosting type of your Database:"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:66
msgid "*Odoo Online*: only the IAP services provided by Odoo can be used (i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:68
msgid "*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party apps can be used."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:72
msgid "Offering my own services"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:74
msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: :doc:`/developer/howtos/provide_iap_services`."
msgid "To be notified when its time to recharge your credits, you can go to your IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and check the Receive threshold warning option. Then, you can provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent by email!"
msgstr ""
#: ../../content/applications/general/reporting.rst:3
@ -2777,7 +2753,7 @@ msgid "Reporting"
msgstr ""
#: ../../content/applications/general/reporting.rst:5
msgid "You can find under the :guilabel:`Reporting` menu of most apps several reports that let you analyze and visualize your records' data."
msgid "You can find several reports under the :guilabel:`Reporting` menu of most apps that let you analyze and visualize the data of your records."
msgstr ""
#: ../../content/applications/general/reporting.rst:11
@ -2800,11 +2776,11 @@ msgstr ""
msgid "Selecting the graph view"
msgstr ""
#: ../../content/applications/general/reporting.rst:34
#: ../../content/applications/general/reporting.rst:33
msgid "Pivot view"
msgstr ""
#: ../../content/applications/general/reporting.rst:36
#: ../../content/applications/general/reporting.rst:35
msgid "The :ref:`pivot view <reporting/using-pivot>` is used to aggregate your records' data and break it down for analysis. The view is often found under the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the **pivot view button** located at the top right to access it."
msgstr ""
@ -2812,23 +2788,23 @@ msgstr ""
msgid "Selecting the pivot view"
msgstr ""
#: ../../content/applications/general/reporting.rst:47
#: ../../content/applications/general/reporting.rst:45
msgid "Choosing measures"
msgstr ""
#: ../../content/applications/general/reporting.rst:49
#: ../../content/applications/general/reporting.rst:47
msgid "After selecting a view, you should ensure only the relevant records are :doc:`filtered <search>`. Next, you should choose what is measured. By default, a measure is always selected. If you wish to edit it, click :guilabel:`Measures` and choose one or, only for pivots, multiple measures."
msgstr ""
#: ../../content/applications/general/reporting.rst:54
#: ../../content/applications/general/reporting.rst:52
msgid "When you select a measure, Odoo aggregates the values recorded on that field for the filtered records. Only numerical fields (:ref:`integer <studio/fields/simple-fields/integer>`, :ref:`decimal <studio/fields/simple-fields/decimal>`, :ref:`monetary <studio/fields/simple-fields/monetary>`) can be measured. In addition, the :guilabel:`Count` option is used to count the total number of filtered records."
msgstr ""
#: ../../content/applications/general/reporting.rst:60
#: ../../content/applications/general/reporting.rst:58
msgid "After choosing what you want to measure, you can define how the data should be :ref:`grouped <search/group>` depending on the dimension you want to analyze. By default, the data is often grouped by *Date > Month*, which is used to analyze the evolution of a measure over the months."
msgstr ""
#: ../../content/applications/general/reporting.rst:65
#: ../../content/applications/general/reporting.rst:63
msgid "When you filter a single time period, the option to compare it against another one appears."
msgstr ""
@ -2836,11 +2812,11 @@ msgstr ""
msgid "Using the comparison option"
msgstr ""
#: ../../content/applications/general/reporting.rst:75
#: ../../content/applications/general/reporting.rst:72
msgid "Select measures"
msgstr ""
#: ../../content/applications/general/reporting.rst:77
#: ../../content/applications/general/reporting.rst:74
msgid "Among other measures, you could add the :guilabel:`Margin` and :guilabel:`Count` measures to the Sales Analysis report. By default, the :guilabel:`Untaxed Amount` measure is selected."
msgstr ""
@ -2848,11 +2824,11 @@ msgstr ""
msgid "Selecting different measures on the Sales Analysis report"
msgstr ""
#: ../../content/applications/general/reporting.rst:85
#: ../../content/applications/general/reporting.rst:81
msgid "Group measures"
msgstr ""
#: ../../content/applications/general/reporting.rst:87
#: ../../content/applications/general/reporting.rst:83
msgid "You could group the measures by :guilabel:`Product Category` at the level of rows on the previous Sales Analysis report example."
msgstr ""
@ -2860,19 +2836,19 @@ msgstr ""
msgid "Adding a group on the Sales Analysis report"
msgstr ""
#: ../../content/applications/general/reporting.rst:97
#: ../../content/applications/general/reporting.rst:92
msgid "Using the pivot view"
msgstr ""
#: ../../content/applications/general/reporting.rst:99
#: ../../content/applications/general/reporting.rst:94
msgid "Grouping data is quintessential to the pivot view. It enables drilling down the data to gain deeper insights. While you can use the :guilabel:`Group By` option to quickly add a group at the level of rows, as shown in the example above, you can also click the plus button (:guilabel:``) next to the :guilabel:`Total` header at the level of rows *and* columns, and then select one of the **preconfigured groups**. To remove one, click the minus button (:guilabel:``)."
msgstr ""
#: ../../content/applications/general/reporting.rst:105
#: ../../content/applications/general/reporting.rst:100
msgid "Once you have added a group, you can add new ones on the opposite axis or the newly created subgroups."
msgstr ""
#: ../../content/applications/general/reporting.rst:109
#: ../../content/applications/general/reporting.rst:104
msgid "You could further divide the measures on the previous Sales Analysis report example by the :guilabel:`Salesperson` group at the level of columns and by the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / Office Furniture` product category."
msgstr ""
@ -2880,39 +2856,39 @@ msgstr ""
msgid "Adding multiple groups on the Sales Analysis report"
msgstr ""
#: ../../content/applications/general/reporting.rst:118
#: ../../content/applications/general/reporting.rst:112
msgid "Switch the rows and columns' groups by clicking the flip axis button (:guilabel:`⇄`)."
msgstr ""
#: ../../content/applications/general/reporting.rst:119
#: ../../content/applications/general/reporting.rst:113
msgid "Click on a measure's label to sort the values by ascending (⏶) or descending (⏷) order."
msgstr ""
#: ../../content/applications/general/reporting.rst:120
#: ../../content/applications/general/reporting.rst:114
msgid "Download a `.xlsx` version of the pivot by clicking the download button (:guilabel:`⭳`)."
msgstr ""
#: ../../content/applications/general/reporting.rst:125
#: ../../content/applications/general/reporting.rst:119
msgid "Using the graph view"
msgstr ""
#: ../../content/applications/general/reporting.rst:127
msgid "Three graphs are available, the bar, line, and pie charts."
#: ../../content/applications/general/reporting.rst:121
msgid "Three graphs are available: the bar, line, and pie charts."
msgstr ""
#: ../../content/applications/general/reporting.rst:129
#: ../../content/applications/general/reporting.rst:123
msgid "**Bar charts** are used to show the distribution or a comparison of several categories. They are especially useful as they can deal with larger data sets."
msgstr ""
#: ../../content/applications/general/reporting.rst:132
#: ../../content/applications/general/reporting.rst:126
msgid "**Line charts** are useful to show changing time series and trends over time."
msgstr ""
#: ../../content/applications/general/reporting.rst:134
#: ../../content/applications/general/reporting.rst:128
msgid "**Pie charts** are used to show the distribution or a comparison of a small number of categories when they form a meaningful whole."
msgstr ""
#: ../../content/applications/general/reporting.rst:139
#: ../../content/applications/general/reporting.rst:133
msgid "Bar chart"
msgstr ""
@ -2920,7 +2896,7 @@ msgstr ""
msgid "Viewing the Sales Analysis report as a bar chart"
msgstr ""
#: ../../content/applications/general/reporting.rst:145
#: ../../content/applications/general/reporting.rst:138
msgid "Line chart"
msgstr ""
@ -2928,7 +2904,7 @@ msgstr ""
msgid "Viewing the Sales Analysis report as a line chart"
msgstr ""
#: ../../content/applications/general/reporting.rst:151
#: ../../content/applications/general/reporting.rst:143
msgid "Pie chart"
msgstr ""
@ -2936,11 +2912,11 @@ msgstr ""
msgid "Viewing the Sales Analysis report as a pie chart"
msgstr ""
#: ../../content/applications/general/reporting.rst:158
#: ../../content/applications/general/reporting.rst:149
msgid "For **bar** and **line** charts, you can use the stacked option when you have at least two groups, which then appear on top of each other instead of next to each other."
msgstr ""
#: ../../content/applications/general/reporting.rst:163
#: ../../content/applications/general/reporting.rst:154
msgid "Stacked bar chart"
msgstr ""
@ -2948,7 +2924,7 @@ msgstr ""
msgid "Stacked bar chart example"
msgstr ""
#: ../../content/applications/general/reporting.rst:169
#: ../../content/applications/general/reporting.rst:159
msgid "Regular bar chart"
msgstr ""
@ -2956,7 +2932,7 @@ msgstr ""
msgid "Non-stacked bar chart example"
msgstr ""
#: ../../content/applications/general/reporting.rst:175
#: ../../content/applications/general/reporting.rst:164
msgid "Stacked line chart"
msgstr ""
@ -2964,8 +2940,8 @@ msgstr ""
msgid "Stacked line chart example"
msgstr ""
#: ../../content/applications/general/reporting.rst:181
#: ../../content/applications/general/reporting.rst:198
#: ../../content/applications/general/reporting.rst:169
#: ../../content/applications/general/reporting.rst:184
msgid "Regular line chart"
msgstr ""
@ -2973,11 +2949,11 @@ msgstr ""
msgid "Non-stacked line chart example"
msgstr ""
#: ../../content/applications/general/reporting.rst:187
#: ../../content/applications/general/reporting.rst:174
msgid "For **line** charts, you can use the cumulative option to sum values, which is especially useful to show the change in growth over a time period."
msgstr ""
#: ../../content/applications/general/reporting.rst:192
#: ../../content/applications/general/reporting.rst:179
msgid "Cumulative line chart"
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-16.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-10-27 12:38+0000\n"
"POT-Creation-Date: 2023-12-19 13:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -131,6 +131,7 @@ msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:22
#: ../../content/applications/hr/payroll/contracts.rst:39
#: ../../content/applications/hr/payroll/payslips.rst:51
msgid "Required fields"
msgstr ""
@ -144,6 +145,7 @@ msgstr ""
#: ../../content/applications/hr/employees/new_employee.rst:33
#: ../../content/applications/hr/payroll/contracts.rst:66
#: ../../content/applications/hr/payroll/payslips.rst:91
msgid "Optional fields"
msgstr ""
@ -471,27 +473,27 @@ msgstr ""
msgid "All uploaded documents associated with the employee appear in the documents smart-button."
msgstr ""
#: ../../content/applications/hr/payroll.rst:3
#: ../../content/applications/hr/payroll.rst:5
msgid "Payroll"
msgstr ""
#: ../../content/applications/hr/payroll.rst:5
#: ../../content/applications/hr/payroll.rst:7
msgid "Odoo *Payroll* is used to process work entries and create payslips for employees, including both regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*, *Timesheets*, *Time Off*, and *Attendances*."
msgstr ""
#: ../../content/applications/hr/payroll.rst:9
#: ../../content/applications/hr/payroll.rst:11
msgid "The *Payroll* app helps ensure there are no issues or conflicts when validating work entries, handles country-specific localizations to ensure that payslips follow local rules and taxes, and allows for salary assignments. Payroll configuration is critical to ensure accurate and timely processing of payslips."
msgstr ""
#: ../../content/applications/hr/payroll.rst:15
#: ../../content/applications/hr/payroll.rst:17
msgid "Settings"
msgstr ""
#: ../../content/applications/hr/payroll.rst:17
#: ../../content/applications/hr/payroll.rst:19
msgid "To access the *Settings*, go to :menuselection:`Payroll --> Configuration --> Settings`. Whether or not payslips are posted in accounting, and whether SEPA payments are created, is selected here."
msgstr ""
#: ../../content/applications/hr/payroll.rst:20
#: ../../content/applications/hr/payroll.rst:22
msgid "The :guilabel:`Settings` screen is where localization settings are configured. *Localizations* are country-specific settings pre-configured in Odoo at the creation of the database, and account for all taxes, fees, and allowances for that particular country. The :guilabel:`Localization` section of the :guilabel:`Settings` includes a detailed view of all benefits provided to employees."
msgstr ""
@ -499,36 +501,36 @@ msgstr ""
msgid "Settings available for Payroll."
msgstr ""
#: ../../content/applications/hr/payroll.rst:29
#: ../../content/applications/hr/payroll.rst:31
msgid "Any country-specific localizations are set up in the :guilabel:`Localization` section of the :guilabel:`Settings` screen. All localization items are pre-populated when the country is specified during the creation of the database. It is not recommended to alter the localization settings unless specifically required."
msgstr ""
#: ../../content/applications/hr/payroll.rst:37
#: ../../content/applications/hr/payroll.rst:39
#: ../../content/applications/hr/payroll/work_entries.rst:3
msgid "Work entries"
msgstr ""
#: ../../content/applications/hr/payroll.rst:39
#: ../../content/applications/hr/payroll.rst:41
msgid "A *work entry* is an individual record on an employee's timesheet. Work entries can be configured to account for all types of work and time off, such as :guilabel:`Attendance`, :guilabel:`Sick Time Off`, :guilabel:`Training`, or :guilabel:`Public Holiday`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:44
#: ../../content/applications/hr/payroll.rst:46
msgid ":doc:`Manage work entries <payroll/work_entries>`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:47
#: ../../content/applications/hr/payroll.rst:49
msgid "Work entry types"
msgstr ""
#: ../../content/applications/hr/payroll.rst:49
#: ../../content/applications/hr/payroll.rst:51
msgid "When creating a work entry in the *Payroll* application, or when an employee enters information in the *Timesheets* application, a :guilabel:`Work Entry Type` needs to be selected. The list of :guilabel:`Work Entry Types` is automatically created based on localization settings set in the database."
msgstr ""
#: ../../content/applications/hr/payroll.rst:54
#: ../../content/applications/hr/payroll.rst:56
msgid "To view the current work entry types available, go to :menuselection:`Payroll --> Configuration --> Work Entry Types`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:57
#: ../../content/applications/hr/payroll.rst:59
msgid "Each work entry type has a code to aid in the creation of payslips, and ensure all taxes and fees are correctly entered."
msgstr ""
@ -536,27 +538,27 @@ msgstr ""
msgid "List of all work entry types currently available."
msgstr ""
#: ../../content/applications/hr/payroll.rst:65
#: ../../content/applications/hr/payroll.rst:67
msgid "New work entry type"
msgstr ""
#: ../../content/applications/hr/payroll.rst:67
#: ../../content/applications/hr/payroll.rst:69
msgid "To create a new work entry type, click the :guilabel:`Create` button. Enter the information on the form:"
msgstr ""
#: ../../content/applications/hr/payroll.rst:70
#: ../../content/applications/hr/payroll.rst:72
msgid ":guilabel:`Work Entry Type Name`: The name should be short and descriptive, such as `Sick Time` or `Public Holiday`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:72
#: ../../content/applications/hr/payroll.rst:74
msgid ":guilabel:`Code`: This code appears with the work entry type on timesheets and payslips. Since the code is used in conjunction with the *Accounting* application, it is advised to check with the accounting department for a code to use."
msgstr ""
#: ../../content/applications/hr/payroll.rst:75
#: ../../content/applications/hr/payroll.rst:77
msgid ":guilabel:`Sequence`: The sequence determines the order that the work entry is computed in the payslip list."
msgstr ""
#: ../../content/applications/hr/payroll.rst:77
#: ../../content/applications/hr/payroll.rst:79
msgid "Check boxes: If any of the items in the list applies to the work entry, check off the box by clicking it. If :guilabel:`Time Off` is checked off, a :guilabel:`Time Off Type` field appears. This field has a drop-down menu to select the specific type of time off, or a new type of time off can be entered."
msgstr ""
@ -564,35 +566,35 @@ msgstr ""
msgid "New work entry type form."
msgstr ""
#: ../../content/applications/hr/payroll.rst:86
#: ../../content/applications/hr/payroll.rst:88
msgid ":guilabel:`Rounding`: The rounding method determines how timesheet entries are displayed on the payslip."
msgstr ""
#: ../../content/applications/hr/payroll.rst:89
#: ../../content/applications/hr/payroll.rst:91
msgid ":guilabel:`No Rounding`: A timesheet entry is not modified."
msgstr ""
#: ../../content/applications/hr/payroll.rst:90
#: ../../content/applications/hr/payroll.rst:92
msgid ":guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount."
msgstr ""
#: ../../content/applications/hr/payroll.rst:91
#: ../../content/applications/hr/payroll.rst:93
msgid ":guilabel:`Day`: A timesheet entry is rounded to the closest full day amount."
msgstr ""
#: ../../content/applications/hr/payroll.rst:94
#: ../../content/applications/hr/payroll.rst:96
msgid "If the working time is set to an 8-hour work day (40-hour work week), and an employee enters a time of 5.5 hours on a timesheet, and :guilabel:`Rounding` is set to :guilabel:`No Rounding`, the entry remains 5.5 hours. If :guilabel:`Rounding` is set to :guilabel:`Half Day`, the entry is changed to 4 hours. If it is set to :guilabel:`Day`, it is changed to 8 hours."
msgstr ""
#: ../../content/applications/hr/payroll.rst:100
#: ../../content/applications/hr/payroll.rst:102
msgid "Working times"
msgstr ""
#: ../../content/applications/hr/payroll.rst:102
#: ../../content/applications/hr/payroll.rst:104
msgid "To view the currently configured working times, go to :menuselection:`Payroll --> Configuration --> Working Times`. The working times that are available for an employee's contracts and work entries are found in this list."
msgstr ""
#: ../../content/applications/hr/payroll.rst:106
#: ../../content/applications/hr/payroll.rst:108
msgid "Working times are company-specific. Each company must identify each type of working time they use. For example, an Odoo database containing multiple companies that use a standard 40-hour work week needs to have a separate working time entry for each company that uses the 40-hour standard work week."
msgstr ""
@ -600,11 +602,11 @@ msgstr ""
msgid "All working times currently set up in the database."
msgstr ""
#: ../../content/applications/hr/payroll.rst:116
#: ../../content/applications/hr/payroll.rst:118
msgid "New working time"
msgstr ""
#: ../../content/applications/hr/payroll.rst:118
#: ../../content/applications/hr/payroll.rst:120
msgid "To create a new working time, click the :guilabel:`Create` button. Enter the information on the form."
msgstr ""
@ -612,43 +614,43 @@ msgstr ""
msgid "New working type form."
msgstr ""
#: ../../content/applications/hr/payroll.rst:125
#: ../../content/applications/hr/payroll.rst:127
msgid "The fields are auto-populated for a regular 40-hour work week but can be modified. First, change the name of the working time by modifying the text in the :guilabel:`Name` field. Next, make any adjustments to the days and times that apply to the new working time."
msgstr ""
#: ../../content/applications/hr/payroll.rst:129
#: ../../content/applications/hr/payroll.rst:131
msgid "In the :guilabel:`Working Hours` tab, modify the :guilabel:`Day of Week`, :guilabel:`Day Period`, and :guilabel:`Work Entry Type` selections by clicking on the drop-down menus in each column and making the desired selection. The :guilabel:`Work From` and :guilabel:`Work To` columns are modified by typing in the time."
msgstr ""
#: ../../content/applications/hr/payroll.rst:135
#: ../../content/applications/hr/payroll.rst:137
msgid "The :guilabel:`Work From` and :guilabel:`Work To` times must be in a 24-hour format. For example, `2:00 PM` would be entered as `14:00`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:138
#: ../../content/applications/hr/payroll.rst:140
msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch To 2 Week Calendar` button. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:142
#: ../../content/applications/hr/payroll.rst:144
msgid "Salary"
msgstr ""
#: ../../content/applications/hr/payroll.rst:147
#: ../../content/applications/hr/payroll.rst:149
msgid "Structure types"
msgstr ""
#: ../../content/applications/hr/payroll.rst:149
#: ../../content/applications/hr/payroll.rst:151
msgid "In Odoo, an employee's payslip is based on *structures* and *structure types*, which both affect how an employee enters timesheets. Each structure type is an individual set of rules for processing a timesheet entry, which consists of different structures nested within it. Structure types define how often an employee gets paid, the working hours, and if wages are based on a salary (fixed) or how many hours the employee worked (varied)."
msgstr ""
#: ../../content/applications/hr/payroll.rst:155
#: ../../content/applications/hr/payroll.rst:157
msgid "For example, a structure type could be `Employee`, and that structure type could have two different structures in it: a `Regular Pay` structure which includes all the separate rules for processing regular pay, as well as a structure for an `End of Year Bonus` which includes the rules only for the end of year bonus. Both the `Regular Pay` structure and `End of Year Bonus` structure are structures within the `Employee` structure type."
msgstr ""
#: ../../content/applications/hr/payroll.rst:161
#: ../../content/applications/hr/payroll.rst:163
msgid "The different structure types can be seen by going to :menuselection:`Payroll --> Configuration --> Structure Types`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:164
#: ../../content/applications/hr/payroll.rst:166
msgid "There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically, *Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and *Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*."
msgstr ""
@ -656,7 +658,7 @@ msgstr ""
msgid "List of all structure types."
msgstr ""
#: ../../content/applications/hr/payroll.rst:172
#: ../../content/applications/hr/payroll.rst:174
msgid "Click the :guilabel:`Create` button to make a new structure type. Most fields are pre-populated, but all fields can be edited. Once the fields are edited, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry."
msgstr ""
@ -664,19 +666,19 @@ msgstr ""
msgid "New structure type box."
msgstr ""
#: ../../content/applications/hr/payroll.rst:181
#: ../../content/applications/hr/payroll.rst:183
msgid "Structures"
msgstr ""
#: ../../content/applications/hr/payroll.rst:183
#: ../../content/applications/hr/payroll.rst:185
msgid "*Salary structures* are the different ways an employee gets paid within a specific *structure*, and are specifically defined by various rules."
msgstr ""
#: ../../content/applications/hr/payroll.rst:186
#: ../../content/applications/hr/payroll.rst:188
msgid "The amount of structures a company needs for each structure type depends on how many different ways employees are paid, and how their pay is calculated. For example, a common structure that could be useful to add may be a `Bonus`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:190
#: ../../content/applications/hr/payroll.rst:192
msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll --> Configuration --> Structures`."
msgstr ""
@ -684,11 +686,11 @@ msgstr ""
msgid "All available salary structures."
msgstr ""
#: ../../content/applications/hr/payroll.rst:197
#: ../../content/applications/hr/payroll.rst:199
msgid "Each :ref:`structure type <payroll/structure-types>` lists the various structures associated with it. Each structure contains a set of rules that define it."
msgstr ""
#: ../../content/applications/hr/payroll.rst:200
#: ../../content/applications/hr/payroll.rst:202
msgid "Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the payslip for the employee."
msgstr ""
@ -696,15 +698,15 @@ msgstr ""
msgid "Salary structure details for Regular Pay."
msgstr ""
#: ../../content/applications/hr/payroll.rst:208
#: ../../content/applications/hr/payroll.rst:210
msgid "Rules"
msgstr ""
#: ../../content/applications/hr/payroll.rst:210
#: ../../content/applications/hr/payroll.rst:212
msgid "Each structure has a set of *salary rules* to follow for accounting purposes. These rules are configured by the localization, and affect the *Accounting* application, so modifications to the default rules, or the creation of new rules, should only be done when necessary."
msgstr ""
#: ../../content/applications/hr/payroll.rst:214
#: ../../content/applications/hr/payroll.rst:216
msgid "To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Rules`. Click on a structure (such as :guilabel:`Regular Pay`) to view all the rules."
msgstr ""
@ -712,7 +714,7 @@ msgstr ""
msgid "Rules for each salary structure type."
msgstr ""
#: ../../content/applications/hr/payroll.rst:221
#: ../../content/applications/hr/payroll.rst:223
msgid "To make a new rule, click :guilabel:`Create`. A new rule form appears. Enter the information in the fields, then click :guilabel:`Save`."
msgstr ""
@ -720,47 +722,47 @@ msgstr ""
msgid "Enter the information for the new rule."
msgstr ""
#: ../../content/applications/hr/payroll.rst:228
#: ../../content/applications/hr/payroll.rst:230
msgid "The required fields for a rule are:"
msgstr ""
#: ../../content/applications/hr/payroll.rst:230
#: ../../content/applications/hr/payroll.rst:232
msgid ":guilabel:`Name`: Enter a name for the rule."
msgstr ""
#: ../../content/applications/hr/payroll.rst:231
#: ../../content/applications/hr/payroll.rst:233
msgid ":guilabel:`Category`: Select a category the rule applies to from the drop-down menu, or enter a new one."
msgstr ""
#: ../../content/applications/hr/payroll.rst:233
#: ../../content/applications/hr/payroll.rst:235
msgid ":guilabel:`Code`: Enter a code to be used for this new rule. It is recommended to coordinate with the accounting department for a code as this will affect them."
msgstr ""
#: ../../content/applications/hr/payroll.rst:235
#: ../../content/applications/hr/payroll.rst:237
msgid ":guilabel:`Salary Structure`: Select a salary structure the rule applies to from the drop-down menu, or enter a new one."
msgstr ""
#: ../../content/applications/hr/payroll.rst:237
#: ../../content/applications/hr/payroll.rst:239
msgid ":guilabel:`Condition Based on`: In the :guilabel:`General` tab, select from the drop-down menu whether the rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` (applies to a specific range, which is entered beneath the selection), or a :guilabel:`Python Expression` (the code is entered beneath the selection)."
msgstr ""
#: ../../content/applications/hr/payroll.rst:241
#: ../../content/applications/hr/payroll.rst:243
msgid ":guilabel:`Amount Type`: In the :guilabel:`General` tab, select from the drop-down menu whether the amount is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a :guilabel:`Python Code`. Depending on what is selected, the fixed amount, percentage, or Python code needs to be entered next."
msgstr ""
#: ../../content/applications/hr/payroll.rst:247
#: ../../content/applications/hr/payroll.rst:249
msgid "Rule parameters"
msgstr ""
#: ../../content/applications/hr/payroll.rst:250
#: ../../content/applications/hr/payroll.rst:252
msgid "Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets."
msgstr ""
#: ../../content/applications/hr/payroll.rst:255
#: ../../content/applications/hr/payroll.rst:257
msgid "Other input types"
msgstr ""
#: ../../content/applications/hr/payroll.rst:257
#: ../../content/applications/hr/payroll.rst:259
msgid "When creating payslips, it is sometimes necessary to add other entries for specific circumstances, like expenses, reimbursements, or deductions. These other inputs can be configured by going to :menuselection:`Payroll --> Configuration --> Other Input Types`."
msgstr ""
@ -768,7 +770,7 @@ msgstr ""
msgid "Other input types for payroll."
msgstr ""
#: ../../content/applications/hr/payroll.rst:265
#: ../../content/applications/hr/payroll.rst:267
msgid "To create a new input type, click the :guilabel:`Create` button. Enter the :guilabel:`Description`, the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure` field. Click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry."
msgstr ""
@ -776,27 +778,27 @@ msgstr ""
msgid "Create a new Input Type."
msgstr ""
#: ../../content/applications/hr/payroll.rst:275
#: ../../content/applications/hr/payroll.rst:277
msgid "Salary package configurator"
msgstr ""
#: ../../content/applications/hr/payroll.rst:277
#: ../../content/applications/hr/payroll.rst:279
msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll --> Configuration` menu all affect an employee's potential salary. These sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, and :guilabel:`Resume`) specify what benefits can be offered to an employee in their salary package."
msgstr ""
#: ../../content/applications/hr/payroll.rst:282
#: ../../content/applications/hr/payroll.rst:284
msgid "Depending on what information an employee enters (such as deductions, dependents, etc.), their salary is adjusted accordingly. When an applicant applies for a job on the company website, the sections under :guilabel:`Salary Package Configurator` directly affect what the applicant sees, and what is populated as the applicant enters information."
msgstr ""
#: ../../content/applications/hr/payroll.rst:288
#: ../../content/applications/hr/payroll.rst:290
msgid "Advantages"
msgstr ""
#: ../../content/applications/hr/payroll.rst:290
#: ../../content/applications/hr/payroll.rst:292
msgid "When offering potential employees a position, there can be certain *advantages* set in Odoo in addition to the salary to make the offer more appealing (such as extra time off, access to a company car, reimbursement for a phone or internet, etc.)."
msgstr ""
#: ../../content/applications/hr/payroll.rst:294
#: ../../content/applications/hr/payroll.rst:296
msgid "To see the advantages, go to :menuselection:`Payroll --> Configuration --> Advantages`. Advantages are grouped by :guilabel:`Structure type`."
msgstr ""
@ -804,7 +806,7 @@ msgstr ""
msgid "Settings available for payroll."
msgstr ""
#: ../../content/applications/hr/payroll.rst:301
#: ../../content/applications/hr/payroll.rst:303
msgid "To make a new advantage, click the :guilabel:`Create` button. Enter the information in the fields, then click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry."
msgstr ""
@ -812,39 +814,39 @@ msgstr ""
msgid "List of advantages employee's can have."
msgstr ""
#: ../../content/applications/hr/payroll.rst:309
#: ../../content/applications/hr/payroll.rst:311
msgid "The required fields for an advantage are:"
msgstr ""
#: ../../content/applications/hr/payroll.rst:311
#: ../../content/applications/hr/payroll.rst:313
msgid ":guilabel:`Name`: Enter the name for the advantage."
msgstr ""
#: ../../content/applications/hr/payroll.rst:312
#: ../../content/applications/hr/payroll.rst:314
msgid ":guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this advantage appears under."
msgstr ""
#: ../../content/applications/hr/payroll.rst:314
#: ../../content/applications/hr/payroll.rst:316
msgid ":guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`, :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:317
#: ../../content/applications/hr/payroll.rst:319
msgid ":guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this advantage applies to."
msgstr ""
#: ../../content/applications/hr/payroll.rst:321
#: ../../content/applications/hr/payroll.rst:323
msgid "Personal info"
msgstr ""
#: ../../content/applications/hr/payroll.rst:323
#: ../../content/applications/hr/payroll.rst:325
msgid "Every employee in Odoo has an *employee card* that includes all of their personal information, resume, work information, and documents. To view an employee's card, go to the main :menuselection:`Payroll` app dashboard, and click on the employee's card, or go to :menuselection:`Payroll --> Employees --> Employees` and click on the employee's card. Employee cards can also be viewed by going to the :menuselection:`Employees` app."
msgstr ""
#: ../../content/applications/hr/payroll.rst:330
#: ../../content/applications/hr/payroll.rst:332
msgid "An employee card can be thought of as an employee personnel file."
msgstr ""
#: ../../content/applications/hr/payroll.rst:332
#: ../../content/applications/hr/payroll.rst:334
msgid "The *Personal Information* section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll --> Configuration --> Personal Info`."
msgstr ""
@ -852,7 +854,7 @@ msgstr ""
msgid "Personal information that appear on employee cards to enter."
msgstr ""
#: ../../content/applications/hr/payroll.rst:340
#: ../../content/applications/hr/payroll.rst:342
msgid "To edit an entry, select it from the list. Then, click the :guilabel:`Edit` button, and modify the entry. When done, click :guilabel:`Save` or :guilabel:`Discard` to save the information or cancel the edits."
msgstr ""
@ -860,23 +862,23 @@ msgstr ""
msgid "New personal information entry."
msgstr ""
#: ../../content/applications/hr/payroll.rst:348
#: ../../content/applications/hr/payroll.rst:350
msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card."
msgstr ""
#: ../../content/applications/hr/payroll.rst:352
#: ../../content/applications/hr/payroll.rst:354
msgid "The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more."
msgstr ""
#: ../../content/applications/hr/payroll.rst:356
#: ../../content/applications/hr/payroll.rst:358
msgid "Once the information is entered, click the :guilabel:`Save` button to save the entry."
msgstr ""
#: ../../content/applications/hr/payroll.rst:359
#: ../../content/applications/hr/payroll.rst:361
msgid "Resume"
msgstr ""
#: ../../content/applications/hr/payroll.rst:362
#: ../../content/applications/hr/payroll.rst:364
msgid "Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets."
msgstr ""
@ -1168,6 +1170,422 @@ msgstr ""
msgid ":guilabel:`Credit Time`: This option is for Belgian companies only. When clicked, a pop-up window appears that allows for the changing of working times, and can compute time off."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:3
msgid "Payslips"
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:5
msgid "Payslips are created either by the employees themselves or their managers, and are approved by authorized employees (typically managers). Then, once payslips are approved, employees are issued payslips and are paid either by check or direct deposit, depending on how their employee profile is configured."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:10
msgid "The :guilabel:`Payslips` drop-down header of the :menuselection:`Payroll` application consists of three sections: :guilabel:`To Pay`, :guilabel:`All Payslips`, and :guilabel:`Batches`."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:13
msgid "These three sections provide all the tools needed to create payslips for employees, including individual payslips, a batch of payslips, or commission payslips."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "Payslips menu selection in Payroll."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:21
msgid "To pay"
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:23
msgid "Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the payslips that need to be paid. On this page, Odoo displays the payslips that have not been generated yet, and can be created from this dashboard."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "View all payslips that need to be paid on the Payslips To Pay page."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:31
msgid "Each payslip will list the :guilabel:`Reference` number for the individual payslip, the :guilabel:`Employee` name, :guilabel:`Batch Name`, the :guilabel:`From` and :guilabel:`To` date range, the :guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:36
msgid "Clicking on an individual payslip entry will show the details for the individual payslip."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:41
msgid "Create new payslip"
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:43
msgid "A new payslip can be created from the :guilabel:`Payslips To Pay` page (:menuselection:`Payroll app --> Payslips --> To Pay`) or the :guilabel:`Employee Payslips` page (:menuselection:`Payroll app --> Payslips --> All Payslips`), by clicking the :guilabel:`Create` button in the top-left corner."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:47
msgid "Clicking :guilabel:`Create` reveals a blank payslip form, wherein the necessary payslip information can be entered."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:53
msgid "On the blank payslip form, a number of fields are required to be filled in with the necessary information. These required fields are represented by **bold** lines."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "The necessary fields for a new payslip."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:60
msgid ":guilabel:`Employee`: Type in the name of an employee, or select the desired employee from the drop-down list. Upon selecting an employee, several other fields on the payslip form may auto-populate. Typically, after making a selection in the :guilabel:`Employee` field, Odoo auto-populates the :guilabel:`Contract`, :guilabel:`Structure`, and :guilabel:`Payslip Name` fields, but **only** if that information is already on that employee's form in the *Employees* app."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:66
msgid ":guilabel:`Period`: Click the default date to reveal a pop-up calendar. On this calendar, use the :guilabel:`< (less-than)` and :guilabel:`> (greater than)` icons to select the desired month, and click on the desired day to select that specific date as the start date for the payslip. Repeat this process to add an end date for the payslip in the field below."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:70
msgid ":guilabel:`Contract`: Using the drop-down menu, select the desired contract for the employee. Only the available corresponding contracts for the selected employee appear as options."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:72
msgid ":guilabel:`Structure`: Using the drop-down menu, select the salary structure type. Only the available corresponding structures for the selected contract for that specific employee appear as options."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:75
msgid ":guilabel:`Payslip Name`: In the blank field, type in the name for the payslip. The name should be short and descriptive, such as `April 2023`."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:77
msgid ":guilabel:`Company`: In the :guilabel:`Accounting Information` tab, select the company the payslip applies to from the :guilabel:`Company` drop-down menu."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:79
msgid ":guilabel:`Salary Journal`: In the :guilabel:`Accounting Information` tab, enter the salary journal in which the payment will be reflected, and found in the *Accounting* application."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "The necessary fields for a new payslip in the Accounting Information tab."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:87
msgid "It is recommended to check with the accounting department to ensure every entry that affects the *Accounting* application is correct."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:93
msgid ":guilabel:`Reference`: Any note or reference message for the new entry can be entered here."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:94
msgid ":guilabel:`Company Car`: If applicable, select the company car from the drop-down."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:95
msgid ":guilabel:`Worked Days`: In the :guilabel:`Worked Days \\& Inputs` tab, the entries under :guilabel:`Worked Days` (including the :guilabel:`Type`, :guilabel:`Description`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, and :guilabel:`Amount`) are automatically filled in, based on what was entered for the :guilabel:`Period`, :guilabel:`Contract`, and :guilabel:`Structure` fields of the payslip form."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:100
msgid ":guilabel:`Salary Computation`: The :guilabel:`Salary Computation` tab is automatically filled in after the :guilabel:`Compute Sheet` button is clicked. Doing so displays all the wages, deductions, taxes, etc. for the entry."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:103
msgid ":guilabel:`Batch Name`: Located in the :guilabel:`Accounting Information` tab, select the payslip batch this new payslip should be added to from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:105
msgid ":guilabel:`Date Account`: Located in the :guilabel:`Accounting Information` tab, enter the date on which the payslip should be posted, by clicking on the drop-down menu, and navigating to the correct month and year using the :guilabel:`< > (less-than/greater-than)` icons in the calendar pop-up window. Then, click on the desired date."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:109
msgid ":guilabel:`Salary Journal`: This field, located in the :guilabel:`Accounting Information` tab, represents the journal that the payslip will be logged in, and is automatically selected when the :guilabel:`Contract` and :guilabel:`Structure` are entered in the payslip form."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:112
msgid ":guilabel:`Accounting Entry`: This field, located in the :guilabel:`Accounting Information` tab, is automatically filled in once the payslip is confirmed."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:116
msgid "Save and process new payslip"
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:118
msgid "When all the necessary information on the payslip is entered, click :guilabel:`Save` to save the data, or click :guilabel:`Discard` to delete the entry."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:122
msgid "Saving the entry is not required in order to compute the sheet, although it is considered best practice to do so. The :guilabel:`Compute Sheet` button can be clicked without first saving the payslip. Doing so will save the entry *and* compute the sheet."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:126
msgid "Click the :guilabel:`Compute Sheet` button to register all the information, and have the :guilabel:`Salary Computation` tab populated. If any modifications need to be made, click the :guilabel:`Edit` button, make the desired changes, then click the :guilabel:`Recompute Worked Days` button to have the changes reflected in the :guilabel:`Worked Days` and :guilabel:`Salary Computation` tabs."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:132
msgid "To print the payslip, click the :guilabel:`Print` button. To cancel the payslip, click the :guilabel:`Cancel Payslip` button."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:135
msgid "Once everything on the payslip form is correct, click the :guilabel:`Create Draft Entry` button to create the payslip. The chatter is automatically updated to show the email sent to the employee, along with a PDF copy of the payslip."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "The new payslip is emailed to the employee and the email appears in the chatter."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:143
msgid "Next, the payment must be sent to the employee. To do this, click the :guilabel:`Make Payment` button. Doing so reveals a pop-up form, in which the desired :guilabel:`Bank Journal` that the payment should be made against must be selected from a drop-down menu. Then, click the :guilabel:`Confirm` button to confirm the journal, and return to the payslip."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "Click Make Payment to send the payment to the employee."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:152
msgid "If a payment needs to be cancelled or refunded, click the corresponding :guilabel:`Refund` or :guilabel:`Cancel Payslip` button, located at the top of the payslip form."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:156
msgid "In order for a payslip to be paid, the employee *must* have a bank account entered in their contact information. If there is no bank information, a payslip cannot be paid, and an error will appear when the :guilabel:`Make Payment` button is clicked. Banking information can be found in the :guilabel:`Private Information` tab on the employee's card. Edit the employee card, and add banking information, if it is missing."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:0
msgid "Banking information can be entered in an employee's card."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:167
msgid "All payslips"
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:169
msgid "To view all payslips regardless of status, go to :menuselection:`Payroll app --> Payslips --> All Payslips`. Here, all payslips are organized by batch (in a default list view)."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:172
msgid "Click on the :guilabel:`▶ (arrow)` next to the individual batch name to view all the payslips in that particular batch, along with all the payslip details. The number of payslips in the batch is written in parenthesis after the batch name. The :guilabel:`Status` for each individual payslip appears on the far-right side, indicating if it is in :guilabel:`Draft Mode`, :guilabel:`Waiting`, or if it is :guilabel:`Done`."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:179
msgid ":guilabel:`Draft` indicates the payslip is created, and there is still time to make edits, since the amounts are not calculated."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:181
msgid "`Waiting` indicates the payslip has been calculated and the salary details can be found in the *Salary Computation* tab."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:183
msgid "`Done` indicates the payslip is calculated and ready to be paid."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "View all payslips organized by batches. Click on the arrow to expand each batch."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:189
msgid "Click on an individual payslip to view the details for that payslip on a separate page. Using the breadcrumb menu, click :guilabel:`Employee Payslips` to go back to the list view of all payslips."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:192
msgid "A new payslip can be created from the :guilabel:`Employee Payslips` page, by clicking the :guilabel:`Create` button in the upper-left corner. Doing so reveals a separate blank payslip form page. On that blank payslip form page, enter all the necessary information, as described in the :ref:`Create a new payslip <payroll/new-payslip>` section."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:197
msgid "To print PDF versions of payslips from the :guilabel:`Payslips to Pay` or :guilabel:`Employee Payslips` pages, first select the desired payslips by clicking on the individual checkbox next to each payslip to be printed. Or, click the box next to :guilabel:`Reference`, which selects all visible payslips on the page. Then, click the :guilabel:`Print` button to print the payslips."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "Click on the Print smart button to print payslips to a PDF."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:206
msgid "Payslips can also be exported to an Excel spreadsheet. When exporting, all payslips are exported regardless of whether some are selected or not. Click on the :guilabel:`Export All` button (download icon) to export all payslips to an Excel spreadsheet."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "Click on the Export All smart button to export all payslips to an Excel payslip."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:215
msgid "Both *To Pay* and *All Payslips* display all the detailed information for each payslip."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:218
msgid "Batches"
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:220
msgid "To view payslips in batches, navigate to :menuselection:`Payroll app --> Payslips --> Batches` to display all the payslip batches that have been created. These payslip batches are displayed in a list view, by default."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:224
msgid "Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and :guilabel:`Date To` dates, whether it was a :guilabel:`Credit note`, its :guilabel:`Status`, and the :guilabel:`Company`."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "View displaying all batches created."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:231
msgid "Click on an individual batch to view the details for that batch on a separate page. On this batch detail page, modifications can be made. To make any modifications to a batch, click the :guilabel:`Edit` button. Then, proceed to make any necessary changes."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:235
msgid "When all desired changes have been made, click either :guilabel:`Save` to save the changes, or :guilabel:`Discard` to revert back to the original data."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:238
msgid "After modifications have been saved, click the :guilabel:`Generate Payslips` button to reveal a :guilabel:`Generate Payslips` pop-up form, in which payslips affected by the changes can be created or modified."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:242
msgid "All payslips associated with the batch are displayed in the employees section of the :guilabel:`Generate Payslips` pop-up. To filter the results by either the :guilabel:`Salary Structure` and/or the :guilabel:`Department`, select a salary structure and/or department from the respective drop-down menus."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:247
msgid "Only employees that match the selected :guilabel:`Salary Structure` and/or :guilabel:`Department` appear in the employees list. Click the :guilabel:`Generate` button at the bottom of the :guilabel:`Generate Payslips` pop-up window to generate the modified payslips, and close the pop-up window."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "Generate payslips from the edited batch."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:256
msgid "Back on the batch details page, click the :guilabel:`Create Draft Entry` smart button to create a draft of the payslips."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:263
msgid "Once the draft payslips are created, the button changes to say :guilabel:`Make Payment`. Click the :guilabel:`Make Payment` button. A pop-up window appears, in which the bank journal information must be entered. Select the :guilabel:`Bank Journal` from the drop-down list, and click :guilabel:`Confirm` to process the payslips, and pay the employees."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:268
msgid "On the batch detail page, the number of payslips in the batch is accessible via the :guilabel:`Payslips` smart button, located in the top-right corner. Individual payslips for the batch can be viewed by clicking the :guilabel:`Payslips` smart button in the top-right corner."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:272
msgid "Use the breadcrumb menu to navigate back to the individual batch detail page, or back to the list of all batches."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "Click the Payslips smart button to view the individual payslips in the batch."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:280
msgid "Create a new batch"
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:282
msgid "To create a new batch of payslips from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`), click the :guilabel:`Create` button in the upper-left corner. Doing so reveals a blank payslip batch form on a separate page."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:286
msgid "On the new payslip batch form, enter the :guilabel:`Name` for the batch, and select the date range to which the batch applies, by clicking the :guilabel:`▼ (drop-down arrow)` icon in the :guilabel:`Period` fields, which reveals a calendar pop-up window. From this calendar pop-up window, navigate to the correct month, and click on the corresponding day for both the start and end dates."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "Enter the details for the new batch."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:295
msgid "If the batch is a credit note, check the box next to :guilabel:`Credit Note`. Then, in the :guilabel:`Generation Date` field, select the date the payslips should be generated from a calendar pop-up window. This generated date is reflected in the accounting journal entries."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:299
msgid "Lastly, in the :guilabel:`Company` field, select the company these payslips are written against."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:301
msgid "When all the information on the payslip batch form is correct, click the :guilabel:`Save` button to save the information. To delete the entry, click the :guilabel:`Discard` button."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:304
msgid "To create the payslips for the newly-created batch, click the :guilabel:`Generate Payslips` button at the top of the form."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:307
msgid "When clicked, a pop-up window appears showing all the payslips that will be created. To remove any individual payslips, click the black :guilabel:`✖ (x mark)` icon at the far right of the payslip line."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:311
msgid "If a specific :guilabel:`Salary Structure` or :guilabel:`Department` needs to be specified for the batch, select them from the corresponding drop-down menus."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:314
msgid "Click the :guilabel:`Generate` button at the bottom of the pop-up window to create the payslips for the batch."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "Generate payslips for the new batch."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:322
msgid "On the :guilabel:`Generate Payslips` pop-up window, selecting a :guilabel:`Department` and/or :guilabel:`Salary Structure` only displays payslips that apply to those specifically-selected parameters."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:326
msgid "If there are any errors or issues preventing the payslips from being generated, an error message appears in the top-right section. This error box disappears on its own after several seconds, or the :guilabel:`✖ (x mark)` icon can be clicked to close the alert."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:330
msgid "To remedy the issue, make any necessary modifications (e.g. removing any payslip lines that cannot be processed), then click the :guilabel:`Generate` button again."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:333
msgid "Once the payslips have been successfully generated, the screen returns to the payslip batch form."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:335
msgid "From here, click the :guilabel:`Generate Draft Entry` button to change the payslips' status from :guilabel:`Draft` to :guilabel:`Done`."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:338
msgid "Once payslips have been generated, click the :guilabel:`Make Payment` button to process the payments. Doing so reveals a pop-up window, in which the proper banking information must be entered. In this pop-up window, select the appropriate :guilabel:`Bank Journal` from the drop-down menu, and enter the appropriate file name."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:343
msgid "When done, click the :guilabel:`Confirm` button to confirm the information, or click :guilabel:`Cancel` to discard."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:347
msgid "Generate commission payslips"
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:349
msgid "Commission payslips can be generated directly from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`). To generate commission payslips from this page, click on the desired batch (or batches) to create commissions payslips for, then click the :guilabel:`Generate Commission Payslips` button."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:354
msgid "Doing so reveals a :guilabel:`Generate Commission Payslip` pop-up window, in which the necessary information **must** be filled out."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:-1
msgid "Enter the commission details."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:361
msgid "On this pop-up window, click on the drop-down menus, located beside the :guilabel:`Period` field, to reveal calendar pop-up windows. On these calendar pop-up windows, select the desired period for which the payslips are being generated. Using the :guilabel:`< (left)` and :guilabel:`> (right)` arrows, navigate to the correct month, and click on the date to select it."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:366
msgid "In the :guilabel:`Department` field, select the desired department from the drop-down menu."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:368
msgid "When a department is selected, the employees listed for that department appear in the :guilabel:`Employee` section."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:371
msgid "Under the :guilabel:`Employee` section, enter the :guilabel:`Commission Amount` for each employee in the appropriate column. To remove an employee, click the :guilabel:`🗑️ (trash)` icon to remove the line."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:375
msgid "Add a new entry by clicking :guilabel:`Add a Line`, and entering the :guilabel:`Employee` and the appropriate :guilabel:`Commission Amount`."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:378
msgid "Click the :guilabel:`Upload Your File` button to add a file, if necessary. Any file type is accepted."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:381
msgid "Using the drop-down menu beside the :guilabel:`Commission Type` field, select either :guilabel:`Classic Commission` or :guilabel:`Warrant`. :guilabel:`Classic` is the most typical of commission, while :guilabel:`Warrant` is primarily used for Belgium companies."
msgstr ""
#: ../../content/applications/hr/payroll/payslips.rst:385
msgid "Once all the commissions are properly entered, click the :guilabel:`Generate Payslips` button to create the commission payslips."
msgstr ""
#: ../../content/applications/hr/payroll/work_entries.rst:5
msgid "The *Work Entries* dashboard, which can be found by going to :menuselection:`Payroll --> Work Entries --> Work Entries`, provides a visual overview of the individual time sheets of every employee, with each day split into a morning shift and an afternoon shift."
msgstr ""

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-16.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-10-27 12:38+0000\n"
"POT-Creation-Date: 2023-12-19 13:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -334,42 +334,38 @@ msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Out
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:106
msgid "After one user syncs their Outlook calendar to the Odoo database, unwanted email notifications are unavoidable because the first synchronized user's events will be in the Odoo Calendar. If the Odoo database is shared amongst multiple users, and another user wants to sync their Outlook calendar with Odoo Calendar, Outlook will again pull the existing Odoo Calendar events during the sync and treat them as new events, causing Outlook to send email invitations to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:113
msgid "In summary, once a user synchronizes their Outlook calendar with the Odoo calendar:"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:115
#: ../../content/applications/productivity/calendar/outlook.rst:108
msgid "Creating an event in Odoo causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:116
#: ../../content/applications/productivity/calendar/outlook.rst:109
msgid "Deleting an event in Odoo causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:117
#: ../../content/applications/productivity/calendar/outlook.rst:110
msgid "Unarchiving an event in Odoo causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:118
#: ../../content/applications/productivity/calendar/outlook.rst:111
msgid "Archiving an event in Odoo causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:119
#: ../../content/applications/productivity/calendar/outlook.rst:112
msgid "Adding a contact to an event causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:120
#: ../../content/applications/productivity/calendar/outlook.rst:113
msgid "Removing a contact from an event causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:123
#: ../../content/applications/productivity/calendar/outlook.rst:116
msgid "Sync Odoo Calendar and Outlook"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:125
#: ../../content/applications/productivity/calendar/outlook.rst:118
msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions."
msgstr ""
@ -377,19 +373,19 @@ msgstr ""
msgid "The \"Outlook\" sync button in Odoo Calendar."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:133
#: ../../content/applications/productivity/calendar/outlook.rst:126
msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (Outlook and Odoo)."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:137
#: ../../content/applications/productivity/calendar/outlook.rst:130
msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook <outlook/sync>`. The configuration of Microsoft's Azure account is only done once, as Microsoft Entra ID tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:144
#: ../../content/applications/productivity/calendar/outlook.rst:137
msgid ":doc:`../mail_plugins/outlook`"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:145
#: ../../content/applications/productivity/calendar/outlook.rst:138
msgid ":doc:`google`"
msgstr ""
@ -623,7 +619,7 @@ msgid "View of the contacts status for Odoo Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/get_started.rst:97
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:65
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:250
msgid ":doc:`team_communication`"
msgstr ""
@ -632,76 +628,302 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3
msgid "Get Organized by Planning Activities"
msgid "Activities"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:5
msgid "When you plan activities you minimize the risk of uncertainties, as you provide clear directions for the course of your next action. In addition to that, you do not leave space for wasteful activities and reduce the chance of having overlapping actions between team members."
msgid "*Activities* are follow-up tasks tied to a record in an Odoo database. Activities can be scheduled on any page of the database that contains a chatter thread, kanban view, list view, or activities view of an application."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:10
msgid "Where do I see my schedule activities?"
msgid "Schedule activities"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:12
msgid "Access and manage your activities wherever you are in Odoo by the *Activities* menu."
msgid "One way that activities are created is by clicking the :guilabel:`Schedule Activity` button, located at the top of the *chatter* on any record. On the pop-up window that appears, select an :guilabel:`Activity Type` from the drop-down menu."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:17
msgid "Individual applications have a list of *Activity Types* dedicated to that application. For example, to view and edit the activities available for the *CRM* application, go to :menuselection:`CRM app --> Configuration --> Activity Types`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:21
msgid "Enter a title for the activity in the :guilabel:`Summary` field, located in the :guilabel:`Schedule Activity` pop-up window."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:24
msgid "To assign the activity to a different user, select a name from the :guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the activity is automatically assigned."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:27
msgid "Lastly, feel free to add any additional information in the optional :guilabel:`Log a note...` field."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:30
msgid "The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up window auto-populates based on the configuration settings for the selected :guilabel:`Activity Type`. However, this date can be changed by selecting a day on the calendar in the :guilabel:`Due Date` field."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:34
msgid "Lastly, click one of the following buttons:"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:36
msgid ":guilabel:`Schedule`: adds the activity to the chatter under :guilabel:`Planned activities`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:37
msgid ":guilabel:`Mark as Done`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, it is automatically marked as completed."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:39
msgid ":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` marked as done, and opens a new activity window."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:41
msgid ":guilabel:`Discard`: discards any changes made on the pop-up window."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1
msgid "View of crm leads page emphasizing the activities menu for Odoo Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:20
msgid "Plan activities"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:22
msgid "Activities can be planned and managed from the chatter by clicking on *Schedule activity*, or through Kanban views."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1
msgid "View of crm leads and the option to schedule an activity for Odoo Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:31
msgid "Set your activity types"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:33
msgid "A number of activities types are available by default in Odoo (call, email, meeting, etc.). However, you can set new ones going to :menuselection:`Settings --> Activity types`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1
msgid "View of the settings page emphasizing the menu activity types for Odoo Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:42
msgid "If you need to create an activity type with an available calendar, make sure to create it with an *Action to Perform* set as *Meeting*."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:46
msgid "Recommend next activities"
msgid "View of CRM leads and the option to schedule an activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:48
msgid "Odoo helps you to plan a flow of activities by allowing you to set *Recommended Next Activities*."
msgid "Depending on the activity type, the :guilabel:`Schedule` button may be replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` button."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:51
msgid "Scheduled activities are added to the chatter for the record under :guilabel:`Planned activities`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:57
msgid "Activities can also be scheduled from the kanban, list, or activities view of an application."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:61
msgid "Kanban view"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:63
msgid "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 (clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill out the pop-up form."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0
msgid "Kanban view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:70
msgid "List view"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:72
msgid "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 (clock)` icon, then :guilabel:`Schedule An Activity`. If the record already has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 (phone)` or an :guilabel:`✉️ (envelope)` icon."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0
msgid "List view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:80
msgid "Activity view"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:82
msgid "To open the activity view for an application, select the :guilabel:`🕘 (clock)` icon from the menu bar anywhere in the database. Select any application from the drop-down menu, and click the :guilabel:`🕘 (clock)` icon for the desired app."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0
msgid "Activity menu drop down with focus on where to open activity view for CRM."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:90
msgid "Select a record on which to schedule an activity. Move across the row to find the desired activity type, then click the :guilabel:` (plus sign)`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0
msgid "Activity view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:98
msgid "Activity colors, and their relation to an activity's due date, is consistent throughout Odoo, regardless of the activity type, or the view."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:101
msgid "Activities that appear in **green** indicate a due date sometime in the future."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:102
msgid "**Yellow** indicates that the activity's due date is today."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:103
msgid "**Red** indicates that the activity is overdue and the due date has passed."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:105
msgid "For example, if an activity is created for a phone call, and the due date passes, the activity appears with a red phone in list view, and a red clock on the kanban view."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:109
msgid "View scheduled activities"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:111
msgid "To view scheduled activities, open either the :menuselection:`Sales app` or :menuselection:`CRM app` and click the :guilabel:`🕘 (clock)` icon, located to the far-right side of the other view options."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:114
msgid "Doing so opens the activities menu, showcasing all the scheduled activities for the user, by default. To show all activities for every user, remove the :guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:118
msgid "To view a consolidated list of activities separated by the application where they were created, and by deadline, click the :guilabel:`🕘 (clock)` icon on the header menu to see the activities for that specific application in a drop-down menu."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:122
msgid "The possibility to :guilabel:`Add new note` and :guilabel:`Request a Document` appear at the bottom of this drop-down menu, when the :guilabel:`🕘 (clock)` icon on the header menu is clicked."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1
msgid "View of an activity type form emphasizing the field recommended next activities for Odoo\n"
"Discuss"
msgid "View of CRM leads page emphasizing the activities menu."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:55
msgid "Once the respective activity is completed, select *Done & Schedule Next* and next steps are suggested to you."
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:130
msgid "Configure activity types"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:132
msgid "To configure the types of activities in the database, go to :menuselection:`Settings app --> Discuss --> Activities --> Activity Types`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1
msgid "View of an activity being schedule emphasizing the recommended activities field being\n"
"shown for Odoo Discuss"
msgid "View of the settings page emphasizing the menu activity types."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:64
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:139
msgid "Doing so reveals the :guilabel:`Activity Types` page, where the existing activity types are found."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:141
msgid "To edit an existing activity type, select it from the list, then click :guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:144
msgid "At the top of a blank activity type form, start by choosing a :guilabel:`Name` for the new activity type."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1
msgid "New activity type form."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:152
msgid "Activity settings"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:155
#: ../../content/applications/productivity/studio/automated_actions.rst:134
msgid "Action"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:157
msgid "The *Action* field specifies the intent of the activity. Some actions trigger specific behaviors after an activity is scheduled."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:160
msgid "If :guilabel:`Upload Document` is selected, a link to upload a document is added directly to the planned activity in the chatter."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:162
msgid "If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users have the option to open their calendar to schedule a time for this activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:164
msgid "If :guilabel:`Request Signature` is selected, a link is added to the planned activity in the chatter that opens a signature request pop-up window."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:168
msgid "The actions available to select on an activity type vary, depending on the applications currently installed in the database."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:172
msgid "Default user"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:174
msgid "To automatically assign this activity to a specific user when this activity type is scheduled, choose a name from the :guilabel:`Default User` drop-down menu. If this field is left blank, the activity is assigned to the user who creates the activity."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:179
msgid "Default summary"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:181
msgid "To include notes whenever this activity type is created, enter them into the :guilabel:`Default Summary` field."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:185
msgid "The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are included when an activity is created. However, they can be altered before the activity is scheduled or saved."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:190
msgid "Next activity"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:192
msgid "To automatically suggest, or trigger, a new activity after an activity has been marked complete, the :guilabel:`Chaining Type` must be set."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:196
msgid "Suggest next activity"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:198
msgid "In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next Activity`. Upon doing so, the field underneath changes to: :guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to select any activities to recommend as follow-up tasks to this activity type."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:202
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:230
msgid "In the :guilabel:`Schedule` field, choose a default deadline for these activities. To do so, configure a desired number of :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur :guilabel:`after completion date` or :guilabel:`after previous activity deadline`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:207
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:235
msgid "This :guilabel:`Schedule` field information can be altered before the activity is scheduled."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:209
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:237
msgid "When all configurations are complete, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1
msgid "Schedule activity popup with emphasis on recommended activities."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:216
msgid "If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest Next Activity`, and has activities listed in the :guilabel:`Suggest` field, users are presented with recommendations for activities as next steps."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:221
msgid "Trigger next activity"
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:223
msgid "Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` immediately launches the next activity once the previous one is completed."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:226
msgid "If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining Type` field, the field beneath changes to: :guilabel:`Trigger`. From the :guilabel:`Trigger` field drop-down menu, select the activity that should be launched once this activity is completed."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1
msgid "Schedule new activity popup with emphasis on Done and launch next button."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:244
msgid "When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger Next Activity`, marking the activity as `Done` immediately launches the next activity listed in the :guilabel:`Trigger` field."
msgstr ""
#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:249
#: ../../content/applications/productivity/discuss/overview/team_communication.rst:113
msgid ":doc:`get_started`"
msgstr ""
@ -822,8 +1044,12 @@ msgstr ""
msgid "Internet of Things (IoT)"
msgstr ""
#: ../../content/applications/productivity/iot.rst:17
msgid "The Open Platform Communications (OPC) Unified Architecture (UA) protocol is now supported by the :abbr:`IoT (Internet of Things)` box. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` is an open standard that specifies information exchange for industrial communication on devices, between machines and between systems. This includes communication between information technology and operational technology. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` can be used with any software platform, on a wide variety of devices, and deployed securely. The :abbr:`IoT (Internet of Things)` box has entered the world of the Industry 4.0 standard and can be utilized in a wide variety of industries, and for things like building automation, packaging, utilities, etc."
msgstr ""
#: ../../content/applications/productivity/iot/config.rst:5
#: ../../content/applications/productivity/mail_plugins/outlook.rst:6
#: ../../content/applications/productivity/mail_plugins/outlook.rst:10
msgid "Configuration"
msgstr ""
@ -2325,7 +2551,7 @@ msgstr ""
#: ../../content/applications/productivity/iot/devices/camera.rst:82
#: ../../content/applications/productivity/iot/devices/footswitch.rst:52
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:90
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:92
#: ../../content/applications/productivity/iot/devices/printer.rst:95
msgid ":ref:`workcenter_iot`"
msgstr ""
@ -2378,19 +2604,19 @@ msgstr ""
msgid "Connect a measurement tool"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:5
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:7
msgid "With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect measurement tools to the Odoo database for use in the *Quality app* on a quality control point/quality check, or for use in a work center during the manufacturing process."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:9
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:11
msgid "Find the list of supported devices here: `Supported devices <https://www.odoo.com/page/iot-hardware>`_."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:13
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15
msgid "Connect with universal serial bus (USB)"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:17
msgid "To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the :abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of Things)` box, and the device appears in the Odoo database."
msgstr ""
@ -2398,11 +2624,11 @@ msgstr ""
msgid "Measurement tool recognized on the IoT box."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:24
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26
msgid "Connect with bluetooth"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:28
msgid "Activate the Bluetooth functionality on the device (see the device manual for further explanation), and the :abbr:`IoT (Internet of Things)` box automatically connects to the device."
msgstr ""
@ -2410,23 +2636,23 @@ msgstr ""
msgid "Bluetooth indicator on measurement tool."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:35
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37
msgid "Link a measurement tool to a quality control point in the manufacturing process"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:39
msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, navigate to :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the measurement tool should be linked."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:41
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:43
msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, where the attached device can be selected."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:45
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:47
msgid "Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. :guilabel:`Save` the changes, if required."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:48
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:50
msgid "At this point, the measurement tool is linked to the chosen quality control point. The value, which usually needs to be changed manually, is automatically updated while the tool is being used."
msgstr ""
@ -2434,40 +2660,40 @@ msgstr ""
msgid "Measurement tool input in the Odoo database."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:56
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:58
#: ../../content/applications/productivity/iot/devices/printer.rst:60
msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`, then select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:61
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:63
msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Measure`. Access a new quality check detail page, by navigating to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:66
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:68
msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:67
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:69
msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:70
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72
msgid "Link a measurement tool to a work center in the Manufacturing app"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:74
msgid "To link a measurement tool to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Then, select the desired work center in which the measurement tool will be used."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:76
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:78
msgid "On the work center page, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Then, the measurement tool can be linked to the :guilabel:`Action` drop-down menu option labeled :guilabel:`Take Measure`. A key can be added to trigger the action."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:82
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:84
msgid "It should be noted that the first listed trigger is chosen first. The order matters, and these triggers can be dragged into any order."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:86
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:88
msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the measurement tool."
msgstr ""
@ -3747,160 +3973,160 @@ msgstr ""
msgid "Outlook Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:8
#: ../../content/applications/productivity/mail_plugins/outlook.rst:5
msgid "Outlook allows for third-party applications to connect in order to execute database actions from emails. Odoo has a plugin for Outlook that allows for the creation of an opportunity from the email panel."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:12
msgid "The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both on Odoo and Outlook."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:13
#: ../../content/applications/productivity/mail_plugins/outlook.rst:17
msgid "Enable Mail Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:15
msgid "First, you need to enable the *Mail Plugin* feature in your database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable *Mail Plugin*, and *Save* the configuration."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:21
msgid "Install the Outlook Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:23
msgid "Open your Outlook mailbox and select any email."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:19
msgid "First, enable the *Mail Plugin* feature in the database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable :guilabel:`Mail Plugin`, and :guilabel:`Save` the configuration."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:25
msgid "Click on the *More actions* button and select *Get Add-ins*."
msgid "Install the Outlook Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "More actions button in Outlook"
#: ../../content/applications/productivity/mail_plugins/outlook.rst:27
msgid "Download (:menuselection:`Save Page As --> Web Page XML only`) the following XML file to upload later: `https://download.odoocdn.com/plugins/outlook/manifest.xml <https://download.odoocdn.com/plugins/outlook/manifest.xml>`_."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:31
msgid "Select the *My add-ins* tab."
msgid "Next, open the Outlook mailbox, and select any email. After completing this, click on the :guilabel:`More actions` button in the upper right-side and select :guilabel:`Get Add-ins`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "More actions button in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:38
msgid "Following this step, select the :guilabel:`My add-ins` tab on the left-side."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "My add-ins in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:37
msgid "Under *Custom add-ins*, click on *+ Add a custom add-in*, and then on *Add from URL...*"
#: ../../content/applications/productivity/mail_plugins/outlook.rst:44
msgid "Under :guilabel:`Custom add-ins` towards the bottom, click on :guilabel:`+ Add a custom add-in`, and then on :guilabel:`Add from file...`"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Custom add-ins in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:43
msgid "Enter the following URL `https://download.odoocdn.com/plugins/v15/outlook/manifest.xml` and press *OK*."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:51
msgid "For the next step, attach the `manifest.xml` file downloaded above, and press :guilabel:`OK`. Next, read the warning and click on :guilabel:`Install`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "Entering the add-in URL in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:50
msgid "Read the warning and click on *Install*."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Custom add-in installation warning in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:59
msgid "Connect your database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:61
msgid "Open any email in your Outlook mailbox, click on the *More actions* button, and select *Odoo for Outlook*."
msgid "Connect the database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:63
msgid "Now, Outlook will be connected to the Odoo database. First, open any email in the Outlook mailbox, click on the :guilabel:`More actions` button in the upper right-side, and select :guilabel:`Odoo for Outlook`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Odoo for Outlook add-in button"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:68
msgid "The right-side panel can now display **Company Insights**. At the bottom, click on *Login*."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:71
msgid "The right-side panel can now display **Company Insights**. At the bottom, click on :guilabel:`Login`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "Logging in your Odoo database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:75
msgid "Only a limited amount of *Company Insights* (*Lead Enrichment*) requests are available as a trial. This feature requires :ref:`prepaid credits <mail_plugins/pricing>`."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Logging in the Odoo database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:79
msgid "If, after a short while, the panel is still empty, it is possible that your browser cookie settings prevented it from loading. Note that these settings also change if you are in \"Incognito\" mode on your browser."
msgid "Only a limited amount of **Company Insights** (*Lead Enrichment*) requests are available as a trial database. This feature requires :ref:`prepaid credits <mail_plugins/pricing>`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:84
msgid "To fix this issue, configure your browser to always allow cookies on Odoo's plugin page."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:83
msgid "If, after a short while, the panel is still empty, it is possible that the browser cookie settings prevented it from loading. Note that these settings also change if the browser is in \"Incognito\" mode."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:86
msgid "For Google Chrome, you can do so by following the guide at: `https://support.google.com/chrome/answer/95647 <https://support.google.com/chrome/answer/95647#:~:text=Allow%20or%20block%20cookies%20for%20a%20specific%20site>`_ and adding `download.odoo.com` to the list of `Sites that can always use cookies`."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:87
msgid "To fix this issue, configure the browser to always allow cookies on Odoo's plugin page."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:90
msgid "Once done, the Outlook panel needs to be opened again."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:89
msgid "For Google Chrome, change the browser cookie settings by following the guide at: `https://support.google.com/chrome/answer/95647 <https://support.google.com/chrome/answer/95647>`_ and adding `download.odoo.com` to the list of :guilabel:`Sites that can always use cookies`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:93
msgid "Enter your Odoo database URL and click on *Login*."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:94
msgid "Once this is complete, the Outlook panel needs to be opened again."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "Entering your Odoo database URL"
#: ../../content/applications/productivity/mail_plugins/outlook.rst:96
msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:99
msgid "Click on *Allow* to open the pop-up window."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Entering the Odoo database URL"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:102
msgid "Next, click on :guilabel:`Allow` to open the pop-up window."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "New window pop-up warning"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:105
msgid "If you aren't logged into your database, enter your credentials."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:108
msgid "If the user isn't logged into the database, enter the credentials. Click on :guilabel:`Allow` to let the Outlook Plugin connect to the database."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:107
msgid "Click on *Allow* to let the Outlook Plugin connect to your database."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Allowing the Outlook Plugin to connect to a database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:116
#: ../../content/applications/productivity/mail_plugins/outlook.rst:118
msgid "Add a shortcut to the plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:118
#: ../../content/applications/productivity/mail_plugins/outlook.rst:120
msgid "By default, the Outlook Plugin can be opened from the *More actions* menu. However, to save time, it's possible to add it next to the other default actions."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:121
msgid "In your Outlook mailbox, click on *Settings*, then on *View all Outlook settings*."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:123
msgid "In the Outlook mailbox, click on :guilabel:`Settings`, then on :guilabel:`View all Outlook settings`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Viewing all Outlook settings"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:127
msgid "Select *Customize actions* under *Mail*, click on *Odoo for Outlook*, and then *Save*."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:130
msgid "Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on :guilabel:`Odoo for Outlook`, and then :guilabel:`Save`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Odoo for Outlook customized action"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:133
msgid "Open any email; the shortcut should be displayed."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:137
msgid "Following this step, open any email; the shortcut should be displayed."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:144
msgid "Using the plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:146
msgid "Now that the plug-in is installed and operational, all that needs to be done to create a lead is to click on the `O` [Odoo icon] or navigate to :guilabel:`More actions` and click on :guilabel:`Odoo for Outlook`. The side panel will appear on the right-side, and under :guilabel:`Opportunities` click on :guilabel:`New`. A new window with the created opportunity in the Odoo database will populate."
msgstr ""
#: ../../content/applications/productivity/studio.rst:6
@ -4083,10 +4309,6 @@ msgstr ""
msgid "Define on which records of the model the automated action should be applied. It works the same way as when you apply filters on a model."
msgstr ""
#: ../../content/applications/productivity/studio/automated_actions.rst:134
msgid "Action"
msgstr ""
#: ../../content/applications/productivity/studio/automated_actions.rst:136
msgid "Determine what the automated action should do (server action). There are eight types of action to choose from."
msgstr ""

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-16.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-10-10 06:13+0000\n"
"POT-Creation-Date: 2023-12-19 13:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -51,7 +51,7 @@ msgid "Configuration"
msgstr ""
#: ../../content/applications/services/field_service/default_warehouse.rst:18
msgid "To set up a user default warehouse, the :doc:`storage locations <../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations>` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database."
msgid "To set up a user default warehouse, the :doc:`storage locations </applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations>` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database."
msgstr ""
#: ../../content/applications/services/field_service/default_warehouse.rst:23
@ -59,7 +59,7 @@ msgid "You can either set it up :ref:`for your profile <default-warehouse/my-pro
msgstr ""
#: ../../content/applications/services/field_service/default_warehouse.rst:27
msgid ":doc:`../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations`"
msgstr ""
#: ../../content/applications/services/field_service/default_warehouse.rst:32
@ -875,7 +875,7 @@ msgid "When the necessary information has been entered, click :guilabel:`Create
msgstr ""
#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:248
msgid ":doc:`/applications/inventory_and_mrp/inventory/management/products/uom`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview.rst:5

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo saas-16.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-10-27 12:38+0000\n"
"POT-Creation-Date: 2023-12-19 13:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -407,7 +407,7 @@ msgid "Own shipping methods"
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:17
msgid "You can create your own custom shipping methods and define rules to compute shipping costs. To do so, go to :menuselection:`Website --> Configuration --> Shipping Methods`, and either select an **existing** shipping method, or :guilabel:`Create` one. When creating a shipping method, you can choose between :doc:`Fixed Price </applications/inventory_and_mrp/inventory/shipping/setup/delivery_method>`, :doc:`Based on Rules </applications/inventory_and_mrp/inventory/shipping/setup/delivery_method>`, and :guilabel:`Pickup in store`."
msgid "You can create your own custom shipping methods and define rules to compute shipping costs. To do so, go to :menuselection:`Website --> Configuration --> Shipping Methods`, and either select an **existing** shipping method, or :guilabel:`Create` one. When creating a shipping method, you can choose between :doc:`Fixed Price </applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method>`, :doc:`Based on Rules </applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method>`, and :guilabel:`Pickup in store`."
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:26
@ -419,21 +419,21 @@ msgid ":guilabel:`Pickup in store` must first be **enabled** in the settings (:m
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:34
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`"
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:35
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/invoicing`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`"
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:36
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/multipack`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`"
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:37
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/cancel`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel`"
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:42
@ -445,20 +445,20 @@ msgid "Another solution is to use one of the integrations with an existing shipp
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:49
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`"
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:50
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/setup/ups_credentials`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`"
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:51
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/setup/dhl_credentials`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`"
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52
#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:84
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping/operation/labels`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels`"
msgstr ""
#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:55
@ -1251,7 +1251,7 @@ msgid "Price per unit"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:56
msgid "It is possible to display a :doc:`price per unit </applications/inventory_and_mrp/inventory/management/products/uom>` on the product page. To do that, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Product Reference Price` under the :guilabel:`Shop - Products` section. When enabled, ensure an amount is set in the :guilabel:`Base Unit Count` field of the **product template**, and in the :guilabel:`Sales Price`."
msgid "It is possible to display a :doc:`price per unit </applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom>` on the product page. To do that, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Product Reference Price` under the :guilabel:`Shop - Products` section. When enabled, ensure an amount is set in the :guilabel:`Base Unit Count` field of the **product template**, and in the :guilabel:`Sales Price`."
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:-1
@ -1271,7 +1271,7 @@ msgid "Pay attention that having the price per unit may be **mandatory** in some
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:78
msgid ":doc:`/applications/inventory_and_mrp/inventory/management/products/uom`"
msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`"
msgstr ""
#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:83
@ -3413,61 +3413,169 @@ msgid "Ratings"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:5
msgid "Giving users the opportunity to rate their interactions can help you improving the experience you offer. That means staying on top of your customers' needs, besides keeping track of your operators performances."
msgid "At the end of a *Live Chat* conversation, customers have the opportunity to rate the quality of support they received from the live chat *operator*. Customers provide ratings as soon as they close the conversation. This allows operators to receive immediate feedback on their performance. It also allows customers the chance to share any final comments before leaving the chat window."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:10
msgid "Customer Rating"
#: ../../content/applications/websites/livechat/ratings.rst:11
msgid "Rate live chat conversations"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:12
msgid "Once the user chooses to close the chat window, he can rate his interaction."
#: ../../content/applications/websites/livechat/ratings.rst:13
msgid "Customers end a *live chat* conversation by clicking the :guilabel:`X` in the upper right-hand corner of the chat window. They are then prompted to select an icon that reflects their level of satisfaction. The icons represent the following ratings:"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:14
msgid "If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing for an explanation is shown."
#: ../../content/applications/websites/livechat/ratings.rst:17
msgid "**Satisfied** - *green smiling face*"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:15
msgid "A copy of the conversation can also be sent by email."
#: ../../content/applications/websites/livechat/ratings.rst:18
msgid "**Okay** - *yellow neutral face*"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:19
msgid "**Dissatisfied** - *red frowning face*"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:-1
msgid "View of the chat window from a users side for Odoo Live Chat"
msgid "View of the chat window from a user's side for Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:22
msgid "The rating is shown on the chat window itself for the operator."
#: ../../content/applications/websites/livechat/ratings.rst:26
msgid "When customers end a conversation, a field marked :guilabel:`Receive a copy of this conversation` appears under the *ratings* icons. Customers can enter their email either before or after they submit a rating."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:30
msgid "If the customer selects :guilabel:`Satisfied (smile)` icon, they are presented with a thank you message and a :guilabel:`Close Conversation` link."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:-1
msgid "View of a chat window from an operators side highlighting a rating for Odoo Live Chat"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:28
msgid "And under :menuselection:`Report --> Customer Ratings`."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:-1
msgid "View of the customer ratings page in Odoo Live Chat"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:35
msgid "Make the rating public"
msgid "View of customer's live chat window with thank you message."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:37
msgid "Go to :menuselection:`Website --> Configuration --> Settings`, access your channel form, click on *Go to Website* and on *Unpublished*, to publish the rating of that channel on your website."
msgid "If the customer selects either :guilabel:`Okay (neutral)` icon or :guilabel:`Dissatisfied (frown)` icon, a text box will appear. Customers can add comments in this text box to explain why they chose this rating. This message will be sent to the live chat operator, along with the rating icon."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:-1
msgid "View of the public ratings in the website for Odoo Live Chat"
msgid "View of a chat window from an operator's window highlighting a rating for Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:45
#: ../../content/applications/websites/livechat/ratings.rst:46
msgid "Publish customer ratings"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:48
msgid "To publish a channel's ratings on the website, first navigate to a live chat channel's record by going to the :menuselection:`Live Chat` app and clicking on the kanban card for that team. Then click on the :guilabel:`Go to Website` smart button. This will open the :guilabel:`Live Chat Channel Statistics` page."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:53
msgid "In the upper right corner of the page, click the red :guilabel:`Unpublished` slider. The slider changes from :guilabel:`Unpublished` to :guilabel:`Published`."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:-1
msgid "View of the published ratings on the portal for Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:61
msgid "The customer notes that are submitted with the rating will *not* be published on the website. These are kept internal. Only a statistical overview of the operators' performance for the *channel* appears on the website."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:66
msgid "Add ratings page to site"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:68
msgid "Once the rating page has been published, it has to be manually added to the website. To do this, go to the main Odoo dashboard and open the *Website* application. :menuselection:`Website app--> Site --> Content --> Pages`, then click :guilabel:`New`."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:72
msgid "This will open a :guilabel:`New Page` pop-up window. In the :guilabel:`Page Title` field, enter `livechat`. This acts as the URL for the published webpage."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:76
msgid "The URL *must* be named `livechat` in order for the database to recognize and connect the ratings page. After the page has been published, the page title can be changed later under the :guilabel:`Menu Editor`."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:80
msgid "Click :guilabel:`Create`, and the newly created webpage will open. The :guilabel:`Webpage Editor` appears in the right panel."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:83
msgid "The page lists the names of the :guilabel:`Live Chat Channels` whose ratings pages have been published. On the left side of the channel name is a speech bubble icon, which users can click on to go to the ratings' page for the respective channel."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:-1
msgid "View of the webpage for Live Chat ratings emphasizing the channel icon."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:91
msgid "Make any desired changes or additions to this page, then click :guilabel:`Save` in the top right of the webpage editor. The website editor side panel closes, and the webpage remains on the screen."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:94
msgid "To publish the `livechat` webpage, return to the list of webpages by navigating to :menuselection:`Site --> Content --> Pages`. Click the checkbox to the left of `livechat` in the list of pages to select the page and highlight the line. Then, click the checkbox under the column labeled :guilabel:`Is Published`. The field with the checkbox is highlighted in white. Click the checkbox a second time to activate the :guilabel:`Is Published` box. The webpage is now published."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:-1
msgid "View of the list of pages for a website with the 'is published' box emphasized."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:104
msgid "Once the page has been added to the site, ratings are set to be published by default. However, individual ratings can be manually selected to be hidden from the public. The rating will still be included in internal reports, and can still be viewed by internal teams. However, public website visitors and portal users will not have access."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:109
msgid "See :ref:`Hide individual ratings <livechat/overview/hide-ratings>` for more information."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:112
msgid "Customer ratings report"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:114
msgid "The :guilabel:`Customer Ratings` report (:menuselection:`Live Chat --> Report --> Customer Ratings`) displays an overview of the ratings received on individual support tickets, as well as any additional comments submitted with the rating."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:-1
msgid "View of the customer ratings report in Odoo Live Chat."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:122
msgid "The report defaults to a kanban view, with each rating represented by a different card. To switch to a different view, click on one of the icons in the upper-right corner of the screen. The report is available in *list* view, *pivot* view, and *graph* view."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:126
msgid "Click on an individual rating to see additional details about the conversation, and the rating."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:131
msgid "Hide individual ratings"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:133
msgid "Ratings are set to be published by default. However, individual ratings can be manually selected to be hidden from the public. The rating will still be included in internal reports, and can still be viewed by internal teams. However, public website visitors and portal users will not have access."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:137
msgid "To hide a rating, go to :menuselection:`Live Chat app --> Reports --> Customer Ratings`. Click on the kanban card for the rating to be hidden. On the individual rating's detail page, check the box labeled :guilabel:`Visible Internally Only`."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:-1
msgid "View of an individual rating's detail page with the visible internally setting checked."
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:146
msgid ":doc:`/applications/websites/livechat`"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:147
msgid ":doc:`responses`"
msgstr ""
#: ../../content/applications/websites/livechat/ratings.rst:148
msgid ":doc:`/applications/websites/website`"
msgstr ""
#: ../../content/applications/websites/livechat/responses.rst:3
msgid "Commands and canned responses"
msgstr ""
@ -4340,63 +4448,199 @@ msgid "Add a language selector menu."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:3
msgid "Unsplash (free images)"
msgid "Unsplash"
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:6
msgid "Generate an Unsplash access key"
#: ../../content/applications/websites/website/configuration/unsplash.rst:5
msgid "**Unsplash** is a recognized stock photography library integrated with Odoo."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:9
msgid "**As an Odoo Online user**, you are ready to use Unsplash. You won't need to follow this guide to set up Unsplash information since you will use our own Odoo Unsplash key in a transparent way."
#: ../../content/applications/websites/website/configuration/unsplash.rst:7
msgid "If your database is hosted on **Odoo Online**, you can access Unsplash pictures without configuration."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:13
msgid "Generate an Unsplash access key for non-Odoo Online users"
#: ../../content/applications/websites/website/configuration/unsplash.rst:10
msgid "If your database is hosted on **Odoo.sh or on-premise**, proceed as follows:"
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:12
msgid "To **generate an Unsplash access key**, create or sign in to an `Unsplash account <https://unsplash.com>`_."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:15
msgid "Create an account on `Unsplash.com <https://unsplash.com/join>`_."
msgid "Access your `applications dashboard <https://unsplash.com/oauth/applications>`_, click :guilabel:`New Application`, select all checkboxes, and click :guilabel:`Accept terms`."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:17
msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on **New Application**."
#: ../../content/applications/websites/website/configuration/unsplash.rst:18
msgid "In the pop-up window, enter your :guilabel:`Application Name`, starting with the prefix `Odoo:` (e.g., `Odoo: connection`), so Unsplash recognizes it as an Odoo instance. Then, add a :guilabel:`Description` and click :guilabel:`Create application`."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:23
msgid "Accept the conditions and click on **Accept terms**."
#: ../../content/applications/websites/website/configuration/unsplash.rst:22
msgid "On the application details page, scroll down to the :guilabel:`Keys` section and copy the :guilabel:`Access Key` and :guilabel:`Application ID`."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:28
msgid "You will be prompted to insert an **Application name** and a **Description**. Please prefix your application name by \"**Odoo:** \" so that Unsplash can recognize it as an Odoo instance. Once done, click on **Create application**."
#: ../../content/applications/websites/website/configuration/unsplash.rst:25
msgid "In Odoo, go to :menuselection:`General Settings` and enable the :guilabel:`Unsplash Image Library` feature. Then, enter the Unsplash :guilabel:`Access Key` and :guilabel:`Application ID`."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:35
msgid "You should be redirected to your application details page. Scroll down a bit to find your **access key**."
#: ../../content/applications/websites/website/configuration/unsplash.rst:29
msgid "As a non-Odoo Online user, you are limited to a test key with a maximum of 50 Unsplash requests per hour."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:42
msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a restriction of 50 Unsplash requests per hour."
#: ../../content/applications/websites/website/mail_groups.rst:3
msgid "Mail groups"
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:46
msgid "Generate an Unsplash application ID"
#: ../../content/applications/websites/website/mail_groups.rst:5
msgid "The **mail groups** feature allows website visitors to have a public discussion by email. They can join a group to receive emails from other group members (i.e., website users who have subscribed to the group) and send new ones to all group members."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:49
msgid "You should first create and set up your Unsplash application."
#: ../../content/applications/websites/website/mail_groups.rst:9
msgid "To activate the feature, :ref:`install <general/install>` the :guilabel:`Website Mail Group` (`website_mail_group`) module."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:51
msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on your newly created Unsplash application under **Your applications**."
#: ../../content/applications/websites/website/mail_groups.rst:13
msgid "The **mail groups** feature is not to be confused with the :doc:`../../marketing/email_marketing/mailing_lists` in the Email Marketing app."
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:57
msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/<application_id>``"
#: ../../content/applications/websites/website/mail_groups.rst:19
msgid "Configuring mail groups"
msgstr ""
#: ../../content/applications/websites/website/configuration/unsplash.rst:65
msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction."
#: ../../content/applications/websites/website/mail_groups.rst:21
msgid "To configure mail groups, proceed as follows:"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:23
msgid "Configure a custom email alias domain by accessing the **General settings**, scrolling down to the :guilabel:`Discuss` section, enabling the :guilabel:`Custom Email Server` feature, and entering the :guilabel:`Alias domain` (e.g., `@mycompany.com`)."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:26
msgid "Go to :menuselection:`Website --> Configuration --> Mailing Lists`, then click :guilabel:`New`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:27
msgid "Specify a :guilabel:`Group Name`, the :guilabel:`Email Alias`, and a :guilabel:`Description`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:28
msgid "Enable :guilabel:`Moderate this group` and specify the :guilabel:`Moderators` if you wish to :ref:`moderate messages <website/mailing_lists/moderate>` from this group. Alternatively, if the group is not moderated, you can define :guilabel:`Responsible Users` who can manage the messages in the group."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:32
msgid "In the :guilabel:`Privacy` tab, define who can subscribe to the mail group:"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:34
msgid ":guilabel:`Everyone`: to make the mail group public so anyone can subscribe to it;"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:35
msgid ":guilabel:`Members only`: to only allow users defined as members to subscribe to the mail group;"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:36
msgid ":guilabel:`Selected group of users`: to only allow users from the :guilabel:`Authorized group` to subscribe to the mail group."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:39
msgid "If the mail group is moderated, you can automatically notify authors when their message is pending moderation by enabling :guilabel:`Automatic notification` in the :guilabel:`Notify Members` tab and writing the :guilabel:`Notification message`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:42
msgid "If you wish to send out guidelines to new subscribers, enable :guilabel:`Send guidelines to new subscribers` and write them in the :guilabel:`Guidelines` tab. This is particularly useful when the mail group is moderated."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:47
msgid "Using mail groups"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:50
msgid "Subscribing/unsubscribing"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:52
msgid "Based on the :ref:`configuration of the mail group <website/mailing_lists/configure_groups>`, users can subscribe to and unsubscribe from mail groups from the website page (`/groups` by default)."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:-1
msgid "Mail group web page."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:58
msgid "Internal users can also do this from :menuselection:`Website --> Configuration --> Mailing Lists`, using the :guilabel:`Join` and :guilabel:`Leave` buttons."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:62
msgid "Sending messages"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:64
msgid "To send messages to a mail group, website users can email the :ref:`mail group's email address <website/mailing_lists/configure_groups>`. Internal users can also create messages directly from Odoo. To do so, go to :menuselection:`Website --> Configuration --> Mailing Lists`, select the mail group, click the :guilabel:`Emails` smart button, and click :guilabel:`New`. Then, fill in the fields and click :guilabel:`Send`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:71
msgid "The list of messages can also be accessed by selecting the group from the `/groups` website page."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:73
msgid "Group members can also unsubscribe from the group, access the mail group page, and send emails to the group using the URLs in the footer of any group email they have received."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:0
msgid "URLs in the footer of a group email."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:82
msgid "Moderating mail group messages"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:84
msgid "If the :guilabel:`Moderate this group` feature has been enabled for the :ref:`mail group <website/mailing_lists/configure_groups>`, one of the :guilabel:`Moderators` must approve the group's messages before they are dispatched to the other members."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:88
msgid "To moderate messages, go to :menuselection:`Website --> Configuration --> Mailing Lists`, select the mail group, and click the :guilabel:`To review` smart button. You can moderate messages using the buttons at the end of the message line or select a message to view its content and moderate it accordingly."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:0
msgid "Moderation buttons in the message line."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:96
msgid "The following actions are available:"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:98
msgid ":guilabel:`Accept`: to accept the email and send it to the mail group members."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:99
msgid ":guilabel:`Reject`: to reject the email. In the pop-up window that opens, click :guilabel:`Reject Silently` to reject the email without notifying the author, or specify an explanation for rejecting the message, then click :guilabel:`Send & Reject` to reject the message and send the explanation to the author."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:103
msgid ":guilabel:`Whitelist`: to whitelist the author, i.e. automatically accept all of their emails. As a result, a :ref:`moderation rule <website/mailing_lists/moderate>` is created for the author's email address with the status :guilabel:`Always allow`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:106
msgid ":guilabel:`Ban`: to blacklist the author, i.e. automatically discard all their emails. In the pop-up window that opens, click :guilabel:`Ban` to ban the author without notifying them, or specify an explanation, then click :guilabel:`Send & Ban` to ban the author and send them the explanation. As a result, a :ref:`moderation rule <website/mailing_lists/moderate>` is created for the author's email address with the status :guilabel:`Permanent ban`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:113
msgid "Messages can also be moderated from the group's list of messages. Go to :menuselection:`Website --> Groups --> Mailing List Groups`, select the mail group and click the :guilabel:`Emails` smart button."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:120
msgid "Whitelisting/Blacklisting authors"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:122
msgid "You can whitelist or blacklist an author either directly :ref:`from a mail group message <website/mailing_lists/moderate>`, or by creating a moderation rule. To do so, go to :menuselection:`Website --> Configuration --> Moderation Rules` and click :guilabel:`New`. Then, select the :guilabel:`Group`, specify the author's :guilabel:`Email` and set the :guilabel:`Status` field."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:129
msgid "You can also access the mail group's moderation rules by going to :menuselection:`Website --> Configuration --> Mailing Lists`, selecting the group, then clicking the :guilabel:`Moderations` smart button."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:5
@ -5512,30 +5756,66 @@ msgid "Website analytics helps website owners understand how people use their si
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:8
msgid "You can track your Odoo website's traffic using :ref:`website/analytics/plausible` or :ref:`website/analytics/GA`. We recommend using Plausible.io as it is privacy-friendly, lightweight, and easy to use. The Plausible analytics dashboard is also integrated into Odoo and can be accessed via :menuselection:`Website --> Reporting --> Analytics`."
msgid "You can track your Odoo website's traffic using :ref:`website/analytics/plausible` or :ref:`website/analytics/GA`. We recommend using Plausible.io as it is privacy-friendly, lightweight, and easy to use."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:16
msgid "Plausible.io"
#: ../../content/applications/websites/website/reporting/analytics.rst:12
msgid "The Plausible analytics dashboard is also integrated into Odoo and can be accessed via :menuselection:`Website --> Reporting --> Analytics`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:18
msgid "If your database is hosted on Odoo Online, the Plausible.io integration is available in Odoo for free. To enable the feature, go to :menuselection:`Website --> Configuration --> Settings`, then, in the :guilabel:`SEO` section, enable :guilabel:`Plausible Analytics` and click :guilabel:`Save`. You can then access your Plausible analytics dashboard by going to :menuselection:`Website --> Reporting --> Analytics`."
msgid "Plausible.io"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:24
msgid "If your database is hosted on Odoo.sh or on-premise, or if you wish to use your own Plausible.io account, proceed as follows:"
#: ../../content/applications/websites/website/reporting/analytics.rst:20
msgid "Odoo hosts its own Plausible.io server and provides a free and ready-to-work Plausible.io solution for **Odoo Online** databases. Go to :menuselection:`Website --> Configuration --> Settings`, and enable the feature in the :guilabel:`SEO` section. Odoo automatically creates and sets up your account. You can start using it by going to :menuselection:`Website --> Reporting --> Analytics`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:27
#: ../../content/applications/websites/website/reporting/analytics.rst:26
msgid "**If you already have a Plausible.io account** and you want to connect it to your Odoo Online database, you must create two `ir.config.parameters` to use Plausible.io's servers. To do so, enable the :ref:`developer mode <developer-mode>` and go to :menuselection:`General Settings --> Technical -- System Parameters`. Click :guilabel:`New` and fill in the following :guilabel:`Key` and :guilabel:`Value` fields:"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:35
msgid "Key"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:36
msgid "Value"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:37
msgid "`website.plausible_script`"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:38
msgid "`https://plausible.io/js/plausible.js`"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:39
msgid "`website.plausible_server`"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:40
msgid "`https://plausible.io`"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:42
msgid "Then, follow the steps below to connect your existing account with Plausible.io servers."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:44
msgid "If your database is hosted on **Odoo.sh** or **On-premise**, or if you wish to use your own Plausible.io account, proceed as follows:"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:47
msgid "Create or sign in to a Plausible account using the following link: `<https://plausible.io/register>`_."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:28
#: ../../content/applications/websites/website/reporting/analytics.rst:48
msgid "If you are creating a new account, go through the registration and activation steps. When asked to provide your website details, add its :guilabel:`Domain` without including `www` (e.g., `example.odoo.com`) and change the :guilabel:`Reporting Timezone` if necessary. Click :guilabel:`Add snippet` to proceed to the next step. Ignore the :guilabel:`Add JavaScript snippet` instructions and click :guilabel:`Start collecting data`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:33
#: ../../content/applications/websites/website/reporting/analytics.rst:53
msgid "Once done, click the Plausible logo in the upper-left part of the page to access your `list of websites <https://plausible.io/sites>`_, then click the gear icon next to the website."
msgstr ""
@ -5543,11 +5823,11 @@ msgstr ""
msgid "Click the gear icon in the list of websites."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:39
#: ../../content/applications/websites/website/reporting/analytics.rst:59
msgid "In the sidebar, select :guilabel:`Visibility`, then click :guilabel:`+ New link`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:40
#: ../../content/applications/websites/website/reporting/analytics.rst:60
msgid "Enter a :guilabel:`Name`, leave the :guilabel:`Password` field empty, as the Plausible analytics dashboard integration in Odoo doesn't support it, then click :guilabel:`Create shared link`."
msgstr ""
@ -5555,7 +5835,7 @@ msgstr ""
msgid "Credentials creation for the new shared link"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:46
#: ../../content/applications/websites/website/reporting/analytics.rst:66
msgid "Copy the shared link."
msgstr ""
@ -5563,44 +5843,44 @@ msgstr ""
msgid "Copy the shared link URL from Plausible.io"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:51
#: ../../content/applications/websites/website/reporting/analytics.rst:98
#: ../../content/applications/websites/website/reporting/analytics.rst:71
#: ../../content/applications/websites/website/reporting/analytics.rst:118
msgid "In Odoo, go to :menuselection:`Website --> Configuration --> Settings`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:52
#: ../../content/applications/websites/website/reporting/analytics.rst:72
msgid "In the :guilabel:`SEO` section, enable :guilabel:`Plausible Analytics`, then paste the :guilabel:`Shared Link` and click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:56
#: ../../content/applications/websites/website/reporting/analytics.rst:76
msgid "If you have :doc:`multiple websites <../configuration/multi_website>`, add your websites to your Plausible.io account by going to `<https://plausible.io/sites>`_ and clicking :guilabel:`+ Add website`. In Odoo, in the **Website settings**, make sure to select the website in the :guilabel:`Settings of Website` field before pasting the :guilabel:`Shared link`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:62
#: ../../content/applications/websites/website/reporting/analytics.rst:82
msgid "Odoo automatically pushes two custom goals: `Lead Generation` and `Shop`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:65
#: ../../content/applications/websites/website/reporting/analytics.rst:85
msgid "`Plausible Analytics documentation <https://plausible.io/docs>`_"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:70
#: ../../content/applications/websites/website/reporting/analytics.rst:90
msgid "Google Analytics"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:72
#: ../../content/applications/websites/website/reporting/analytics.rst:92
msgid "To follow your Odoo website's traffic with Google Analytics:"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:74
#: ../../content/applications/websites/website/reporting/analytics.rst:94
msgid "Create or sign in to a Google account using the following link: `<https://analytics.google.com>`_."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:75
#: ../../content/applications/websites/website/reporting/analytics.rst:95
msgid "If you are setting up Google Analytics for the first time, click :guilabel:`Start measuring` and go through the account creation step."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:77
#: ../../content/applications/websites/website/reporting/analytics.rst:97
msgid "If you already have a Google Analytics account, sign in and click the gear icon in the bottom-left corner of the page to access the **Admin** page. Then, click :guilabel:`+ Create Property`."
msgstr ""
@ -5608,11 +5888,11 @@ msgstr ""
msgid "Measurement ID in Google Analytics."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:84
#: ../../content/applications/websites/website/reporting/analytics.rst:104
msgid "Complete the next steps: `property creation <https://support.google.com/analytics/answer/9304153?hl=en/&visit_id=638278591144564289-3612494643&rd=2#property>`_, business details, and business objectives."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:86
#: ../../content/applications/websites/website/reporting/analytics.rst:106
msgid "When you reach the **Data collection** step, choose the :guilabel:`Web` platform."
msgstr ""
@ -5620,23 +5900,23 @@ msgstr ""
msgid "Choose a platform for your Google Analytics property."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:91
#: ../../content/applications/websites/website/reporting/analytics.rst:111
msgid "Set up your data stream: Specify your :guilabel:`Website URL` and a :guilabel:`Stream name`, then click :guilabel:`Create stream`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:93
#: ../../content/applications/websites/website/reporting/analytics.rst:113
msgid "Copy the :guilabel:`Measurement ID`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:99
#: ../../content/applications/websites/website/reporting/analytics.rst:119
msgid "In the :guilabel:`SEO` section, enable :guilabel:`Google Analytics`, then paste the :guilabel:`Measurement ID` and click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:103
#: ../../content/applications/websites/website/reporting/analytics.rst:123
msgid "If you have :doc:`multiple websites <../configuration/multi_website>` with separate domains, it is recommended to create `one property <https://support.google.com/analytics/answer/9304153?hl=en/&visit_id=638278591144564289-3612494643&rd=2#property>`_ per domain. In Odoo, in the **Website settings**, make sure to select the website in the :guilabel:`Settings of Website` field before pasting the :guilabel:`Measurement ID`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:109
#: ../../content/applications/websites/website/reporting/analytics.rst:129
msgid "`Google documentation on setting up Analytics for a website <https://support.google.com/analytics/answer/1008015?hl=en/>`_"
msgstr ""