[I18N] Update translation terms from Transifex

locale/es/LC_MESSAGES/administration.po

@@ -5976,7 +5976,7 @@ msgstr "Fin del soporte"
 
 #: ../../content/administration/maintain/supported_versions.rst:29
 msgid "Odoo saas~16.2"
-msgstr ""
+msgstr "Odoo saas~16.2"
 
 #: ../../content/administration/maintain/supported_versions.rst:29
 #: ../../content/administration/maintain/supported_versions.rst:31
@@ -6003,11 +6003,11 @@ msgstr "N/A"
 
 #: ../../content/administration/maintain/supported_versions.rst:29
 msgid "March 2023"
-msgstr ""
+msgstr "Marzo de 2023"
 
 #: ../../content/administration/maintain/supported_versions.rst:29
 msgid "June 2023 (planned)"
-msgstr ""
+msgstr "Junio de 2023 (previsto)"
 
 #: ../../content/administration/maintain/supported_versions.rst:31
 msgid "Odoo saas~16.1"
@@ -6019,7 +6019,7 @@ msgstr "Febrero de 2023"
 
 #: ../../content/administration/maintain/supported_versions.rst:31
 msgid "April 2023"
-msgstr ""
+msgstr "Abril de 2023"
 
 #: ../../content/administration/maintain/supported_versions.rst:33
 msgid "**Odoo 16.0**"

locale/es/LC_MESSAGES/general.po

@@ -11,14 +11,12 @@
 # Julián Andrés Osorio López <mcjulian1107@gmail.com>, 2022
 # Lina Maria Avendaño Carvajal <lina8823@gmail.com>, 2022
 # Fairuoz Hussein Naranjo <l92hunaf@gmail.com>, 2022
+# jabelchi, 2022
 # Lucia Pacheco <lpo@odoo.com>, 2022
 # Marian Cuadra, 2022
 # Jesús Alan Ramos Rodríguez <alan.ramos@jarsa.com.mx>, 2022
-# Raquel Iciarte <ric@odoo.com>, 2022
-# jabelchi, 2022
 # marcescu, 2022
 # Patricia Gutiérrez Capetillo <pagc@odoo.com>, 2022
-# Pedro M. Baeza <pedro.baeza@tecnativa.com>, 2023
 # Nelson Ramírez <info@konos.cl>, 2023
 # Martin Trigaux, 2023
 # Pablo Rojas <rojaspablo88@gmail.com>, 2023
@@ -29,7 +27,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:53+0000\n"
 "Last-Translator: Braulio D. López Vázquez <bdl@odoo.com>, 2023\n"
 "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
@@ -435,11 +433,10 @@ msgstr ""
 " momento."
 
 #: ../../content/applications/general/auth/azure.rst:9
-msgid ":doc:`/applications/general/calendars/outlook/outlook_calendar`"
+msgid ":doc:`../../productivity/calendar/outlook`"
 msgstr ""
 
 #: ../../content/applications/general/auth/azure.rst:10
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:67
 msgid ":doc:`/administration/maintain/azure_oauth`"
 msgstr ":doc:`/administration/maintain/azure_oauth`"
@@ -466,12 +463,10 @@ msgstr ""
 "empleados de su empresa se conecten a Odoo con sus cuentas de Google"
 
 #: ../../content/applications/general/auth/google.rst:12
-msgid ""
+msgid ":doc:`../../productivity/calendar/google`"
-":doc:`/applications/general/calendars/google/google_calendar_credentials`"
 msgstr ""
 
 #: ../../content/applications/general/auth/google.rst:13
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:66
 msgid ":doc:`/administration/maintain/google_oauth`"
 msgstr ":doc:`/administration/maintain/google_oauth`"
@@ -757,499 +752,6 @@ msgstr ""
 "creados. Si se deja en blanco, el perfil de administrador se utilizará como "
 "plantilla."
 
-#: ../../content/applications/general/calendars.rst:5
-msgid "Calendars"
-msgstr "Calendarios"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:3
-msgid "Synchronize Google Calendar with Odoo"
-msgstr "Sincronice su calendario de Google con Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5
-msgid ""
-"Synchronize Google Calendar with Odoo to see and manage meetings from both "
-"platforms (updates go in both directions). This integration helps organize "
-"your schedule so you never miss a meeting."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9
-msgid ":doc:`/applications/general/auth/google`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:13
-msgid "Setup in Google"
-msgstr "Configuración en Google"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:16
-msgid "Enable Google Calendar API"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18
-msgid ""
-"Begin by creating a new Google API project and enabling the Google Calendar "
-"API. Then, go to the `Google API Console "
-"<https://console.developers.google.com>`_ and log into your Google account."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22
-msgid ""
-"If this is your first time visiting this page, Google will prompt you to "
-"enter a country and agree to the Terms of Service. Select a country from the"
-" drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:26
-msgid ""
-"Next, click :guilabel:`Select a project` and select or create an API project"
-" to store credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Create a new API project to store credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:33
-msgid ""
-"Give the API Project a clear name like \"Odoo Sync\" so you can easily find "
-"it."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
-msgid ""
-"Then, open the API Project and click :guilabel:`Enable APIs and Services`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable APIs and Services on the API Project."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:41
-msgid ""
-"After that, search for *Google Calendar API* using the search bar and select"
-" :guilabel:`Google Calendar API` from the search results. Click "
-":guilabel:`Enable`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable the Google Calendar API."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:49
-msgid "Create credentials"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51
-msgid ""
-"Now that you have created your API project and enabled the Google Calendar "
-"API, you need to create credentials. Begin by clicking :guilabel:`Create "
-"Credentials`. Google will then guide you through four steps to create your "
-"API credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
-msgid ""
-"In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google"
-" Calendar API` and :guilabel:`User Data` options. Then, click "
-":guilabel:`Next`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Select Google Calendar API and User Data for the Credential Type."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:62
-msgid ""
-"In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the "
-":guilabel:`App name` field, select your email address for the "
-":guilabel:`User support email` field, and type your email address for the "
-":guilabel:`Developer contact information` section. Then, click "
-":guilabel:`Save and Continue`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
-msgid ""
-"Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and "
-"Continue`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
-msgid ""
-"In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website "
-"application` for the :guilabel:`Application Type` field and type *My Odoo "
-"Database* for the :guilabel:`Name`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:72
-msgid ""
-"Under the :guilabel:`Authorized JavaScript Origins` section, click "
-":guilabel:`+ Add URI` and type your company's Odoo URL address."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
-msgid ""
-"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ "
-"Add URI` and type your company's Odoo URL address followed by "
-"*/google_account/authentication*. Finally, click :guilabel:`Create` and "
-":guilabel:`Done`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Add the authorized JavaScript origins and the authorized redirect URIs."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83
-msgid ""
-"After successfully creating a new API project, enabling the Google Calendar "
-"API, and generating the Google Calendar API credentials, you should now have"
-" a Client ID and Client Secret."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:87
-msgid "Client ID & Client Secret"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
-msgid ""
-"The **Client ID** and the **Client Secret** are both needed to connect "
-"Google Calendar to Odoo. Find the Client ID and the Client Secret by opening"
-" the Google Cloud Platform navigation menu and going to :menuselection:`API "
-"& Services --> Credentials --> OAuth 2.0 Client IDs`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:93
-msgid ""
-"Next, locate the credentials you just created for the Google Calendar API. "
-"Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page "
-"will redirect to the edit page, where you can view the Client ID and the "
-"Client Secret."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Click Edit OAuth Client to view the credential details."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:102
-msgid "Setup in Odoo"
-msgstr "Configuración en Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:104
-msgid ""
-"Once the Client ID and the Client Secret are located, open the Odoo database"
-" and go to :menuselection:`Settings --> General Settings --> Integrations "
-"--> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "The Google Calendar checkbox in General Settings."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
-msgid ""
-"Next, copy and paste the Client ID and the Client Secret from the Google "
-"Calendar API Credentials page into their respective fields below the "
-":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:116
-msgid ""
-"Finally, open the Calendar module in Odoo and click on the "
-":guilabel:`Google` sync button to sync Google Calendar with Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Click the Google sync button in Odoo Calendar to sync Google Calendar with "
-"Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:124
-msgid ""
-"The first time you sync your Google Calendar with Odoo, the page will "
-"redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` "
-"to authorize Odoo to access Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Give Odoo permission to access Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:131
-msgid "Now, Odoo Calendar is successfully synced with Google Calendar!"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Successfully sync between Odoo and Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
-msgid "Synchronize Outlook Calendar with Odoo"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5
-msgid ""
-"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping "
-"track of their tasks and appointments across all related applications."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9
-msgid ":doc:`/applications/general/auth/azure`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:13
-msgid "Register the application with Microsoft Azure"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:15
-msgid ""
-"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account"
-" is needed. Creating an account is free for users who have never tried or "
-"paid for Azure. For more information, `click here "
-"<https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:19
-msgid ""
-"Refer to `Microsoft's documentation <https://docs.microsoft.com/en-"
-"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to"
-" set up an Azure AD Tenant (also called an *environment*), which is a "
-"representation of an organization to manage and register apps."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:23
-msgid ""
-"Then, `Register an Application <https://docs.microsoft.com/en-"
-"us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the "
-"appropriate :guilabel:`Supported account type`. Users who wish to connect "
-"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any "
-"organizational directory (Any Azure AD directory - Multitenant) and personal"
-" Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported "
-"account types`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:29
-msgid ""
-"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and "
-"copy the Odoo database URI (URL) followed by "
-"`/microsoft_account/authentication`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:33
-msgid ""
-"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` "
-"for the :guilabel:`Redirect URI`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid ""
-"The \"Supported account type\" and \"Redirect URI\" settings in the "
-"Microsoft Azure AD portal."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:40
-msgid ""
-"For more information on the restrictions and limitations of URIs, `check "
-"this page <https://docs. microsoft.com/en-us/azure/active-"
-"directory/develop/reply-url>`_."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:43
-msgid ""
-"Regarding the application credentials, the user *must* add a client secret, "
-"which allows Odoo to authenticate itself, requiring no interaction from the "
-"user's side. :guilabel:`Certificates` are optional."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:47
-msgid ""
-"To do add a client secret, click :guilabel:`Add a certificate or secret` and"
-" then click :guilabel:`New client secret`. Next, type a "
-":guilabel:`Description` and select when the client secret "
-":guilabel:`Expires`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:51
-msgid ""
-"Since resetting the synchronization can be tricky, Odoo recommends setting "
-"the maximum allowed expiration date for the client secret (24 months), so "
-"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to "
-"generate the client secret (:guilabel:`Secret ID`)."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:56
-msgid "Configuration in Odoo"
-msgstr "Configuración en Odoo"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:58
-msgid ""
-"In the Odoo database, go to :menuselection:`Settings --> General Settings "
-"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook Calendar\" setting activated in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:65
-msgid ""
-"From the Microsoft Azure portal, under the :guilabel:`Overview` section of "
-"the application, copy the :guilabel:`Application (Client) ID`, and paste it "
-"into the :guilabel:`Client ID` field in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client ID\" in the Microsoft Azure portal."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:72
-msgid ""
-"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` "
-"section, copy the :guilabel:`Client Secret Value` and paste it into the "
-":guilabel:`Client Secret` field in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:79
-msgid ""
-"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, "
-"click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:84
-msgid "Sync with Outlook"
-msgstr "Sincronizar con Odoo"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:88
-msgid ""
-"Odoo highly recommends testing the Outlook calendar synchronization on a "
-"test database and a test email address (that is not used for any other "
-"purpose) before attempting to sync the desired Outlook Calendar with the "
-"user's production database."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:92
-msgid ""
-"If the user has any past, present, or future events on their Odoo calendar "
-"before syncing their Outlook calendar, Outlook will treat the events pulled "
-"from Odoo's calendar during the sync as new events, causing an email "
-"notification to be sent from Outlook to all the event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:96
-msgid ""
-"To avoid unwanted emails being sent to all past, present, and future event "
-"attendees, the user must add the events from the Odoo calendar to the "
-"Outlook calendar before the first ever sync, delete the events from Odoo, "
-"and then start the sync."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:100
-msgid ""
-"Even after synchronizing the Odoo Calendar with the Outlook calendar, "
-"Outlook will still send a notification to all event participants every time "
-"an event is edited (created, deleted, unarchived, or event date/time "
-"changed), with no exceptions. This is a limitation that cannot be fixed from"
-" Odoo's side."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:105
-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/general/calendars/outlook/outlook_calendar.rst:112
-msgid ""
-"In summary, once a user synchronizes their Outlook calendar with the Odoo "
-"calendar:"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:114
-msgid ""
-"Creating an event in Odoo causes Outlook to send an invitation to all event "
-"attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:115
-msgid ""
-"Deleting an event in Odoo causes Outlook to send a cancellation to all event"
-" attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:116
-msgid ""
-"Unarchiving an event in Odoo causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:117
-msgid ""
-"Archiving an event in Odoo causes Outlook to send a cancellation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:118
-msgid ""
-"Adding a contact to an event causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:119
-msgid ""
-"Removing a contact from an event causes Outlook to send a cancellation to "
-"all event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:122
-msgid "Sync Odoo Calendar and Outlook"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:124
-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 ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook\" sync button in Odoo Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:132
-msgid ""
-"The synchronization is a two-way process, meaning that events are reconciled"
-" in both accounts (Outlook and Odoo)."
-msgstr ""
-"La sincronización es un proceso de dos lados, esto significa que los eventos"
-" se concilian en ambas cuentas (Outlook y Odoo)."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:136
-msgid ""
-"All users that want to use the synchronization simply need to :ref:`sync "
-"their calendar with Outlook <outlook_calendar/sync_with_outlook>`. The "
-"configuration of Microsoft's Azure account is only done once, as Azure AD "
-"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/general/calendars/outlook/outlook_calendar.rst:143
-msgid ":doc:`../../../productivity/mail_plugins/outlook`"
-msgstr ":doc:`../../../productivity/mail_plugins/outlook`"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:144
-msgid ":doc:`../google/google_calendar_credentials`"
-msgstr ":doc:`../google/google_calendar_credentials`"
-
 #: ../../content/applications/general/developer_mode.rst:5
 msgid "Developer Mode (debug mode)"
 msgstr "Modo de desarrollador (modo depuración)"
@@ -2099,23 +1601,23 @@ msgstr ""
 
 #: ../../content/applications/general/email_communication/email_domain.rst:160
 msgid "pct"
-msgstr ""
+msgstr "pct"
 
 #: ../../content/applications/general/email_communication/email_domain.rst:161
 msgid "Percentage of messages subjected to filtering"
-msgstr ""
+msgstr "Porcentaje de mensajes que se someten a filtrado"
 
 #: ../../content/applications/general/email_communication/email_domain.rst:162
 msgid "`pct=20`"
-msgstr ""
+msgstr "`pct=20`"
 
 #: ../../content/applications/general/email_communication/email_domain.rst:163
 msgid "ruf"
-msgstr ""
+msgstr "ruf"
 
 #: ../../content/applications/general/email_communication/email_domain.rst:164
 msgid "Reporting URI for forensic reports"
-msgstr ""
+msgstr "Reportar un URI para reportes forenses "
 
 #: ../../content/applications/general/email_communication/email_domain.rst:165
 msgid "`ruf=mailto:authfail@example.com`"
@@ -4890,20 +4392,26 @@ msgid ""
 "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 ""
+"Después de elegir qué desea medir, puede definir cómo se deben :ref:`agrupar"
+" <search/group>` los datos, según la dimensión que desea analizar. De forma "
+"predeterminada, los datos se agrupan por *Fecha > Mes*, lo cual se utiliza "
+"para analizar la evolución de las medidas a lo largo de los meses."
 
 #: ../../content/applications/general/reporting.rst:65
 msgid ""
 "When you filter a single time period, the option to compare it against "
 "another one appears."
 msgstr ""
+"Cuando filtra un único periodo de tiempo, se habilita la opción de "
+"compararlo con otro."
 
 #: ../../content/applications/general/reporting.rst:0
 msgid "Using the comparison option"
-msgstr ""
+msgstr "Usar la opción de comparación"
 
 #: ../../content/applications/general/reporting.rst:75
 msgid "Select measures"
-msgstr ""
+msgstr "Seleccionar medidas"
 
 #: ../../content/applications/general/reporting.rst:77
 msgid ""
@@ -4911,28 +4419,33 @@ msgid ""
 ":guilabel:`Count` measures to the Sales Analysis report. By default, the "
 ":guilabel:`Untaxed Amount` measure is selected."
 msgstr ""
+"Entre otras medidas, puede agregar las medidas de :guilabel:`margen` y "
+":guilabel:`conteo` al reporte de análisis de ventas. De forma "
+"predeterminada, se selecciona la medida :guilabel:`importe sin impuestos`."
 
 #: ../../content/applications/general/reporting.rst:0
 msgid "Selecting different measures on the Sales Analysis report"
-msgstr ""
+msgstr "Selección de distintas medidas en el reporte de análisis de ventas"
 
 #: ../../content/applications/general/reporting.rst:85
 msgid "Group measures"
-msgstr ""
+msgstr "Agrupar medidas"
 
 #: ../../content/applications/general/reporting.rst:87
 msgid ""
 "You could group the measures by :guilabel:`Product Category` at the level of"
 " rows on the previous Sales Analysis report example."
 msgstr ""
+"Puede agrupar las medidas por :guilabel:`categoría de producto` en el nivel "
+"de filas del ejemplo anterior de reporte de análisis de ventas."
 
 #: ../../content/applications/general/reporting.rst:0
 msgid "Adding a group on the Sales Analysis report"
-msgstr ""
+msgstr "Agregar un grupo en el reporte de análisis de ventas"
 
 #: ../../content/applications/general/reporting.rst:97
 msgid "Using the pivot view"
-msgstr ""
+msgstr "Utilizar la vista de tabla dinámica"
 
 #: ../../content/applications/general/reporting.rst:99
 msgid ""
@@ -4944,12 +4457,22 @@ msgid ""
 " one of the **preconfigured groups**. To remove one, click the minus button "
 "(:guilabel:`➖`)."
 msgstr ""
+"Agrupar datos es esencial para la vista de tabla dinámica. Le permite "
+"desglosar los datos para obtener información más detallada. Aunque puede "
+"usar la opción :guilabel:`agrupar por` para agregar con rapidez un grupo en "
+"el nivel de las filas, como se muestra en el ejemplo anterior, también puede"
+" hacer clic en el botón con el signo de más (:guilabel:`➕`) a lado del "
+"encabezado de :guilabel:`total` en el nivel de las filas *y* columnas, y "
+"luego seleccionar uno de los **grupos preconfigurados**. Para eliminar uno, "
+"haga clic en el botón con el signo de menos (:guilabel:`➖`)."
 
 #: ../../content/applications/general/reporting.rst:105
 msgid ""
 "Once you have added a group, you can add new ones on the opposite axis or "
 "the newly created subgroups."
 msgstr ""
+"Una vez que agregue un grupo, puede agregar nuevos en el eje opuesto o en "
+"los subgrupos recién creados."
 
 #: ../../content/applications/general/reporting.rst:109
 msgid ""
@@ -4958,36 +4481,46 @@ msgid ""
 "the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / "
 "Office Furniture` product category."
 msgstr ""
+"Puede dividir aún más las medidas en el ejemplo anterior de reporte de "
+"análisis de ventas mediante el grupo :guilabel:`vendedor` en el nivel de "
+"columnas y el grupo :guilabel:`Fecha de orden > Mes` en la categoría de "
+"producto :guilabel:`Todos / Se pueden vender / Muebles de oficina`."
 
 #: ../../content/applications/general/reporting.rst:0
 msgid "Adding multiple groups on the Sales Analysis report"
-msgstr ""
+msgstr "Agregar varios grupos en un reporte de análisis de ventas"
 
 #: ../../content/applications/general/reporting.rst:118
 msgid ""
 "Switch the rows and columns' groups by clicking the flip axis button "
 "(:guilabel:`⇄`)."
 msgstr ""
+"Puede cambiar los grupos de las filas y columnas al hacer clic en el botón "
+"\"cambiar eje\" (:guilabel:`⇄`)."
 
 #: ../../content/applications/general/reporting.rst:119
 msgid ""
 "Click on a measure's label to sort the values by ascending (⏶) or descending"
 " (⏷) order."
 msgstr ""
+"Puede hacer clic en la etiqueta de una medida para ordenar los valores en "
+"orden ascendente (⏶) o descendente (⏷)."
 
 #: ../../content/applications/general/reporting.rst:120
 msgid ""
 "Download a `.xlsx` version of the pivot by clicking the download button "
 "(:guilabel:`⭳`)."
 msgstr ""
+"Puede descargar una versión `.xlsx` de la tabla dinámica al hacer clic en el"
+" botón de descarga (:guilabel:`⭳`)."
 
 #: ../../content/applications/general/reporting.rst:125
 msgid "Using the graph view"
-msgstr ""
+msgstr "Utilizar la vista de gráfico"
 
 #: ../../content/applications/general/reporting.rst:127
 msgid "Three graphs are available, the bar, line, and pie charts."
-msgstr ""
+msgstr "Hay tres gráficos disponibles: de barras, de líneas y circular."
 
 #: ../../content/applications/general/reporting.rst:129
 msgid ""
@@ -4995,30 +4528,38 @@ msgid ""
 "categories. They are especially useful as they can deal with larger data "
 "sets."
 msgstr ""
+"Los **gráficos de barras** se utilizan para mostrar la distribución o una "
+"comparación de varias categorías. Son especialmente útiles porque pueden "
+"trabajar con conjuntos grandes de datos."
 
 #: ../../content/applications/general/reporting.rst:132
 msgid ""
 "**Line charts** are useful to show changing time series and trends over "
 "time."
 msgstr ""
+"Los **gráficos de líneas** son útiles para mostrar los cambios en series "
+"temporales y tendencias a lo largo del tiempo."
 
 #: ../../content/applications/general/reporting.rst:134
 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 ""
+"Los **gráficos circulares** se utilizan para mostrar la distribución o "
+"comparación de un pequeño número de categorías cuando son parte de un "
+"conjunto significativo."
 
 #: ../../content/applications/general/reporting.rst:139
 msgid "Bar chart"
-msgstr ""
+msgstr "Gráfico de barras"
 
 #: ../../content/applications/general/reporting.rst:0
 msgid "Viewing the Sales Analysis report as a bar chart"
-msgstr ""
+msgstr "Reporte de análisis de ventas como gráfico de barras"
 
 #: ../../content/applications/general/reporting.rst:145
 msgid "Line chart"
-msgstr ""
+msgstr "Gráfico de líneas"
 
 #: ../../content/applications/general/reporting.rst:0
 msgid "Viewing the Sales Analysis report as a line chart"
@@ -5825,8 +5366,8 @@ msgstr ""
 "**GUARDAR**."
 
 #: ../../content/applications/general/users/language.rst:61
-msgid ":doc:`../../websites/website/publish/translate`"
+msgid ":doc:`../../websites/website/configuration/translate`"
-msgstr ":doc:`../../websites/website/publish/translate`"
+msgstr ""
 
 #: ../../content/applications/general/users/manage_users.rst:3
 msgid "Manage users"
@@ -6072,7 +5613,7 @@ msgstr ""
 
 #: ../../content/applications/general/users/manage_users.rst:136
 msgid "Multi Companies"
-msgstr "Multi-compañía"
+msgstr "Multiempresas"
 
 #: ../../content/applications/general/users/manage_users.rst:138
 msgid ""

locale/es/LC_MESSAGES/marketing.po

@@ -8,8 +8,8 @@
 # Raquel Iciarte <ric@odoo.com>, 2022
 # Lucia Pacheco <lpo@odoo.com>, 2023
 # marcescu, 2023
-# Braulio D. López Vázquez <bdl@odoo.com>, 2023
 # Martin Trigaux, 2023
+# Braulio D. López Vázquez <bdl@odoo.com>, 2023
 # 
 #, fuzzy
 msgid ""
@@ -18,7 +18,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-04-06 08:12+0000\n"
 "PO-Revision-Date: 2022-10-04 12:54+0000\n"
-"Last-Translator: Martin Trigaux, 2023\n"
+"Last-Translator: Braulio D. López Vázquez <bdl@odoo.com>, 2023\n"
 "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -1979,11 +1979,11 @@ msgstr "Marketing por SMS"
 
 #: ../../content/applications/marketing/sms_marketing/essentials.rst:5
 msgid "Essentials"
-msgstr ""
+msgstr "Fundamentos"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:3
 msgid "Mailing lists and blacklists"
-msgstr ""
+msgstr "Listas de correo y listas negras"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:5
 msgid ""
@@ -1993,6 +1993,11 @@ msgid ""
 "company is migrating from another system, and already has a established "
 "audience."
 msgstr ""
+"Crear o importar listas de correo en Odoo es muy útil al organizar  "
+"contenido para grupos específicos de personas que ya comparten una "
+"demografía o intereses similares. Las listas de correo también son una buena"
+" forma de iniciar si una empresa está migrando desde otro sistema y ya tiene"
+" un público establecido."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:10
 msgid ""
@@ -2000,10 +2005,13 @@ msgid ""
 "mailings, helps businesses maintain good customer relations, by giving "
 "recipients the power to control what they are (and aren't) sent."
 msgstr ""
+"Además, brindarle a su público la opción de anular la suscripción a sus "
+"correos ayuda a las empresas a mantener una buena relación con los clientes,"
+" ya que les da el poder de controlar lo que se les envía."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:15
 msgid "Mailing lists"
-msgstr ""
+msgstr "Listas de correo"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:17
 msgid ""
@@ -2011,18 +2019,26 @@ msgid ""
 "called :guilabel:`Mailing Lists`. When clicked, a sub-menu is revealed with "
 "options for :guilabel:`Mailing Lists` and :guilabel:`Mailing List Contacts`."
 msgstr ""
+"En la aplicación :guilabel:`Marketing por SMS` hay una opción en el menú de "
+"la parte superior de la página denominada :guilabel:`listas de correo`. "
+"Hacer clic en ella abre un submenú con las opciones :guilabel:`listas de "
+"correo` y :guilabel:`contactos de la lista de correo`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:21
 msgid ""
 "Click :menuselection:`Mailing Lists --> Mailing Lists` to see an overview of"
 " all mailing lists in the database."
 msgstr ""
+"Haga clic en :menuselection:`Listas de correo --> Listas de correo` para ver"
+" un resumen de todas las listas de correo en la base de datos."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1
 msgid ""
 "View of the main SMS mailing list page on the Odoo SMS Marketing "
 "application."
 msgstr ""
+"Vista de la página principal de lista de correo de SMS en la aplicación "
+"Marketing por SMS de Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:28
 msgid ""
@@ -2030,6 +2046,8 @@ msgid ""
 ":guilabel:`Mailing Lists` page, and proceed to modify it in a number of "
 "ways."
 msgstr ""
+"Para editar una lista existente, seleccione la lista deseada en la página de"
+" :guilabel:`listas de correo` y modifíquela de varias formas."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:31
 msgid ""
@@ -2037,10 +2055,15 @@ msgid ""
 "corner of the :guilabel:`Mailing Lists` page. Doing so, will reveal a blank "
 "mailing list template form."
 msgstr ""
+"Para crear una nueva lista de correo, haga clic en :guilabel:`crear` en la "
+"esquina superior izquierda de la página de :guilabel:`listas de correo`. "
+"Hacer esto abre un formulario de plantilla de lista de correo en blanco."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1
 msgid "View of the mailing list pop-up window in Odoo SMS Marketing."
 msgstr ""
+"Vista de la ventana emergente de lista de coreo en la aplicación Marketing "
+"por SMS de Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:38
 msgid ""
@@ -2049,12 +2072,19 @@ msgid ""
 "recipients on the :guilabel:`Subscription Management page`. Doing so allows "
 "users to update their subscription preferences at any time."
 msgstr ""
+"Primero, elija el nombre de la :guilabel:`lista de correo` y active la "
+"opción :guilabel:`es público` para que los destinatarios puedan acceder a la"
+" lista de correo en la :guilabel:`página de gestión de suscripción`. Hacer "
+"esto permite a los usuarios actualizar sus preferencias de suscripción en "
+"cualquier momento."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:43
 msgid ""
 "Checking the :guilabel:`Is Public` box is not required, but is recommended "
 "to maintain good customer relations."
 msgstr ""
+"No es necesario seleccionar la casilla :guilabel:`es público`, pero es "
+"recomendable para mantener una buena relación con sus clientes."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:46
 msgid ""
@@ -2062,6 +2092,9 @@ msgid ""
 "form. Then on the main :guilabel:`Mailing Lists` dashboard, the new mailing "
 "list that was just created will be accessible."
 msgstr ""
+"Cuando complete esos campos, haga clic en :guilabel:`crear` para finalizar "
+"el formulario. Después, podrá acceder a la nueva lista de correo que acaba "
+"de crear en el tablero principal de :guilabel:`listas de correo`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:49
 msgid ""
@@ -2069,6 +2102,9 @@ msgid ""
 "the main :guilabel:`Mailing Lists` page to reveal the mailing list detail "
 "form."
 msgstr ""
+"Para editar o personalizar más la lista de correo, seleccionela de la página"
+" principal de :guilabel:`listas de correo` para abrir el formulario "
+"detallado."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:52
 msgid ""
@@ -2076,31 +2112,45 @@ msgid ""
 "smart buttons displaying statistics for different metrics related to the "
 "mailing list (e.g. :guilabel:`Recipients`, :guilabel:`Mailings`, etc.)."
 msgstr ""
+"En la parte superior del formulario detallado de la lista de correo hay "
+"varios botones inteligentes de estadísticas analíticas para distintas "
+"métricas relacionadas con la lista de correo (por ejemplo, "
+":guilabel:`destinatarios`, :guilabel:`correos`, etc.)."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:56
 msgid ""
 "To review or edit any of those elements, click the desired smart button to "
 "reveal a separate page with in-depth data associated with the mailing list."
 msgstr ""
+"Para revisar o editar cualquiera de esos elementos, haga clic en el botón "
+"inteligente que desee para abrir una página separada con datos detallados de"
+" la lista de correo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:59
 msgid ""
 "To make changes to the mailing list itself, click the :guilabel:`Edit` "
 "button in the upper-left corner of the mailing list detail form."
 msgstr ""
+"Para hacer cambios a la lista de correo, haga clic en el botón "
+":guilabel:`editar` en la esquina superior izquierda del formulario detallado"
+" de lista de correo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1
 msgid "View of the mailing list template form in Odoo SMS Marketing."
 msgstr ""
+"Vista del formulario de la plantilla de lista de correo en la aplicación "
+"Marketing por SMS de Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:67
 msgid ""
 "Don't forget to hit the :guilabel:`Save` button once changes have been made."
 msgstr ""
+"No olvide hacer clic en el botón :guilabel:`guardar` una vez que haya hecho "
+"los cambios."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:70
 msgid "Mailing lists contacts"
-msgstr ""
+msgstr "Contactos de las listas de correo"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:72
 msgid ""
@@ -2109,12 +2159,18 @@ msgid ""
 "dashboard with with all the contacts associated with one or more of the "
 "configured mailing lists in the database."
 msgstr ""
+"Para acceder a la información de los contactos de una o más listas de "
+"correo, vaya a :menuselection:`Listas de correo --> Contactos de la lista de"
+" correo` para abrir un tablero con todos los contactos vinculados con una o "
+"más de las listas de correo configuradas en la base de datos."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1
 msgid ""
 "View of the mailing lists contact page in the Odoo SMS Marketing "
 "application."
 msgstr ""
+"Vista de la página de contactos de las listas de correo en la aplicación "
+"Marketing por SMS de Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:81
 msgid ""
@@ -2123,10 +2179,14 @@ msgid ""
 "only showing contact information for recipients who still want to receive "
 "communications and mailings."
 msgstr ""
+"De forma predeterminada, Odoo abre la página de :guilabel:`contactos de las "
+"listas de correo` con el filtro :guilabel:`excluir teléfono en la lista "
+"negra` en la barra de búsqueda. Por lo tanto, solo se muestra la información"
+" de contacto de los destinatarios que aún desean recibir correos."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:86
 msgid "Communication history in the Chatter"
-msgstr ""
+msgstr "Historial de comunicación en el chatter"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:88
 msgid ""
@@ -2134,6 +2194,9 @@ msgid ""
 "*chatter* section, located beneath a recipient's contact form (in the "
 "*Contacts* application)."
 msgstr ""
+"En la sección *chatter* de cada destinatario se lleva el registro de todos "
+"los correos que se le enviaron, se ubica debajo del formulario de contacto "
+"del destinatario (en la aplicación *Contactos*)."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:91
 msgid ""
@@ -2141,6 +2204,9 @@ msgid ""
 "communications, and see a history of interactions with contacts and "
 "prospects."
 msgstr ""
+"Los usuarios de la base de datos pueden consultar el chatter para llevar un "
+"mejor seguimiento de la comunicación y ver un historial de las interacciones"
+" con contactos y prospectos."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:94
 msgid ""
@@ -2148,10 +2214,13 @@ msgid ""
 "which :abbr:`SMS (Short Message Service)` mailing promotions a certain "
 "customer has received (or not received)."
 msgstr ""
+"Por ejemplo, un representante de ventas puede usar el chatter para encontrar"
+" con rapidez qué promociones de :abbr:`SMS (servicio de mensajes cortos, por"
+" sus siglas en inglés)` un determinado cliente ha recibido o no."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1
 msgid "View of what the chatter looks like in the Odoo Contacts app."
-msgstr ""
+msgstr "Vista de cómo se ve el chatter en la aplicación Contactos de Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:102
 msgid "Blacklist"
@@ -2163,6 +2232,9 @@ msgid ""
 "recipients with the power to add their phone number to a list of people who "
 "no longer want to receieve communications or mailings."
 msgstr ""
+"La aplicación *Marketing por SMS* de Odoo tiene una función :guilabel:`lista"
+" negra` que permite a los destinatarios agregar su número de teléfono a una "
+"lista de personas que ya no quieren recibir correos."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:108
 msgid ""
@@ -2171,6 +2243,11 @@ msgid ""
 "their :guilabel:`Subscription Management` page. Customers can also be added "
 "manually to the blacklist, if necessary."
 msgstr ""
+"También se conoce como el proceso de anular suscripción: se agregará a los "
+"clientes a una *lista negra* de forma automática si hacen clic en "
+":guilabel:`anular suscripción` en su página de :guilabel:`gestión de "
+"suscripción`. También puede agregar clientes a la lista negra de forma "
+"manual si es necesario."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:112
 msgid ""
@@ -2179,10 +2256,14 @@ msgid ""
 "Numbers` to reveal a dashboard containing every blacklisted phone number in "
 "the database."
 msgstr ""
+"Para ver una lista completa de los números en la lista negra vaya a "
+":menuselection:`Marketing por SMS --> Configuración --> Números en la lista "
+"negra` para abrir el tablero que contiene todos los números en la lista "
+"negra en la base de datos."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1
 msgid "SMS Blacklist menu in the application."
-msgstr ""
+msgstr "Menú de lista negra de SMS en la aplicación"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:120
 msgid ""
@@ -2191,6 +2272,11 @@ msgid ""
 " next page's form. There's also a checkbox to indicate whether that "
 "particular phone numnber is :guilabel:`Active` (or not)."
 msgstr ""
+"Para agregar de forma manual un número a una lista negra, haga clic en el "
+"botón :guilabel:`crear` en la esquina superior izquierda del tablero e "
+"introduzca el número de teléfono en el formulario de la siguiente página. "
+"También hay una casilla para indicar si ese número de teléfono en particular"
+" está :guilabel:`activo` (o no)."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:128
 msgid ""
@@ -2199,10 +2285,15 @@ msgid ""
 "blacklist, select the desired number on the dashboard, and then, on the "
 "phone number's form, click :guilabel:`Unblacklist`."
 msgstr ""
+"Una vez que complete el formulario, haga clic en :guilabel:`guardar` para "
+"agregarlo a los :guilabel:`números de teléfono en la lista negra`. Para "
+"quitar cualquier número de la lista negra, selecciónelo en el tablero y, en "
+"el formulario del número de teléfono, haga clic en :guilabel:`quitar de la "
+"lista negra`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:133
 msgid "Importing blacklists"
-msgstr ""
+msgstr "Importar listas negras"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:135
 msgid ""
@@ -2211,6 +2302,10 @@ msgid ""
 "already asked to be blacklisted` on :abbr:`SMS (Short Message Service)` "
 "mailings."
 msgstr ""
+"Durante una migración de software o plataforma es posible importar una lista"
+" negra de contactos existente. Esto incluye a los clientes que ya "
+"solicitaron que se les agregara a la lista negra de :abbr:`SMS (servicio de "
+"mensajes cortos, por sus siglas en inglés)`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:139
 msgid ""
@@ -2219,14 +2314,20 @@ msgid ""
 "drop-down menu (beneath the search bar), and click :guilabel:`Import "
 "records`."
 msgstr ""
+"Para hacerlo, vaya a :menuselection:`Marketing por SMS --> Configuración -->"
+" Números de teléfono en la lista negra` y seleccione el menú desplegable "
+":guilabel:`favoritos` (debajo de la barra de búsqueda) y haga clic en "
+":guilabel:`importar registros`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1
 msgid "View of how to import a blacklist in Odoo SMS Marketing."
 msgstr ""
+"Vista de cómo importar una lista negra en la aplicación Marketing por SMS de"
+" Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:3
 msgid "SMS campaign settings"
-msgstr ""
+msgstr "Ajustes de campaña de SMS"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:5
 msgid ""
@@ -2235,16 +2336,23 @@ msgid ""
 " way to remind people about upcoming events, issued invoices, and so much "
 "more."
 msgstr ""
+"Utilizar campañas de :abbr:`SMS (servicio de mensajes cortos, por sus siglas"
+" en inglés)` con la aplicación *Marketing SMS* no solo es una estrategia "
+"publicitaria eficaz, también es una gran forma para recordarle a las "
+"personas sobre sus próximos eventos, facturas emitidas y mucho más."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:9
 msgid ""
 "But, before :abbr:`SMS (Short Message Service)` campaigns can be created "
 "(and sent), a few specific settings and features must be enabled first."
 msgstr ""
+"Pero, antes de crear (y enviar) campañas de :abbr:`SMS (servicio de mensajes"
+" cortos, por sus siglas en inglés)`, se deben habilitar algunos ajustes y "
+"funciones específicas."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:13
 msgid "SMS campaign setting"
-msgstr ""
+msgstr "Ajuste de campaña de SMS"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:15
 msgid ""
@@ -2253,16 +2361,23 @@ msgid ""
 ":menuselection:`Email Marketing --> Configuration --> Settings`, and then "
 "enable :guilabel:`Mailing Campaigns` and :guilabel:`Save` the changes."
 msgstr ""
+"Para habilitar las campañas de :abbr:`SMS (servicio de mensajes cortos, por "
+"sus siglas en inglés)` en Odoo, asegúrese de que la función *campañas de "
+"correo* este activada en :menuselection:`Marketing por correo electrónico "
+"--> Configuración --> Ajustes`, habilite la función :guilabel:`campañas de "
+"correo` y :guilabel:`guarde` los cambios."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1
 msgid "View of the mailing campaigns setting in Odoo."
-msgstr ""
+msgstr "Vista del ajuste \"campañas de correo\" en Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:24
 msgid ""
 "Activating the *Mailing Campaigns* feature in the *General Settings* also "
 "enables the *A/B Test* feature."
 msgstr ""
+"Activar la función *campañas de correo* en los *ajustes generales* también "
+"habilita la función *prueba A/B Test*."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:27
 msgid ""
@@ -2271,10 +2386,16 @@ msgid ""
 "available for use. Similarly, the :guilabel:`A/B Test` tab is now also "
 "available on every :abbr:`SMS (Short Message Service)` template form."
 msgstr ""
+"Una vez que habilite el ajuste, regrese a la aplicación "
+":menuselection:`Marketing por SMS`. Notará que el menú :guilabel:`campañas` "
+"ahora está disponible en el encabezado. De igual forma, la pestaña "
+":guilabel:`prueba A/B` ahora está disponible en todos los formularios de "
+"plantilla de :abbr:`SMS (servicio de mensajes cortos, por sus siglas en "
+"inglés)`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:32
 msgid "A/B tests"
-msgstr ""
+msgstr "Pruebas A/B"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:34
 msgid ""
@@ -2283,6 +2404,11 @@ msgid ""
 "order to compare which version is the most successful in producing "
 "engagement and/or conversion outcomes."
 msgstr ""
+"Las :guilabel:`pruebas A/B` permiten realizar pruebas a cualquier :abbr:`SMS"
+" (servicio de mensajes cortos, por sus siglas en inglés)` frente a otras "
+"versiones en la misma campaña. Esto se hace para comparar qué versión tiene "
+"más éxito en cuanto a producir interacciones y/o los resultados de "
+"conversión."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:38
 msgid ""
@@ -2290,21 +2416,29 @@ msgid ""
 ":guilabel:`A/B Tests` tab, initially, there's only a single checkbox "
 "labeled: :guilabel:`Allow A/B Testing.`"
 msgstr ""
+"En un formulario de plantilla de :abbr:`SMS (servicio de mensajes cortos, "
+"por sus siglas en inglés)`, en la pestaña :guilabel:`prueba A/B`, al "
+"principio, hay una única casilla denominada :guilabel:`permitir pruebas "
+"A/B.`"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:41
 msgid "When clicked, a series of other options appear."
-msgstr ""
+msgstr "Al seleccionarla, aparecen otras opciones."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1
 msgid ""
 "The A/B Test tab is located on an Odoo SMS Marketing app campaign form."
 msgstr ""
+"La pestaña de prueba A/B se ubica en el formulario de campaña en la "
+"aplicación Marketing por SMS de Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:47
 msgid ""
 "In the first field, enter a desired percentage of recipients to conduct the "
 "A/B Test on."
 msgstr ""
+"En el primer campo, introduzca el porcentaje de destinatarios al que desea "
+"aplicar la prueba A/B."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:49
 msgid ""
@@ -2312,6 +2446,10 @@ msgid ""
 " is what Odoo will use to determine the successful result of an A/B Test. In"
 " other words, this tells Odoo how to pick a winning A/B test."
 msgstr ""
+"Debajo del campo \"porcentaje\" se encuentra el campo :guilabel:`selección "
+"del ganador`. Esto es lo que se utilizará para determinar el resultado "
+"exitoso de una prueba A/B. Es decir, esto le dice a Odoo cómo elegir al "
+"ganador de la prueba A/B."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:53
 msgid ""
@@ -2319,6 +2457,9 @@ msgid ""
 " Click Rate`, :guilabel:`Leads`, :guilabel:`Quotations`, or "
 ":guilabel:`Revenues`."
 msgstr ""
+"Las siguientes secciones están disponibles: :guilabel:`manual`, "
+":guilabel:`mayor índice de clics`, :guilabel:`leads`, "
+":guilabel:`cotizaciones` o :guilabel:`ingresos`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:56
 msgid ""
@@ -2327,22 +2468,30 @@ msgid ""
 "variation. Then, Odoo sends that winning mailing variation to the remaining "
 "recipients, who weren't involved in the test, at that prior date and time."
 msgstr ""
+"Por último tenemos el campo :guilabel:`enviar final en`. Representa la fecha"
+" y hora que Odoo utiliza como fecha límite para determinar la variación de "
+"correo ganadora. Luego, Odoo envía esa variación ganadora a los demás "
+"destinatarios que no formaron parte de la prueba."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:62
 msgid ""
 "Quickly create different versions of the mailing to add to the A/B Test by "
 "clicking the :guilabel:`Create an Alternate Version` button."
 msgstr ""
+"Cree con rapidez distintas versiones del correo para agregar a la prueba A/B"
+" al hacer clic en el botón :guilabel:`crear una versión alterna`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:66
 msgid ""
 "Remember, the winning mailing variation is based on the criteria selected in"
 " the :guilabel:`Winner Selection` field."
 msgstr ""
+"Recuerde que la variación de correo ganadora se basa en los criterios que "
+"seleccionó en el campo :guilabel:`selección del ganador`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:70
 msgid "Campaigns page"
-msgstr ""
+msgstr "Página de campañas"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:72
 msgid ""
@@ -2352,16 +2501,24 @@ msgid ""
 "related to the mailings associated with that campaign (e.g. number of "
 "emails, social posts, SMSs, and push notifications)."
 msgstr ""
+"Para crear, editar o analizar cualquier campaña, haga clic en "
+":menuselection:`campañas` en el menú del encabezado de la aplicación "
+":guilabel:`Marketing por SMS`. En la página de :guilabel:`campañas`, cada "
+"campaña muestra información relacionada con los correos vinculados a esa "
+"campaña (por ejemplo, el número de correos electrónicos, publicaciones en "
+"redes sociales, mensajes de SMS y notificaciones push)."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1
 msgid ""
 "Dasbhoard view of different Campaigns in the Odoo SMS Marketing app, "
 "separated by stage."
 msgstr ""
+"Tablero donde se ven distintas campañas en la aplicación Marketing por SMS "
+"de Odoo, separadas por etapa."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:82
 msgid "Campaign templates"
-msgstr ""
+msgstr "Plantillas de campaña"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:84
 msgid ""
@@ -2370,10 +2527,16 @@ msgid ""
 "made campaign in order to duplicate, review, or edit its campaign template "
 "form."
 msgstr ""
+"Haga clic en :guilabel:`crear` para crear una nueva campaña. Odoo abrirá un "
+"formulario de plantilla de campaña en blanco para que lo complete. Por otro "
+"lado, seleccione cualquier campaña creada previamente para duplicarla, "
+"revisarla o editar su formulario de plantilla de campaña."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1
 msgid "View of an SMS campaign template in Odoo SMS marketing."
 msgstr ""
+"Vista de una plantilla de campaña de SMS en la aplicación Marketing por SMS "
+"de Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:92
 msgid ""
@@ -2381,6 +2544,10 @@ msgid ""
 ":guilabel:`Send SMS`, :guilabel:`Send Social Post`, and :guilabel:`Push "
 "Notifications` are available above the template form."
 msgstr ""
+"En cada campaña, las opciones para :guilabel:`enviar nuevo correo`, "
+":guilabel:`enviar SMS`, :guilabel:`enviar publicación de redes sociales` y "
+":guilabel:`notificaciones push` están disponibles en el formulario de la "
+"plantilla."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:96
 msgid ""
@@ -2389,6 +2556,10 @@ msgid ""
 "of messages can be reviewed or edited, along with various data sets related "
 "to each specific mailing."
 msgstr ""
+"Cuando se agrega a la campaña una de esas opciones de comunicación, Odoo "
+"creará una nueva pestaña correspondiente en el formulario de la plantilla, "
+"en donde se pueden revisar o editar esos tipos de mensaje, junto con varios "
+"conjuntos de datos relacionados con cada correo específico."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:100
 msgid ""
@@ -2397,6 +2568,11 @@ msgid ""
 " :guilabel:`Engagement`, :guilabel:`Opportunities`, etc.) on a separate "
 "page."
 msgstr ""
+"En la parte superior de la plantilla se encuentran varios botones "
+"analíticos. Cuando se hace clic en ellos, Odoo abre las métricas detalladas "
+"relacionadas con ese tema específico (por ejemplo, "
+":guilabel:`interacciones`, :guilabel:`oportunidades`, etc.) en una página "
+"separada."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:104
 msgid ""
@@ -2404,16 +2580,22 @@ msgid ""
 ":guilabel:`Responsible`. Odoo also allows for various :guilabel:`Tags` to be"
 " added, as well (if necessary)."
 msgstr ""
+"Debajo de los botones inteligentes se encuentran los campos "
+":guilabel:`nombre de la campaña` y :guilabel:`responsable`. Odoo también "
+"permite agregar varias :guilabel:`etiquetas` (si es necesario)."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:108
 msgid "Sending SMSs through the Contacts app"
-msgstr ""
+msgstr "Enviar SMS mediante la aplicación Contactos"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:110
 msgid ""
 "Sending :abbr:`SMS (Short Message Service)` mailings directly through a "
 "contact's form is available by default."
 msgstr ""
+"Puede enviar :abbr:`SMS (servicio de mensajes cortos, por sus siglas en "
+"inglés)` directamente a través del formulario de contacto de forma "
+"predeterminada."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:113
 msgid ""
@@ -2422,11 +2604,18 @@ msgid ""
 " the database, and click on the :guilabel:`SMS` icon on the contact form "
 "(next to the :guilabel:`Phone Number` field)."
 msgstr ""
+"Para enviar un :abbr:`SMS (servicio de mensajes cortos, por sus siglas en "
+"inglés)` de esta forma, vaya a la aplicación :menuselection:`Contactos`, "
+"seleccione el contacto deseado en la base de datos y haga clic en el icono "
+":guilabel:`SMS` en el formulario de contacto (a lado del campo "
+":guilabel:`número de teléfono`)."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1
 msgid ""
 "The SMS icon is located on an individual's contact form in Odoo Contacts."
 msgstr ""
+"El icono de SMS se ubica en el formulario de contacto de un individuo en la "
+"aplicación Contactos de Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:121
 msgid ""
@@ -2435,15 +2624,22 @@ msgid ""
 "View`, and select all the desired contacts to whom the message should be "
 "sent. Then, under :guilabel:`Action`, select :guilabel:`Send SMS`."
 msgstr ""
+"Para enviar un mensaje a varios contactos a la vez, vaya al tablero "
+"principal de la aplicación :menuselection:`Contactos`, elija la "
+":guilabel:`vista de lista` y seleccione todos los contactos a los que desea "
+"enviar el mensaje. Luego, en :guilabel:`acción`, selecione :guilabel:`enviar"
+" SMS`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1
 msgid ""
 "Select a number of contacts, click action, and select send multiple SMSs."
 msgstr ""
+"Seleccione un número de contactos, haga clic en acción y seleccione \"enviar"
+" varios SMS\"."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:130
 msgid "Set up SMS templates for future use"
-msgstr ""
+msgstr "Configurar plantillas de SMS para usos posteriores"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:132
 msgid ""
@@ -2453,6 +2649,12 @@ msgid ""
 "app`. Then, scroll down to the :guilabel:`Developer Tools` section, and "
 "click :guilabel:`Activate the Developer Mode`."
 msgstr ""
+"Para configurar :guilabel:`plantillas de SMS` para usar en el futuro, active"
+" el :ref:`modo de desarrollador <developer-mode>`. Para hacerlo, vaya al "
+"tablero principal de Odoo y seleccione la aplicación "
+":menuselection:`Ajustes`. Luego, baje a la sección :guilabel:`herramientas "
+"de desarrollador` y haga clic en :guilabel:`activar el modo de "
+"desarrollador`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:137
 msgid ""
@@ -2461,6 +2663,10 @@ msgid ""
 "of the dashboard; this bug icon indicates that developer mode is currently "
 "active."
 msgstr ""
+"Una vez que active el *modo de desarrollador*, volverá al tablero principal "
+"de Odoo, y ahora aparecerá un icono de bug, el cual se ubica en la esquina "
+"superior derecha del tablero. Este icono de bug indica que el modo de "
+"desarrollador está activo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:141
 msgid ""
@@ -2469,12 +2675,19 @@ msgid ""
 " to begin setting up :abbr:`SMS (Short Message Service)` templates for "
 "future marketing campaigns."
 msgstr ""
+"A continuación, regrese a la aplicación :menuselection:`Ajustes` y, en los "
+"menús que ahora aparecen en la parte superior seleccione "
+":menuselection:`Técnico --> Plantillas SMS` para empezar a configurar las "
+"plantillas de :abbr:`SMS (servicio de mensajes cortos, por sus siglas en "
+"inglés)` para futuras campañas de marketing."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1
 msgid ""
 "Select the SMS Template option in the Technical dropdown on the Settings "
 "app."
 msgstr ""
+"Seleccione la opción \"plantilla de SMS\" en el menú desplegable técnico en "
+"la aplicación Ajustes."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:149
 msgid ""
@@ -2483,22 +2696,30 @@ msgid ""
 ":guilabel:`List` view showcases each template's name, and to which "
 "recipients it applies."
 msgstr ""
+"En el tablero de :guilabel:`plantillas de SMS`, Odoo abre una página entera "
+"de plantillas de :abbr:`SMS (servicio de mensajes cortos, por sus siglas en "
+"inglés)`. La vista de :guilabel:`lista` predetermina muestra el nombre de "
+"cada plantilla y a qué destinatarios se aplica."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:153
 msgid ""
 "On this page, :abbr:`SMS (Short Message Service)` templates can be edited or"
 " created from scratch."
 msgstr ""
+"En esta página puede editar o crear desde cero plantillas de :abbr:`SMS "
+"(servicio de mensajes cortos, por sus siglas en inglés)`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1
 msgid ""
 "The SMS Templates page in Odoo is available after enabling developer mode in the General\n"
 "Settings"
 msgstr ""
+"La página de plantillas de SMS en Odoo está disponible después de habilitar en el modo de desarrollador en los ajustes\n"
+"generales."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:3
 msgid "SMS essentials"
-msgstr ""
+msgstr "Fundamentos de SMS"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:5
 msgid ""
@@ -2506,6 +2727,11 @@ msgid ""
 "strategies can help companies expand their market reach, especially in some "
 "countries, where emails might not be very common, or even used at all."
 msgstr ""
+"Utilizar la divulgación por :abbr:`SMS (servicio de mensajes cortos, por sus"
+" siglas en inglés)` en las estrategias de comunicación puede ayudar a las "
+"empresas a expandir su alcance en el mercado, especialmente en algunos "
+"países donde el correo electrónico puede no ser muy común, o incluso no "
+"utilizarse en absoluto."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:9
 msgid ""
@@ -2515,10 +2741,15 @@ msgid ""
 "yield higher :abbr:`CTOR (click-to-open rate)` and :abbr:`CTR (click-through"
 " rate)` outcomes."
 msgstr ""
+"La aplicación *Marketing por SMS* también puede ayudar a aumentar las tasas "
+"de conversión en torno a acciones valiosas, como el registro a eventos, "
+"pruebas gratis, compras, etc., ya que los canales de marketing basados en "
+"texto y móvil suelen tener mejores resultados de :abbr:`CTOR (tasa de clics "
+"abiertos)` y :abbr:`CTR (tasa de clics)`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:15
 msgid "SMS marketing dashboard"
-msgstr ""
+msgstr "Tablero de Marketing por SMS"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:17
 msgid ""
@@ -2527,6 +2758,10 @@ msgid ""
 "been created, along with pertinent information and data related to that "
 "specific message."
 msgstr ""
+"Cuando se abre la aplicación, Odoo muestra el tablero principal de "
+":guilabel:`Marketing por SMS`, el cual muestra los diversos envíos de SMS "
+"que se han creado, junto con la información pertinente y los datos "
+"relacionados con ese mensaje en específico."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:21
 msgid ""
@@ -2534,6 +2769,9 @@ msgid ""
 " opened, which provides an organized display of the SMS mailings that have "
 "been created, and what their current status is at the moment."
 msgstr ""
+"La vista de :guilabel:`kanban` es la que Odoo utiliza de forma "
+"predeterminada cuando se abre la aplicación, muestra una visualización "
+"organizada de los SMS que se han creado y cuál es su estado actual."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:26
 msgid ""
@@ -2541,6 +2779,9 @@ msgid ""
 " statuses: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, or "
 ":guilabel:`Sent`."
 msgstr ""
+"Un :abbr:`SMS (servicio de mensajes cortos, por sus siglas en inglés)` puede"
+" tener alguno de los siguientes estados: :guilabel:`borrador`, :guilabel:`en"
+" cola`, :guilabel:`enviando` o :guilabel:`enviado`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:29
 msgid ""
@@ -2548,12 +2789,18 @@ msgid ""
 "there are a few different view options to choose from. Each one provides a "
 "unique take on the same SMS information."
 msgstr ""
+"En la esquina superior derecha del tablero principal de :guilabel:`Marketing"
+" por SMS` hay varias opciones de vista entre las que elegir. Cada una de "
+"ellas ofrece una visión única de la misma información del SMS."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:32
 msgid ""
 "The :guilabel:`List` view provides the same useful data related to SMS "
 "mailings, but in a more traditional list layout."
 msgstr ""
+"La vista de :guilabel:`lista` proporciona los mismos datos útiles "
+"relacionados con el envío de SMS, pero en un diseño de lista más "
+"tradicional."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:35
 msgid ""
@@ -2562,6 +2809,11 @@ msgid ""
 "date is clicked, Odoo reveals a blank SMS template that, when completed, "
 "will be scheduled to be sent on that specific future date."
 msgstr ""
+"La vista de :guilabel:`calendario` proporciona un calendario simple, lo que "
+"facilita ver cuándo se enviarán los SMS (o cuando se enviaron). Si se hace "
+"clic en una fecha futura, Odoo abre una plantilla de SMS en blanco que, una "
+"vez completada, se programará para enviarse en esa fecha específica en el "
+"futuro."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:39
 msgid ""
@@ -2569,10 +2821,14 @@ msgid ""
 "series of graphs and charts. Odoo also provides various ways to sort and "
 "group the data for more detailed analysis."
 msgstr ""
+"Por último, la vista de :guilabel:`gráfico` muestra los mismos datos "
+"relacionados con SMS en series de gráficos y diagramas. Odoo también "
+"proporciona varias formas de ordenar y agrupar los datos para un análisis "
+"más detallado."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:43
 msgid "Create SMS messages"
-msgstr ""
+msgstr "Crear mensajes de SMS"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:45
 msgid ""
@@ -2580,16 +2836,21 @@ msgid ""
 "dashboard, and Odoo reveals a blank SMS template form, which can be "
 "configured in a number of different ways."
 msgstr ""
+"Para empezar, haga clic en :guilabel:`crear` en el tablero principal de "
+":guilabel:`Marketing por SMS`, Odoo abrirá un formulario de plantilla de SMS"
+" en blanco, el cual se puede configurar de distintas formas."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1
 msgid "Creating an SMS marketing template."
-msgstr ""
+msgstr "Creación de una plantilla de Marketing por SMS."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:52
 msgid ""
 "First, give the mailing a :guilabel:`Subject`, which describes what the "
 "mailing is about."
 msgstr ""
+"Primero, agregue un :guilabel:`asunto` para el envío, el cual describe de "
+"qué trata."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:54
 msgid ""
@@ -2600,6 +2861,13 @@ msgid ""
 "send this :abbr:`SMS (Short Message Service)` to in the :guilabel:`Select "
 "Mailing List` field."
 msgstr ""
+"A continuación, en el campo :guilabel:`destinatarios`, elija a quién se le "
+"enviará este :abbr:`SMS (servicio de mensajes cortos, por sus siglas en "
+"inglés)`. De forma predeterminada, Odoo selecciona :guilabel:`lista de "
+"correo`. Si esta es la opción deseada en el campo :guilabel:`destinatarios`,"
+" especifique a qué lista de correo Odoo debe enviar este :abbr:`SMS "
+"(servicio de mensajes cortos, por sus siglas en inglés)` en el campo "
+":guilabel:`seleccionar lista de correo`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:60
 msgid ""
@@ -2608,22 +2876,33 @@ msgid ""
 "along with various types of data related to that specific list (e.g. number "
 "of contacts, mailings, recipients, etc.)."
 msgstr ""
+"Para crear (o editar) una lista de correo, vaya a :menuselection:`Listas de "
+"correo --> Lista de correo`. Ahí, Odoo muestra todas las listas de correo "
+"que se crearon previamente, junto con varios tipos de datos relacionados con"
+" esa lista específica (por ejemplo, número de contactos, envíos, "
+"destinatarios, etc.)."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:64
 msgid ""
 "To learn more about mailing lists and contacts, check out "
 ":doc:`mailing_lists_blacklists`"
 msgstr ""
+"Para saber más sobre listas de correo y contactos consulte "
+":doc:`mailing_lists_blacklists`"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1
 msgid "View of the mailing list page in the SMS marketing application."
 msgstr ""
+"Vista de la página de listas de correo en la aplicación de Marketing por "
+"SMS."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:71
 msgid ""
 "To reveal all the possible options in the :guilabel:`Recipients` field, "
 "click the field to see all the choices Odoo makes avaialble."
 msgstr ""
+"Para abrir todas las posibles opciones en el campo :guilabel:`destinatarios`"
+" haga clic en el campo para ver todas las opciones disponibles en Odoo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:74
 msgid ""
@@ -2633,6 +2912,12 @@ msgid ""
 "can be customized to fit any business need), or, if no default recipient "
 "filter equation is present, an :guilabel:`Add Filter` button will appear."
 msgstr ""
+"Cuando se selecciona otro campo (que no sea :guilabel:`lista de correo`), "
+"aparece la opción de especificar aún más ese campo elegido, ya sea con una "
+"ecuación de filtro de destinatario predeterminada que aparece de forma "
+"automática (la cual se puede personalizar para satisfacer cualquier "
+"necesidad empresarial) o, si no hay una ecuación de filtro de destinatario "
+"predeterminada, aparecerá un botón :guilabel:`agregar filtro`."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:79
 msgid ""
@@ -2640,6 +2925,10 @@ msgid ""
 "domain rule fields, which can be configured similar to an equation. You can "
 "create multiple recipient rules, if necessary."
 msgstr ""
+"Hacer clic en el botón :guilabel:`agregar filtro` agrega campos de reglas de"
+" dominio totalmente personalizables, las cuales se pueden configurar de "
+"forma similar a una ecuación. Puede crear varias reglas de destinatario si "
+"es necesario."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:82
 msgid ""
@@ -2647,6 +2936,9 @@ msgid ""
 "recipients who fit into whatever criteria is configured in those fields. "
 "Multiple rules can be added."
 msgstr ""
+"Odoo solo enviará el :abbr:`SMS (servicio de mensajes cortos, por sus siglas"
+" en inglés)` a destinatarios que cumplan con los criterios configurados en "
+"esos campos. Se pueden agregar varias reglas."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:86
 msgid ""
@@ -2655,6 +2947,11 @@ msgid ""
 "Message Service)`, by default — unless more specific recipient rules are "
 "entered."
 msgstr ""
+"Si se elige :guilabel:`contacto`, todos los registros de *contacto* en la "
+"base de datos de Odoo (proveedores, clientes, etc.) recibirán el :abbr:`SMS "
+"(servicio de mensajes cortos, por sus siglas en inglés)` de forma "
+"predeterminada, a menos que se introduzcan reglas de destinatarios más "
+"específicas."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:90
 msgid ""
@@ -2663,14 +2960,19 @@ msgid ""
 "Name` equals `United States`), and they haven't blacklisted themselves from "
 "any mailings (e.g. `Blacklist` > `is` > `not set`)."
 msgstr ""
+"Por ejemplo, el siguiente mensaje solo se enviará a los contactos de la base"
+" de datos que se ubican en los Estados Unidos (por ejemplo, `País` > `Nombre"
+" del país` es igual a `Estados Unidos`) y que no se hayan agregado a una "
+"lista negra de correo (por ejemplo, `Lista negra` > `es` > `no "
+"establecido`)."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:0
 msgid "Contact recipients on SMS marketing."
-msgstr ""
+msgstr "Contactos destinatarios en la aplicación Marketing por SMS."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:99
 msgid "Writing SMS messages"
-msgstr ""
+msgstr "Escribir mensajes de SMS"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:101
 msgid ""
@@ -2680,16 +2982,25 @@ msgid ""
 "used in the message, along with how many :abbr:`SMS (Short Message Service)`"
 " mailings it will take to deliver the complete message."
 msgstr ""
+"Introduzca el contenido del :abbr:`SMS (servicio de mensajes cortos, por sus"
+" siglas en inglés)` en el campo de texto de la pestaña :guilabel:`contenido "
+"del SMS`. Puede incluir enlaces y emojis. Odoo muestra debajo del texto "
+"cuántos caracteres se utilizan en el mensaje, junto con cuántos envíos de "
+":abbr:`SMS (servicio de mensajes cortos, por sus siglas en inglés)` se "
+"necesitarán para entregar el mensaje completo."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:107
 msgid ""
 "To check the price of sending an :abbr:`SMS (Short Message Service)` for a "
 "country, click on the :guilabel:`Information` icon."
 msgstr ""
+"Haga clic en el icono :guilabel:`información` para revisar el precio de "
+"enviar un :abbr:`SMS (servicio de mensajes cortos, por sus siglas en "
+"inglés)` para un país."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1
 msgid "SMS price check icon."
-msgstr ""
+msgstr "Icono para revisar precios de SMS."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:115
 msgid ""
@@ -2697,14 +3008,19 @@ msgid ""
 "Marketing* app; :abbr:`SMS (Short Message Service)` messages will not be "
 "sent without credits."
 msgstr ""
+"Debe comprar créditos en Odoo para aprovechar al máximo la aplicación "
+"*Marketing por SMS*, los mensajes de :abbr:`SMS (servicio de mensajes "
+"cortos, por sus siglas en inglés)` no se enviarán si no tiene créditos."
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:119
 msgid "`Odoo SMS - FAQ <https://iap-services.odoo.com/iap/sms/pricing>`_"
 msgstr ""
+"`SMS en Odoo - Preguntas frecuentes <https://iap-"
+"services.odoo.com/iap/sms/pricing>`_"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:122
 msgid "Track links used in SMS messages"
-msgstr ""
+msgstr "Rastrear los enlaces que se utilizan en mensajes de SMS"
 
 #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:124
 msgid ""

locale/es/LC_MESSAGES/services.po

@@ -9,7 +9,6 @@
 # marcescu, 2022
 # Jesse Garza <jga@odoo.com>, 2022
 # Alejandro Kutulas <alk@odoo.com>, 2022
-# Pedro M. Baeza <pedro.baeza@tecnativa.com>, 2022
 # Lucia Pacheco <lpo@odoo.com>, 2022
 # Martin Trigaux, 2023
 # Braulio D. López Vázquez <bdl@odoo.com>, 2023
@@ -19,7 +18,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:54+0000\n"
 "Last-Translator: Braulio D. López Vázquez <bdl@odoo.com>, 2023\n"
 "Language-Team: Spanish (https://app.transifex.com/odoo/teams/41243/es/)\n"
@@ -377,80 +376,215 @@ msgstr ""
 "programs-640?fullscreen=1>`_"
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
-msgid "Allow customers to close their tickets"
+msgid "Closing tickets"
-msgstr "Permitir a los clientes cerrar sus tickets"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
 msgid ""
-"Allowing customers to close their own tickets gives them autonomy and "
+"Once work has been completed on a *Helpdesk* ticket in Odoo, there are "
-"minimizes misunderstandings around when an issue is considered solved or "
+"several ways it can be closed. Manually closing solved tickets keeps the "
-"not. This results in operational capacity for support teams, and higher "
+"pipeline up to date, while automatically closing inactive tickets prevents "
-"satisfaction for the customer."
+"unnecessary blocking issues. Allowing customers to close their own tickets "
-msgstr ""
+"minimizes confusion around whether an issue is considered solved or not. "
-
+"This results in increased operational capacity for support teams, and higher"
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:10
+" customer satisfaction."
-msgid "Enable ticket closing"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12
+msgid "Manually close solved tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
 msgid ""
-"Start by navigating to :menuselection:`Helpdesk --> Configuration --> "
+"As work on a ticket progresses, it is moved along to the next stage in the "
-"Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit`"
+"pipeline. Once the issue is solved, the ticket is moved to a *folded* stage."
-" and enable :guilabel:`Ticket closing` by checking the field box."
+" This marks the ticket as *closed*."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17
+msgid ""
+"To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and "
+"click on a team to open the pipeline. Hover over a stage's heading, and then"
+" click the gear icon that appears in the top-right corner of that stage's "
+"kanban column."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid "Ticket closing feature in Odoo Helpdesk."
+msgid ""
+"View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage"
+" option."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:19
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
 msgid ""
-"To designate which stage the ticket migrates to once it is closed, navigate "
+"Clicking the gear icon also displays the option to :guilabel:`Fold` the "
-"to the ticket pipeline by going to :menuselection:`Helpdesk --> Overview` "
+"stage. This setting folds the stage *temporarily* to simplify the kanban "
-"and clicking :guilabel:`Tickets` on the team's card."
+"view. This does *not* close the tickets in this stage. It also does not "
+"permanently fold the stage. If a stage needs to be folded so the tickets can"
+" be marked as closed, continue following the steps below."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:23
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
 msgid ""
-"There are two options: create a new Kanban stage or work with an existing "
+"From the menu that appears, select :guilabel:`Edit Stage`. This will open "
-"one. For both scenarios, click the :guilabel:`Settings (gear)` icon next to "
+"the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` "
-"the stage name, select :guilabel:`Edit Stage`, and enable :guilabel:`Closing"
+"towards the top of the window, and then :guilabel:`Save & Close` to confirm "
-" Stage`. After checking the field box, click :guilabel:`Save` to finish."
+"the changes. Now, tickets that reach this stage will be considered as "
+"*closed*."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:29
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
-msgid ""
+msgid "Stage settings page."
-"If a closing stage is not specified, by default, the ticket is moved to the "
-"last stage in the kanban. If more than one stage is set as a closing stage, "
-"the ticket is placed in the first closing stage column."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:33
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41
+msgid "Automatically close inactive tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43
 msgid ""
-"With the ticket closing settings now complete, customers can now view the "
+"Tickets that are inactive for a set period of time can be automatically "
-"option to :guilabel:`Close this ticket` when they log into their portal."
+"closed. At that point, they will be moved to a folded stage."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46
+msgid ""
+"Go to the team's settings page by going to :menuselection:`Helpdesk --> "
+"Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable"
+" :guilabel:`Automatic Closing`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
+msgid ""
+"If one of the team's stages is set to be folded in the kanban view, it will "
+"be the default selection in the :guilabel:`Move to Stage` field. If the team"
+" has more than one folded stage, the stage that occurs first in the pipeline"
+" will be the default. If no stage is folded, the default selection will be "
+"the last stage in the pipeline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54
+msgid ""
+"The :guilabel:`After days of inactivity` field defaults to `7`, but can be "
+"adjusted if necessary."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57
+msgid ""
+"The :guilabel:`After days of inactivity` field does **not** take the working"
+" calendar into account when tracking the amount of time a ticket has been "
+"inactive."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60
+msgid ""
+"If only certain stages should be used to track days of inactivity, they can "
+"be added to the :guilabel:`In Stages` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64
+msgid "A team's pipeline is created with the following stages:"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66
+msgid "`New`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67
+msgid "`In Progress`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68
+msgid "`Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69
+msgid "`Closed`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71
+msgid ""
+"Tickets can linger in the :guilabel:`Customer Feedback stage`, because once "
+"an issue is solved, customers may not respond immediately. At that point, "
+"the tickets can be closed automatically. However, tickets in the "
+":guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due "
+"to assignment or workload issues. Closing these tickets automatically would "
+"result in issues going unsolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
+msgid ""
+"Therefore, the :guilabel:`Automatic Closing` settings would be configured as"
+" below\\:\\"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
+msgid ":guilabel:`Automatic Closing`: *checked*"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
+msgid ":guilabel:`Move to Stage`: `Solved`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
+msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
+msgid ":guilabel:`In Stages`: `Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
+msgid "Example of Automatic Closing settings."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89
+msgid "Allow customers to close their own tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
+msgid ""
+"Enabling the :guilabel:`Closure by Customers` setting allows customers to "
+"close their own ticket(s) when they determine that their issue has been "
+"resolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94
+msgid ""
+"Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams`"
+" and select a team. On the team's settings page, scroll to the "
+":guilabel:`Self-Service` section and check the box for :guilabel:`Closure by"
+" Customers`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
+msgid "Customer closing setting in Odoo Helpdesk."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
+msgid ""
+"Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` "
+"button will be available for customers when they view their ticket through "
+"the customer portal."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
 msgid "Customer view of ticket closing in Odoo Helpdesk."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:40
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110
-msgid "Get reports on tickets closed by customers"
+msgid ""
+"Customers are able to view their tickets by clicking the :guilabel:`View the"
+" ticket` link they receive by email. The link is included in the "
+":guilabel:`Request Acknowledgment` template, which is added to the first "
+"stage of a team by default. This link does not require a customer to have "
+"access to the portal to view or respond to their ticket."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:42
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
 msgid ""
-"To analyze the tickets that have been closed by customers, go to "
+"Customers with access to the portal will be able to view their tickets under"
-":menuselection:`Helpdesk --> Reporting --> Tickets`. Then, click on the "
+" :menuselection:`My Account --> Tickets`."
-":guilabel:`Filters` menu and choose :guilabel:`Add Custom filter`. Next, set"
-" the custom filter parameters to :guilabel:`Closed by partner` and "
-":guilabel:`is true`. Finally, click :guilabel:`Apply`."
-msgstr ""
-
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid ""
-"Filter for tickets closed by customers on Odoo Helpdesk's reporting page."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview.rst:5
@@ -883,6 +1017,9 @@ msgid ""
 "Check the :guilabel:`Folded in Kanban` box on the :guilabel:`Stages` form to"
 " display this stage as *folded* by default in the kanban view for this team."
 msgstr ""
+"Marque la casilla :guilabel:`plegado en kanban` en el formulario de "
+":guilabel:`etapas` para visualizar esta etapa como *plegada* de forma "
+"predeterminada en la vista de kanban de este equipo."
 
 #: ../../content/applications/services/helpdesk/overview/getting_started.rst:156
 msgid ""
@@ -891,18 +1028,26 @@ msgid ""
 "issues. This setting should only be enabled for stages that are considered "
 "*closing* stages."
 msgstr ""
+"Los tickets que llegan a una etapa *plegada* se consideran cerrados. Cerrar "
+"un ticket antes de completar el trabajo puede resultar en problemas de "
+"reportes y comunicación. Este ajuste solo se debe habilitar para etapas que "
+"se consideran *de cierre*"
 
 #: ../../content/applications/services/helpdesk/overview/getting_started.rst:160
 msgid ""
 "Alternatively, stages can be temporarily folded in the kanban view, by "
 "clicking on the settings icon and selecting :guilabel:`Fold`."
 msgstr ""
+"También puede plegar etapas de forma temporal en la vista de kanban, haga "
+"clic en el icono de ajustes y seleccione :guilabel:`plegar`."
 
 #: ../../content/applications/services/helpdesk/overview/getting_started.rst:164
 msgid ""
 "Manually folding a stage from the kanban view will not close the tickets in "
 "the stage."
 msgstr ""
+"Plegar manualmente una etapa en la vista de kanban no cerrará los tickets de"
+" dicha etapa."
 
 #: ../../content/applications/services/helpdesk/overview/ratings.rst:3
 msgid "Ratings"
@@ -1008,7 +1153,6 @@ msgstr ""
 "en la aplicación Servicio de asistencia de Odoo"
 
 #: ../../content/applications/services/helpdesk/overview/ratings.rst:51
-#: ../../content/applications/services/helpdesk/overview/sla.rst:47
 msgid ":doc:`../advanced/close_tickets`"
 msgstr ":doc:`../advanced/close_tickets`"
 
@@ -1076,7 +1220,7 @@ msgid ""
 "The *Email Alias* setting automatically creates tickets from messages sent "
 "to that team's specified email alias."
 msgstr ""
-"La opción *correo electrónico* crea tickets de forma automática a paritr de "
+"La opción *correo electrónico* crea tickets de forma automática a partir de "
 "mensajes que se envían al seudónimo de correo electrónico del equipo."
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:29
@@ -1340,13 +1484,13 @@ msgid ""
 "The *Live Chat* feature allows website visitors to connect directly with a "
 "support agent or chatbot. During these conversations, *Helpdesk* tickets can"
 " be instantly created by using the :doc:`response command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk`."
+"</applications/websites/livechat/responses>` `/helpdesk`."
 msgstr ""
 "La función *chat en vivo* permite a los visitantes del sitio web contactar "
 "directamente a un agente de soporte o a un bot de chat. En estas "
-"conversaciones, puede crear tickets de *servicio de asistencia* de forma "
+"conversaciones se pueden crear tickets de *Servicio de asistencia* de forma "
-"instanánea mediante el :doc:`response comando "
+"instantánea mediante el :doc:`comando de respuesta "
-"</applications/websites/livechat/overview/responses>` `/helpdesk`."
+"</applications/websites/livechat/responses>` `/helpdesk`."
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125
 msgid ""
@@ -1710,15 +1854,14 @@ msgstr ""
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261
 msgid ""
 "During the conversation, an operator can use the shortcut :doc:`command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk` to create "
+"</applications/websites/livechat/responses>` `/helpdesk` to create a ticket "
-"a ticket without leaving the chat window. The transcript from the "
+"without leaving the chat window. The transcript from the conversation will "
-"conversation will be added to the new ticket, under the "
+"be added to the new ticket, under the :guilabel:`Description` tab."
-":guilabel:`Description` tab."
 msgstr ""
 "Durante la conversación, el operador puede utilizar el :doc:`comando "
-"</applications/websites/livechat/overview/responses>` de atajo `/helpdesk` "
+"</applications/websites/livechat/responses>` de atajo `/helpdesk` para crear"
-"para crear un ticket sin abandonar la ventana de chat. La transcripción de "
+" un ticket sin abandonar la ventana de chat. La transcripción de la "
-"la conversación se agregará al nuevo ticket, en la pestaña "
+"conversación se agregará al nuevo ticket, en la pestaña "
 ":guilabel:`descripción`."
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267
@@ -1791,8 +1934,8 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
 msgstr ":doc:`/applications/general/email_communication/email_servers`"
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293
-msgid ":doc:`/applications/websites/livechat/overview/get_started`"
+msgid ":doc:`/applications/websites/livechat`"
-msgstr ":doc:`/applications/websites/livechat/overview/get_started`"
+msgstr ":doc:`/applications/websites/livechat`"
 
 #: ../../content/applications/services/helpdesk/overview/reports.rst:3
 msgid "Reports for a Better Support"
@@ -1937,103 +2080,402 @@ msgstr "Acuerdos de nivel de servicio (SLA)"
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:5
 msgid ""
-"Service Level Agreements (SLA) are commitments you make with your customers "
+"A Service Level Agreement (SLA) defines the level of service a customer can "
-"to outline how a service is delivered. It bolsters trust between you and "
+"expect from a supplier. SLAs provide a timeline that tells customers when "
-"your customers as it makes clear what needs to be done, to what standard, "
+"they can expect results, and keeps the support team on target."
-"and when."
 msgstr ""
-"Los Acuerdos de nivel de servicio (SLA, por sus siglas en inglés) son "
+"Un acuerdo de nivel de servicio (SLA, por sus siglas en inglés) define el "
-"compromisos que hace con sus clientes para describir cómo se presta un "
+"nivel de servicio que un cliente puede esperar de un proveedor. Los SLA "
-"servicio. Refuerza la confianza entre usted y sus clientes, ya que aclara lo"
+"brindan una línea de tiempo que indica a los clientes cuándo pueden esperar "
-" que hay que hacer, con qué estándar y cuándo."
+"resultados, y ayudan al equipo de soporte a alcanzar sus objetivos."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:10
-msgid "Create your policies"
+msgid "Create a new SLA policy"
-msgstr "Crear sus políticas"
+msgstr "Crear una nueva política de SLA"
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:13
+#: ../../content/applications/services/helpdesk/overview/sla.rst:12
 msgid ""
-"First, enable the feature on the settings of the team you would like "
+"To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to "
-"policies to be applied, going to :menuselection:`Helpdesk --> Configuration "
+"the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`."
-"--> Helpdesk Teams`."
+" Select a team, scroll to the :guilabel:`Performance` section, and then "
+"check the selection box next to :guilabel:`SLA Policies` to enable it for "
+"that specific team."
 msgstr ""
-"Primero, habilite la función en los ajustes del equipo al que desea aplicar "
+"Para crear una nueva política de :abbr:`SLA (acuerdo de nivel de servicio, "
-"las políticas, vaya a :menuselection:`Servicio de asistencia --> "
+"por sus siglas en inglés)`, vaya a la página del equipo en "
-"Configuración --> Equipos de Servicio de asistencia`."
+":menuselection:`Servicio de asistencia --> Configuración --> Equipos`. "
-
+"Seleccione un equipo, baje a la sección :guilabel:`rendimiento` y seleccione"
-#: ../../content/applications/services/helpdesk/overview/sla.rst:15
+" la casilla a lado de :guilabel:`políticas SLA` para habilitarlas para ese "
-msgid ""
+"equipo en específico."
-"Create your policies through the team’s settings page or go to "
-":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
-msgstr ""
-"Cree sus políticas en la página de ajustes del equipo o vaya a "
-":menuselection:`Servicio de asistencia --> Configuración --> Políticas SLA`."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
-msgid "View of an SLA form in Odoo Helpdesk"
+msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
 msgstr ""
-"Vista de un formulario de acuerdo de nivel de servicio en la aplicación "
+"Vista del ajuste \"políticas SLA\" en la página de un equipo en la "
-"Servicio de asistencia de Odoo"
+"aplicación Servicio de asistencia"
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:23
+#: ../../content/applications/services/helpdesk/overview/sla.rst:22
 msgid ""
-"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
+"The value indicated next to the :guilabel:`Working Hours` field is used to "
-" a ticket needs to have for the policy to be applied."
+"determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. "
+"By default, this is determined by the value set in the :guilabel:`Company "
+"Working Hours` field under :menuselection:`Settings app --> Employees --> "
+"Work Organization`."
 msgstr ""
-"Elija el **Equipo** para el que la política es relevante y la **Prioridad "
+"El valor que aparece en el campo :guilabel:`horas laborables` se utiliza "
-"mínima** que un ticket necesita tener para que la política se aplique."
+"para determinar la fecha límite de las políticas :abbr:`SLA (acuerdo de "
+"nivel de servicio, por sus siglas en inglés)`. De forma predeterminada, se "
+"determina mediante el valor establecido en el campo :guilabel:`horas "
+"laborables de la empresa` en :menuselection:`Ajustes --> Empleados --> "
+"organización de trabajo`."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:27
 msgid ""
-"**Target** is the stage a ticket needs to reach within the period defined to"
+"To create a new policy, click the smart button on the team`s settings page "
-" satisfy the SLA. The period is based on the ticket’s creation date, and a "
+"or go to :menuselection:`Helpdesk -->  Configuration --> SLA Policies`, and "
-"deadline is set on the ticket’s form once it matches an SLA policy rule. If "
+"click :guilabel:`New`. Start by entering a :guilabel:`Title` and a "
-"a ticket has more than one policy applied to it, the closest deadline of all"
+":guilabel:`Description` for the new policy, and proceed to fill out the form"
-" SLAs is the one considered."
+" using the steps below."
 msgstr ""
-"El **Objetivo** es la etapa a la que el ticket debe llegar en el periodo "
+"Para crear una nueva política, haga clic en el botón inteligente en la "
-"definido para satisfacer el SLA. El periodo se basa en la fecha de creación "
+"página de ajustes del equipo o vaya a :menuselection:`Servicio de asistencia"
-"del ticket, y se establece una fecha límite en el formulario del ticket una "
+" -->  Configuración --> Políticas SLA` y haga clic en :guilabel:`nuevo`. "
-"vez que coincida con una regla de política de SLA. Si más de una política "
+"Agregue un :guilabel:`título` y una :guilabel:`descripción` para la nueva "
-"aplica a un ticket, se elige la fecha límite más cercana de todos los SLA."
+"política y complete el formulario siguiendo los pasos a continuación."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:29
+#: ../../content/applications/services/helpdesk/overview/sla.rst:33
+msgid "Define the criteria for an SLA policy"
+msgstr "Definir los criterios de una política SLA"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:35
 msgid ""
-"When a ticket has satisfied an SLA policy, the SLA tag appears in green and "
+"The :guilabel:`Criteria` section is used to identify what tickets this "
-"the deadline field is not shown anymore."
+"policy will be applied to. Fill out the following fields to adjust the "
+"selection criteria:"
 msgstr ""
-"Cuando un ticket ha satisfecho una política de SLA, la etiqueta SLA aparece "
+"La sección :guilabel:`criterios` se utiliza para identificar a qué tickets "
-"en verde y el campo de la fecha límite ya no se muestra."
+"se aplicará esta política. Complete los siguientes campos para ajustar los "
+"criterios de selección:"
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+#: ../../content/applications/services/helpdesk/overview/sla.rst:38
-msgid "View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk"
+msgid ""
+":guilabel:`Team`: a policy can only be applied to one team. *This field is "
+"required.*"
 msgstr ""
-"Vista de un formulario de ticket con énfasis en un acuerdo de nivel de "
+":guilabel:`Equipo`: la política solo se puede aplicar a un equipo. *Este "
-"servicio cumplido en la aplicación Servicio de asistencia de Odoo"
+"campo es obligatorio*."
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst:37
-msgid "SLA Analysis"
-msgstr "Análisis del SLA"
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:39
 msgid ""
-"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply"
+":guilabel:`Priority`: the priority level for a ticket is identified by "
-" *Filters* and *Group by* to identify tickets that should be prioritized and"
+"selecting the number of stars representing the priority level on the kanban "
-" keep track of upcoming deadlines."
+"card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will "
+"only be applied once the priority level has been updated on the ticket to "
+"match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is"
+" made in this field, this policy will only apply to tickets marked as `Low "
+"Priority` (zero stars)."
 msgstr ""
-"Vaya a :menuselection:`Servicio de asistencia --> Reportes --> Análisis del "
+":guilabel:`Prioridad`: el nivel de prioridad de un ticket se identifica al "
-"estado del SLA`. Aplique *Filtros* y *Agrupar por* para identificar tickets "
+"seleccionar el número de estrellas que representa la prioridad en la tarjeta"
-"que se deben priorizar y llevar el seguimiento de las próximas fechas "
+" de kanban o en el ticket. El :abbr:`SLA (acuerdo de nivel de servicio, por "
-"límite."
+"sus siglas en inglés)` solo se aplicará una vez que se actualice el nivel de"
+" prioridad en el ticket para que coincida con el criterio del :abbr:`SLA "
+"(acuerdo de nivel de servicio)`. Si no se selecciona nada en este campo, "
+"esta política solo se aplicará a los tickets de `baja prioridad` (cero "
+"estrellas)."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:44
+msgid ""
+":guilabel:`Types`: ticket types can be helpful when indicating when a ticket"
+" is a customer question, that can be solved with a quick response, or an "
+"issue, that may require additional investigation. Multiple ticket types can "
+"be selected for this field. If no selection is made, this policy will apply "
+"to all ticket types."
+msgstr ""
+":guilabel:`Tipos`: los tipos de ticket pueden ser útiles para indicar cuando"
+" un ticket es una pregunta de cliente que se puede responder con rapidez, o "
+"un problema que puede necesitar investigación más profunda. Se pueden "
+"seleccionar varios tipos de ticket en este campo. Si no se selecciona nada, "
+"esta política aplica a todos los tipos de ticket."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:48
+msgid ""
+":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is "
+"about. Multiple tags can be applied to a single ticket."
+msgstr ""
+":guilabel:`Etiquetas`: las etiquetas se aplican para indicar brevemente de "
+"qué trata el ticket. Se pueden aplicar varias etiquetas a un solo ticket."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:50
+msgid ""
+":guilabel:`Customers`: individual contacts or companies may be selected in "
+"this field."
+msgstr ""
+":guilabel:`Clientes`: se pueden seleccionar tanto contactos de individuos "
+"como de empresas en este campo."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:51
+msgid ""
+":guilabel:`Sales Order Items`: this field is available only if a team has "
+"the *Timesheets* app enabled. This allows the ticket to tie directly to a "
+"specific line on a sales order, which must be indicated on the ticket in the"
+" :guilabel:`Sales Order Item` field."
+msgstr ""
+":guilabel:`Artículos de la orden de venta`: este campo está disponible solo "
+"si se habilita la aplicación *Hojas de horas* para un equipo. Esto permite "
+"vincular el ticket directamente con una línea específica de una orden de "
+"venta, la cual se debe indicar en el campo :guilabel:`artículo en la orden "
+"de venta` del ticket."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:56
+msgid ""
+"Unless otherwise indicated, multiple selections can be made for each field. "
+"(i.e. multiple :guilabel:`Tags` can be included in a policy, but only one "
+":guilabel:`Priority` level)"
+msgstr ""
+"A menos que se indique lo contrario, se pueden hacer varias selecciones en "
+"cada campo. (Es decir, se pueden incluir varias :guilabel:`etiquetas` en una"
+" política, pero solo un nivel de :guilabel:`prioridad`)."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a blank SLA policy record"
+msgstr "Vista de un registro de política SLA en blanco"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:64
+msgid "Establish a target for an SLA policy"
+msgstr "Establecer un objetivo para una política SLA"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:66
+msgid ""
+"The :guilabel:`Target` is the stage a ticket needs to reach, and the time "
+"alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service "
+"Level Agreement)` policy. Any stage assigned to a team may be selected for "
+"the :guilabel:`Reach Stage` field. Time spent in stages selected in "
+":guilabel:`Excluding Stages` will not be included in the calculation of the "
+":abbr:`SLA (Service Level Agreement)` deadline."
+msgstr ""
+"El :guilabel:`objetivo` es la etapa a la que un ticket debe llegar y el "
+"tiempo asignado para llegar a dicha etapa para satisfacer la política "
+":abbr:`SLA (acuerdo de nivel de servicio)`. En el campo :guilabel:`llegar a "
+"la etapa` se puede seleccionar cualquier etapa asignada a un equipo. El "
+"tiempo dedicado a etapas seleccionadas en el campo :guilabel:`excluir "
+"etapas` no se incluirá en el cálculo de la fecha límite del :abbr:`SLA "
+"(acuerdo de nivel de servicio, por sus siglas en inglés)`."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:73
+msgid ""
+"An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks "
+"the working time before a ticket is completed, and would have `Solved` as "
+"the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level "
+"Agreement)` was titled `2 Days to Start`, it tracks the working time before "
+"work on a ticket has begun, and would have `In Progress` as the "
+":guilabel:`Reach Stage`."
+msgstr ""
+"Un :abbr:`SLA (acuerdo de nivel de servicio, por sus siglas en inglés)` con "
+"el nombre `8 horas para cerrar` lleva el registro del tiempo de trabajo "
+"antes de completar un ticket, y tendría que :guilabel:`llegar a la etapa` "
+"`resuelto`. Sin embargo, si el :abbr:`SLA (acuerdo de nivel de servicio, por"
+" sus siglas en inglés)` se llama `2 días para iniciar`, registra el tiempo "
+"de trabajo antes de empezar a trabajar en un ticket, y tendría que "
+":guilabel:`llegar a la etapa` `en progreso`."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:79
+msgid "Meeting SLA deadlines"
+msgstr "Cumplir con las fechas límites de SLA"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:81
+msgid ""
+"Once it is determined that a ticket fits the criteria of an :abbr:`SLA "
+"(Service Level Agreement)` policy, a deadline is calculated. The deadline is"
+" based on the creation date of the ticket, and the targeted working hours. "
+"The deadline is then added to the ticket, as well as a white tag indicating "
+"the name of the :abbr:`SLA (Service Level Agreement)` applied."
+msgstr ""
+"Una vez que se determina que un ticket cumple con los criterios de una "
+"política :abbr:`SLA (acuerdo de nivel de servicio, por sus siglas en "
+"inglés)`, se calcula una fecha límite. La fecha límite se calcula según la "
+"fecha de creación del ticket y el objetivo de horas de trabajo. La fecha "
+"límite se agrega al ticket, así como una etiqueta blanca que indica el "
+":abbr:`SLA (acuerdo de nivel de servicio, por sus siglas en inglés)` que se "
+"aplica."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
 msgid ""
-"View of the SLA status analysis page emphasizing the group by option in Odoo"
+"View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo"
 " Helpdesk"
 msgstr ""
-"Vista de la página de análisis de estado del acuerdo de nivel de servicio, "
+"Vista de un formulario de ticket que muestra una fecha límite de SLA abierta"
-"con énfasis en la opción de \"Agrupar por\" en la aplicación Servicio de "
+" en un ticket de la aplicación Servicio de asistencia de Odoo"
-"asistencia de Odoo"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:91
+msgid ""
+"If a ticket fits the criteria for more than one :abbr:`SLA (Service Level "
+"Agreement)`, the earliest occurring deadline will be displayed on the "
+"ticket. Once that deadline has passed, the next deadline will be displayed."
+msgstr ""
+"Si un ticket cumple los criterios de más de un :abbr:`SLA (acuerdo de nivel "
+"de servicio, por sus siglas en inglés)`, se mostrará en el ticket la fecha "
+"límite más cercana. Una vez que pase esa fecha límite, se mostrará la "
+"siguiente fecha límite."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:95
+msgid ""
+"Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the"
+" :abbr:`SLA (Service Level Agreement)` tag turns green, and the "
+":guilabel:`Deadline` field disappears from view on the."
+msgstr ""
+"Una vez que un ticket cumpla una política :abbr:`SLA (acuerdo de nivel de "
+"servicio, por sus siglas en inglés)`, la etiquetal del :abbr:`SLA (acuerdo "
+"de nivel de servicio, por sus siglas en inglés)` se vuelve de color verde, y"
+" el campo :guilabel:`fecha límite` desaparece."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk"
+msgstr ""
+"Vista de un formulario de ticket que muestra un SLA cumplido en la "
+"aplicación Servicio de asistencia de Odoo"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:102
+msgid ""
+"If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket "
+"has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level "
+"Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level "
+"Agreement)` has failed, the red tag will stay on the ticket, even after the "
+"ticket is moved to the :guilabel:`Reach Stage`."
+msgstr ""
+"Si se alcanza la fecha límite del :abbr:`SLA (acuerdo de nivel de servicio, "
+"por sus siglas en inglés)` y el ticket no ha pasado a la :guilabel:`etapa "
+"objetivo`, la etiquetal del :abbr:`SLA (acuerdo de nivel de servicio, por "
+"sus siglas en inglés)` se vuelve de color rojo. Una vez que no se cumplió el"
+" :abbr:`SLA (acuerdo de nivel de servicio, por sus siglas en inglés)`, la "
+"etiqueta roja permanecerá en el ticket incluso después de mover el ticket a "
+"la :guilabel:`etapa objetivo`."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid ""
+"View of a ticket's form with a failing and passing SLA in Odoo Helpdesk"
+msgstr ""
+"Vista de un formulario de ticket con un SLA fallido y un cumplido en la "
+"aplicación Servicio de asistencia de Odoo"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:112
+msgid "Analyzing SLA performance"
+msgstr "Analizar el rendimiento del SLA"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:114
+msgid ""
+"The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA "
+"(Service Level Agreement)` is fulfilled, as well as the success rate of "
+"individual policies. Navigate to the report and corresponding pivot table by"
+" going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`."
+msgstr ""
+"El reporte de :guilabel:`análisis del estado del SLA` lleva el registro de "
+"qué tan rápido se cumple un :abbr:`SLA (acuerdo de nivel de servicio, por "
+"sus siglas en inglés)`, así como la tasa de éxito de políticas individuales."
+" Puede acceder al reporte y a la respectiva tabla dinámica en "
+":menuselection:`Servicio de asistencia --> Reportes --> Análisis del estado "
+"del SLA`."
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:120
+msgid "Using the Pivot view"
+msgstr "Utilizar la vista de tabla dinámica"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:122
+msgid ""
+"By default, the report is displayed in a :guilabel:`Pivot` view, and is "
+"filtered to show the number of SLAs failed and the failure rate over the "
+"last 30 days, grouped by team."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:129
+msgid ""
+"To add the number of SLAs passed or in progress, click the "
+":guilabel:`Measures` button to reveal a drop-down menu of reporting "
+"criteria, and choose from the options available based on the measurements "
+"preferred. Whenever a measurement is picked, a check mark will appear in the"
+" drop-down menu to indicate that that measurement is included, and a "
+"corresponding new column will emerge in the pivot table to show the relevant"
+" calculations."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:135
+msgid ""
+"To add a group to a row or column, click the plus :guilabel:` + ` button "
+"next to :guilabel:`Total`, and then select one of the groups. To remove one,"
+" click the minus :guilabel:` - ` button and deselect."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:140
+msgid "Using the Graph view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:142
+msgid ""
+"The :guilabel:`Status Analysis` report can also be viewed as a "
+":guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between "
+"these views by selecting the appropriate icon at the top of the chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:148
+msgid "Bar Chart"
+msgstr "Gráfico de barras"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in bar view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:154
+msgid "Line Chart"
+msgstr "Gráfico de líneas"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in line view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:160
+msgid "Pie Chart"
+msgstr "Gráfico circular"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in pie chart view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:167
+msgid ""
+"Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed "
+":guilabel:`Stacked`. This presents two or more groups to appear on top of "
+"each other instead of next to each other, making it easier to compare data."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:172
+msgid "Using the Cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:174
+msgid ""
+"The :guilabel:`Cohort` view is used to track the changes in data over a "
+"period of time. To display the :guilabel:`Status Analysis` report in a "
+":guilabel:`Cohort` view, click the icon in the top right corner above the "
+"chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:183
+msgid ":ref:`Reporting views <reporting/views>`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:184
+msgid ""
+":doc:`Allow customers to close their tickets "
+"</applications/services/helpdesk/advanced/close_tickets>`"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5
 msgid "Timesheet and Invoice"
@@ -2779,7 +3221,7 @@ msgstr ""
 
 #: ../../content/applications/services/timesheets.rst:8
 msgid "Timesheets"
-msgstr "Partes de horas"
+msgstr "Hojas de horas"
 
 #: ../../content/applications/services/timesheets/overview/time_off.rst:3
 msgid "Create Timesheets upon Time Off Validation"

locale/fr/LC_MESSAGES/general.po

@@ -11,8 +11,8 @@
 # Michell Portrait <mportrait@happylibre.fr>, 2022
 # Vallen Delobel <edv@odoo.com>, 2022
 # Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2022
-# Fernanda Marques <fem@odoo.com>, 2022
 # Renaud de Colombel <rdecolombel@sgen.cfdt.fr>, 2022
+# Fernanda Marques <fem@odoo.com>, 2022
 # Cécile Collart <cco@odoo.com>, 2022
 # Camille Dantinne <cmd@odoo.com>, 2022
 # Alexandra Jubert, 2023
@@ -26,7 +26,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:53+0000\n"
 "Last-Translator: Jolien De Paepe, 2023\n"
 "Language-Team: French (https://app.transifex.com/odoo/teams/41243/fr/)\n"
@@ -441,11 +441,10 @@ msgstr ""
 "avec Odoo pour l'instant."
 
 #: ../../content/applications/general/auth/azure.rst:9
-msgid ":doc:`/applications/general/calendars/outlook/outlook_calendar`"
+msgid ":doc:`../../productivity/calendar/outlook`"
-msgstr ":doc:`/applications/general/calendars/outlook/outlook_calendar`"
+msgstr ":doc:`../../productivity/calendar/outlook`"
 
 #: ../../content/applications/general/auth/azure.rst:10
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:67
 msgid ":doc:`/administration/maintain/azure_oauth`"
 msgstr ":doc:`/administration/maintain/azure_oauth`"
@@ -473,13 +472,10 @@ msgstr ""
 "connectent à Odoo avec leurs comptes Google."
 
 #: ../../content/applications/general/auth/google.rst:12
-msgid ""
+msgid ":doc:`../../productivity/calendar/google`"
-":doc:`/applications/general/calendars/google/google_calendar_credentials`"
+msgstr ":doc:`../../productivity/calendar/google`"
-msgstr ""
-":doc:`/applications/general/calendars/google/google_calendar_credentials`"
 
 #: ../../content/applications/general/auth/google.rst:13
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:66
 msgid ":doc:`/administration/maintain/google_oauth`"
 msgstr ":doc:`/administration/maintain/google_oauth`"
@@ -767,685 +763,6 @@ msgstr ""
 "profils créés. Si ce champ n'est pas rempli, le profil administrateur sera "
 "utilisé comme modèle."
 
-#: ../../content/applications/general/calendars.rst:5
-msgid "Calendars"
-msgstr "Calendriers"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:3
-msgid "Synchronize Google Calendar with Odoo"
-msgstr "Synchroniser Google Agenda avec Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5
-msgid ""
-"Synchronize Google Calendar with Odoo to see and manage meetings from both "
-"platforms (updates go in both directions). This integration helps organize "
-"your schedule so you never miss a meeting."
-msgstr ""
-"Synchronisez Google Agenda avec Odoo pour voir et gérer les réunions à "
-"partir des deux plateformes (les mises à jour vont dans les deux sens). "
-"Cette intégration permet d'organiser votre emploi du temps afin de ne jamais"
-" manquer une réunion."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9
-msgid ":doc:`/applications/general/auth/google`"
-msgstr ":doc:`/applications/general/auth/google`"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:13
-msgid "Setup in Google"
-msgstr "Configuration dans Google"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:16
-msgid "Enable Google Calendar API"
-msgstr "Activer l'API Google Agenda"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18
-msgid ""
-"Begin by creating a new Google API project and enabling the Google Calendar "
-"API. Then, go to the `Google API Console "
-"<https://console.developers.google.com>`_ and log into your Google account."
-msgstr ""
-"Commencez par créer un nouveau projet API Google et activer Google Agenda "
-"API. Ensuite, allez à la `Console Google API "
-"<https://console.developers.google.com>`_ et connectez-vous à votre compte "
-"Google."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22
-msgid ""
-"If this is your first time visiting this page, Google will prompt you to "
-"enter a country and agree to the Terms of Service. Select a country from the"
-" drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
-msgstr ""
-"Si c'est la première fois que vous visitez cette page, Google vous demandera"
-" de saisir un pays et d'accepter les conditions générales d'utilisation. "
-"Sélectionnez un pays dans la liste déroulante et acceptez les :abbr:`CGS "
-"(Conditions générales de service)`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:26
-msgid ""
-"Next, click :guilabel:`Select a project` and select or create an API project"
-" to store credentials."
-msgstr ""
-"Ensuite, cliquez sur :guilabel:`Sélectionner un projet` et sélectionnez ou "
-"créez un projet API pour stocker les identifiants."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Create a new API project to store credentials."
-msgstr "Créer un nouveau projet API pour stocker les identifiants."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:33
-msgid ""
-"Give the API Project a clear name like \"Odoo Sync\" so you can easily find "
-"it."
-msgstr ""
-"Donnez au Projet API un nom évident tel que \"Odoo Sync\" pour que vous "
-"puissez le retrouver facilement."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
-msgid ""
-"Then, open the API Project and click :guilabel:`Enable APIs and Services`."
-msgstr ""
-"Ensuite, ouvrez le Projet API et cliquez sur :guilabel:`Activer les APIs et "
-"les services`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable APIs and Services on the API Project."
-msgstr "Activer les APIs et les services dans le Projet API."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:41
-msgid ""
-"After that, search for *Google Calendar API* using the search bar and select"
-" :guilabel:`Google Calendar API` from the search results. Click "
-":guilabel:`Enable`."
-msgstr ""
-"Ensuite, recherchez *Google Agenda API* à l'aide de la barre de recherche et"
-" sélectionnez :guilabel:`Google Agenda API` dans les résultats de recherche."
-" Cliquez sur :guilabel:`Activer`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable the Google Calendar API."
-msgstr "Activer le Google Agenda API."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:49
-msgid "Create credentials"
-msgstr "Créer des identifiants"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51
-msgid ""
-"Now that you have created your API project and enabled the Google Calendar "
-"API, you need to create credentials. Begin by clicking :guilabel:`Create "
-"Credentials`. Google will then guide you through four steps to create your "
-"API credentials."
-msgstr ""
-"Maintenant que vous avez créé votre projet API et activé Google Agenda API, "
-"vous devez créer des identifiants. Commencez par cliquer sur "
-":guilabel:`Créer des identifiants`. Google vous guidera ensuite à travers "
-"quatre étapes pour créer vos identifiants API."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
-msgid ""
-"In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google"
-" Calendar API` and :guilabel:`User Data` options. Then, click "
-":guilabel:`Next`."
-msgstr ""
-"Dans la première étape, :guilabel:`Type d'identifiant`, sélectionnez "
-":guilabel:`Google Agenda API` et les options :guilabel:`Données "
-"d'utilisateur`. Cliquez ensuite sur :guilabel:`Suivant`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Select Google Calendar API and User Data for the Credential Type."
-msgstr ""
-"Sélectionner Google Agenda API et données d'utilisateur pour le type "
-"d'identifiant."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:62
-msgid ""
-"In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the "
-":guilabel:`App name` field, select your email address for the "
-":guilabel:`User support email` field, and type your email address for the "
-":guilabel:`Developer contact information` section. Then, click "
-":guilabel:`Save and Continue`."
-msgstr ""
-"Pour la deuxième étape, :guilabel:`Écran de consentement OAuth`, écrivez "
-"*Odoo* dans le champ :guilabel:`nom d'App`, sélectionnez votre adresse mail "
-"dans le champ :guilabel:`Utilisateur support email` et tapez votre adresse "
-"mail dans la section :guilabel:`Coordonnées du développeur`. Cliquez ensuite"
-" sur :guilabel:`Sauver et continuer`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
-msgid ""
-"Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and "
-"Continue`."
-msgstr ""
-"Passez la troisième étape :guilabel:`Champs d'application`, en cliquant sur "
-":guilabel:`Sauver et continuer`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
-msgid ""
-"In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website "
-"application` for the :guilabel:`Application Type` field and type *My Odoo "
-"Database* for the :guilabel:`Name`."
-msgstr ""
-"Pour la dernière étape :guilabel:`ID OAuth Client`, sélectionnez "
-":guilabel:`Application site web` pour le champ :guilabel:`Type "
-"d'application` et saisissez *Ma base de données Odoo* pour le "
-":guilabel:`Nom`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:72
-msgid ""
-"Under the :guilabel:`Authorized JavaScript Origins` section, click "
-":guilabel:`+ Add URI` and type your company's Odoo URL address."
-msgstr ""
-"Dans la section :guilabel:`Authorized JavaScript Origins (Origines "
-"JavaScript autorisées)`, cliquez sur :guilabel:`+ Ajouter URL` et saisissez "
-"l'adresse URL d'Odoo de votre entreprise."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
-msgid ""
-"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ "
-"Add URI` and type your company's Odoo URL address followed by "
-"*/google_account/authentication*. Finally, click :guilabel:`Create` and "
-":guilabel:`Done`."
-msgstr ""
-"Dans la section :guilabel:`Authorized redirect URIs (URL de redirection "
-"autorisées)`, cliquez sur :guilabel:`+ Ajouter URL` et saisissez l'adresse "
-"URL d'Odoo de votre entreprise, suivie par */google_account/authentication*."
-" Enfin, cliquez sur :guilabel:`Créer` et :guilabel:`Fini`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Add the authorized JavaScript origins and the authorized redirect URIs."
-msgstr ""
-"Ajouter les origines JavaScript autorisées et les URLs de redirection "
-"autorisées."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83
-msgid ""
-"After successfully creating a new API project, enabling the Google Calendar "
-"API, and generating the Google Calendar API credentials, you should now have"
-" a Client ID and Client Secret."
-msgstr ""
-"Après avoir créé un nouveau projet API, activé Google Agenda API et généré "
-"les identifiants de Google Agenda API, vous devez disposer d'un ID Client et"
-" d'un Secret Client."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:87
-msgid "Client ID & Client Secret"
-msgstr "ID Client & Secret Client"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
-msgid ""
-"The **Client ID** and the **Client Secret** are both needed to connect "
-"Google Calendar to Odoo. Find the Client ID and the Client Secret by opening"
-" the Google Cloud Platform navigation menu and going to :menuselection:`API "
-"& Services --> Credentials --> OAuth 2.0 Client IDs`."
-msgstr ""
-"L'**ID Client** et le **Secret Client** sont tous les deux nécessaires pour "
-"connecter Google Agenda à Odoo. Vous trouverez l'ID Client et le Secret "
-"Client en ouvrant le menu de navigation de la plateforme Google Cloud et en "
-"allant à :menuselection:`API & Services --> Identifiants --> OAuth 2.0 ID "
-"Client`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:93
-msgid ""
-"Next, locate the credentials you just created for the Google Calendar API. "
-"Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page "
-"will redirect to the edit page, where you can view the Client ID and the "
-"Client Secret."
-msgstr ""
-"Localisez ensuite les identifiants que vous venez de créer pour Google "
-"Agenda API et cliquez sur :guilabel:`Modifier OAuth Client` (l'icône "
-"crayon). La page vous redirigera vers la page d'édition, où vous pourrez "
-"voir l'ID Client et le Secret Client."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Click Edit OAuth Client to view the credential details."
-msgstr "Cliquer sur éditer OAuth Client pour voir les identifiants."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:102
-msgid "Setup in Odoo"
-msgstr "Configuration dans Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:104
-msgid ""
-"Once the Client ID and the Client Secret are located, open the Odoo database"
-" and go to :menuselection:`Settings --> General Settings --> Integrations "
-"--> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
-msgstr ""
-"Une fois l'ID Client et le Secret Client localisés, ouvrez la base de "
-"données Odoo et allez aux :menuselection:`Paramètres --> Paramètres généraux"
-" --> Intégrations --> Google Agenda`. Cochez la case à côté de "
-":guilabel:`Google Agenda`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "The Google Calendar checkbox in General Settings."
-msgstr "La case à cocher Google Agenda dans les Paramètres généraux."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
-msgid ""
-"Next, copy and paste the Client ID and the Client Secret from the Google "
-"Calendar API Credentials page into their respective fields below the "
-":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
-msgstr ""
-"Ensuite, copiez et collez l'ID Client et le Secret Client dans la page des "
-"identifiants Google Agenda API dans les champs respectifs situés sous la "
-"case :guilabel:`Google Agenda`. Cliquez ensuite sur :guilabel:`Sauvegarder`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:116
-msgid ""
-"Finally, open the Calendar module in Odoo and click on the "
-":guilabel:`Google` sync button to sync Google Calendar with Odoo."
-msgstr ""
-"Enfin, ouvrez le module Agenda dans Odoo et cliquez sur le bouton de "
-"synchronisation :guilabel:`Google` pour synchroniser Google Agenda avec "
-"Odoo."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Click the Google sync button in Odoo Calendar to sync Google Calendar with "
-"Odoo."
-msgstr ""
-"Cliquez sur le bouton de synchronisation Google dans Odoo Agenda pour "
-"synchroniser Odoo Agenda avec Odoo."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:124
-msgid ""
-"The first time you sync your Google Calendar with Odoo, the page will "
-"redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` "
-"to authorize Odoo to access Google Calendar."
-msgstr ""
-"La première fois que vous synchronisez votre Google Agenda avec Odoo, la "
-"page vous redirigera vers votre compte Google. Cliquez sur :guilabel:`OK` et"
-" :guilabel:`Autoriser` pour autoriser Odoo à accéder à Google Agenda."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Give Odoo permission to access Google Calendar."
-msgstr "Autoriser Odoo à accéder à Google Agenda."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:131
-msgid "Now, Odoo Calendar is successfully synced with Google Calendar!"
-msgstr "À présent, Odoo Agenda est synchronisé avec succès avec Odoo Agenda !"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Successfully sync between Odoo and Google Calendar."
-msgstr "Synchronisation réussie entre Odoo et Google Agenda."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
-msgid "Synchronize Outlook Calendar with Odoo"
-msgstr "Synchroniser Outlook Calendrier avec Odoo"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5
-msgid ""
-"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping "
-"track of their tasks and appointments across all related applications."
-msgstr ""
-"La synchronisation du Calendrier Outlook d'un utilisateur avec Odoo est "
-"utile pour suivre ses tâches et ses rendez-vous dans toutes les applications"
-" associées."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9
-msgid ":doc:`/applications/general/auth/azure`"
-msgstr ":doc:`/applications/general/auth/azure`"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:13
-msgid "Register the application with Microsoft Azure"
-msgstr "Inscrire l'application via Microsoft Azure"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:15
-msgid ""
-"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account"
-" is needed. Creating an account is free for users who have never tried or "
-"paid for Azure. For more information, `click here "
-"<https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_."
-msgstr ""
-"Afin de synchroniser le Calendrier Outlook avec celui d'Odoo, vous avez "
-"besoin d'un compte Microsoft Azure. La création d'un compte est gratuite "
-"pour les utilisateurs qui n'ont jamais essayé ou payé Azure. Pour plus "
-"d'informations, `cliquez ici <https://azure.microsoft.com/en-"
-"us/free/?WT.mc_id=A261C142F>`_."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:19
-msgid ""
-"Refer to `Microsoft's documentation <https://docs.microsoft.com/en-"
-"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to"
-" set up an Azure AD Tenant (also called an *environment*), which is a "
-"representation of an organization to manage and register apps."
-msgstr ""
-"Consultez la `documentation de Microsoft <https://docs.microsoft.com/en-"
-"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ pour "
-"savoir comment configurer un locataire Azure AD (également appelé "
-"*environnement*), qui est la représentation d'une organisation pour gérer et"
-" inscrire des applications."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:23
-msgid ""
-"Then, `Register an Application <https://docs.microsoft.com/en-"
-"us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the "
-"appropriate :guilabel:`Supported account type`. Users who wish to connect "
-"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any "
-"organizational directory (Any Azure AD directory - Multitenant) and personal"
-" Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported "
-"account types`."
-msgstr ""
-"Ensuite, `inscrivez une application <https://docs.microsoft.com/en-"
-"us/azure/active-directory/develop/ quickstart-register-app>`_, en "
-"choisissant le :guilabel:`type de comptes pris en charge` approprié. Les "
-"utilisateurs qui souhaitent connecter leur calendrier Outlook à Odoo doivent"
-" sélectionner l'option :guilabel:`Comptes dans un annuaire organisationnel "
-"(Tout annuaire Azure AD - Multilocataire) et comptes personnels Microsoft "
-"(par ex. Skype, Xbox)` pour les :guilabel:`type de comptes pris en charge`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:29
-msgid ""
-"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and "
-"copy the Odoo database URI (URL) followed by "
-"`/microsoft_account/authentication`."
-msgstr ""
-"Lors de la configuration de :guilabel:`l'URL de redirection`, choisissez "
-":guilabel:`Web` et copiez l'URL de la base de données Odoo, suivie de "
-"`/microsoft_account/authentication`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:33
-msgid ""
-"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` "
-"for the :guilabel:`Redirect URI`."
-msgstr ""
-"Saisissez "
-"`https://www.companyname.odoo.com/microsoft_account/authentication` pour "
-":guilabel:`l'URL de redirection`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid ""
-"The \"Supported account type\" and \"Redirect URI\" settings in the "
-"Microsoft Azure AD portal."
-msgstr ""
-"Les paramètres \"types de comptes pris en charge\" et \"l'URL de "
-"redirection\" dans le portail Microsoft Azure AD."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:40
-msgid ""
-"For more information on the restrictions and limitations of URIs, `check "
-"this page <https://docs. microsoft.com/en-us/azure/active-"
-"directory/develop/reply-url>`_."
-msgstr ""
-"Pour plus d'informations sur les restrictions et les limitations des URL, "
-"`consultez cette page <https://docs. microsoft.com/en-us/azure/active-"
-"directory/develop/reply-url>`_."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:43
-msgid ""
-"Regarding the application credentials, the user *must* add a client secret, "
-"which allows Odoo to authenticate itself, requiring no interaction from the "
-"user's side. :guilabel:`Certificates` are optional."
-msgstr ""
-"En ce qui concerne les identifiants de l'application, l'utilisateur *doit* "
-"ajouter un secret client, qui permet à Odoo de s'authentifier, ne "
-"nécessitant aucune intervention de la part de l'utilisateur. Les "
-":guilabel:`certificats` sont optionnels."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:47
-msgid ""
-"To do add a client secret, click :guilabel:`Add a certificate or secret` and"
-" then click :guilabel:`New client secret`. Next, type a "
-":guilabel:`Description` and select when the client secret "
-":guilabel:`Expires`."
-msgstr ""
-"Pour ajouter un secret client, cliquez sur :guilabel:`Ajouter un certificat "
-"ou un secret` et cliquez ensuite sur :guilabel:`Nouveau secret client`. "
-"Ensuite, tapez une :guilabel:`Description` et sélectionnez quand le secret "
-"client :guilabel:`expire`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:51
-msgid ""
-"Since resetting the synchronization can be tricky, Odoo recommends setting "
-"the maximum allowed expiration date for the client secret (24 months), so "
-"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to "
-"generate the client secret (:guilabel:`Secret ID`)."
-msgstr ""
-"Étant donné que la réinitialisation de la synchronisation peut être "
-"délicate, Odoo recommande de définir la date d'expiration maximale autorisée"
-" pour le secret client (24 mois), de sorte qu'il ne soit pas nécessaire de "
-"procéder à une nouvelle synchronisation prochainement. Enfin, cliquez sur "
-":guilabel:`Ajouter` pour générer le secret client (:guilabel:`Secret ID`)."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:56
-msgid "Configuration in Odoo"
-msgstr "Configuration dans Odoo "
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:58
-msgid ""
-"In the Odoo database, go to :menuselection:`Settings --> General Settings "
-"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting."
-msgstr ""
-"Dans la base de données Odoo, allez aux :menuselection:`Paramètres --> "
-"Paramètres généraux --> Intégrations` et activez le paramètre "
-":guilabel:`Calendrier Outlook`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook Calendar\" setting activated in Odoo."
-msgstr "Le paramètre \"Calendrier Outlook\" activé dans Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:65
-msgid ""
-"From the Microsoft Azure portal, under the :guilabel:`Overview` section of "
-"the application, copy the :guilabel:`Application (Client) ID`, and paste it "
-"into the :guilabel:`Client ID` field in Odoo."
-msgstr ""
-"Depuis le portail de Microsoft Azure, sous la section :guilabel:`Aperçu` de "
-"l'application, copiez :guilabel:`l'ID Application (Client)` et copiez-le "
-"dans le champ :guilabel:`ID client` dans Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client ID\" in the Microsoft Azure portal."
-msgstr "L'\"ID client\" dans le portail de Microsoft Azure."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:72
-msgid ""
-"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` "
-"section, copy the :guilabel:`Client Secret Value` and paste it into the "
-":guilabel:`Client Secret` field in Odoo."
-msgstr ""
-"Dans le portail de Microsoft Azure, sous la section :guilabel:`Certificats &"
-" Secrets`, copiez la :guilabel:`Valeur secret client` et copiez-la dans le "
-"champ :guilabel:`Secret client` dans Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo."
-msgstr "Le jeton \"Secret client\" à copier de Microsoft à Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:79
-msgid ""
-"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, "
-"click :guilabel:`Save`."
-msgstr ""
-"Enfin, sur la page :menuselection:`Paramètres --> Paramètres généraux` "
-"d'Odoo, cliquez sur :guilabel:`Sauvegarder`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:84
-msgid "Sync with Outlook"
-msgstr "Synchroniser avec Outlook"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:88
-msgid ""
-"Odoo highly recommends testing the Outlook calendar synchronization on a "
-"test database and a test email address (that is not used for any other "
-"purpose) before attempting to sync the desired Outlook Calendar with the "
-"user's production database."
-msgstr ""
-"Odoo recommande vivement de tester la synchronisation du calendrier Outlook "
-"sur une base de données de test et une adresse mail de test (qui n'est pas "
-"utilisée à d'autres fins) avant de tenter de synchroniser le calendrier "
-"Outlook souhaité avec la base de données de production de l'utilisateur."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:92
-msgid ""
-"If the user has any past, present, or future events on their Odoo calendar "
-"before syncing their Outlook calendar, Outlook will treat the events pulled "
-"from Odoo's calendar during the sync as new events, causing an email "
-"notification to be sent from Outlook to all the event attendees."
-msgstr ""
-"Si l'utilisateur a des événements passés, présents ou futurs dans son "
-"calendrier Outlook avant de le synchroniser, Outlook traitera les événements"
-" tirés du calendrier d'Odoo comme de nouveaux événements, ce qui entraînera "
-"l'envoi par Outlook d'une notification par email à tous les participants à "
-"l'événement."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:96
-msgid ""
-"To avoid unwanted emails being sent to all past, present, and future event "
-"attendees, the user must add the events from the Odoo calendar to the "
-"Outlook calendar before the first ever sync, delete the events from Odoo, "
-"and then start the sync."
-msgstr ""
-"Pour éviter l'envoi d'emails non désirés à tous les participants "
-"d'événements passés, présents et futurs, l'utilisateur doit ajouter les "
-"événements du calendrier Odoo au calendrier Outlook avant la toute première "
-"synchronisation, supprimer les événements dans Odoo et relancer la "
-"synchronisation."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:100
-msgid ""
-"Even after synchronizing the Odoo Calendar with the Outlook calendar, "
-"Outlook will still send a notification to all event participants every time "
-"an event is edited (created, deleted, unarchived, or event date/time "
-"changed), with no exceptions. This is a limitation that cannot be fixed from"
-" Odoo's side."
-msgstr ""
-"Même après avoir synchronisé le calendrier Odoo avec le calendrier Outlook, "
-"Outlook enverra toujours une notification à tous les participants chaque "
-"fois qu'un événement est modifié (créé, supprimé, archivé ou changement de "
-"date/heure), sans exception. Il s'agit d'une limitation qui ne peut être "
-"corrigée par Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:105
-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 ""
-"Après qu'un utilisateur a synchronisé son calendrier Outlook avec la base de"
-" données Odoo, des notifications par email non désirés sont inévitables, car"
-" les événements du premier utilisateur synchronisé se trouveront dans le "
-"calendrier Odoo. Si la base de données Odoo est partagée entre plusieurs "
-"utilisateurs et un autre utilisateur veut synchroniser son calendrier "
-"Outlook avec le calendrier Odoo, Outlook récupérera à nouveau tous les "
-"événements existants du calendrier Odoo pendant la synchronisation et les "
-"traitera comme de nouveaux événements, poussant Outlook à envoyer des "
-"invitations par email à tous les participants."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:112
-msgid ""
-"In summary, once a user synchronizes their Outlook calendar with the Odoo "
-"calendar:"
-msgstr ""
-"En résumé, une fois qu'un utilisateur synchronise son calendrier Outlook "
-"avec le calendrier Odoo :"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:114
-msgid ""
-"Creating an event in Odoo causes Outlook to send an invitation to all event "
-"attendees."
-msgstr ""
-"La création d'un événement Odoo pousse Outlook à envoyer une invitation à "
-"tous les participants."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:115
-msgid ""
-"Deleting an event in Odoo causes Outlook to send a cancellation to all event"
-" attendees."
-msgstr ""
-"L'annulation d'un événement Odoo pousse Outlook à envoyer une annulation à "
-"tous les participants."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:116
-msgid ""
-"Unarchiving an event in Odoo causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-"La restauration d'un événement dans Odoo pousse Outlook à envoyer une "
-"invitation à tous les participants."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:117
-msgid ""
-"Archiving an event in Odoo causes Outlook to send a cancellation to all "
-"event attendees."
-msgstr ""
-"L'archivage d'un événement dans Odoo pousse Outlook à envoyer une annulation"
-" à tous les participants."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:118
-msgid ""
-"Adding a contact to an event causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-"L'ajout d'un contact à un événement pousse Outlook à envoyer une invitation "
-"à tous les participants."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:119
-msgid ""
-"Removing a contact from an event causes Outlook to send a cancellation to "
-"all event attendees."
-msgstr ""
-"La suppression d'un contact d'un événement pousse Outlook à envoyer une "
-"annulation à tous les participants."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:122
-msgid "Sync Odoo Calendar and Outlook"
-msgstr "Synchroniser le calendrier Odoo et Outlook"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:124
-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 ""
-"Dans la base de données Odoo, allez au module :guilabel:`Calendrier` et "
-"cliquez sur le bouton de synchronisation :guilabel:`Outlook`. La page "
-"redirigera vers une page de connexion Microsoft et l'utilisateur est demandé"
-" de se connecter à son compte, si ce n'est pas encore fait, et de fournir "
-"les autorisations requises."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook\" sync button in Odoo Calendar."
-msgstr "Le bouton de synchronisation \"Outlook\" dans Odoo Calendrier"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:132
-msgid ""
-"The synchronization is a two-way process, meaning that events are reconciled"
-" in both accounts (Outlook and Odoo)."
-msgstr ""
-"La synchronisation est un processus bidirectionnel, ce qui signifie que les "
-"événements sont réconciliés dans les deux comptes (Outlook et Odoo)."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:136
-msgid ""
-"All users that want to use the synchronization simply need to :ref:`sync "
-"their calendar with Outlook <outlook_calendar/sync_with_outlook>`. The "
-"configuration of Microsoft's Azure account is only done once, as Azure AD "
-"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 ""
-"Tous les utilisateurs qui souhaitent utiliser la synchronisation doivent "
-"simplement ref:`synchroniser leur calendrier avec Outlook "
-"<outlook_calendar/sync_with_outlook>`. La configuration du compte Azure de "
-"Microsoft n'est effectuée qu'une seule fois, car les ID client et Secrets "
-"clients des locataires Azure AD sont uniques et représentent une "
-"organisation qui aide l'utilisateur à gérer une instance spécifique des "
-"services cloud de Microsoft pour leurs utilisateurs internes et externes."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:143
-msgid ":doc:`../../../productivity/mail_plugins/outlook`"
-msgstr ":doc:`../../../productivity/mail_plugins/outlook`"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:144
-msgid ":doc:`../google/google_calendar_credentials`"
-msgstr ":doc:`../google/google_calendar_credentials`"
-
 #: ../../content/applications/general/developer_mode.rst:5
 msgid "Developer Mode (debug mode)"
 msgstr "Mode développeur (mode débogage)"
@@ -6254,8 +5571,8 @@ msgstr ""
 "précédemment installée et cliquer sur **SAUVEGARDER.**"
 
 #: ../../content/applications/general/users/language.rst:61
-msgid ":doc:`../../websites/website/publish/translate`"
+msgid ":doc:`../../websites/website/configuration/translate`"
-msgstr ":doc:`../../websites/website/publish/translate`"
+msgstr ":doc:`../../websites/website/configuration/translate`"
 
 #: ../../content/applications/general/users/manage_users.rst:3
 msgid "Manage users"

locale/fr/LC_MESSAGES/services.po

@@ -18,7 +18,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:54+0000\n"
 "Last-Translator: Jolien De Paepe, 2023\n"
 "Language-Team: French (https://app.transifex.com/odoo/teams/41243/fr/)\n"
@@ -404,113 +404,216 @@ msgstr ""
 "programs-640?fullscreen=1>`_"
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
-msgid "Allow customers to close their tickets"
+msgid "Closing tickets"
-msgstr "Permettre aux clients de clôturer leurs tickets"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
 msgid ""
-"Allowing customers to close their own tickets gives them autonomy and "
+"Once work has been completed on a *Helpdesk* ticket in Odoo, there are "
-"minimizes misunderstandings around when an issue is considered solved or "
+"several ways it can be closed. Manually closing solved tickets keeps the "
-"not. This results in operational capacity for support teams, and higher "
+"pipeline up to date, while automatically closing inactive tickets prevents "
-"satisfaction for the customer."
+"unnecessary blocking issues. Allowing customers to close their own tickets "
+"minimizes confusion around whether an issue is considered solved or not. "
+"This results in increased operational capacity for support teams, and higher"
+" customer satisfaction."
 msgstr ""
-"Permettre aux clients de clôturer leurs propres tickets leur donne de "
-"l'autonomie et minimise les malentendus sur le moment où un problème est "
-"considéré comme résolu ou non. Il en résulte une capacité opérationnelle "
-"pour les équipes d'assistance et une plus grande satisfaction pour le "
-"client."
-
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:10
-msgid "Enable ticket closing"
-msgstr "Activer la clôture des tickets"
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12
-msgid ""
+msgid "Manually close solved tickets"
-"Start by navigating to :menuselection:`Helpdesk --> Configuration --> "
+msgstr ""
-"Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit`"
+
-" and enable :guilabel:`Ticket closing` by checking the field box."
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
+msgid ""
+"As work on a ticket progresses, it is moved along to the next stage in the "
+"pipeline. Once the issue is solved, the ticket is moved to a *folded* stage."
+" This marks the ticket as *closed*."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17
+msgid ""
+"To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and "
+"click on a team to open the pipeline. Hover over a stage's heading, and then"
+" click the gear icon that appears in the top-right corner of that stage's "
+"kanban column."
 msgstr ""
-"Allez à :menuselection:`Assistance --> Configuration --> Équipes` et "
-"choisissez la bonne équipe. Cliquez ensuite sur :guilabel:`Éditer` et "
-"activez la :guilabel:`Clôture des tickets` en cochant la case."
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid "Ticket closing feature in Odoo Helpdesk."
-msgstr "Fonctionnalité de clôture des tickets dans Odoo Assistance."
-
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:19
 msgid ""
-"To designate which stage the ticket migrates to once it is closed, navigate "
+"View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage"
-"to the ticket pipeline by going to :menuselection:`Helpdesk --> Overview` "
+" option."
-"and clicking :guilabel:`Tickets` on the team's card."
 msgstr ""
-"Pour désigner l'étape vers laquelle le ticket migre une fois clôturé, "
-"naviguez vers le pipeline du ticket en allant à :menuselection:`Assistance "
-"--> Vue d'ensemble` et en cliquant sur :guilabel:`Tickets` sur la carte de "
-"l'équipe."
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:23
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
 msgid ""
-"There are two options: create a new Kanban stage or work with an existing "
+"Clicking the gear icon also displays the option to :guilabel:`Fold` the "
-"one. For both scenarios, click the :guilabel:`Settings (gear)` icon next to "
+"stage. This setting folds the stage *temporarily* to simplify the kanban "
-"the stage name, select :guilabel:`Edit Stage`, and enable :guilabel:`Closing"
+"view. This does *not* close the tickets in this stage. It also does not "
-" Stage`. After checking the field box, click :guilabel:`Save` to finish."
+"permanently fold the stage. If a stage needs to be folded so the tickets can"
+" be marked as closed, continue following the steps below."
 msgstr ""
-"Il y a deux options : créer une nouvelle étape Kanban ou travailler avec une"
-" étape existante. Pour les deux cas, cliquez sur l'icône "
-":guilabel:`Paramètres (engrenage)` à côté du nom de l'étape, sélectionnez "
-":guilabel:`Modifier l'étape` et activez :guilabel:`Étape de clôture`. Après "
-"avoir coché la case, cliquez sur :guilabel:`Sauvegarder` pour terminer."
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:29
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
 msgid ""
-"If a closing stage is not specified, by default, the ticket is moved to the "
+"From the menu that appears, select :guilabel:`Edit Stage`. This will open "
-"last stage in the kanban. If more than one stage is set as a closing stage, "
+"the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` "
-"the ticket is placed in the first closing stage column."
+"towards the top of the window, and then :guilabel:`Save & Close` to confirm "
+"the changes. Now, tickets that reach this stage will be considered as "
+"*closed*."
 msgstr ""
-"Si aucune étape de clôture n'est définie, par défaut, le ticket est déplacé "
-"vers la dernière étape du kanban. Si plus d'une étape est définie comme "
-"étape de clôture, le ticket est déplacé vers la première colonne d'étape de "
-"clôture."
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:33
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
-msgid ""
+msgid "Stage settings page."
-"With the ticket closing settings now complete, customers can now view the "
+msgstr ""
-"option to :guilabel:`Close this ticket` when they log into their portal."
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41
+msgid "Automatically close inactive tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43
+msgid ""
+"Tickets that are inactive for a set period of time can be automatically "
+"closed. At that point, they will be moved to a folded stage."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46
+msgid ""
+"Go to the team's settings page by going to :menuselection:`Helpdesk --> "
+"Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable"
+" :guilabel:`Automatic Closing`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
+msgid ""
+"If one of the team's stages is set to be folded in the kanban view, it will "
+"be the default selection in the :guilabel:`Move to Stage` field. If the team"
+" has more than one folded stage, the stage that occurs first in the pipeline"
+" will be the default. If no stage is folded, the default selection will be "
+"the last stage in the pipeline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54
+msgid ""
+"The :guilabel:`After days of inactivity` field defaults to `7`, but can be "
+"adjusted if necessary."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57
+msgid ""
+"The :guilabel:`After days of inactivity` field does **not** take the working"
+" calendar into account when tracking the amount of time a ticket has been "
+"inactive."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60
+msgid ""
+"If only certain stages should be used to track days of inactivity, they can "
+"be added to the :guilabel:`In Stages` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64
+msgid "A team's pipeline is created with the following stages:"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66
+msgid "`New`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67
+msgid "`In Progress`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68
+msgid "`Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69
+msgid "`Closed`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71
+msgid ""
+"Tickets can linger in the :guilabel:`Customer Feedback stage`, because once "
+"an issue is solved, customers may not respond immediately. At that point, "
+"the tickets can be closed automatically. However, tickets in the "
+":guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due "
+"to assignment or workload issues. Closing these tickets automatically would "
+"result in issues going unsolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
+msgid ""
+"Therefore, the :guilabel:`Automatic Closing` settings would be configured as"
+" below\\:\\"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
+msgid ":guilabel:`Automatic Closing`: *checked*"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
+msgid ":guilabel:`Move to Stage`: `Solved`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
+msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
+msgid ":guilabel:`In Stages`: `Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
+msgid "Example of Automatic Closing settings."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89
+msgid "Allow customers to close their own tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
+msgid ""
+"Enabling the :guilabel:`Closure by Customers` setting allows customers to "
+"close their own ticket(s) when they determine that their issue has been "
+"resolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94
+msgid ""
+"Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams`"
+" and select a team. On the team's settings page, scroll to the "
+":guilabel:`Self-Service` section and check the box for :guilabel:`Closure by"
+" Customers`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
+msgid "Customer closing setting in Odoo Helpdesk."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
+msgid ""
+"Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` "
+"button will be available for customers when they view their ticket through "
+"the customer portal."
 msgstr ""
-"Une fois les paramètres de clôture du ticket terminés, les clients peuvent "
-"maintenant voir l'option :guilabel:`Clôturer ce ticket` lorsqu'ils se "
-"connectent à leur portail."
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
 msgid "Customer view of ticket closing in Odoo Helpdesk."
 msgstr "Vue client d'une clôture de ticket dans Odoo Assistance."
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:40
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110
-msgid "Get reports on tickets closed by customers"
-msgstr "Obtenir des rapports sur les tickets clôturés par les clients"
-
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:42
 msgid ""
-"To analyze the tickets that have been closed by customers, go to "
+"Customers are able to view their tickets by clicking the :guilabel:`View the"
-":menuselection:`Helpdesk --> Reporting --> Tickets`. Then, click on the "
+" ticket` link they receive by email. The link is included in the "
-":guilabel:`Filters` menu and choose :guilabel:`Add Custom filter`. Next, set"
+":guilabel:`Request Acknowledgment` template, which is added to the first "
-" the custom filter parameters to :guilabel:`Closed by partner` and "
+"stage of a team by default. This link does not require a customer to have "
-":guilabel:`is true`. Finally, click :guilabel:`Apply`."
+"access to the portal to view or respond to their ticket."
 msgstr ""
-"Pour analyser les tickets clôturés par les clients, allez à "
-":menuselection:`Assistance --> Analyse --> Tickets`. Ensuite, cliquez sur le"
-" menu des :guilabel:`Filtres` et choisissez :guilabel:`Ajouter un filtre "
-"personnalisé`. Ensuite, définissez les paramètres du filtre personnalisé sur"
-" :guilabel:`Clôturé par partenaire` et :guilabel:`est vrai`. Enfin, cliquez "
-"sur :guilabel:`Appliquer`."
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
 msgid ""
-"Filter for tickets closed by customers on Odoo Helpdesk's reporting page."
+"Customers with access to the portal will be able to view their tickets under"
+" :menuselection:`My Account --> Tickets`."
 msgstr ""
-"Filtre des tickets clôturés par les clients sur la page d'analyse d'Odoo "
-"Assistance."
 
 #: ../../content/applications/services/helpdesk/overview.rst:5
 #: ../../content/applications/services/timesheets/overview.rst:5
@@ -1183,7 +1286,6 @@ msgstr ""
 "dans Odoo Assistance"
 
 #: ../../content/applications/services/helpdesk/overview/ratings.rst:51
-#: ../../content/applications/services/helpdesk/overview/sla.rst:47
 msgid ":doc:`../advanced/close_tickets`"
 msgstr ":doc:`../advanced/close_tickets`"
 
@@ -1517,13 +1619,8 @@ msgid ""
 "The *Live Chat* feature allows website visitors to connect directly with a "
 "support agent or chatbot. During these conversations, *Helpdesk* tickets can"
 " be instantly created by using the :doc:`response command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk`."
+"</applications/websites/livechat/responses>` `/helpdesk`."
 msgstr ""
-"La fonctionnalité de *Live Chat* permet aux visiteurs du site web d'être "
-"directement en contact avec un agent d'assistance ou un chatbot. Au cours de"
-" ces conversations, des tickets d'*Assistance* peuvent être créés "
-"instantanément en utilisant la :doc:`commande de réponse "
-"</applications/websites/livechat/overview/responses>` `/assistance`."
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125
 msgid ""
@@ -1880,16 +1977,10 @@ msgstr ""
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261
 msgid ""
 "During the conversation, an operator can use the shortcut :doc:`command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk` to create "
+"</applications/websites/livechat/responses>` `/helpdesk` to create a ticket "
-"a ticket without leaving the chat window. The transcript from the "
+"without leaving the chat window. The transcript from the conversation will "
-"conversation will be added to the new ticket, under the "
+"be added to the new ticket, under the :guilabel:`Description` tab."
-":guilabel:`Description` tab."
 msgstr ""
-"Pendant la conversation, un opérateur peut utiliser le code court "
-":doc:`commande </applications/websites/livechat/overview/responses>` "
-"`/assistance` pour créer un ticket sans quitter la fenêtre de discussion. La"
-" transcription de la conversation sera ajoutée au nouveau ticket dans "
-"l'onglet :guilabel:`Description`."
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267
 msgid "Prioritizing tickets"
@@ -1959,8 +2050,8 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
 msgstr ":doc:`/applications/general/email_communication/email_servers`"
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293
-msgid ":doc:`/applications/websites/livechat/overview/get_started`"
+msgid ":doc:`/applications/websites/livechat`"
-msgstr ":doc:`/applications/websites/livechat/overview/get_started`"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/reports.rst:3
 msgid "Reports for a Better Support"
@@ -2106,100 +2197,301 @@ msgstr "Accords de niveau de service (SLA)"
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:5
 msgid ""
-"Service Level Agreements (SLA) are commitments you make with your customers "
+"A Service Level Agreement (SLA) defines the level of service a customer can "
-"to outline how a service is delivered. It bolsters trust between you and "
+"expect from a supplier. SLAs provide a timeline that tells customers when "
-"your customers as it makes clear what needs to be done, to what standard, "
+"they can expect results, and keeps the support team on target."
-"and when."
 msgstr ""
-"Les accords de niveau de service (SLA) sont des engagements que vous prenez "
-"avec vos clients pour décrire comment un service est fourni. Ils renforcent "
-"la confiance entre vous et vos clients, car ils indiquent clairement ce qui "
-"doit être fait, selon quelles normes et à quel moment."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:10
-msgid "Create your policies"
+msgid "Create a new SLA policy"
-msgstr "Créer vos politiques"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst:13
-msgid ""
-"First, enable the feature on the settings of the team you would like "
-"policies to be applied, going to :menuselection:`Helpdesk --> Configuration "
-"--> Helpdesk Teams`."
 msgstr ""
-"Tout d'abord, activez la fonctionnalité dans les paramètres de l'équipe à "
-"laquelle vous souhaitez appliquer les politiques, en allant à "
-":menuselection:`Assistance --> Configuration --> Équipes`."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:15
+#: ../../content/applications/services/helpdesk/overview/sla.rst:12
 msgid ""
-"Create your policies through the team’s settings page or go to "
+"To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to "
-":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
+"the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`."
+" Select a team, scroll to the :guilabel:`Performance` section, and then "
+"check the selection box next to :guilabel:`SLA Policies` to enable it for "
+"that specific team."
 msgstr ""
-"Créez vos politiques via la page des paramètres de l'équipe ou allez à "
-":menuselection:`Assistance --> Configuration --> Politiques SLA`."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
-msgid "View of an SLA form in Odoo Helpdesk"
+msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
-msgstr "Vue d'un formulaire SLA dans Odoo Assistance"
+msgstr ""
-
+
-#: ../../content/applications/services/helpdesk/overview/sla.rst:23
+#: ../../content/applications/services/helpdesk/overview/sla.rst:22
-msgid ""
+msgid ""
-"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
+"The value indicated next to the :guilabel:`Working Hours` field is used to "
-" a ticket needs to have for the policy to be applied."
+"determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. "
+"By default, this is determined by the value set in the :guilabel:`Company "
+"Working Hours` field under :menuselection:`Settings app --> Employees --> "
+"Work Organization`."
 msgstr ""
-"Choisissez l'**équipe** à laquelle la politique s'applique et la **priorité "
-"minimale** qu'un ticket doit avoir pour que la politique soit appliquée."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:27
 msgid ""
-"**Target** is the stage a ticket needs to reach within the period defined to"
+"To create a new policy, click the smart button on the team`s settings page "
-" satisfy the SLA. The period is based on the ticket’s creation date, and a "
+"or go to :menuselection:`Helpdesk -->  Configuration --> SLA Policies`, and "
-"deadline is set on the ticket’s form once it matches an SLA policy rule. If "
+"click :guilabel:`New`. Start by entering a :guilabel:`Title` and a "
-"a ticket has more than one policy applied to it, the closest deadline of all"
+":guilabel:`Description` for the new policy, and proceed to fill out the form"
-" SLAs is the one considered."
+" using the steps below."
 msgstr ""
-"**L'Objectif** est le stade qu'un ticket doit atteindre dans la période "
-"définie pour satisfaire le SLA. La période est basée sur la date de création"
-" du ticket, et une date limite est définie sur le formulaire du ticket une "
-"fois qu'il correspond à une règle du SLA. Si plusieurs politiques sont "
-"appliquées à un ticket, c'est la date limite la plus proche de tous les SLA "
-"qui est prise en compte."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:29
+#: ../../content/applications/services/helpdesk/overview/sla.rst:33
+msgid "Define the criteria for an SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:35
 msgid ""
-"When a ticket has satisfied an SLA policy, the SLA tag appears in green and "
+"The :guilabel:`Criteria` section is used to identify what tickets this "
-"the deadline field is not shown anymore."
+"policy will be applied to. Fill out the following fields to adjust the "
+"selection criteria:"
 msgstr ""
-"Lorsqu'un ticket a satisfait à une politique SLA, l'étiquette SLA apparaît "
-"en vert et le champ de la date limite n'est plus affiché."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+#: ../../content/applications/services/helpdesk/overview/sla.rst:38
-msgid "View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk"
+msgid ""
+":guilabel:`Team`: a policy can only be applied to one team. *This field is "
+"required.*"
 msgstr ""
-"Vue d'un formulaire de ticket mettant en évidence un SLA satisfait dans Odoo"
-" Assistance"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst:37
-msgid "SLA Analysis"
-msgstr "Analyse SLA"
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:39
 msgid ""
-"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply"
+":guilabel:`Priority`: the priority level for a ticket is identified by "
-" *Filters* and *Group by* to identify tickets that should be prioritized and"
+"selecting the number of stars representing the priority level on the kanban "
-" keep track of upcoming deadlines."
+"card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will "
+"only be applied once the priority level has been updated on the ticket to "
+"match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is"
+" made in this field, this policy will only apply to tickets marked as `Low "
+"Priority` (zero stars)."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:44
+msgid ""
+":guilabel:`Types`: ticket types can be helpful when indicating when a ticket"
+" is a customer question, that can be solved with a quick response, or an "
+"issue, that may require additional investigation. Multiple ticket types can "
+"be selected for this field. If no selection is made, this policy will apply "
+"to all ticket types."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:48
+msgid ""
+":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is "
+"about. Multiple tags can be applied to a single ticket."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:50
+msgid ""
+":guilabel:`Customers`: individual contacts or companies may be selected in "
+"this field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:51
+msgid ""
+":guilabel:`Sales Order Items`: this field is available only if a team has "
+"the *Timesheets* app enabled. This allows the ticket to tie directly to a "
+"specific line on a sales order, which must be indicated on the ticket in the"
+" :guilabel:`Sales Order Item` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:56
+msgid ""
+"Unless otherwise indicated, multiple selections can be made for each field. "
+"(i.e. multiple :guilabel:`Tags` can be included in a policy, but only one "
+":guilabel:`Priority` level)"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a blank SLA policy record"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:64
+msgid "Establish a target for an SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:66
+msgid ""
+"The :guilabel:`Target` is the stage a ticket needs to reach, and the time "
+"alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service "
+"Level Agreement)` policy. Any stage assigned to a team may be selected for "
+"the :guilabel:`Reach Stage` field. Time spent in stages selected in "
+":guilabel:`Excluding Stages` will not be included in the calculation of the "
+":abbr:`SLA (Service Level Agreement)` deadline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:73
+msgid ""
+"An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks "
+"the working time before a ticket is completed, and would have `Solved` as "
+"the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level "
+"Agreement)` was titled `2 Days to Start`, it tracks the working time before "
+"work on a ticket has begun, and would have `In Progress` as the "
+":guilabel:`Reach Stage`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:79
+msgid "Meeting SLA deadlines"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:81
+msgid ""
+"Once it is determined that a ticket fits the criteria of an :abbr:`SLA "
+"(Service Level Agreement)` policy, a deadline is calculated. The deadline is"
+" based on the creation date of the ticket, and the targeted working hours. "
+"The deadline is then added to the ticket, as well as a white tag indicating "
+"the name of the :abbr:`SLA (Service Level Agreement)` applied."
 msgstr ""
-"Allez à :menuselection:`Assistance --> Analyse --> Analyse du Statut SLA`. "
-"Appliquez des *Filtres* et *Regrouper par* pour identifier les tickets qui "
-"doivent être priorisés et suivre les échéances à venir."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
 msgid ""
-"View of the SLA status analysis page emphasizing the group by option in Odoo"
+"View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo"
 " Helpdesk"
 msgstr ""
-"Vue de la page d'analyse du statut SLA mettant en évidence l'option "
+
-"Regrouper par dans Odoo Assistance"
+#: ../../content/applications/services/helpdesk/overview/sla.rst:91
+msgid ""
+"If a ticket fits the criteria for more than one :abbr:`SLA (Service Level "
+"Agreement)`, the earliest occurring deadline will be displayed on the "
+"ticket. Once that deadline has passed, the next deadline will be displayed."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:95
+msgid ""
+"Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the"
+" :abbr:`SLA (Service Level Agreement)` tag turns green, and the "
+":guilabel:`Deadline` field disappears from view on the."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:102
+msgid ""
+"If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket "
+"has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level "
+"Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level "
+"Agreement)` has failed, the red tag will stay on the ticket, even after the "
+"ticket is moved to the :guilabel:`Reach Stage`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid ""
+"View of a ticket's form with a failing and passing SLA in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:112
+msgid "Analyzing SLA performance"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:114
+msgid ""
+"The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA "
+"(Service Level Agreement)` is fulfilled, as well as the success rate of "
+"individual policies. Navigate to the report and corresponding pivot table by"
+" going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:120
+msgid "Using the Pivot view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:122
+msgid ""
+"By default, the report is displayed in a :guilabel:`Pivot` view, and is "
+"filtered to show the number of SLAs failed and the failure rate over the "
+"last 30 days, grouped by team."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:129
+msgid ""
+"To add the number of SLAs passed or in progress, click the "
+":guilabel:`Measures` button to reveal a drop-down menu of reporting "
+"criteria, and choose from the options available based on the measurements "
+"preferred. Whenever a measurement is picked, a check mark will appear in the"
+" drop-down menu to indicate that that measurement is included, and a "
+"corresponding new column will emerge in the pivot table to show the relevant"
+" calculations."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:135
+msgid ""
+"To add a group to a row or column, click the plus :guilabel:` + ` button "
+"next to :guilabel:`Total`, and then select one of the groups. To remove one,"
+" click the minus :guilabel:` - ` button and deselect."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:140
+msgid "Using the Graph view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:142
+msgid ""
+"The :guilabel:`Status Analysis` report can also be viewed as a "
+":guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between "
+"these views by selecting the appropriate icon at the top of the chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:148
+msgid "Bar Chart"
+msgstr "Graphique à barres"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in bar view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:154
+msgid "Line Chart"
+msgstr "Graphique linéaire"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in line view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:160
+msgid "Pie Chart"
+msgstr "Graphique circulaire"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in pie chart view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:167
+msgid ""
+"Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed "
+":guilabel:`Stacked`. This presents two or more groups to appear on top of "
+"each other instead of next to each other, making it easier to compare data."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:172
+msgid "Using the Cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:174
+msgid ""
+"The :guilabel:`Cohort` view is used to track the changes in data over a "
+"period of time. To display the :guilabel:`Status Analysis` report in a "
+":guilabel:`Cohort` view, click the icon in the top right corner above the "
+"chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:183
+msgid ":ref:`Reporting views <reporting/views>`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:184
+msgid ""
+":doc:`Allow customers to close their tickets "
+"</applications/services/helpdesk/advanced/close_tickets>`"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5
 msgid "Timesheet and Invoice"

locale/ko/LC_MESSAGES/general.po

@@ -13,7 +13,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:53+0000\n"
 "Last-Translator: Sarah Park, 2023\n"
 "Language-Team: Korean (https://app.transifex.com/odoo/teams/41243/ko/)\n"
@@ -324,11 +324,10 @@ msgstr ""
 "Odoo와 호환되지 않습니다."
 
 #: ../../content/applications/general/auth/azure.rst:9
-msgid ":doc:`/applications/general/calendars/outlook/outlook_calendar`"
+msgid ":doc:`../../productivity/calendar/outlook`"
 msgstr ""
 
 #: ../../content/applications/general/auth/azure.rst:10
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:67
 msgid ":doc:`/administration/maintain/azure_oauth`"
 msgstr ""
@@ -353,12 +352,10 @@ msgstr ""
 "있습니다."
 
 #: ../../content/applications/general/auth/google.rst:12
-msgid ""
+msgid ":doc:`../../productivity/calendar/google`"
-":doc:`/applications/general/calendars/google/google_calendar_credentials`"
 msgstr ""
 
 #: ../../content/applications/general/auth/google.rst:13
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:66
 msgid ":doc:`/administration/maintain/google_oauth`"
 msgstr ""
@@ -606,500 +603,6 @@ msgid ""
 "left blanked, the admin profile will be used as template."
 msgstr ""
 
-#: ../../content/applications/general/calendars.rst:5
-msgid "Calendars"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:3
-msgid "Synchronize Google Calendar with Odoo"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5
-msgid ""
-"Synchronize Google Calendar with Odoo to see and manage meetings from both "
-"platforms (updates go in both directions). This integration helps organize "
-"your schedule so you never miss a meeting."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9
-msgid ":doc:`/applications/general/auth/google`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:13
-msgid "Setup in Google"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:16
-msgid "Enable Google Calendar API"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18
-msgid ""
-"Begin by creating a new Google API project and enabling the Google Calendar "
-"API. Then, go to the `Google API Console "
-"<https://console.developers.google.com>`_ and log into your Google account."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22
-msgid ""
-"If this is your first time visiting this page, Google will prompt you to "
-"enter a country and agree to the Terms of Service. Select a country from the"
-" drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:26
-msgid ""
-"Next, click :guilabel:`Select a project` and select or create an API project"
-" to store credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Create a new API project to store credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:33
-msgid ""
-"Give the API Project a clear name like \"Odoo Sync\" so you can easily find "
-"it."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
-msgid ""
-"Then, open the API Project and click :guilabel:`Enable APIs and Services`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable APIs and Services on the API Project."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:41
-msgid ""
-"After that, search for *Google Calendar API* using the search bar and select"
-" :guilabel:`Google Calendar API` from the search results. Click "
-":guilabel:`Enable`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable the Google Calendar API."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:49
-msgid "Create credentials"
-msgstr "자격증명 생성"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51
-msgid ""
-"Now that you have created your API project and enabled the Google Calendar "
-"API, you need to create credentials. Begin by clicking :guilabel:`Create "
-"Credentials`. Google will then guide you through four steps to create your "
-"API credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
-msgid ""
-"In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google"
-" Calendar API` and :guilabel:`User Data` options. Then, click "
-":guilabel:`Next`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Select Google Calendar API and User Data for the Credential Type."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:62
-msgid ""
-"In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the "
-":guilabel:`App name` field, select your email address for the "
-":guilabel:`User support email` field, and type your email address for the "
-":guilabel:`Developer contact information` section. Then, click "
-":guilabel:`Save and Continue`."
-msgstr ""
-"두번째 단계로, :guilabel:`OAuth 동의 화면`의 메뉴에서 :guilabel:`앱 이름` 필드에 *Odoo* 를 입력하고, "
-":guilabel:`사용자 지원 이메일`필드에서 이메일 주소를 선택한 후, :guilabel:`개발자 연락처 정보` 항목에서 이메일 "
-"주소를 입력합니다. 그런 다음 :guilabel:`저장 후 계속하기`를 클릭합니다."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
-msgid ""
-"Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and "
-"Continue`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
-msgid ""
-"In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website "
-"application` for the :guilabel:`Application Type` field and type *My Odoo "
-"Database* for the :guilabel:`Name`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:72
-msgid ""
-"Under the :guilabel:`Authorized JavaScript Origins` section, click "
-":guilabel:`+ Add URI` and type your company's Odoo URL address."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
-msgid ""
-"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ "
-"Add URI` and type your company's Odoo URL address followed by "
-"*/google_account/authentication*. Finally, click :guilabel:`Create` and "
-":guilabel:`Done`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Add the authorized JavaScript origins and the authorized redirect URIs."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83
-msgid ""
-"After successfully creating a new API project, enabling the Google Calendar "
-"API, and generating the Google Calendar API credentials, you should now have"
-" a Client ID and Client Secret."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:87
-msgid "Client ID & Client Secret"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
-msgid ""
-"The **Client ID** and the **Client Secret** are both needed to connect "
-"Google Calendar to Odoo. Find the Client ID and the Client Secret by opening"
-" the Google Cloud Platform navigation menu and going to :menuselection:`API "
-"& Services --> Credentials --> OAuth 2.0 Client IDs`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:93
-msgid ""
-"Next, locate the credentials you just created for the Google Calendar API. "
-"Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page "
-"will redirect to the edit page, where you can view the Client ID and the "
-"Client Secret."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Click Edit OAuth Client to view the credential details."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:102
-msgid "Setup in Odoo"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:104
-msgid ""
-"Once the Client ID and the Client Secret are located, open the Odoo database"
-" and go to :menuselection:`Settings --> General Settings --> Integrations "
-"--> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "The Google Calendar checkbox in General Settings."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
-msgid ""
-"Next, copy and paste the Client ID and the Client Secret from the Google "
-"Calendar API Credentials page into their respective fields below the "
-":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:116
-msgid ""
-"Finally, open the Calendar module in Odoo and click on the "
-":guilabel:`Google` sync button to sync Google Calendar with Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Click the Google sync button in Odoo Calendar to sync Google Calendar with "
-"Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:124
-msgid ""
-"The first time you sync your Google Calendar with Odoo, the page will "
-"redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` "
-"to authorize Odoo to access Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Give Odoo permission to access Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:131
-msgid "Now, Odoo Calendar is successfully synced with Google Calendar!"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Successfully sync between Odoo and Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
-msgid "Synchronize Outlook Calendar with Odoo"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5
-msgid ""
-"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping "
-"track of their tasks and appointments across all related applications."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9
-msgid ":doc:`/applications/general/auth/azure`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:13
-msgid "Register the application with Microsoft Azure"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:15
-msgid ""
-"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account"
-" is needed. Creating an account is free for users who have never tried or "
-"paid for Azure. For more information, `click here "
-"<https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:19
-msgid ""
-"Refer to `Microsoft's documentation <https://docs.microsoft.com/en-"
-"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to"
-" set up an Azure AD Tenant (also called an *environment*), which is a "
-"representation of an organization to manage and register apps."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:23
-msgid ""
-"Then, `Register an Application <https://docs.microsoft.com/en-"
-"us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the "
-"appropriate :guilabel:`Supported account type`. Users who wish to connect "
-"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any "
-"organizational directory (Any Azure AD directory - Multitenant) and personal"
-" Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported "
-"account types`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:29
-msgid ""
-"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and "
-"copy the Odoo database URI (URL) followed by "
-"`/microsoft_account/authentication`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:33
-msgid ""
-"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` "
-"for the :guilabel:`Redirect URI`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid ""
-"The \"Supported account type\" and \"Redirect URI\" settings in the "
-"Microsoft Azure AD portal."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:40
-msgid ""
-"For more information on the restrictions and limitations of URIs, `check "
-"this page <https://docs. microsoft.com/en-us/azure/active-"
-"directory/develop/reply-url>`_."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:43
-msgid ""
-"Regarding the application credentials, the user *must* add a client secret, "
-"which allows Odoo to authenticate itself, requiring no interaction from the "
-"user's side. :guilabel:`Certificates` are optional."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:47
-msgid ""
-"To do add a client secret, click :guilabel:`Add a certificate or secret` and"
-" then click :guilabel:`New client secret`. Next, type a "
-":guilabel:`Description` and select when the client secret "
-":guilabel:`Expires`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:51
-msgid ""
-"Since resetting the synchronization can be tricky, Odoo recommends setting "
-"the maximum allowed expiration date for the client secret (24 months), so "
-"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to "
-"generate the client secret (:guilabel:`Secret ID`)."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:56
-msgid "Configuration in Odoo"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:58
-msgid ""
-"In the Odoo database, go to :menuselection:`Settings --> General Settings "
-"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook Calendar\" setting activated in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:65
-msgid ""
-"From the Microsoft Azure portal, under the :guilabel:`Overview` section of "
-"the application, copy the :guilabel:`Application (Client) ID`, and paste it "
-"into the :guilabel:`Client ID` field in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client ID\" in the Microsoft Azure portal."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:72
-msgid ""
-"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` "
-"section, copy the :guilabel:`Client Secret Value` and paste it into the "
-":guilabel:`Client Secret` field in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:79
-msgid ""
-"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, "
-"click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:84
-msgid "Sync with Outlook"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:88
-msgid ""
-"Odoo highly recommends testing the Outlook calendar synchronization on a "
-"test database and a test email address (that is not used for any other "
-"purpose) before attempting to sync the desired Outlook Calendar with the "
-"user's production database."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:92
-msgid ""
-"If the user has any past, present, or future events on their Odoo calendar "
-"before syncing their Outlook calendar, Outlook will treat the events pulled "
-"from Odoo's calendar during the sync as new events, causing an email "
-"notification to be sent from Outlook to all the event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:96
-msgid ""
-"To avoid unwanted emails being sent to all past, present, and future event "
-"attendees, the user must add the events from the Odoo calendar to the "
-"Outlook calendar before the first ever sync, delete the events from Odoo, "
-"and then start the sync."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:100
-msgid ""
-"Even after synchronizing the Odoo Calendar with the Outlook calendar, "
-"Outlook will still send a notification to all event participants every time "
-"an event is edited (created, deleted, unarchived, or event date/time "
-"changed), with no exceptions. This is a limitation that cannot be fixed from"
-" Odoo's side."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:105
-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/general/calendars/outlook/outlook_calendar.rst:112
-msgid ""
-"In summary, once a user synchronizes their Outlook calendar with the Odoo "
-"calendar:"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:114
-msgid ""
-"Creating an event in Odoo causes Outlook to send an invitation to all event "
-"attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:115
-msgid ""
-"Deleting an event in Odoo causes Outlook to send a cancellation to all event"
-" attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:116
-msgid ""
-"Unarchiving an event in Odoo causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:117
-msgid ""
-"Archiving an event in Odoo causes Outlook to send a cancellation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:118
-msgid ""
-"Adding a contact to an event causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:119
-msgid ""
-"Removing a contact from an event causes Outlook to send a cancellation to "
-"all event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:122
-msgid "Sync Odoo Calendar and Outlook"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:124
-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 ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook\" sync button in Odoo Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:132
-msgid ""
-"The synchronization is a two-way process, meaning that events are reconciled"
-" in both accounts (Outlook and Odoo)."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:136
-msgid ""
-"All users that want to use the synchronization simply need to :ref:`sync "
-"their calendar with Outlook <outlook_calendar/sync_with_outlook>`. The "
-"configuration of Microsoft's Azure account is only done once, as Azure AD "
-"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/general/calendars/outlook/outlook_calendar.rst:143
-msgid ":doc:`../../../productivity/mail_plugins/outlook`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:144
-msgid ":doc:`../google/google_calendar_credentials`"
-msgstr ""
-
 #: ../../content/applications/general/developer_mode.rst:5
 msgid "Developer Mode (debug mode)"
 msgstr ""
@@ -1976,11 +1479,11 @@ msgstr ""
 
 #: ../../content/applications/general/email_communication/email_servers.rst:3
 msgid "Send and receive emails in Odoo with an email server"
-msgstr ""
+msgstr "이메일 서버를 사용하여 Odoo에서 이메일 보내기 및 받기"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:6
 msgid "Odoo Online or Odoo.sh users"
-msgstr ""
+msgstr "Odoo 온라인 또는 Odoo.sh 사용자"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:8
 msgid ""
@@ -1988,6 +1491,8 @@ msgid ""
 "incoming emails already work out-of-the-box. So for **Odoo Online** and "
 "**Odoo.sh** customers, nothing needs to be configured!"
 msgstr ""
+"**Odoo에서는 데이터베이스용 자체 메일 서버를 운영**하고 있기 때문에, 이메일 수발신이 기본으로 설정되어 있습니다. 따라서 "
+"**Odoo 온라인** 및 **Odoo.sh** 고객들께서는 따로 관련 내용을 구성하실 필요가 없습니다!"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:12
 msgid ""
@@ -1995,6 +1500,8 @@ msgid ""
 "emails, simply use the standard online Odoo database normally since it has "
 "already been pre-configured to send email."
 msgstr ""
+"외부 메일 서버로 이메일 대량 발송을 하지 않는 한, 일반 이메일 발송용으로 이미 사전 구성이 완료되어 있으므로 표준 온라인 Odoo "
+"데이터베이스를 사용하시기만 하면 됩니다. "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:16
 msgid ""
@@ -2004,10 +1511,13 @@ msgid ""
 "conditions. See the :doc:`FAQ <faq>` or contact support for more "
 "information."
 msgstr ""
+"Odoo 서버는 악용을 막기 위한 목적으로 이메일에 일일 발송 한도를 적용하고 있습니다. 기본 제한 용량은 **엔터프라이즈** 구독 중인"
+" 데이터베이스의 경우 하루에 200개의 이메일을 전송할 수 있습니다. 특정한 상황의 경우에는 기본 사용 제한 용량을 늘리실 수 있습니다."
+" 자세한 내용은  :doc:`FAQ <faq>`를 참조하시거나 고객지원팀으로 문의하시기 바랍니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:22
 msgid "Scope of this documentation"
-msgstr ""
+msgstr "본 문서에서 다루고 있는 범위"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:24
 msgid ""
@@ -2017,12 +1527,15 @@ msgid ""
 "<https://www.odoo.sh>`_. Incoming and outgoing servers must be configured "
 "for on-premise databases."
 msgstr ""
+"이 문서는, `Odoo 온라인 <https://www.odoo. com/trial>`_ 및 `Odoo.sh "
+"<https://www.odoo.sh>`_ 과는 달리 Odoo에서 이메일을 통해서 솔루션을 즉시 확인할 수 없는 **Odoo 온프레미스 "
+"데이터베이스 전용**  문서입니다.  온프레미스 데이터베이스에 대해서 반드시 수발신 서버를 구성해야 합니다.. "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:29
 msgid ""
 "The following sections below contain information on how to integrate an "
 "external email server with Odoo."
-msgstr ""
+msgstr "아래의 섹션에서 외부 이메일 서버를 Odoo에 통합시키는 방법을 확인하실 수 있습니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:33
 msgid ""
@@ -2033,16 +1546,21 @@ msgid ""
 "manage the email server's reputation themselves. For more information see "
 ":doc:`Configure DNS records to send emails in Odoo <email_domain>`"
 msgstr ""
+"회사에서 이메일 서버를 관리하는 직원이 없는 경우, Odoo 온라인 및 Odoo.sh 를 사용하시는 것을 적극 권해드립니다. Odoo에서"
+" 호스팅하는 경우 이메일 수발신 기능이 즉시 작동할 뿐 아니라 관련 전문가들이 모니터링하게 됩니다. 그럼에도 불구하고 회사에서 이메일 "
+"서버를 직접 관리하고자 하는 경우 자체 이메일 서버를 사용할 수 있습니다. 자세한 내용은 :doc:` Odoo에서 이메일을 발송하기 위한"
+" DNS 레코드 구성 <email_domain>` 문서를 확인하시기 바랍니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:42
 msgid "Default notifications system"
-msgstr ""
+msgstr "기본 알림 시스템"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:44
 msgid ""
 "Documents in Odoo (such as a CRM opportunity, a sales order, an invoice, "
 "etc.) have a discussion thread, called *chatter*."
 msgstr ""
+"Odoo 문서 (CRM 영업기회, 판매발주서나 청구서 등)에는 관련 업무에 대해 논의한 내용을 담은 스레드인 *채터* 창이 있습니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:47
 msgid ""
@@ -2054,6 +1572,10 @@ msgid ""
 "in the chatter from their respective email, or as the name listed in their "
 "*Contacts* record."
 msgstr ""
+"데이터베이스를 사용하는 사용자가 대화창에 메시지를 남길 경우, 이 메시지는 알림으로 해당 문서의 팔로워들에게 이메일을 통해 전송됩니다 "
+"(발신자 제외). 팔로워가 메시지에 답신하게 되면 답신 내용이 대화창에 표시되며, Odoo에서는 알림 이메일을 팔로워들에게 추가로 "
+"전송하게 됩니다. 내외부 사용자들이 보내온 메시지는 해당 이메일의 대화창에 표시되거나 *연락처* 레코드에 저장되어 있는 이름으로 "
+"표시됩니다.  "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:53
 msgid ""
@@ -2061,10 +1583,12 @@ msgid ""
 "information see :ref:`Use a default email address "
 "<email_communication/default>`."
 msgstr ""
+"주소 정보를 기본 설정으로 하여 이러한 알림을 전송합니다. 자세한 내용은 :ref:`기본 이메일 주소 "
+"<email_communication/default>` 항목을 참고하시기 바랍니다. "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:57
 msgid "Manage outbound messages"
-msgstr ""
+msgstr "외부 발송 메시지 관리"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:59
 msgid ""
@@ -2075,6 +1599,10 @@ msgid ""
 " Odoo. Reference the SMTP data of the external email server. Once all the "
 "information has been filled out, click :guilabel:`Test Connection`."
 msgstr ""
+"시스템관리자로 Odoo 에서 :menuselection:`설정 --> 일반 설정 --> 메일 및 채팅` 메뉴로 이동합니다. "
+":guilabel:`저장`을 클릭합니다. :guilabel:`이메일 발신 서버`를 클릭 후 :guilabel:`생성` 메뉴를 이용하여 "
+"Odoo에서 새로운 메일 발신 서버를 생성합니다. 외부 이메일 서버의 SMTP 데이터를 참조 작성하십시오. 입력이 완료되면 "
+":guilabel:`테스트 접속`을 클릭하십시오."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:70
 msgid ""
@@ -2084,26 +1612,32 @@ msgid ""
 "(Domain Name System)` will improve deliverability. For more information see "
 ":doc:`email_domain`."
 msgstr ""
+"실행면에서 더 나은 품질을 위해 발신 도메인의 :abbr:`DNS (Domain Name System)`에 :abbr:`SPF "
+"(Sender Policy Framework)`, :abbr:`DKIM (DomainKeys Identified Mail)` 및 "
+":abbr:`DMARC (Domain-based Message Authentication, Reporting, & "
+"Conformance)`이 설정되어 있는지 확인하십시오. 자세한 내용은 :doc:`email_domain`을 참조하시기 바랍니다. "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:78
 msgid "Port restriction"
-msgstr ""
+msgstr "포트 제한"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:80
 msgid ""
 "Note that port 25 is blocked for security reasons on the Odoo Online and "
 "Odoo.sh platforms. Try using ports 465, 587, or 2525 instead."
 msgstr ""
+"Odoo 온라인 및 Odoo.sh 플랫폼에서는 보안상의 이유로 포트 25가 차단되어 있습니다. 포트 465, 587 또는 2525를 대신"
+" 사용하시기를 권합니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:86
 msgid "Use a default \"From\" email address"
-msgstr ""
+msgstr "\"보낸 사람\"에 기본 이메일 주소 사용하기"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:88
 msgid ""
 "Sometimes, an email's \"From\" (outgoing) address can belong to a different "
 "domain, and that can be a problem."
-msgstr ""
+msgstr "\"보낸 사람\" (외부 발신)의 이메일 주소가 도메인 주소와 다른 경우가 있는데, 때에 따라서 문제가 될 수 있습니다. "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:91
 msgid ""
@@ -2114,12 +1648,16 @@ msgid ""
 " security, the email that Odoo is trying to redistribute would get rejected "
 "by some recipients' email servers."
 msgstr ""
+"예를 들어, 이메일 주소가 `mary\\@customer.example.com` 인 고객이 메시지에 답신해온 경우에 Odoo에서는 "
+"스레드에 있는 다른 구독자들에게 동일한 이메일을 재전송하게 됩니다. 그러나, `customer.example.com` 도메인에서 해당 "
+"작업을 보안상의 이유로 금지하는 경우 Odoo에서 재전송하려는 이메일은 일부 수신자들의 이메일 서버에서 수신이 거부됩니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:96
 msgid ""
 "To avoid that problem, Odoo sends all emails using a \"From\" address from "
 "the same authorized domain."
 msgstr ""
+"이러한 문제를 방지하기 위해, Odoo에서는 이메일 전송 시 인증받은 동일 도메인에서 \"보낸사람\" 주소를 사용하도록 하고 있습니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:99
 msgid ""
@@ -2127,24 +1665,26 @@ msgid ""
 "<developer-mode>` and going to :menuselection:`Settings --> Technical --> "
 "Parameters --> System Parameters` menu."
 msgstr ""
+":ref:`개발자 모드 <developer-mode>를 활성화하여 :guilabel:`시스템 설정` 메뉴로 들어가서 "
+":menuselection:`설정 --> 기술 -->  --> 시스템 매개변수` 메뉴를 선택합니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:102
 msgid ""
 "To force the email address from which emails are sent, a combination of the "
 "following keys needs to be set in the system parameters of the database:"
-msgstr ""
+msgstr "이메일을 전송할 이메일 주소를 강제 지정하려면, 데이터베이스의 시스템 매개변수에 다음의 키 조합을 설정해야 합니다:"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:105
 msgid ""
 "`mail.default.from`: accepts the local part or a complete email address as "
 "value"
-msgstr ""
+msgstr "`mail.default.from`: 로컬 부분 또는 이메일 주소 전체를 값으로 허용합니다"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:106
 msgid ""
 "`mail.default.from_filter`: accepts a domain name or a full email address as"
 " value"
-msgstr ""
+msgstr "`mail.default.from_filter`: 도메인 이름이나 이메일 주소 전체를 값으로 허용합니다"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:109
 msgid ""
@@ -2152,6 +1692,8 @@ msgid ""
 "the default Odoo email server, otherwise this parameter can be set using the"
 " `from_filter` field on `ir.mail_server`."
 msgstr ""
+"`mail.default.from_filter` 은 `odoo-bin` 을 구성하거나 기본 Odoo 이메일 서버를 사용하는 경우에만 "
+"작동하며, 다른 경우 `ir.mail_server`의  `from_filter` 필드를 사용하여 해당 매개변수를 설정할 수 있습니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:112
 msgid ""
@@ -2160,6 +1702,9 @@ msgid ""
 "the email will be encapsulated using a combination of the two system "
 "parameters: `mail.default.from` and `mail.catchall.domain`."
 msgstr ""
+"도메인 이름이나 이메일 주소 전체를 필드에 사용할 수 있으며, 공란으로 둘 수도 있습니다. 이메일 발신 주소가 설정된 해당 필터와 "
+"일치하지 않는 경우 이메일은 `mail.default.from` 및 `mail.catchall.domain` 두 가지 시스템 매개변수 "
+"조합을 이용하여 저장됩니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:117
 msgid ""
@@ -2169,6 +1714,9 @@ msgid ""
 "in Odoo: ``“Admin” <admin@example.com>`` => ``“Admin” "
 "<notifications@mycompany.com>``."
 msgstr ""
+"다음 예시와 같이, 보낸사람의 이메일 주소는 두 개의 시스템 매개변수 (`mail.default.from` 및 "
+"`mail.catchall.domain`)를 조합하여 변경됩니다. 다음은 Odoo에서의 기본 알림 구성입니다. ``“어드민” "
+"<admin@example.com>`` => ``“어드민” <notifications@mycompany.com>``."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:122
 msgid ""
@@ -2177,6 +1725,9 @@ msgid ""
 "`mail.default.from` (if it contains a full email address) or a combination "
 "of `mail.default.from` and `mail.catchall.domain`."
 msgstr ""
+"즉 이메일 발신자 주소가 `mail.default.from_filter`와 일치하지 않는 경우, 해당 주소를 "
+"`mail.default.from` (전체 이메일 주소를 포함하는 경우) 또는  `mail.default.from` 및 "
+"`mail.catchall.domain`를 조합하여 변경시킵니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:126
 msgid ""
@@ -2185,10 +1736,12 @@ msgid ""
 "addresses that are different from `mail.default.from` will be encapsulated "
 "in `mail.default.from`."
 msgstr ""
+"`from_filter`에 전체 이메일 주소가 포함되어 있고 `mail.default.from`이 해당 주소와 동일한 경우에는, "
+"`mail.default.from`와 일치하지 않는 이메일은 모두 `mail.default.from`에 저장됩니다. "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:133
 msgid "Utilizing the \"From\" filter on an outgoing email server"
-msgstr ""
+msgstr "이메일 발신 서버에 \"보낸 사람\" 필터 활용하기 "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:135
 msgid ""
@@ -2201,6 +1754,11 @@ msgid ""
 "field in Odoo by navigating to :menuselection:`Settings --> Discuss --> "
 "Custom Mail Servers --> Outgoing Mail Servers --> New`."
 msgstr ""
+":guilabel:`보낸사람 필터` 필드를 사용하면 Odoo를 통해서 전송하는 :guilabel:`보낸사람` 이메일 주소나 도메인에 따라"
+" 특정 발송용 이메일 서버를 사용하도록 할 수 있습니다. 이렇게 설정함으로써 데이터베이스에서 보내는 이메일의 전달 가능성과 전송 성공률을"
+" 높일 수 있습니다.  :guilabel:`보낸사람 필터` 필터를 설정하면 여러 개의 회사가 운영되는 환경에서 다른 도메인으로 전송하는 "
+"경우에도 사용할 수 있습니다. :menuselection:`설정 --> 메일 및 채팅 --> 사용자 지정 메일 서버 --> 메일 발신 "
+"서버 --> 새로 만들기`로 이동하여 Odoo에서 해당 필드를 확인할 수 있습니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst-1
 msgid "Outgoing email server settings and the FROM filter settings."
@@ -2211,6 +1769,8 @@ msgid ""
 "When an email is sent from Odoo while the :guilabel:`FROM Filtering` field "
 "is set, an email server is chosen in the following sequence:"
 msgstr ""
+":guilabel:`보낸사람 필터` 필드가 설정된 상태에서 Odoo에서 이메일을 보낼 경우, 다음과 같은 순서로 이메일 서버가 "
+"선택됩니다. "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:149
 msgid ""
@@ -2220,6 +1780,10 @@ msgid ""
 "address) is `test\\@example.com`, only the email servers that have the "
 ":guilabel:`FROM Filtering` value equal to `test\\@example.com` are returned."
 msgstr ""
+"먼저, Odoo에서는 발신 이메일의 :guilabel:`보낸사람` 값 (이메일 주소)과 동일한 :guilabel:`보낸사람 필터` 값이 "
+"존재하는지 이메일 서버에서 검색합니다. 예를 들어, :guilabel:`보낸사람` 값 (이메일 주소)이 "
+"`test\\@example.com`인 경우, :guilabel:`보낸사람 필터` 값이 `test\\@example.com` 인 이메일 "
+"서버만이 표시됩니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:153
 msgid ""
@@ -2230,6 +1794,10 @@ msgid ""
 " the email servers that have the :guilabel:`FROM Filtering` value equal to "
 "`example.com` are returned."
 msgstr ""
+"그러나 :guilabel:`보낸사람` 값을 사용하는 이메일 서버가 검색되지 않는 경우에는 Odoo에서는 발신 이메일에서 사용된 "
+":guilabel:`보낸사람` 값 (이메일 주소)과 *도메인*이 동일한 이메일 서버를 검색하게 됩니다. 예를 들어, "
+":guilabel:`보낸사람` 이메일 주소가 `test\\@example.com`인 경우, :guilabel:`보낸사람 필터` 값이 "
+"`example.com`인 경우에만 해당 이메일 서버가 표시됩니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:159
 msgid ""
@@ -2237,6 +1805,8 @@ msgid ""
 "returns all email servers that do not have any :guilabel:`FROM Filtering` "
 "value(s) set."
 msgstr ""
+"도메인 확인 후에도 이메일 서버가 검색되지 않는 경우에, Odoo에서는 :guilabel:`보낸사람 필터` 값이 설정되어 있지 않은 "
+"이메일 서버 전체를 표시합니다.  "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:162
 msgid ""
@@ -2246,6 +1816,9 @@ msgid ""
 "attempts to find a match. If no email server is found, Odoo returns the "
 "first outgoing email server (sorted by priority)."
 msgstr ""
+"이 쿼리의 반환값이 없는 경우, Odoo에서는 시스템 매개변수인  `mail.default.from` 를 사용하여 이메일 서버를 "
+"검색합니다. 먼저 이메일 주소 목록에서 일치하는 이메일 서버를 확인한 후, 일치하는 도메인 정보를 검색합니다. 이메일 서버가 검색되지 "
+"않는 경우에 Odoo에서는 순서상 가장 첫번째인 이메일 발신 서버를 표시합니다 (우선순위에 따라 정렬)."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:168
 msgid ""
@@ -2254,10 +1827,12 @@ msgid ""
 "priority of `10` and the other with a priority of `20`, then the email "
 "server with a priority of `10` is used first."
 msgstr ""
+"검색된 이메일 서버가 여러 개인 경우에, Odoo에서는 가장 우선순위가 높은 서버를 사용합니다. 예를 들어, 우선순위가 `10`인 이메일"
+" 서버와 `20`인 서버 두 개가 있는 경우에, 우선순위 `10`인 이메일 서버를 먼저 사용합니다. "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:175
 msgid "Set up different dedicated servers for transactional and mass emails"
-msgstr ""
+msgstr "업무 이메일과 대량 발송 이메일을 각각의 전용 서버로 설정하기"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:177
 msgid ""
@@ -2266,6 +1841,9 @@ msgid ""
 " and Amazon SES, Mailgun, Sendgrid or :doc:`Mailjet "
 "</administration/maintain/mailjet_api>` for mass mailings."
 msgstr ""
+"Odoo에서 업무용 이메일과 대량 발송 메일을 구분하여 별도의 이메일 서버를 사용할 수 있습니다. 예를 들어, 업무 이메일에는 "
+"Postmark나 SendinBlue를 사용하고, 대량 발송 메일용으로는 Amazon SES, Mailgun, Sendgrid나 "
+":doc:`Mailjet </administration/maintain/mailjet_api>` 를 사용하도록 할 수 있습니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:182
 msgid ""
@@ -2273,6 +1851,8 @@ msgid ""
 "alternative one unless a specific external outgoing email server is needed "
 "for technical reasons."
 msgstr ""
+"발신 이메일 서버는 이미 기본으로 구성되어 있습니다. 기술적인 문제로 인해 외부의 특정 이메일 발신 서버가 필요한 경우를 제외하고 대체 "
+"서버를 생성하지 마십시오."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:185
 msgid ""
@@ -2283,6 +1863,10 @@ msgid ""
 "priority to the transactional server over the mass mailing server by "
 "providing a lower priority number for the transactional email server."
 msgstr ""
+"이렇게 하려면, 먼저  :ref:`개발자 모드<developer-mode>`를 활성화한 후 :menuselection:`설정 --> 기술"
+" --> 발신` 메일 서버 메뉴로 이동합니다. 해당 메뉴에서 발신용 이메일 서버에 대해서 두 가지 설정 항목을 생성합니다. 하나는 업무 "
+"이메일용으로, 다른 하나는 대량 발송용 서버입니다. 업무용 이메일 서버에 작은 숫자를 우선순위 번호로 부여하여 대량 메일 서버보다 업무용"
+" 서버가 우선적으로 사용할 수 있도록 합니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:191
 msgid ""
@@ -2293,6 +1877,10 @@ msgid ""
 " in this case, the domain's Sender Policy Framework (SPF) records must be "
 "set to include both transactional and mass mail servers."
 msgstr ""
+"이제 `이메일 마케팅 --> 설정`으로 이동하여 :guilabel:`전용 서버`를 활성화시킵니다. 알맞은 이메일 서버를 선택하십시오. "
+"해당 설정을 통하여 Odoo 에서 우선순위 번호가 낮은 서버는 업무용 이메일에 사용하고, 여기에서 선택한 서버는 대량 메일 발송용으로 "
+"사용하게 됩니다. 이 경우 업무용 및 대량 발송 메일 서버가 모두 포함될 수 있도록 도메인의 SPF (Sender Policy "
+"Framework) 레코드가 설정되어야 합니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:198
 msgid ":doc:`email_domain`"
@@ -2300,11 +1888,11 @@ msgstr ""
 
 #: ../../content/applications/general/email_communication/email_servers.rst:203
 msgid "Manage inbound messages"
-msgstr ""
+msgstr "수신 메시지 관리"
 
 #: ../../content/applications/general/email_communication/email_servers.rst:205
 msgid "Odoo relies on generic email aliases to fetch incoming messages."
-msgstr ""
+msgstr "Odoo에서는 일반 이메일의 계정 별칭을 사용하여 수신 메시지를 가져옵니다. "
 
 #: ../../content/applications/general/email_communication/email_servers.rst:207
 msgid ""
@@ -2316,6 +1904,10 @@ msgid ""
 "not have another action attached to it like other aliases might, it is only "
 "used to collect replies."
 msgstr ""
+"**응답 메시지**는 Odoo에서 보낸 메시지의 경우 전체 별칭(**catchall@**)이나 다른 별칭을 사용하는 모델의 경우 해당 "
+"모델 별칭을 통해 원래 논의가 계속되던 스레드 (및 팔로워 전체의 받은편지함)로 라우팅됩니다 . 사용자가 지정해놓은 계정 별칭이 없는 "
+"모델의 경우에는 전체 계정 별칭(`catchall@mycompany.odoo.com`)을 사용하여 회신하게 됩니다. 그러나 다른 계정 "
+"별칭과는 달리 전체 주소를 사용할 경우에는 다른 내용을 첨부할 수 없으며 응답 수집 목적으로만 사용할 수 있습니다."
 
 #: ../../content/applications/general/email_communication/email_servers.rst:212
 msgid ""
@@ -4652,7 +4244,7 @@ msgstr ""
 " 버튼을 클릭합니다. 개인 설정 메뉴에서 이전에 설치한 언어를 선택한 후 **저장** 을 선택하면 언어를 변경할 수 있습니다. "
 
 #: ../../content/applications/general/users/language.rst:61
-msgid ":doc:`../../websites/website/publish/translate`"
+msgid ":doc:`../../websites/website/configuration/translate`"
 msgstr ""
 
 #: ../../content/applications/general/users/manage_users.rst:3

locale/nl/LC_MESSAGES/general.po

@@ -19,7 +19,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:53+0000\n"
 "Last-Translator: Erwin van der Ploeg <erwin@odooexperts.nl>, 2023\n"
 "Language-Team: Dutch (https://app.transifex.com/odoo/teams/41243/nl/)\n"
@@ -335,11 +335,10 @@ msgid ""
 msgstr ""
 
 #: ../../content/applications/general/auth/azure.rst:9
-msgid ":doc:`/applications/general/calendars/outlook/outlook_calendar`"
+msgid ":doc:`../../productivity/calendar/outlook`"
 msgstr ""
 
 #: ../../content/applications/general/auth/azure.rst:10
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:67
 msgid ":doc:`/administration/maintain/azure_oauth`"
 msgstr ""
@@ -362,12 +361,10 @@ msgid ""
 msgstr ""
 
 #: ../../content/applications/general/auth/google.rst:12
-msgid ""
+msgid ":doc:`../../productivity/calendar/google`"
-":doc:`/applications/general/calendars/google/google_calendar_credentials`"
 msgstr ""
 
 #: ../../content/applications/general/auth/google.rst:13
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:66
 msgid ":doc:`/administration/maintain/google_oauth`"
 msgstr ""
@@ -602,497 +599,6 @@ msgid ""
 "left blanked, the admin profile will be used as template."
 msgstr ""
 
-#: ../../content/applications/general/calendars.rst:5
-msgid "Calendars"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:3
-msgid "Synchronize Google Calendar with Odoo"
-msgstr "Synchroniseer Google agenda met Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5
-msgid ""
-"Synchronize Google Calendar with Odoo to see and manage meetings from both "
-"platforms (updates go in both directions). This integration helps organize "
-"your schedule so you never miss a meeting."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9
-msgid ":doc:`/applications/general/auth/google`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:13
-msgid "Setup in Google"
-msgstr "Opzet in Google"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:16
-msgid "Enable Google Calendar API"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18
-msgid ""
-"Begin by creating a new Google API project and enabling the Google Calendar "
-"API. Then, go to the `Google API Console "
-"<https://console.developers.google.com>`_ and log into your Google account."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22
-msgid ""
-"If this is your first time visiting this page, Google will prompt you to "
-"enter a country and agree to the Terms of Service. Select a country from the"
-" drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:26
-msgid ""
-"Next, click :guilabel:`Select a project` and select or create an API project"
-" to store credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Create a new API project to store credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:33
-msgid ""
-"Give the API Project a clear name like \"Odoo Sync\" so you can easily find "
-"it."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
-msgid ""
-"Then, open the API Project and click :guilabel:`Enable APIs and Services`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable APIs and Services on the API Project."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:41
-msgid ""
-"After that, search for *Google Calendar API* using the search bar and select"
-" :guilabel:`Google Calendar API` from the search results. Click "
-":guilabel:`Enable`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable the Google Calendar API."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:49
-msgid "Create credentials"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51
-msgid ""
-"Now that you have created your API project and enabled the Google Calendar "
-"API, you need to create credentials. Begin by clicking :guilabel:`Create "
-"Credentials`. Google will then guide you through four steps to create your "
-"API credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
-msgid ""
-"In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google"
-" Calendar API` and :guilabel:`User Data` options. Then, click "
-":guilabel:`Next`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Select Google Calendar API and User Data for the Credential Type."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:62
-msgid ""
-"In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the "
-":guilabel:`App name` field, select your email address for the "
-":guilabel:`User support email` field, and type your email address for the "
-":guilabel:`Developer contact information` section. Then, click "
-":guilabel:`Save and Continue`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
-msgid ""
-"Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and "
-"Continue`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
-msgid ""
-"In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website "
-"application` for the :guilabel:`Application Type` field and type *My Odoo "
-"Database* for the :guilabel:`Name`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:72
-msgid ""
-"Under the :guilabel:`Authorized JavaScript Origins` section, click "
-":guilabel:`+ Add URI` and type your company's Odoo URL address."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
-msgid ""
-"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ "
-"Add URI` and type your company's Odoo URL address followed by "
-"*/google_account/authentication*. Finally, click :guilabel:`Create` and "
-":guilabel:`Done`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Add the authorized JavaScript origins and the authorized redirect URIs."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83
-msgid ""
-"After successfully creating a new API project, enabling the Google Calendar "
-"API, and generating the Google Calendar API credentials, you should now have"
-" a Client ID and Client Secret."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:87
-msgid "Client ID & Client Secret"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
-msgid ""
-"The **Client ID** and the **Client Secret** are both needed to connect "
-"Google Calendar to Odoo. Find the Client ID and the Client Secret by opening"
-" the Google Cloud Platform navigation menu and going to :menuselection:`API "
-"& Services --> Credentials --> OAuth 2.0 Client IDs`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:93
-msgid ""
-"Next, locate the credentials you just created for the Google Calendar API. "
-"Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page "
-"will redirect to the edit page, where you can view the Client ID and the "
-"Client Secret."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Click Edit OAuth Client to view the credential details."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:102
-msgid "Setup in Odoo"
-msgstr "Opzetten in Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:104
-msgid ""
-"Once the Client ID and the Client Secret are located, open the Odoo database"
-" and go to :menuselection:`Settings --> General Settings --> Integrations "
-"--> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "The Google Calendar checkbox in General Settings."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
-msgid ""
-"Next, copy and paste the Client ID and the Client Secret from the Google "
-"Calendar API Credentials page into their respective fields below the "
-":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:116
-msgid ""
-"Finally, open the Calendar module in Odoo and click on the "
-":guilabel:`Google` sync button to sync Google Calendar with Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Click the Google sync button in Odoo Calendar to sync Google Calendar with "
-"Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:124
-msgid ""
-"The first time you sync your Google Calendar with Odoo, the page will "
-"redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` "
-"to authorize Odoo to access Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Give Odoo permission to access Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:131
-msgid "Now, Odoo Calendar is successfully synced with Google Calendar!"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Successfully sync between Odoo and Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
-msgid "Synchronize Outlook Calendar with Odoo"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5
-msgid ""
-"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping "
-"track of their tasks and appointments across all related applications."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9
-msgid ":doc:`/applications/general/auth/azure`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:13
-msgid "Register the application with Microsoft Azure"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:15
-msgid ""
-"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account"
-" is needed. Creating an account is free for users who have never tried or "
-"paid for Azure. For more information, `click here "
-"<https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:19
-msgid ""
-"Refer to `Microsoft's documentation <https://docs.microsoft.com/en-"
-"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to"
-" set up an Azure AD Tenant (also called an *environment*), which is a "
-"representation of an organization to manage and register apps."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:23
-msgid ""
-"Then, `Register an Application <https://docs.microsoft.com/en-"
-"us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the "
-"appropriate :guilabel:`Supported account type`. Users who wish to connect "
-"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any "
-"organizational directory (Any Azure AD directory - Multitenant) and personal"
-" Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported "
-"account types`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:29
-msgid ""
-"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and "
-"copy the Odoo database URI (URL) followed by "
-"`/microsoft_account/authentication`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:33
-msgid ""
-"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` "
-"for the :guilabel:`Redirect URI`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid ""
-"The \"Supported account type\" and \"Redirect URI\" settings in the "
-"Microsoft Azure AD portal."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:40
-msgid ""
-"For more information on the restrictions and limitations of URIs, `check "
-"this page <https://docs. microsoft.com/en-us/azure/active-"
-"directory/develop/reply-url>`_."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:43
-msgid ""
-"Regarding the application credentials, the user *must* add a client secret, "
-"which allows Odoo to authenticate itself, requiring no interaction from the "
-"user's side. :guilabel:`Certificates` are optional."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:47
-msgid ""
-"To do add a client secret, click :guilabel:`Add a certificate or secret` and"
-" then click :guilabel:`New client secret`. Next, type a "
-":guilabel:`Description` and select when the client secret "
-":guilabel:`Expires`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:51
-msgid ""
-"Since resetting the synchronization can be tricky, Odoo recommends setting "
-"the maximum allowed expiration date for the client secret (24 months), so "
-"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to "
-"generate the client secret (:guilabel:`Secret ID`)."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:56
-msgid "Configuration in Odoo"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:58
-msgid ""
-"In the Odoo database, go to :menuselection:`Settings --> General Settings "
-"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook Calendar\" setting activated in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:65
-msgid ""
-"From the Microsoft Azure portal, under the :guilabel:`Overview` section of "
-"the application, copy the :guilabel:`Application (Client) ID`, and paste it "
-"into the :guilabel:`Client ID` field in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client ID\" in the Microsoft Azure portal."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:72
-msgid ""
-"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` "
-"section, copy the :guilabel:`Client Secret Value` and paste it into the "
-":guilabel:`Client Secret` field in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:79
-msgid ""
-"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, "
-"click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:84
-msgid "Sync with Outlook"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:88
-msgid ""
-"Odoo highly recommends testing the Outlook calendar synchronization on a "
-"test database and a test email address (that is not used for any other "
-"purpose) before attempting to sync the desired Outlook Calendar with the "
-"user's production database."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:92
-msgid ""
-"If the user has any past, present, or future events on their Odoo calendar "
-"before syncing their Outlook calendar, Outlook will treat the events pulled "
-"from Odoo's calendar during the sync as new events, causing an email "
-"notification to be sent from Outlook to all the event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:96
-msgid ""
-"To avoid unwanted emails being sent to all past, present, and future event "
-"attendees, the user must add the events from the Odoo calendar to the "
-"Outlook calendar before the first ever sync, delete the events from Odoo, "
-"and then start the sync."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:100
-msgid ""
-"Even after synchronizing the Odoo Calendar with the Outlook calendar, "
-"Outlook will still send a notification to all event participants every time "
-"an event is edited (created, deleted, unarchived, or event date/time "
-"changed), with no exceptions. This is a limitation that cannot be fixed from"
-" Odoo's side."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:105
-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/general/calendars/outlook/outlook_calendar.rst:112
-msgid ""
-"In summary, once a user synchronizes their Outlook calendar with the Odoo "
-"calendar:"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:114
-msgid ""
-"Creating an event in Odoo causes Outlook to send an invitation to all event "
-"attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:115
-msgid ""
-"Deleting an event in Odoo causes Outlook to send a cancellation to all event"
-" attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:116
-msgid ""
-"Unarchiving an event in Odoo causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:117
-msgid ""
-"Archiving an event in Odoo causes Outlook to send a cancellation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:118
-msgid ""
-"Adding a contact to an event causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:119
-msgid ""
-"Removing a contact from an event causes Outlook to send a cancellation to "
-"all event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:122
-msgid "Sync Odoo Calendar and Outlook"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:124
-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 ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook\" sync button in Odoo Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:132
-msgid ""
-"The synchronization is a two-way process, meaning that events are reconciled"
-" in both accounts (Outlook and Odoo)."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:136
-msgid ""
-"All users that want to use the synchronization simply need to :ref:`sync "
-"their calendar with Outlook <outlook_calendar/sync_with_outlook>`. The "
-"configuration of Microsoft's Azure account is only done once, as Azure AD "
-"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/general/calendars/outlook/outlook_calendar.rst:143
-msgid ":doc:`../../../productivity/mail_plugins/outlook`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:144
-msgid ":doc:`../google/google_calendar_credentials`"
-msgstr ""
-
 #: ../../content/applications/general/developer_mode.rst:5
 msgid "Developer Mode (debug mode)"
 msgstr ""
@@ -4705,7 +4211,7 @@ msgid ""
 msgstr ""
 
 #: ../../content/applications/general/users/language.rst:61
-msgid ":doc:`../../websites/website/publish/translate`"
+msgid ":doc:`../../websites/website/configuration/translate`"
 msgstr ""
 
 #: ../../content/applications/general/users/manage_users.rst:3

locale/nl/LC_MESSAGES/services.po

@@ -13,7 +13,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:54+0000\n"
 "Last-Translator: Martin Trigaux, 2023\n"
 "Language-Team: Dutch (https://app.transifex.com/odoo/teams/41243/nl/)\n"
@@ -361,80 +361,215 @@ msgstr ""
 "programs-640?fullscreen=1>`_"
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
-msgid "Allow customers to close their tickets"
+msgid "Closing tickets"
-msgstr "Sta klanten toe om hun tickets af te sluiten"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
 msgid ""
-"Allowing customers to close their own tickets gives them autonomy and "
+"Once work has been completed on a *Helpdesk* ticket in Odoo, there are "
-"minimizes misunderstandings around when an issue is considered solved or "
+"several ways it can be closed. Manually closing solved tickets keeps the "
-"not. This results in operational capacity for support teams, and higher "
+"pipeline up to date, while automatically closing inactive tickets prevents "
-"satisfaction for the customer."
+"unnecessary blocking issues. Allowing customers to close their own tickets "
-msgstr ""
+"minimizes confusion around whether an issue is considered solved or not. "
-
+"This results in increased operational capacity for support teams, and higher"
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:10
+" customer satisfaction."
-msgid "Enable ticket closing"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12
+msgid "Manually close solved tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
 msgid ""
-"Start by navigating to :menuselection:`Helpdesk --> Configuration --> "
+"As work on a ticket progresses, it is moved along to the next stage in the "
-"Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit`"
+"pipeline. Once the issue is solved, the ticket is moved to a *folded* stage."
-" and enable :guilabel:`Ticket closing` by checking the field box."
+" This marks the ticket as *closed*."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17
+msgid ""
+"To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and "
+"click on a team to open the pipeline. Hover over a stage's heading, and then"
+" click the gear icon that appears in the top-right corner of that stage's "
+"kanban column."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid "Ticket closing feature in Odoo Helpdesk."
+msgid ""
+"View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage"
+" option."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:19
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
 msgid ""
-"To designate which stage the ticket migrates to once it is closed, navigate "
+"Clicking the gear icon also displays the option to :guilabel:`Fold` the "
-"to the ticket pipeline by going to :menuselection:`Helpdesk --> Overview` "
+"stage. This setting folds the stage *temporarily* to simplify the kanban "
-"and clicking :guilabel:`Tickets` on the team's card."
+"view. This does *not* close the tickets in this stage. It also does not "
+"permanently fold the stage. If a stage needs to be folded so the tickets can"
+" be marked as closed, continue following the steps below."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:23
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
 msgid ""
-"There are two options: create a new Kanban stage or work with an existing "
+"From the menu that appears, select :guilabel:`Edit Stage`. This will open "
-"one. For both scenarios, click the :guilabel:`Settings (gear)` icon next to "
+"the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` "
-"the stage name, select :guilabel:`Edit Stage`, and enable :guilabel:`Closing"
+"towards the top of the window, and then :guilabel:`Save & Close` to confirm "
-" Stage`. After checking the field box, click :guilabel:`Save` to finish."
+"the changes. Now, tickets that reach this stage will be considered as "
+"*closed*."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:29
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
-msgid ""
+msgid "Stage settings page."
-"If a closing stage is not specified, by default, the ticket is moved to the "
-"last stage in the kanban. If more than one stage is set as a closing stage, "
-"the ticket is placed in the first closing stage column."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:33
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41
+msgid "Automatically close inactive tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43
 msgid ""
-"With the ticket closing settings now complete, customers can now view the "
+"Tickets that are inactive for a set period of time can be automatically "
-"option to :guilabel:`Close this ticket` when they log into their portal."
+"closed. At that point, they will be moved to a folded stage."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46
+msgid ""
+"Go to the team's settings page by going to :menuselection:`Helpdesk --> "
+"Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable"
+" :guilabel:`Automatic Closing`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
+msgid ""
+"If one of the team's stages is set to be folded in the kanban view, it will "
+"be the default selection in the :guilabel:`Move to Stage` field. If the team"
+" has more than one folded stage, the stage that occurs first in the pipeline"
+" will be the default. If no stage is folded, the default selection will be "
+"the last stage in the pipeline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54
+msgid ""
+"The :guilabel:`After days of inactivity` field defaults to `7`, but can be "
+"adjusted if necessary."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57
+msgid ""
+"The :guilabel:`After days of inactivity` field does **not** take the working"
+" calendar into account when tracking the amount of time a ticket has been "
+"inactive."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60
+msgid ""
+"If only certain stages should be used to track days of inactivity, they can "
+"be added to the :guilabel:`In Stages` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64
+msgid "A team's pipeline is created with the following stages:"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66
+msgid "`New`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67
+msgid "`In Progress`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68
+msgid "`Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69
+msgid "`Closed`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71
+msgid ""
+"Tickets can linger in the :guilabel:`Customer Feedback stage`, because once "
+"an issue is solved, customers may not respond immediately. At that point, "
+"the tickets can be closed automatically. However, tickets in the "
+":guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due "
+"to assignment or workload issues. Closing these tickets automatically would "
+"result in issues going unsolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
+msgid ""
+"Therefore, the :guilabel:`Automatic Closing` settings would be configured as"
+" below\\:\\"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
+msgid ":guilabel:`Automatic Closing`: *checked*"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
+msgid ":guilabel:`Move to Stage`: `Solved`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
+msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
+msgid ":guilabel:`In Stages`: `Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
+msgid "Example of Automatic Closing settings."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89
+msgid "Allow customers to close their own tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
+msgid ""
+"Enabling the :guilabel:`Closure by Customers` setting allows customers to "
+"close their own ticket(s) when they determine that their issue has been "
+"resolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94
+msgid ""
+"Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams`"
+" and select a team. On the team's settings page, scroll to the "
+":guilabel:`Self-Service` section and check the box for :guilabel:`Closure by"
+" Customers`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
+msgid "Customer closing setting in Odoo Helpdesk."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
+msgid ""
+"Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` "
+"button will be available for customers when they view their ticket through "
+"the customer portal."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
 msgid "Customer view of ticket closing in Odoo Helpdesk."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:40
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110
-msgid "Get reports on tickets closed by customers"
+msgid ""
+"Customers are able to view their tickets by clicking the :guilabel:`View the"
+" ticket` link they receive by email. The link is included in the "
+":guilabel:`Request Acknowledgment` template, which is added to the first "
+"stage of a team by default. This link does not require a customer to have "
+"access to the portal to view or respond to their ticket."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:42
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
 msgid ""
-"To analyze the tickets that have been closed by customers, go to "
+"Customers with access to the portal will be able to view their tickets under"
-":menuselection:`Helpdesk --> Reporting --> Tickets`. Then, click on the "
+" :menuselection:`My Account --> Tickets`."
-":guilabel:`Filters` menu and choose :guilabel:`Add Custom filter`. Next, set"
-" the custom filter parameters to :guilabel:`Closed by partner` and "
-":guilabel:`is true`. Finally, click :guilabel:`Apply`."
-msgstr ""
-
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid ""
-"Filter for tickets closed by customers on Odoo Helpdesk's reporting page."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview.rst:5
@@ -978,7 +1113,6 @@ msgid ""
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/ratings.rst:51
-#: ../../content/applications/services/helpdesk/overview/sla.rst:47
 msgid ":doc:`../advanced/close_tickets`"
 msgstr ":doc:`../advanced/close_tickets`"
 
@@ -1218,7 +1352,7 @@ msgid ""
 "The *Live Chat* feature allows website visitors to connect directly with a "
 "support agent or chatbot. During these conversations, *Helpdesk* tickets can"
 " be instantly created by using the :doc:`response command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk`."
+"</applications/websites/livechat/responses>` `/helpdesk`."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125
@@ -1469,10 +1603,9 @@ msgstr ""
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261
 msgid ""
 "During the conversation, an operator can use the shortcut :doc:`command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk` to create "
+"</applications/websites/livechat/responses>` `/helpdesk` to create a ticket "
-"a ticket without leaving the chat window. The transcript from the "
+"without leaving the chat window. The transcript from the conversation will "
-"conversation will be added to the new ticket, under the "
+"be added to the new ticket, under the :guilabel:`Description` tab."
-":guilabel:`Description` tab."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267
@@ -1533,7 +1666,7 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293
-msgid ":doc:`/applications/websites/livechat/overview/get_started`"
+msgid ":doc:`/applications/websites/livechat`"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/reports.rst:3
@@ -1670,97 +1803,302 @@ msgstr "Service Level Agreements (SLA)"
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:5
 msgid ""
-"Service Level Agreements (SLA) are commitments you make with your customers "
+"A Service Level Agreement (SLA) defines the level of service a customer can "
-"to outline how a service is delivered. It bolsters trust between you and "
+"expect from a supplier. SLAs provide a timeline that tells customers when "
-"your customers as it makes clear what needs to be done, to what standard, "
+"they can expect results, and keeps the support team on target."
-"and when."
 msgstr ""
-"Service Level Agreements (SLA) zijn toezeggingen die u met uw klanten "
-"aangaat om te beschrijven hoe een service wordt geleverd. Het versterkt het "
-"vertrouwen tussen u en uw klanten omdat het duidelijk maakt wat er moet "
-"gebeuren, volgens welke norm en wanneer."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:10
-msgid "Create your policies"
+msgid "Create a new SLA policy"
-msgstr "Maak uw beleid"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst:13
-msgid ""
-"First, enable the feature on the settings of the team you would like "
-"policies to be applied, going to :menuselection:`Helpdesk --> Configuration "
-"--> Helpdesk Teams`."
 msgstr ""
-"Schakel eerst de functie in op de instellingen van het team waarop u wilt "
-"dat het beleid wordt toegepast, ga naar :menuselection:`Helpdesk --> "
-"Configuratie --> Helpdeskteams`."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:15
+#: ../../content/applications/services/helpdesk/overview/sla.rst:12
 msgid ""
-"Create your policies through the team’s settings page or go to "
+"To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to "
-":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
+"the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`."
+" Select a team, scroll to the :guilabel:`Performance` section, and then "
+"check the selection box next to :guilabel:`SLA Policies` to enable it for "
+"that specific team."
 msgstr ""
-"Maak uw beleid via de instellingenpagina van het team of ga naar "
-":menuselection:`Helpdesk --> Configuratie --> SLA-beleid`."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
-msgid "View of an SLA form in Odoo Helpdesk"
+msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:23
+#: ../../content/applications/services/helpdesk/overview/sla.rst:22
 msgid ""
-"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
+"The value indicated next to the :guilabel:`Working Hours` field is used to "
-" a ticket needs to have for the policy to be applied."
+"determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. "
+"By default, this is determined by the value set in the :guilabel:`Company "
+"Working Hours` field under :menuselection:`Settings app --> Employees --> "
+"Work Organization`."
 msgstr ""
-"Kies voor welk **Team** het beleid relevant is en de **Minimumprioriteit** "
-"die een ticket moet hebben om het beleid toe te passen."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:27
 msgid ""
-"**Target** is the stage a ticket needs to reach within the period defined to"
+"To create a new policy, click the smart button on the team`s settings page "
-" satisfy the SLA. The period is based on the ticket’s creation date, and a "
+"or go to :menuselection:`Helpdesk -->  Configuration --> SLA Policies`, and "
-"deadline is set on the ticket’s form once it matches an SLA policy rule. If "
+"click :guilabel:`New`. Start by entering a :guilabel:`Title` and a "
-"a ticket has more than one policy applied to it, the closest deadline of all"
+":guilabel:`Description` for the new policy, and proceed to fill out the form"
-" SLAs is the one considered."
+" using the steps below."
 msgstr ""
-"**Doel** is het stadium dat een ticket moet bereiken binnen de gedefinieerde"
-" periode om aan de SLA te voldoen. De periode is gebaseerd op de "
-"aanmaakdatum van het ticket en er wordt een deadline ingesteld op het "
-"ticketformulier zodra het overeenkomt met een SLA-beleidsregel. Als op een "
-"ticket meer dan één beleid van toepassing is, is de dichtstbijzijnde "
-"deadline van alle SLA's degene die in overweging wordt genomen."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:29
+#: ../../content/applications/services/helpdesk/overview/sla.rst:33
+msgid "Define the criteria for an SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:35
 msgid ""
-"When a ticket has satisfied an SLA policy, the SLA tag appears in green and "
+"The :guilabel:`Criteria` section is used to identify what tickets this "
-"the deadline field is not shown anymore."
+"policy will be applied to. Fill out the following fields to adjust the "
-msgstr ""
+"selection criteria:"
-"Wanneer een ticket aan een SLA-beleid voldoet, wordt de SLA-tag groen "
-"weergegeven en wordt het deadlineveld niet meer weergegeven."
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst-1
-msgid "View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk"
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:37
+#: ../../content/applications/services/helpdesk/overview/sla.rst:38
-msgid "SLA Analysis"
+msgid ""
-msgstr "SLA-analyse"
+":guilabel:`Team`: a policy can only be applied to one team. *This field is "
+"required.*"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:39
 msgid ""
-"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply"
+":guilabel:`Priority`: the priority level for a ticket is identified by "
-" *Filters* and *Group by* to identify tickets that should be prioritized and"
+"selecting the number of stars representing the priority level on the kanban "
-" keep track of upcoming deadlines."
+"card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will "
+"only be applied once the priority level has been updated on the ticket to "
+"match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is"
+" made in this field, this policy will only apply to tickets marked as `Low "
+"Priority` (zero stars)."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:44
+msgid ""
+":guilabel:`Types`: ticket types can be helpful when indicating when a ticket"
+" is a customer question, that can be solved with a quick response, or an "
+"issue, that may require additional investigation. Multiple ticket types can "
+"be selected for this field. If no selection is made, this policy will apply "
+"to all ticket types."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:48
+msgid ""
+":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is "
+"about. Multiple tags can be applied to a single ticket."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:50
+msgid ""
+":guilabel:`Customers`: individual contacts or companies may be selected in "
+"this field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:51
+msgid ""
+":guilabel:`Sales Order Items`: this field is available only if a team has "
+"the *Timesheets* app enabled. This allows the ticket to tie directly to a "
+"specific line on a sales order, which must be indicated on the ticket in the"
+" :guilabel:`Sales Order Item` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:56
+msgid ""
+"Unless otherwise indicated, multiple selections can be made for each field. "
+"(i.e. multiple :guilabel:`Tags` can be included in a policy, but only one "
+":guilabel:`Priority` level)"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a blank SLA policy record"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:64
+msgid "Establish a target for an SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:66
+msgid ""
+"The :guilabel:`Target` is the stage a ticket needs to reach, and the time "
+"alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service "
+"Level Agreement)` policy. Any stage assigned to a team may be selected for "
+"the :guilabel:`Reach Stage` field. Time spent in stages selected in "
+":guilabel:`Excluding Stages` will not be included in the calculation of the "
+":abbr:`SLA (Service Level Agreement)` deadline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:73
+msgid ""
+"An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks "
+"the working time before a ticket is completed, and would have `Solved` as "
+"the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level "
+"Agreement)` was titled `2 Days to Start`, it tracks the working time before "
+"work on a ticket has begun, and would have `In Progress` as the "
+":guilabel:`Reach Stage`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:79
+msgid "Meeting SLA deadlines"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:81
+msgid ""
+"Once it is determined that a ticket fits the criteria of an :abbr:`SLA "
+"(Service Level Agreement)` policy, a deadline is calculated. The deadline is"
+" based on the creation date of the ticket, and the targeted working hours. "
+"The deadline is then added to the ticket, as well as a white tag indicating "
+"the name of the :abbr:`SLA (Service Level Agreement)` applied."
 msgstr ""
-"Ga naar :menuselectie:`Helpdesk --> Rapportage --> SLA Statusanalyse`. Pas "
-"*Filters* en *Groep op* toe om tickets te identificeren die prioriteit "
-"moeten krijgen en om de komende deadlines bij te houden."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
 msgid ""
-"View of the SLA status analysis page emphasizing the group by option in Odoo"
+"View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo"
 " Helpdesk"
 msgstr ""
 
+#: ../../content/applications/services/helpdesk/overview/sla.rst:91
+msgid ""
+"If a ticket fits the criteria for more than one :abbr:`SLA (Service Level "
+"Agreement)`, the earliest occurring deadline will be displayed on the "
+"ticket. Once that deadline has passed, the next deadline will be displayed."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:95
+msgid ""
+"Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the"
+" :abbr:`SLA (Service Level Agreement)` tag turns green, and the "
+":guilabel:`Deadline` field disappears from view on the."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:102
+msgid ""
+"If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket "
+"has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level "
+"Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level "
+"Agreement)` has failed, the red tag will stay on the ticket, even after the "
+"ticket is moved to the :guilabel:`Reach Stage`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid ""
+"View of a ticket's form with a failing and passing SLA in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:112
+msgid "Analyzing SLA performance"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:114
+msgid ""
+"The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA "
+"(Service Level Agreement)` is fulfilled, as well as the success rate of "
+"individual policies. Navigate to the report and corresponding pivot table by"
+" going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:120
+msgid "Using the Pivot view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:122
+msgid ""
+"By default, the report is displayed in a :guilabel:`Pivot` view, and is "
+"filtered to show the number of SLAs failed and the failure rate over the "
+"last 30 days, grouped by team."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:129
+msgid ""
+"To add the number of SLAs passed or in progress, click the "
+":guilabel:`Measures` button to reveal a drop-down menu of reporting "
+"criteria, and choose from the options available based on the measurements "
+"preferred. Whenever a measurement is picked, a check mark will appear in the"
+" drop-down menu to indicate that that measurement is included, and a "
+"corresponding new column will emerge in the pivot table to show the relevant"
+" calculations."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:135
+msgid ""
+"To add a group to a row or column, click the plus :guilabel:` + ` button "
+"next to :guilabel:`Total`, and then select one of the groups. To remove one,"
+" click the minus :guilabel:` - ` button and deselect."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:140
+msgid "Using the Graph view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:142
+msgid ""
+"The :guilabel:`Status Analysis` report can also be viewed as a "
+":guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between "
+"these views by selecting the appropriate icon at the top of the chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:148
+msgid "Bar Chart"
+msgstr "Staafdiagram"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in bar view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:154
+msgid "Line Chart"
+msgstr "Lijndiagram"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in line view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:160
+msgid "Pie Chart"
+msgstr "Taartdiagram"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in pie chart view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:167
+msgid ""
+"Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed "
+":guilabel:`Stacked`. This presents two or more groups to appear on top of "
+"each other instead of next to each other, making it easier to compare data."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:172
+msgid "Using the Cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:174
+msgid ""
+"The :guilabel:`Cohort` view is used to track the changes in data over a "
+"period of time. To display the :guilabel:`Status Analysis` report in a "
+":guilabel:`Cohort` view, click the icon in the top right corner above the "
+"chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:183
+msgid ":ref:`Reporting views <reporting/views>`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:184
+msgid ""
+":doc:`Allow customers to close their tickets "
+"</applications/services/helpdesk/advanced/close_tickets>`"
+msgstr ""
+
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5
 msgid "Timesheet and Invoice"
 msgstr "Urenstaat en factuur"

locale/pt_BR/LC_MESSAGES/general.po

@@ -6,8 +6,8 @@
 # Translators:
 # Marcio Nunes, 2023
 # Éder Brito <britoederr@gmail.com>, 2023
-# Luis Gustavo Almeida <luis.gustavo@kmee.com.br>, 2023
 # Luis Felipe Miléo <mileo@kmee.com.br>, 2023
+# Luis Gustavo Almeida <luis.gustavo@kmee.com.br>, 2023
 # Marcel Savegnago <marcel.savegnago@gmail.com>, 2023
 # Martin Trigaux, 2023
 # Marcos Rodrigues, 2023
@@ -18,7 +18,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:53+0000\n"
 "Last-Translator: Kevilyn Rosa, 2023\n"
 "Language-Team: Portuguese (Brazil) (https://app.transifex.com/odoo/teams/41243/pt_BR/)\n"
@@ -386,11 +386,10 @@ msgstr ""
 "momento."
 
 #: ../../content/applications/general/auth/azure.rst:9
-msgid ":doc:`/applications/general/calendars/outlook/outlook_calendar`"
+msgid ":doc:`../../productivity/calendar/outlook`"
 msgstr ""
 
 #: ../../content/applications/general/auth/azure.rst:10
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:67
 msgid ":doc:`/administration/maintain/azure_oauth`"
 msgstr ""
@@ -413,12 +412,10 @@ msgid ""
 msgstr ""
 
 #: ../../content/applications/general/auth/google.rst:12
-msgid ""
+msgid ":doc:`../../productivity/calendar/google`"
-":doc:`/applications/general/calendars/google/google_calendar_credentials`"
 msgstr ""
 
 #: ../../content/applications/general/auth/google.rst:13
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:66
 msgid ":doc:`/administration/maintain/google_oauth`"
 msgstr ""
@@ -664,499 +661,6 @@ msgstr ""
 "Em **Modelo de Usuário**, indique um modelo para os novos perfis criados. Se"
 " deixado em branco, o perfil de administrador será usado como modelo."
 
-#: ../../content/applications/general/calendars.rst:5
-msgid "Calendars"
-msgstr "Calendários"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:3
-msgid "Synchronize Google Calendar with Odoo"
-msgstr "Sincronizar o Google Calendar com o Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5
-msgid ""
-"Synchronize Google Calendar with Odoo to see and manage meetings from both "
-"platforms (updates go in both directions). This integration helps organize "
-"your schedule so you never miss a meeting."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9
-msgid ":doc:`/applications/general/auth/google`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:13
-msgid "Setup in Google"
-msgstr "Configuração no Google"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:16
-msgid "Enable Google Calendar API"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18
-msgid ""
-"Begin by creating a new Google API project and enabling the Google Calendar "
-"API. Then, go to the `Google API Console "
-"<https://console.developers.google.com>`_ and log into your Google account."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22
-msgid ""
-"If this is your first time visiting this page, Google will prompt you to "
-"enter a country and agree to the Terms of Service. Select a country from the"
-" drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:26
-msgid ""
-"Next, click :guilabel:`Select a project` and select or create an API project"
-" to store credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Create a new API project to store credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:33
-msgid ""
-"Give the API Project a clear name like \"Odoo Sync\" so you can easily find "
-"it."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
-msgid ""
-"Then, open the API Project and click :guilabel:`Enable APIs and Services`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable APIs and Services on the API Project."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:41
-msgid ""
-"After that, search for *Google Calendar API* using the search bar and select"
-" :guilabel:`Google Calendar API` from the search results. Click "
-":guilabel:`Enable`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable the Google Calendar API."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:49
-msgid "Create credentials"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51
-msgid ""
-"Now that you have created your API project and enabled the Google Calendar "
-"API, you need to create credentials. Begin by clicking :guilabel:`Create "
-"Credentials`. Google will then guide you through four steps to create your "
-"API credentials."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
-msgid ""
-"In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google"
-" Calendar API` and :guilabel:`User Data` options. Then, click "
-":guilabel:`Next`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Select Google Calendar API and User Data for the Credential Type."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:62
-msgid ""
-"In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the "
-":guilabel:`App name` field, select your email address for the "
-":guilabel:`User support email` field, and type your email address for the "
-":guilabel:`Developer contact information` section. Then, click "
-":guilabel:`Save and Continue`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
-msgid ""
-"Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and "
-"Continue`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
-msgid ""
-"In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website "
-"application` for the :guilabel:`Application Type` field and type *My Odoo "
-"Database* for the :guilabel:`Name`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:72
-msgid ""
-"Under the :guilabel:`Authorized JavaScript Origins` section, click "
-":guilabel:`+ Add URI` and type your company's Odoo URL address."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
-msgid ""
-"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ "
-"Add URI` and type your company's Odoo URL address followed by "
-"*/google_account/authentication*. Finally, click :guilabel:`Create` and "
-":guilabel:`Done`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Add the authorized JavaScript origins and the authorized redirect URIs."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83
-msgid ""
-"After successfully creating a new API project, enabling the Google Calendar "
-"API, and generating the Google Calendar API credentials, you should now have"
-" a Client ID and Client Secret."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:87
-msgid "Client ID & Client Secret"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
-msgid ""
-"The **Client ID** and the **Client Secret** are both needed to connect "
-"Google Calendar to Odoo. Find the Client ID and the Client Secret by opening"
-" the Google Cloud Platform navigation menu and going to :menuselection:`API "
-"& Services --> Credentials --> OAuth 2.0 Client IDs`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:93
-msgid ""
-"Next, locate the credentials you just created for the Google Calendar API. "
-"Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page "
-"will redirect to the edit page, where you can view the Client ID and the "
-"Client Secret."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Click Edit OAuth Client to view the credential details."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:102
-msgid "Setup in Odoo"
-msgstr "Configuração em Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:104
-msgid ""
-"Once the Client ID and the Client Secret are located, open the Odoo database"
-" and go to :menuselection:`Settings --> General Settings --> Integrations "
-"--> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "The Google Calendar checkbox in General Settings."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
-msgid ""
-"Next, copy and paste the Client ID and the Client Secret from the Google "
-"Calendar API Credentials page into their respective fields below the "
-":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:116
-msgid ""
-"Finally, open the Calendar module in Odoo and click on the "
-":guilabel:`Google` sync button to sync Google Calendar with Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Click the Google sync button in Odoo Calendar to sync Google Calendar with "
-"Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:124
-msgid ""
-"The first time you sync your Google Calendar with Odoo, the page will "
-"redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` "
-"to authorize Odoo to access Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Give Odoo permission to access Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:131
-msgid "Now, Odoo Calendar is successfully synced with Google Calendar!"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Successfully sync between Odoo and Google Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
-msgid "Synchronize Outlook Calendar with Odoo"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5
-msgid ""
-"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping "
-"track of their tasks and appointments across all related applications."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9
-msgid ":doc:`/applications/general/auth/azure`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:13
-msgid "Register the application with Microsoft Azure"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:15
-msgid ""
-"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account"
-" is needed. Creating an account is free for users who have never tried or "
-"paid for Azure. For more information, `click here "
-"<https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:19
-msgid ""
-"Refer to `Microsoft's documentation <https://docs.microsoft.com/en-"
-"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to"
-" set up an Azure AD Tenant (also called an *environment*), which is a "
-"representation of an organization to manage and register apps."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:23
-msgid ""
-"Then, `Register an Application <https://docs.microsoft.com/en-"
-"us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the "
-"appropriate :guilabel:`Supported account type`. Users who wish to connect "
-"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any "
-"organizational directory (Any Azure AD directory - Multitenant) and personal"
-" Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported "
-"account types`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:29
-msgid ""
-"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and "
-"copy the Odoo database URI (URL) followed by "
-"`/microsoft_account/authentication`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:33
-msgid ""
-"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` "
-"for the :guilabel:`Redirect URI`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid ""
-"The \"Supported account type\" and \"Redirect URI\" settings in the "
-"Microsoft Azure AD portal."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:40
-msgid ""
-"For more information on the restrictions and limitations of URIs, `check "
-"this page <https://docs. microsoft.com/en-us/azure/active-"
-"directory/develop/reply-url>`_."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:43
-msgid ""
-"Regarding the application credentials, the user *must* add a client secret, "
-"which allows Odoo to authenticate itself, requiring no interaction from the "
-"user's side. :guilabel:`Certificates` are optional."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:47
-msgid ""
-"To do add a client secret, click :guilabel:`Add a certificate or secret` and"
-" then click :guilabel:`New client secret`. Next, type a "
-":guilabel:`Description` and select when the client secret "
-":guilabel:`Expires`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:51
-msgid ""
-"Since resetting the synchronization can be tricky, Odoo recommends setting "
-"the maximum allowed expiration date for the client secret (24 months), so "
-"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to "
-"generate the client secret (:guilabel:`Secret ID`)."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:56
-msgid "Configuration in Odoo"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:58
-msgid ""
-"In the Odoo database, go to :menuselection:`Settings --> General Settings "
-"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook Calendar\" setting activated in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:65
-msgid ""
-"From the Microsoft Azure portal, under the :guilabel:`Overview` section of "
-"the application, copy the :guilabel:`Application (Client) ID`, and paste it "
-"into the :guilabel:`Client ID` field in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client ID\" in the Microsoft Azure portal."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:72
-msgid ""
-"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` "
-"section, copy the :guilabel:`Client Secret Value` and paste it into the "
-":guilabel:`Client Secret` field in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:79
-msgid ""
-"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, "
-"click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:84
-msgid "Sync with Outlook"
-msgstr "Sincronizar com Outlook"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:88
-msgid ""
-"Odoo highly recommends testing the Outlook calendar synchronization on a "
-"test database and a test email address (that is not used for any other "
-"purpose) before attempting to sync the desired Outlook Calendar with the "
-"user's production database."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:92
-msgid ""
-"If the user has any past, present, or future events on their Odoo calendar "
-"before syncing their Outlook calendar, Outlook will treat the events pulled "
-"from Odoo's calendar during the sync as new events, causing an email "
-"notification to be sent from Outlook to all the event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:96
-msgid ""
-"To avoid unwanted emails being sent to all past, present, and future event "
-"attendees, the user must add the events from the Odoo calendar to the "
-"Outlook calendar before the first ever sync, delete the events from Odoo, "
-"and then start the sync."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:100
-msgid ""
-"Even after synchronizing the Odoo Calendar with the Outlook calendar, "
-"Outlook will still send a notification to all event participants every time "
-"an event is edited (created, deleted, unarchived, or event date/time "
-"changed), with no exceptions. This is a limitation that cannot be fixed from"
-" Odoo's side."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:105
-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/general/calendars/outlook/outlook_calendar.rst:112
-msgid ""
-"In summary, once a user synchronizes their Outlook calendar with the Odoo "
-"calendar:"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:114
-msgid ""
-"Creating an event in Odoo causes Outlook to send an invitation to all event "
-"attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:115
-msgid ""
-"Deleting an event in Odoo causes Outlook to send a cancellation to all event"
-" attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:116
-msgid ""
-"Unarchiving an event in Odoo causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:117
-msgid ""
-"Archiving an event in Odoo causes Outlook to send a cancellation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:118
-msgid ""
-"Adding a contact to an event causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:119
-msgid ""
-"Removing a contact from an event causes Outlook to send a cancellation to "
-"all event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:122
-msgid "Sync Odoo Calendar and Outlook"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:124
-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 ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook\" sync button in Odoo Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:132
-msgid ""
-"The synchronization is a two-way process, meaning that events are reconciled"
-" in both accounts (Outlook and Odoo)."
-msgstr ""
-"A sincronização é um processo bidirecional, o que significa que os eventos "
-"são reconciliados em ambas as contas (Outlook e Odoo)."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:136
-msgid ""
-"All users that want to use the synchronization simply need to :ref:`sync "
-"their calendar with Outlook <outlook_calendar/sync_with_outlook>`. The "
-"configuration of Microsoft's Azure account is only done once, as Azure AD "
-"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/general/calendars/outlook/outlook_calendar.rst:143
-msgid ":doc:`../../../productivity/mail_plugins/outlook`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:144
-msgid ":doc:`../google/google_calendar_credentials`"
-msgstr ":doc:`../google/google_calendar_credentials`"
-
 #: ../../content/applications/general/developer_mode.rst:5
 msgid "Developer Mode (debug mode)"
 msgstr ""
@@ -4889,8 +4393,8 @@ msgstr ""
 "instalado anteriormente e clicar em **SALVAR.**"
 
 #: ../../content/applications/general/users/language.rst:61
-msgid ":doc:`../../websites/website/publish/translate`"
+msgid ":doc:`../../websites/website/configuration/translate`"
-msgstr ":doc:`../../websites/website/publish/translate`"
+msgstr ""
 
 #: ../../content/applications/general/users/manage_users.rst:3
 msgid "Manage users"

locale/pt_BR/LC_MESSAGES/services.po

@@ -14,7 +14,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:54+0000\n"
 "Last-Translator: Martin Trigaux, 2023\n"
 "Language-Team: Portuguese (Brazil) (https://app.transifex.com/odoo/teams/41243/pt_BR/)\n"
@@ -365,80 +365,215 @@ msgstr ""
 "programs-640?fullscreen=1>`_"
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
-msgid "Allow customers to close their tickets"
+msgid "Closing tickets"
-msgstr "Permitir aos clientes a fechar seus tickets"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
 msgid ""
-"Allowing customers to close their own tickets gives them autonomy and "
+"Once work has been completed on a *Helpdesk* ticket in Odoo, there are "
-"minimizes misunderstandings around when an issue is considered solved or "
+"several ways it can be closed. Manually closing solved tickets keeps the "
-"not. This results in operational capacity for support teams, and higher "
+"pipeline up to date, while automatically closing inactive tickets prevents "
-"satisfaction for the customer."
+"unnecessary blocking issues. Allowing customers to close their own tickets "
-msgstr ""
+"minimizes confusion around whether an issue is considered solved or not. "
-
+"This results in increased operational capacity for support teams, and higher"
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:10
+" customer satisfaction."
-msgid "Enable ticket closing"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12
+msgid "Manually close solved tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
 msgid ""
-"Start by navigating to :menuselection:`Helpdesk --> Configuration --> "
+"As work on a ticket progresses, it is moved along to the next stage in the "
-"Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit`"
+"pipeline. Once the issue is solved, the ticket is moved to a *folded* stage."
-" and enable :guilabel:`Ticket closing` by checking the field box."
+" This marks the ticket as *closed*."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17
+msgid ""
+"To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and "
+"click on a team to open the pipeline. Hover over a stage's heading, and then"
+" click the gear icon that appears in the top-right corner of that stage's "
+"kanban column."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid "Ticket closing feature in Odoo Helpdesk."
+msgid ""
+"View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage"
+" option."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:19
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
 msgid ""
-"To designate which stage the ticket migrates to once it is closed, navigate "
+"Clicking the gear icon also displays the option to :guilabel:`Fold` the "
-"to the ticket pipeline by going to :menuselection:`Helpdesk --> Overview` "
+"stage. This setting folds the stage *temporarily* to simplify the kanban "
-"and clicking :guilabel:`Tickets` on the team's card."
+"view. This does *not* close the tickets in this stage. It also does not "
+"permanently fold the stage. If a stage needs to be folded so the tickets can"
+" be marked as closed, continue following the steps below."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:23
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
 msgid ""
-"There are two options: create a new Kanban stage or work with an existing "
+"From the menu that appears, select :guilabel:`Edit Stage`. This will open "
-"one. For both scenarios, click the :guilabel:`Settings (gear)` icon next to "
+"the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` "
-"the stage name, select :guilabel:`Edit Stage`, and enable :guilabel:`Closing"
+"towards the top of the window, and then :guilabel:`Save & Close` to confirm "
-" Stage`. After checking the field box, click :guilabel:`Save` to finish."
+"the changes. Now, tickets that reach this stage will be considered as "
+"*closed*."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:29
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
-msgid ""
+msgid "Stage settings page."
-"If a closing stage is not specified, by default, the ticket is moved to the "
-"last stage in the kanban. If more than one stage is set as a closing stage, "
-"the ticket is placed in the first closing stage column."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:33
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41
+msgid "Automatically close inactive tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43
 msgid ""
-"With the ticket closing settings now complete, customers can now view the "
+"Tickets that are inactive for a set period of time can be automatically "
-"option to :guilabel:`Close this ticket` when they log into their portal."
+"closed. At that point, they will be moved to a folded stage."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46
+msgid ""
+"Go to the team's settings page by going to :menuselection:`Helpdesk --> "
+"Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable"
+" :guilabel:`Automatic Closing`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
+msgid ""
+"If one of the team's stages is set to be folded in the kanban view, it will "
+"be the default selection in the :guilabel:`Move to Stage` field. If the team"
+" has more than one folded stage, the stage that occurs first in the pipeline"
+" will be the default. If no stage is folded, the default selection will be "
+"the last stage in the pipeline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54
+msgid ""
+"The :guilabel:`After days of inactivity` field defaults to `7`, but can be "
+"adjusted if necessary."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57
+msgid ""
+"The :guilabel:`After days of inactivity` field does **not** take the working"
+" calendar into account when tracking the amount of time a ticket has been "
+"inactive."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60
+msgid ""
+"If only certain stages should be used to track days of inactivity, they can "
+"be added to the :guilabel:`In Stages` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64
+msgid "A team's pipeline is created with the following stages:"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66
+msgid "`New`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67
+msgid "`In Progress`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68
+msgid "`Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69
+msgid "`Closed`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71
+msgid ""
+"Tickets can linger in the :guilabel:`Customer Feedback stage`, because once "
+"an issue is solved, customers may not respond immediately. At that point, "
+"the tickets can be closed automatically. However, tickets in the "
+":guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due "
+"to assignment or workload issues. Closing these tickets automatically would "
+"result in issues going unsolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
+msgid ""
+"Therefore, the :guilabel:`Automatic Closing` settings would be configured as"
+" below\\:\\"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
+msgid ":guilabel:`Automatic Closing`: *checked*"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
+msgid ":guilabel:`Move to Stage`: `Solved`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
+msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
+msgid ":guilabel:`In Stages`: `Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
+msgid "Example of Automatic Closing settings."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89
+msgid "Allow customers to close their own tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
+msgid ""
+"Enabling the :guilabel:`Closure by Customers` setting allows customers to "
+"close their own ticket(s) when they determine that their issue has been "
+"resolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94
+msgid ""
+"Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams`"
+" and select a team. On the team's settings page, scroll to the "
+":guilabel:`Self-Service` section and check the box for :guilabel:`Closure by"
+" Customers`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
+msgid "Customer closing setting in Odoo Helpdesk."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
+msgid ""
+"Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` "
+"button will be available for customers when they view their ticket through "
+"the customer portal."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
 msgid "Customer view of ticket closing in Odoo Helpdesk."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:40
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110
-msgid "Get reports on tickets closed by customers"
+msgid ""
+"Customers are able to view their tickets by clicking the :guilabel:`View the"
+" ticket` link they receive by email. The link is included in the "
+":guilabel:`Request Acknowledgment` template, which is added to the first "
+"stage of a team by default. This link does not require a customer to have "
+"access to the portal to view or respond to their ticket."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:42
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
 msgid ""
-"To analyze the tickets that have been closed by customers, go to "
+"Customers with access to the portal will be able to view their tickets under"
-":menuselection:`Helpdesk --> Reporting --> Tickets`. Then, click on the "
+" :menuselection:`My Account --> Tickets`."
-":guilabel:`Filters` menu and choose :guilabel:`Add Custom filter`. Next, set"
-" the custom filter parameters to :guilabel:`Closed by partner` and "
-":guilabel:`is true`. Finally, click :guilabel:`Apply`."
-msgstr ""
-
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid ""
-"Filter for tickets closed by customers on Odoo Helpdesk's reporting page."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview.rst:5
@@ -981,7 +1116,6 @@ msgid ""
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/ratings.rst:51
-#: ../../content/applications/services/helpdesk/overview/sla.rst:47
 msgid ":doc:`../advanced/close_tickets`"
 msgstr "doc:`.../advanced/close_tickets`"
 
@@ -1221,7 +1355,7 @@ msgid ""
 "The *Live Chat* feature allows website visitors to connect directly with a "
 "support agent or chatbot. During these conversations, *Helpdesk* tickets can"
 " be instantly created by using the :doc:`response command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk`."
+"</applications/websites/livechat/responses>` `/helpdesk`."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125
@@ -1472,10 +1606,9 @@ msgstr ""
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261
 msgid ""
 "During the conversation, an operator can use the shortcut :doc:`command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk` to create "
+"</applications/websites/livechat/responses>` `/helpdesk` to create a ticket "
-"a ticket without leaving the chat window. The transcript from the "
+"without leaving the chat window. The transcript from the conversation will "
-"conversation will be added to the new ticket, under the "
+"be added to the new ticket, under the :guilabel:`Description` tab."
-":guilabel:`Description` tab."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267
@@ -1536,7 +1669,7 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293
-msgid ":doc:`/applications/websites/livechat/overview/get_started`"
+msgid ":doc:`/applications/websites/livechat`"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/reports.rst:3
@@ -1674,97 +1807,302 @@ msgstr "Acordos de Nível de Serviço (SLA)"
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:5
 msgid ""
-"Service Level Agreements (SLA) are commitments you make with your customers "
+"A Service Level Agreement (SLA) defines the level of service a customer can "
-"to outline how a service is delivered. It bolsters trust between you and "
+"expect from a supplier. SLAs provide a timeline that tells customers when "
-"your customers as it makes clear what needs to be done, to what standard, "
+"they can expect results, and keeps the support team on target."
-"and when."
 msgstr ""
-"Acordos de Nível de Serviço (SLA) são compromissos que você assume com seus "
-"clientes para delinear como um serviço é fornecido. Ele reforça a confiança "
-"entre você e seus clientes, pois deixa claro o que precisa ser feito, em que"
-" padrão e quando."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:10
-msgid "Create your policies"
+msgid "Create a new SLA policy"
-msgstr "Crie suas políticas"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst:13
-msgid ""
-"First, enable the feature on the settings of the team you would like "
-"policies to be applied, going to :menuselection:`Helpdesk --> Configuration "
-"--> Helpdesk Teams`."
 msgstr ""
-"Primeiro, habilite o recurso sobre as configurações da equipe que você "
-"gostaria que as políticas fossem aplicadas, indo para "
-":menuselection:`Helpdesk --> Configuration --> Helpdesk Teams'."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:15
+#: ../../content/applications/services/helpdesk/overview/sla.rst:12
 msgid ""
-"Create your policies through the team’s settings page or go to "
+"To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to "
-":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
+"the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`."
+" Select a team, scroll to the :guilabel:`Performance` section, and then "
+"check the selection box next to :guilabel:`SLA Policies` to enable it for "
+"that specific team."
 msgstr ""
-"Crie suas políticas através da página de configurações da equipe ou vá para "
-":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
-msgid "View of an SLA form in Odoo Helpdesk"
+msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:23
+#: ../../content/applications/services/helpdesk/overview/sla.rst:22
 msgid ""
-"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
+"The value indicated next to the :guilabel:`Working Hours` field is used to "
-" a ticket needs to have for the policy to be applied."
+"determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. "
+"By default, this is determined by the value set in the :guilabel:`Company "
+"Working Hours` field under :menuselection:`Settings app --> Employees --> "
+"Work Organization`."
 msgstr ""
-"Escolha para qual **equipa** a apólice é relevante e a **Prioridade Mínima**"
-" um ingresso necessário para que a apólice seja aplicada."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:27
 msgid ""
-"**Target** is the stage a ticket needs to reach within the period defined to"
+"To create a new policy, click the smart button on the team`s settings page "
-" satisfy the SLA. The period is based on the ticket’s creation date, and a "
+"or go to :menuselection:`Helpdesk -->  Configuration --> SLA Policies`, and "
-"deadline is set on the ticket’s form once it matches an SLA policy rule. If "
+"click :guilabel:`New`. Start by entering a :guilabel:`Title` and a "
-"a ticket has more than one policy applied to it, the closest deadline of all"
+":guilabel:`Description` for the new policy, and proceed to fill out the form"
-" SLAs is the one considered."
+" using the steps below."
 msgstr ""
-"**Target** é o estágio que um bilhete precisa alcançar dentro do período "
-"definido para satisfazer o SLA. O período é baseado na data de criação do "
-"ingresso, e um prazo é estabelecido no formulário do ingresso uma vez que "
-"ele corresponda a uma regra da política do SLA. Se um ingresso tem mais de "
-"uma política aplicada a ele, o prazo mais próximo de todos os SLAs é o prazo"
-" considerado."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:29
+#: ../../content/applications/services/helpdesk/overview/sla.rst:33
+msgid "Define the criteria for an SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:35
 msgid ""
-"When a ticket has satisfied an SLA policy, the SLA tag appears in green and "
+"The :guilabel:`Criteria` section is used to identify what tickets this "
-"the deadline field is not shown anymore."
+"policy will be applied to. Fill out the following fields to adjust the "
-msgstr ""
+"selection criteria:"
-"Quando um bilhete tiver satisfeito uma política SLA, a etiqueta SLA aparece "
-"em verde e o campo de prazo não é mais exibido."
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst-1
-msgid "View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk"
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:37
+#: ../../content/applications/services/helpdesk/overview/sla.rst:38
-msgid "SLA Analysis"
+msgid ""
-msgstr "Análise de SLA"
+":guilabel:`Team`: a policy can only be applied to one team. *This field is "
+"required.*"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:39
 msgid ""
-"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply"
+":guilabel:`Priority`: the priority level for a ticket is identified by "
-" *Filters* and *Group by* to identify tickets that should be prioritized and"
+"selecting the number of stars representing the priority level on the kanban "
-" keep track of upcoming deadlines."
+"card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will "
+"only be applied once the priority level has been updated on the ticket to "
+"match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is"
+" made in this field, this policy will only apply to tickets marked as `Low "
+"Priority` (zero stars)."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:44
+msgid ""
+":guilabel:`Types`: ticket types can be helpful when indicating when a ticket"
+" is a customer question, that can be solved with a quick response, or an "
+"issue, that may require additional investigation. Multiple ticket types can "
+"be selected for this field. If no selection is made, this policy will apply "
+"to all ticket types."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:48
+msgid ""
+":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is "
+"about. Multiple tags can be applied to a single ticket."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:50
+msgid ""
+":guilabel:`Customers`: individual contacts or companies may be selected in "
+"this field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:51
+msgid ""
+":guilabel:`Sales Order Items`: this field is available only if a team has "
+"the *Timesheets* app enabled. This allows the ticket to tie directly to a "
+"specific line on a sales order, which must be indicated on the ticket in the"
+" :guilabel:`Sales Order Item` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:56
+msgid ""
+"Unless otherwise indicated, multiple selections can be made for each field. "
+"(i.e. multiple :guilabel:`Tags` can be included in a policy, but only one "
+":guilabel:`Priority` level)"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a blank SLA policy record"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:64
+msgid "Establish a target for an SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:66
+msgid ""
+"The :guilabel:`Target` is the stage a ticket needs to reach, and the time "
+"alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service "
+"Level Agreement)` policy. Any stage assigned to a team may be selected for "
+"the :guilabel:`Reach Stage` field. Time spent in stages selected in "
+":guilabel:`Excluding Stages` will not be included in the calculation of the "
+":abbr:`SLA (Service Level Agreement)` deadline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:73
+msgid ""
+"An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks "
+"the working time before a ticket is completed, and would have `Solved` as "
+"the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level "
+"Agreement)` was titled `2 Days to Start`, it tracks the working time before "
+"work on a ticket has begun, and would have `In Progress` as the "
+":guilabel:`Reach Stage`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:79
+msgid "Meeting SLA deadlines"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:81
+msgid ""
+"Once it is determined that a ticket fits the criteria of an :abbr:`SLA "
+"(Service Level Agreement)` policy, a deadline is calculated. The deadline is"
+" based on the creation date of the ticket, and the targeted working hours. "
+"The deadline is then added to the ticket, as well as a white tag indicating "
+"the name of the :abbr:`SLA (Service Level Agreement)` applied."
 msgstr ""
-"Ir para :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis'. "
-"Aplique *Filtros* e *Grupos por* para identificar os bilhetes que devem ser "
-"priorizados e acompanhar os próximos prazos."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
 msgid ""
-"View of the SLA status analysis page emphasizing the group by option in Odoo"
+"View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo"
 " Helpdesk"
 msgstr ""
 
+#: ../../content/applications/services/helpdesk/overview/sla.rst:91
+msgid ""
+"If a ticket fits the criteria for more than one :abbr:`SLA (Service Level "
+"Agreement)`, the earliest occurring deadline will be displayed on the "
+"ticket. Once that deadline has passed, the next deadline will be displayed."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:95
+msgid ""
+"Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the"
+" :abbr:`SLA (Service Level Agreement)` tag turns green, and the "
+":guilabel:`Deadline` field disappears from view on the."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:102
+msgid ""
+"If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket "
+"has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level "
+"Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level "
+"Agreement)` has failed, the red tag will stay on the ticket, even after the "
+"ticket is moved to the :guilabel:`Reach Stage`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid ""
+"View of a ticket's form with a failing and passing SLA in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:112
+msgid "Analyzing SLA performance"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:114
+msgid ""
+"The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA "
+"(Service Level Agreement)` is fulfilled, as well as the success rate of "
+"individual policies. Navigate to the report and corresponding pivot table by"
+" going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:120
+msgid "Using the Pivot view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:122
+msgid ""
+"By default, the report is displayed in a :guilabel:`Pivot` view, and is "
+"filtered to show the number of SLAs failed and the failure rate over the "
+"last 30 days, grouped by team."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:129
+msgid ""
+"To add the number of SLAs passed or in progress, click the "
+":guilabel:`Measures` button to reveal a drop-down menu of reporting "
+"criteria, and choose from the options available based on the measurements "
+"preferred. Whenever a measurement is picked, a check mark will appear in the"
+" drop-down menu to indicate that that measurement is included, and a "
+"corresponding new column will emerge in the pivot table to show the relevant"
+" calculations."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:135
+msgid ""
+"To add a group to a row or column, click the plus :guilabel:` + ` button "
+"next to :guilabel:`Total`, and then select one of the groups. To remove one,"
+" click the minus :guilabel:` - ` button and deselect."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:140
+msgid "Using the Graph view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:142
+msgid ""
+"The :guilabel:`Status Analysis` report can also be viewed as a "
+":guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between "
+"these views by selecting the appropriate icon at the top of the chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:148
+msgid "Bar Chart"
+msgstr "Gráfico de Barras"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in bar view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:154
+msgid "Line Chart"
+msgstr "Gráfico de linha"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in line view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:160
+msgid "Pie Chart"
+msgstr "Gráfico de Pizza"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in pie chart view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:167
+msgid ""
+"Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed "
+":guilabel:`Stacked`. This presents two or more groups to appear on top of "
+"each other instead of next to each other, making it easier to compare data."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:172
+msgid "Using the Cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:174
+msgid ""
+"The :guilabel:`Cohort` view is used to track the changes in data over a "
+"period of time. To display the :guilabel:`Status Analysis` report in a "
+":guilabel:`Cohort` view, click the icon in the top right corner above the "
+"chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:183
+msgid ":ref:`Reporting views <reporting/views>`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:184
+msgid ""
+":doc:`Allow customers to close their tickets "
+"</applications/services/helpdesk/advanced/close_tickets>`"
+msgstr ""
+
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5
 msgid "Timesheet and Invoice"
 msgstr "Folha de horas de trabalho e fatura"

locale/ro/LC_MESSAGES/general.po

@@ -14,7 +14,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:53+0000\n"
 "Last-Translator: Foldi Robert <foldirobert@nexterp.ro>, 2023\n"
 "Language-Team: Romanian (https://app.transifex.com/odoo/teams/41243/ro/)\n"
@@ -418,11 +418,10 @@ msgstr ""
 "OAuth Microsoft Azure NU este compatibilă cu Odoo în acest moment."
 
 #: ../../content/applications/general/auth/azure.rst:9
-msgid ":doc:`/applications/general/calendars/outlook/outlook_calendar`"
+msgid ":doc:`../../productivity/calendar/outlook`"
 msgstr ""
 
 #: ../../content/applications/general/auth/azure.rst:10
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:67
 msgid ":doc:`/administration/maintain/azure_oauth`"
 msgstr ""
@@ -450,12 +449,10 @@ msgstr ""
 "Odoo cu conturile Google."
 
 #: ../../content/applications/general/auth/google.rst:12
-msgid ""
+msgid ":doc:`../../productivity/calendar/google`"
-":doc:`/applications/general/calendars/google/google_calendar_credentials`"
 msgstr ""
 
 #: ../../content/applications/general/auth/google.rst:13
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:66
 msgid ":doc:`/administration/maintain/google_oauth`"
 msgstr ""
@@ -737,675 +734,6 @@ msgstr ""
 "În **Șablon utilizator**, indicați un șablon pentru profilele noi create. "
 "Dacă este lăsat gol, profilul admin va fi utilizat ca șablon."
 
-#: ../../content/applications/general/calendars.rst:5
-msgid "Calendars"
-msgstr "Calendar"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:3
-msgid "Synchronize Google Calendar with Odoo"
-msgstr "Sincronizați Google Calendar cu Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5
-msgid ""
-"Synchronize Google Calendar with Odoo to see and manage meetings from both "
-"platforms (updates go in both directions). This integration helps organize "
-"your schedule so you never miss a meeting."
-msgstr ""
-"Sincronizați Google Calendar cu Odoo pentru a vedea și gestiona întâlnirile "
-"de pe ambele platforme (actualizările merg în ambele direcții). Această "
-"integrare vă ajută să organizați programul dvs. astfel încât să nu ratați "
-"niciodată o întâlnire."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9
-msgid ":doc:`/applications/general/auth/google`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:13
-msgid "Setup in Google"
-msgstr "Configurare în Google"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:16
-msgid "Enable Google Calendar API"
-msgstr "Activați API-ul Google Calendar"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18
-msgid ""
-"Begin by creating a new Google API project and enabling the Google Calendar "
-"API. Then, go to the `Google API Console "
-"<https://console.developers.google.com>`_ and log into your Google account."
-msgstr ""
-"Începeți prin crearea unui nou proiect API Google și activarea API-ului "
-"Google Calendar. Apoi, mergeți la `Google API Console "
-"<https://console.developers.google.com>`_ și conectați-vă la contul dvs. "
-"Google."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22
-msgid ""
-"If this is your first time visiting this page, Google will prompt you to "
-"enter a country and agree to the Terms of Service. Select a country from the"
-" drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
-msgstr ""
-"Dacă vizitați prima dată această pagină, Google vă va solicita să "
-"introduceți un țară și să acceptați Termenii de utilizare. Selectați o țară "
-"din lista și acceptați :abbr:`ToS (Termenii de utilizare)`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:26
-msgid ""
-"Next, click :guilabel:`Select a project` and select or create an API project"
-" to store credentials."
-msgstr ""
-"În continuare, faceți clic pe :guilabel:`Selectați un proiect` și selectați "
-"sau creați un proiect API pentru a stoca credențialele."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Create a new API project to store credentials."
-msgstr "Creați un nou proiect API pentru a stoca credențialele."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:33
-msgid ""
-"Give the API Project a clear name like \"Odoo Sync\" so you can easily find "
-"it."
-msgstr ""
-"Dați un nume clar proiectului API, de exemplu \"Odoo Sync\", astfel încât să"
-" puteți găsi ușor."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
-msgid ""
-"Then, open the API Project and click :guilabel:`Enable APIs and Services`."
-msgstr ""
-"Apoi, deschideți proiectul API și faceți clic pe :guilabel:`Activați API-"
-"urile și serviciile`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable APIs and Services on the API Project."
-msgstr "Activați API-urile și serviciile pe proiectul API."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:41
-msgid ""
-"After that, search for *Google Calendar API* using the search bar and select"
-" :guilabel:`Google Calendar API` from the search results. Click "
-":guilabel:`Enable`."
-msgstr ""
-"După aceea, căutați *Google Calendar API* folosind bara de căutare și "
-"selectați :guilabel:`Google Calendar API` din rezultatele căutării. Faceți "
-"clic pe :guilabel:`Activați`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable the Google Calendar API."
-msgstr "Activați API-ul Google Calendar."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:49
-msgid "Create credentials"
-msgstr "Creați credențiale"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51
-msgid ""
-"Now that you have created your API project and enabled the Google Calendar "
-"API, you need to create credentials. Begin by clicking :guilabel:`Create "
-"Credentials`. Google will then guide you through four steps to create your "
-"API credentials."
-msgstr ""
-"Acum că ați creat proiectul API și ați activat API-ul Google Calendar, "
-"trebuie să creați credențiale. Începeți prin a face clic pe "
-":guilabel:`Creați credențiale`. Google vă va ghida prin patru pași pentru a "
-"crea credențialele API."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
-msgid ""
-"In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google"
-" Calendar API` and :guilabel:`User Data` options. Then, click "
-":guilabel:`Next`."
-msgstr ""
-"În primul pas, :guilabel:`Tipul credențialei`, selectați opțiunile "
-":guilabel:`Google Calendar API` și :guilabel:`Datele utilizatorului`. Apoi, "
-"faceți clic pe :guilabel:`Următorul`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Select Google Calendar API and User Data for the Credential Type."
-msgstr ""
-"Selectați Google Calendar API și Datele utilizatorului pentru tipul de "
-"credențiale."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:62
-msgid ""
-"In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the "
-":guilabel:`App name` field, select your email address for the "
-":guilabel:`User support email` field, and type your email address for the "
-":guilabel:`Developer contact information` section. Then, click "
-":guilabel:`Save and Continue`."
-msgstr ""
-"În al doilea pas, :guilabel:`Ecranul de consimțământ OAuth`, introduceți "
-"*Odoo* în câmpul :guilabel:`Numele aplicației`, selectați adresa dvs. de "
-"e-mail pentru câmpul :guilabel:`E-mail de asistență pentru utilizator`, și "
-"introduceți adresa dvs. de e-mail pentru secțiunea :guilabel:`Informații de "
-"contact pentru dezvoltatori`. Apoi, faceți clic pe :guilabel:`Salvați și "
-"continuați`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
-msgid ""
-"Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and "
-"Continue`."
-msgstr ""
-"Omiteți al treilea pas, :guilabel:`Scopuri`, făcând clic pe "
-":guilabel:`Salvați și continuați`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
-msgid ""
-"In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website "
-"application` for the :guilabel:`Application Type` field and type *My Odoo "
-"Database* for the :guilabel:`Name`."
-msgstr ""
-"În ultimul pas, :guilabel:`ID-ul clientului OAuth`, selectați "
-":guilabel:`Aplicație web` pentru câmpul :guilabel:`Tipul aplicației` și "
-"introduceți *Baza mea de date Odoo* pentru :guilabel:`Nume`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:72
-msgid ""
-"Under the :guilabel:`Authorized JavaScript Origins` section, click "
-":guilabel:`+ Add URI` and type your company's Odoo URL address."
-msgstr ""
-"În secțiune :guilabel:`Origini JavaScript autorizate`, faceți clic pe "
-":guilabel:`+ Adăugați URI` și introduceți adresa URL Odoo a companiei dvs."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
-msgid ""
-"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ "
-"Add URI` and type your company's Odoo URL address followed by "
-"*/google_account/authentication*. Finally, click :guilabel:`Create` and "
-":guilabel:`Done`."
-msgstr ""
-"În secțiunea :guilabel:`Redirect URI-uri autorizate`, faceți clic pe "
-":guilabel:`+ Adăugați URI` și introduceți adresa URL Odoo a companiei dvs. "
-"urmată de*/google_account/authentication*. În cele din urmă, faceți clic pe "
-":guilabel:`Creați` și :guilabel:`Gata`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Add the authorized JavaScript origins and the authorized redirect URIs."
-msgstr ""
-"Adăugați originile JavaScript autorizate și redirecturile URI-uri "
-"autorizate."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83
-msgid ""
-"After successfully creating a new API project, enabling the Google Calendar "
-"API, and generating the Google Calendar API credentials, you should now have"
-" a Client ID and Client Secret."
-msgstr ""
-"După ce ați creat cu succes un nou proiect API, ați activat API-ul Google "
-"Calendar și ați generat credențialele API Google Calendar, acum ar trebui să"
-" aveți un ID de client și un secret de client."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:87
-msgid "Client ID & Client Secret"
-msgstr "Client ID & Client Secret"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
-msgid ""
-"The **Client ID** and the **Client Secret** are both needed to connect "
-"Google Calendar to Odoo. Find the Client ID and the Client Secret by opening"
-" the Google Cloud Platform navigation menu and going to :menuselection:`API "
-"& Services --> Credentials --> OAuth 2.0 Client IDs`."
-msgstr ""
-"**Client ID** și **Client Secret** sunt ambele necesare pentru conectarea "
-"Google Calendar la Odoo. Găsiți Client ID și Client Secret deschizând meniul"
-" de navigare Google Cloud Platform și mergând la :menuselection:`API & "
-"Servicii --> Credențiale --> ID-uri client OAuth 2.0`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:93
-msgid ""
-"Next, locate the credentials you just created for the Google Calendar API. "
-"Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page "
-"will redirect to the edit page, where you can view the Client ID and the "
-"Client Secret."
-msgstr ""
-"În continuare, localizați credențialele pe care tocmai le-ați creat pentru "
-"API-ul Google Calendar. Apoi, faceți clic pe :guilabel:`Editați clientul "
-"OAuth` (pictograma creionului). Pagina va redirecționa către pagina de "
-"editare, unde puteți vizualiza Client ID și Client Secret."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Click Edit OAuth Client to view the credential details."
-msgstr "Clic Edit OAuth Client pentru a vizualiza detaliile credențialelor."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:102
-msgid "Setup in Odoo"
-msgstr "Setare în Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:104
-msgid ""
-"Once the Client ID and the Client Secret are located, open the Odoo database"
-" and go to :menuselection:`Settings --> General Settings --> Integrations "
-"--> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
-msgstr ""
-"Odată ce Client ID și Client Secret sunt identificați, deschideți baza de "
-"date Odoo și mergeți la :menuselection:`Setări --> Setări generale --> "
-"Integrări --> Google Calendar`. Bifați caseta de lângă :guilabel:`Google "
-"Calendar`."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "The Google Calendar checkbox in General Settings."
-msgstr "Caseta Google Calendar în Setări generale."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
-msgid ""
-"Next, copy and paste the Client ID and the Client Secret from the Google "
-"Calendar API Credentials page into their respective fields below the "
-":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:116
-msgid ""
-"Finally, open the Calendar module in Odoo and click on the "
-":guilabel:`Google` sync button to sync Google Calendar with Odoo."
-msgstr ""
-"În cele din urmă, deschideți modulul Calendar în Odoo și faceți clic pe "
-"butonul :guilabel:`Google` pentru a sincroniza Google Calendar cu Odoo."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Click the Google sync button in Odoo Calendar to sync Google Calendar with "
-"Odoo."
-msgstr ""
-"Faceți clic pe butonul de sincronizare Google în Calendarul Odoo pentru a "
-"sincroniza Google Calendar cu Odoo."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:124
-msgid ""
-"The first time you sync your Google Calendar with Odoo, the page will "
-"redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` "
-"to authorize Odoo to access Google Calendar."
-msgstr ""
-"Prima dată când sincronizați Calendarul Google cu Odoo, pagina va "
-"redirecționa către contul dvs. Google. Faceți clic pe :guilabel:`OK` și "
-":guilabel:`Permiteți` pentru a autoriza Odoo să acceseze Google Calendar."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Give Odoo permission to access Google Calendar."
-msgstr "Permiteți Odoo să acceseze Google Calendar."
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:131
-msgid "Now, Odoo Calendar is successfully synced with Google Calendar!"
-msgstr "Acum, Calendarul Odoo este sincronizat cu succes cu Google Calendar!"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Successfully sync between Odoo and Google Calendar."
-msgstr "Sincronizare cu succes între Odoo și Google Calendar."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
-msgid "Synchronize Outlook Calendar with Odoo"
-msgstr "Sincronizați Calendarul Outlook cu Odoo"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5
-msgid ""
-"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping "
-"track of their tasks and appointments across all related applications."
-msgstr ""
-"Sincronizarea Calendarului Outlook al unui utilizator cu Odoo este utilă "
-"pentru a urmări sarcinile și programările lor în toate aplicațiile asociate."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9
-msgid ":doc:`/applications/general/auth/azure`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:13
-msgid "Register the application with Microsoft Azure"
-msgstr "Înregistrați aplicația cu Microsoft Azure"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:15
-msgid ""
-"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account"
-" is needed. Creating an account is free for users who have never tried or "
-"paid for Azure. For more information, `click here "
-"<https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_."
-msgstr ""
-"Pentru a sincroniza Calendarul Outlook cu Calendarul Odoo, este necesar un "
-"cont Microsoft Azure. Crearea unui cont este gratuită pentru utilizatorii "
-"care nu au încercat sau plătit pentru Azure. Pentru mai multe informații, "
-"`faceți clic aici<https://azure.microsoft.com/en-"
-"us/free/?WT.mc_id=A261C142F>`_."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:19
-msgid ""
-"Refer to `Microsoft's documentation <https://docs.microsoft.com/en-"
-"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to"
-" set up an Azure AD Tenant (also called an *environment*), which is a "
-"representation of an organization to manage and register apps."
-msgstr ""
-"Consultați `documentația Microsoft <https://docs.microsoft.com/en-"
-"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ despre "
-"cum să setați un Azure AD Tenant (de asemenea numit *environment*), care "
-"este o reprezentare a unei organizații pentru a gestiona și înregistra "
-"aplicații."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:23
-msgid ""
-"Then, `Register an Application <https://docs.microsoft.com/en-"
-"us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the "
-"appropriate :guilabel:`Supported account type`. Users who wish to connect "
-"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any "
-"organizational directory (Any Azure AD directory - Multitenant) and personal"
-" Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported "
-"account types`."
-msgstr ""
-"În continuare, `Înregistrați o aplicație <https://docs.microsoft.com/en-"
-"us/azure/active-directory/develop/ quickstart-register-app>`_, alegând tipul"
-" de cont potrivit: :guilabel:`Tipuri de conturi acceptate`. Utilizatorii "
-"care doresc să se conecteze la calendarul lor Outlook cu Odoo ar trebui să "
-"selecteze opțiunea :guilabel:`Conturi din orice director organizatoric "
-"(Orice director Azure AD - Multitenant) și conturi personale Microsoft (de "
-"ex. Skype, Xbox)` pentru :guilabel:`Tipuri de conturi acceptate`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:29
-msgid ""
-"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and "
-"copy the Odoo database URI (URL) followed by "
-"`/microsoft_account/authentication`."
-msgstr ""
-"Când configurați :guilabel:`Redirect URI`, alegeți :guilabel:`Web` și "
-"copiați adresa URL a bazei de date Odoo (URL) urmată de "
-"`/microsoft_account/authentication`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:33
-msgid ""
-"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` "
-"for the :guilabel:`Redirect URI`."
-msgstr ""
-"Introduceți "
-"`https://www.companyname.odoo.com/microsoft_account/authentication` pentru "
-":guilabel:`Redirect URI`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid ""
-"The \"Supported account type\" and \"Redirect URI\" settings in the "
-"Microsoft Azure AD portal."
-msgstr ""
-"Setările \"Tipuri de conturi acceptate\" și \"Redirect URI\" în portalul "
-"Microsoft Azure AD."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:40
-msgid ""
-"For more information on the restrictions and limitations of URIs, `check "
-"this page <https://docs. microsoft.com/en-us/azure/active-"
-"directory/develop/reply-url>`_."
-msgstr ""
-"Pentru mai multe informații despre restricțiile și limitările URIs, "
-"`verificați această pagină <https://docs. microsoft.com/en-us/azure/active-"
-"directory/develop/reply-url>`_."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:43
-msgid ""
-"Regarding the application credentials, the user *must* add a client secret, "
-"which allows Odoo to authenticate itself, requiring no interaction from the "
-"user's side. :guilabel:`Certificates` are optional."
-msgstr ""
-"În ceea ce privește credențialele aplicației, utilizatorul *trebuie* să "
-"adauge un secret de client, care permite Odoo să se autentifice, fără a "
-"necesita nicio interacțiune de la partea utilizatorului. "
-":guilabel:`Certificates` sunt opționale."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:47
-msgid ""
-"To do add a client secret, click :guilabel:`Add a certificate or secret` and"
-" then click :guilabel:`New client secret`. Next, type a "
-":guilabel:`Description` and select when the client secret "
-":guilabel:`Expires`."
-msgstr ""
-"Pentru a adăuga un client secret, faceți clic pe :guilabel:`Adăugați un "
-"certificat sau un secret` și apoi faceți clic pe :guilabel:`New client "
-"secret` . În continuare, introduceți o :guilabel:`Descriere` și selectați "
-"când clientul secret :guilabel:`Expiră`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:51
-msgid ""
-"Since resetting the synchronization can be tricky, Odoo recommends setting "
-"the maximum allowed expiration date for the client secret (24 months), so "
-"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to "
-"generate the client secret (:guilabel:`Secret ID`)."
-msgstr ""
-"Deoarece resetarea sincronizării poate fi dificilă, Odoo recomandă setarea "
-"datei maximale de expirare permisă pentru client secret  (24 de luni), "
-"astfel încât nu este necesar să resincronizați în curând. În cele din urmă, "
-"faceți clic pe :guilabel:`Adăugați` pentru a genera client secret  "
-"(:guilabel:`Secret ID`)."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:56
-msgid "Configuration in Odoo"
-msgstr "Configurare în Odoo"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:58
-msgid ""
-"In the Odoo database, go to :menuselection:`Settings --> General Settings "
-"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting."
-msgstr ""
-"În baza de date Odoo, mergeți la :menuselection:`Setări --> Setări generale "
-"--> Integrări` și activați setarea :guilabel:`Calendar Outlook`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook Calendar\" setting activated in Odoo."
-msgstr "Setarea \"Calendar Outlook\" activată în Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:65
-msgid ""
-"From the Microsoft Azure portal, under the :guilabel:`Overview` section of "
-"the application, copy the :guilabel:`Application (Client) ID`, and paste it "
-"into the :guilabel:`Client ID` field in Odoo."
-msgstr ""
-"Din portalul Microsoft Azure, în secțiunea :guilabel:`Overview` a "
-"aplicației, copiați :guilabel:`Application (Client) ID`, și lipiți-l în "
-"câmpul :guilabel:`Client ID` în Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client ID\" in the Microsoft Azure portal."
-msgstr "Câmpul \"Client ID\" în portalul Microsoft Azure."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:72
-msgid ""
-"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` "
-"section, copy the :guilabel:`Client Secret Value` and paste it into the "
-":guilabel:`Client Secret` field in Odoo."
-msgstr ""
-"Din portalul Microsoft Azure, în secțiunea :guilabel:`Certificates & "
-"secrets` , copiați :guilabel:`Client Secret Value` și lipiți-l în câmpul "
-":guilabel:`Client Secret` în Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo."
-msgstr "Tokenul \"Client Secret\" de copiat de la Microsoft în Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:79
-msgid ""
-"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, "
-"click :guilabel:`Save`."
-msgstr ""
-"În cele din urmă, pe pagina :menuselection:`Setări --> Setări generale` din "
-"Odoo, faceți clic pe :guilabel:`Salvați`."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:84
-msgid "Sync with Outlook"
-msgstr "Sincronizați cu Outlook"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:88
-msgid ""
-"Odoo highly recommends testing the Outlook calendar synchronization on a "
-"test database and a test email address (that is not used for any other "
-"purpose) before attempting to sync the desired Outlook Calendar with the "
-"user's production database."
-msgstr ""
-"Odoo recomandă în mod deosebit să testați sincronizarea calendarului Outlook"
-" pe o bază de date de testare și o adresă de e-mail de testare (care nu este"
-" folosită pentru nici un alt scop) înainte de a încerca să sincronizați "
-"calendarul Outlook dorit cu baza de date de producție a utilizatorului."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:92
-msgid ""
-"If the user has any past, present, or future events on their Odoo calendar "
-"before syncing their Outlook calendar, Outlook will treat the events pulled "
-"from Odoo's calendar during the sync as new events, causing an email "
-"notification to be sent from Outlook to all the event attendees."
-msgstr ""
-"Dacă utilizatorul are orice evenimente trecute, prezente sau viitoare pe "
-"calendarul său Odoo înainte de sincronizarea calendarului Outlook, Outlook "
-"va trata evenimentele extrase din calendarul Odoo în timpul sincronizării ca"
-" evenimente noi, provocând trimiterea unei notificări prin e-mail de la "
-"Outlook tuturor participanților la eveniment."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:96
-msgid ""
-"To avoid unwanted emails being sent to all past, present, and future event "
-"attendees, the user must add the events from the Odoo calendar to the "
-"Outlook calendar before the first ever sync, delete the events from Odoo, "
-"and then start the sync."
-msgstr ""
-"Pentru a evita trimiterea neașteptată a e-mailurilor tuturor participanților"
-" la evenimentele trecute, prezente și viitoare, utilizatorul trebuie să "
-"adauge evenimentele din calendarul Odoo în calendarul Outlook înainte de "
-"prima sincronizare, să șteargă evenimentele din Odoo, și apoi să înceapă "
-"sincronizarea."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:100
-msgid ""
-"Even after synchronizing the Odoo Calendar with the Outlook calendar, "
-"Outlook will still send a notification to all event participants every time "
-"an event is edited (created, deleted, unarchived, or event date/time "
-"changed), with no exceptions. This is a limitation that cannot be fixed from"
-" Odoo's side."
-msgstr ""
-"Chiar și după sincronizarea calendarului Odoo cu calendarul Outlook, Outlook"
-" va trimite totuși o notificare tuturor participanților la eveniment la "
-"fiecare dată când un eveniment este editat (creat, șters, dezarhivat, sau "
-"dată/timpul evenimentului modificat), fără excepții. Aceasta este o limitare"
-" care nu poate fi rezolvată pe partea de Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:105
-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 ""
-"După ce un utilizator sincronizează calendarul Outlook cu baza de date Odoo,"
-" notificările prin e-mail neașteptate sunt inevitabile deoarece evenimentele"
-" primului utilizator sincronizat vor fi în calendarul Odoo. Dacă baza de "
-"date Odoo este partajată între mai mulți utilizatori, și alt utilizator "
-"dorește să sincronizeze calendarul Outlook cu calendarul Odoo, Outlook va "
-"din nou extrage evenimentele existente din calendarul Odoo în timpul "
-"sincronizării și le va trata ca evenimente noi, provocând trimiterea unei "
-"invitații prin e-mail tuturor participanților la eveniment."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:112
-msgid ""
-"In summary, once a user synchronizes their Outlook calendar with the Odoo "
-"calendar:"
-msgstr ""
-"În concluzie, odată ce un utilizator sincronizează calendarul Outlook cu "
-"calendarul Odoo:"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:114
-msgid ""
-"Creating an event in Odoo causes Outlook to send an invitation to all event "
-"attendees."
-msgstr ""
-"Crearea unui eveniment în Odoo provoacă trimiterea unei invitații prin "
-"e-mail tuturor participanților la eveniment de la Outlook."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:115
-msgid ""
-"Deleting an event in Odoo causes Outlook to send a cancellation to all event"
-" attendees."
-msgstr ""
-"Ștergerea unui eveniment în Odoo provoacă trimiterea unei anulații prin "
-"e-mail tuturor participanților la eveniment de la Outlook."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:116
-msgid ""
-"Unarchiving an event in Odoo causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-"Dezarhivarea unui eveniment în Odoo provoacă trimiterea unei invitații prin "
-"e-mail tuturor participanților la eveniment de la Outlook."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:117
-msgid ""
-"Archiving an event in Odoo causes Outlook to send a cancellation to all "
-"event attendees."
-msgstr ""
-"Arhivarea unui eveniment în Odoo provoacă trimiterea unei anulații prin "
-"e-mail tuturor participanților la eveniment de la Outlook."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:118
-msgid ""
-"Adding a contact to an event causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-"Adăugarea unui contact la un eveniment provoacă trimiterea unei invitații "
-"prin e-mail tuturor participanților la eveniment de la Outlook."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:119
-msgid ""
-"Removing a contact from an event causes Outlook to send a cancellation to "
-"all event attendees."
-msgstr ""
-"Eliminarea unui contact dintr-un eveniment provoacă trimiterea unei anulații"
-" prin e-mail tuturor participanților la eveniment de la Outlook."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:122
-msgid "Sync Odoo Calendar and Outlook"
-msgstr "Sincronizare calendar Odoo și Outlook"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:124
-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 ""
-"În baza de date Odoo, mergeți la modulul :guilabel:`Calendar` și faceți clic"
-" pe butonul de sincronizare :guilabel:`Outlook`. Pagina va fi redirecționată"
-" la o pagină de autentificare Microsoft, și utilizatorul este rugat să se "
-"autentifice în contul său, dacă nu este deja, și să acorde permisiunile "
-"necesare."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook\" sync button in Odoo Calendar."
-msgstr "Butonul de sincronizare \"Outlook\" în calendarul Odoo."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:132
-msgid ""
-"The synchronization is a two-way process, meaning that events are reconciled"
-" in both accounts (Outlook and Odoo)."
-msgstr ""
-"Sincronizarea este un proces bidirecțional, ceea ce înseamnă că evenimentele"
-" sunt reconciliate în ambele conturi (Outlook și Odoo)."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:136
-msgid ""
-"All users that want to use the synchronization simply need to :ref:`sync "
-"their calendar with Outlook <outlook_calendar/sync_with_outlook>`. The "
-"configuration of Microsoft's Azure account is only done once, as Azure AD "
-"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 ""
-"Toți utilizatorii care doresc să utilizeze sincronizarea trebuie doar să "
-":ref:`sincronizeze calendarul lor cu Outlook "
-"<outlook_calendar/sync_with_outlook>`. Configurarea contului Microsoft Azure"
-" se face o singură dată, deoarece ID-urile de client și secretele de client "
-"ale tenant-ului Azure AD sunt unice, și reprezintă o organizație care ajută "
-"utilizatorul să gestioneze o instanță specifică a serviciilor cloud "
-"Microsoft pentru utilizatorii interni și externi."
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:143
-msgid ":doc:`../../../productivity/mail_plugins/outlook`"
-msgstr ":doc:`../../../productivity/mail_plugins/outlook`"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:144
-msgid ":doc:`../google/google_calendar_credentials`"
-msgstr ":doc:`../google/google_calendar_credentials`"
-
 #: ../../content/applications/general/developer_mode.rst:5
 msgid "Developer Mode (debug mode)"
 msgstr "Modul dezvoltator (modul de depanare)"
@@ -5751,8 +5079,8 @@ msgstr ""
 "limbă instalată anterior și faceți clic pe**SALVEAZĂ.**"
 
 #: ../../content/applications/general/users/language.rst:61
-msgid ":doc:`../../websites/website/publish/translate`"
+msgid ":doc:`../../websites/website/configuration/translate`"
-msgstr ":doc:`../../websites/website/publish/translate`"
+msgstr ""
 
 #: ../../content/applications/general/users/manage_users.rst:3
 msgid "Manage users"

locale/ro/LC_MESSAGES/services.po

@@ -5,17 +5,17 @@
 # 
 # Translators:
 # Dragos Vasile, 2023
-# Cozmin Candea <office@terrabit.ro>, 2023
 # Dorin Hongu <dhongu@gmail.com>, 2023
+# Cozmin Candea <office@terrabit.ro>, 2023
 # 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:54+0000\n"
-"Last-Translator: Dorin Hongu <dhongu@gmail.com>, 2023\n"
+"Last-Translator: Cozmin Candea <office@terrabit.ro>, 2023\n"
 "Language-Team: Romanian (https://app.transifex.com/odoo/teams/41243/ro/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -363,80 +363,215 @@ msgstr ""
 "programs-640?fullscreen=1>`_"
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
-msgid "Allow customers to close their tickets"
+msgid "Closing tickets"
-msgstr "Permiteți clienților să își închidă tichetele"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
 msgid ""
-"Allowing customers to close their own tickets gives them autonomy and "
+"Once work has been completed on a *Helpdesk* ticket in Odoo, there are "
-"minimizes misunderstandings around when an issue is considered solved or "
+"several ways it can be closed. Manually closing solved tickets keeps the "
-"not. This results in operational capacity for support teams, and higher "
+"pipeline up to date, while automatically closing inactive tickets prevents "
-"satisfaction for the customer."
+"unnecessary blocking issues. Allowing customers to close their own tickets "
-msgstr ""
+"minimizes confusion around whether an issue is considered solved or not. "
-
+"This results in increased operational capacity for support teams, and higher"
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:10
+" customer satisfaction."
-msgid "Enable ticket closing"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12
+msgid "Manually close solved tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
 msgid ""
-"Start by navigating to :menuselection:`Helpdesk --> Configuration --> "
+"As work on a ticket progresses, it is moved along to the next stage in the "
-"Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit`"
+"pipeline. Once the issue is solved, the ticket is moved to a *folded* stage."
-" and enable :guilabel:`Ticket closing` by checking the field box."
+" This marks the ticket as *closed*."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17
+msgid ""
+"To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and "
+"click on a team to open the pipeline. Hover over a stage's heading, and then"
+" click the gear icon that appears in the top-right corner of that stage's "
+"kanban column."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid "Ticket closing feature in Odoo Helpdesk."
+msgid ""
+"View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage"
+" option."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:19
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
 msgid ""
-"To designate which stage the ticket migrates to once it is closed, navigate "
+"Clicking the gear icon also displays the option to :guilabel:`Fold` the "
-"to the ticket pipeline by going to :menuselection:`Helpdesk --> Overview` "
+"stage. This setting folds the stage *temporarily* to simplify the kanban "
-"and clicking :guilabel:`Tickets` on the team's card."
+"view. This does *not* close the tickets in this stage. It also does not "
+"permanently fold the stage. If a stage needs to be folded so the tickets can"
+" be marked as closed, continue following the steps below."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:23
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
 msgid ""
-"There are two options: create a new Kanban stage or work with an existing "
+"From the menu that appears, select :guilabel:`Edit Stage`. This will open "
-"one. For both scenarios, click the :guilabel:`Settings (gear)` icon next to "
+"the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` "
-"the stage name, select :guilabel:`Edit Stage`, and enable :guilabel:`Closing"
+"towards the top of the window, and then :guilabel:`Save & Close` to confirm "
-" Stage`. After checking the field box, click :guilabel:`Save` to finish."
+"the changes. Now, tickets that reach this stage will be considered as "
+"*closed*."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:29
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
-msgid ""
+msgid "Stage settings page."
-"If a closing stage is not specified, by default, the ticket is moved to the "
-"last stage in the kanban. If more than one stage is set as a closing stage, "
-"the ticket is placed in the first closing stage column."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:33
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41
+msgid "Automatically close inactive tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43
 msgid ""
-"With the ticket closing settings now complete, customers can now view the "
+"Tickets that are inactive for a set period of time can be automatically "
-"option to :guilabel:`Close this ticket` when they log into their portal."
+"closed. At that point, they will be moved to a folded stage."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46
+msgid ""
+"Go to the team's settings page by going to :menuselection:`Helpdesk --> "
+"Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable"
+" :guilabel:`Automatic Closing`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
+msgid ""
+"If one of the team's stages is set to be folded in the kanban view, it will "
+"be the default selection in the :guilabel:`Move to Stage` field. If the team"
+" has more than one folded stage, the stage that occurs first in the pipeline"
+" will be the default. If no stage is folded, the default selection will be "
+"the last stage in the pipeline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54
+msgid ""
+"The :guilabel:`After days of inactivity` field defaults to `7`, but can be "
+"adjusted if necessary."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57
+msgid ""
+"The :guilabel:`After days of inactivity` field does **not** take the working"
+" calendar into account when tracking the amount of time a ticket has been "
+"inactive."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60
+msgid ""
+"If only certain stages should be used to track days of inactivity, they can "
+"be added to the :guilabel:`In Stages` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64
+msgid "A team's pipeline is created with the following stages:"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66
+msgid "`New`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67
+msgid "`In Progress`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68
+msgid "`Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69
+msgid "`Closed`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71
+msgid ""
+"Tickets can linger in the :guilabel:`Customer Feedback stage`, because once "
+"an issue is solved, customers may not respond immediately. At that point, "
+"the tickets can be closed automatically. However, tickets in the "
+":guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due "
+"to assignment or workload issues. Closing these tickets automatically would "
+"result in issues going unsolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
+msgid ""
+"Therefore, the :guilabel:`Automatic Closing` settings would be configured as"
+" below\\:\\"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
+msgid ":guilabel:`Automatic Closing`: *checked*"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
+msgid ":guilabel:`Move to Stage`: `Solved`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
+msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
+msgid ":guilabel:`In Stages`: `Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
+msgid "Example of Automatic Closing settings."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89
+msgid "Allow customers to close their own tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
+msgid ""
+"Enabling the :guilabel:`Closure by Customers` setting allows customers to "
+"close their own ticket(s) when they determine that their issue has been "
+"resolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94
+msgid ""
+"Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams`"
+" and select a team. On the team's settings page, scroll to the "
+":guilabel:`Self-Service` section and check the box for :guilabel:`Closure by"
+" Customers`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
+msgid "Customer closing setting in Odoo Helpdesk."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
+msgid ""
+"Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` "
+"button will be available for customers when they view their ticket through "
+"the customer portal."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
 msgid "Customer view of ticket closing in Odoo Helpdesk."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:40
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110
-msgid "Get reports on tickets closed by customers"
+msgid ""
+"Customers are able to view their tickets by clicking the :guilabel:`View the"
+" ticket` link they receive by email. The link is included in the "
+":guilabel:`Request Acknowledgment` template, which is added to the first "
+"stage of a team by default. This link does not require a customer to have "
+"access to the portal to view or respond to their ticket."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:42
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
 msgid ""
-"To analyze the tickets that have been closed by customers, go to "
+"Customers with access to the portal will be able to view their tickets under"
-":menuselection:`Helpdesk --> Reporting --> Tickets`. Then, click on the "
+" :menuselection:`My Account --> Tickets`."
-":guilabel:`Filters` menu and choose :guilabel:`Add Custom filter`. Next, set"
-" the custom filter parameters to :guilabel:`Closed by partner` and "
-":guilabel:`is true`. Finally, click :guilabel:`Apply`."
-msgstr ""
-
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid ""
-"Filter for tickets closed by customers on Odoo Helpdesk's reporting page."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview.rst:5
@@ -996,7 +1131,6 @@ msgstr ""
 "echipei de helpdesk în Odoo Helpdesk"
 
 #: ../../content/applications/services/helpdesk/overview/ratings.rst:51
-#: ../../content/applications/services/helpdesk/overview/sla.rst:47
 msgid ":doc:`../advanced/close_tickets`"
 msgstr ":doc:`../advanced/close_tickets`"
 
@@ -1236,7 +1370,7 @@ msgid ""
 "The *Live Chat* feature allows website visitors to connect directly with a "
 "support agent or chatbot. During these conversations, *Helpdesk* tickets can"
 " be instantly created by using the :doc:`response command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk`."
+"</applications/websites/livechat/responses>` `/helpdesk`."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125
@@ -1487,10 +1621,9 @@ msgstr ""
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261
 msgid ""
 "During the conversation, an operator can use the shortcut :doc:`command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk` to create "
+"</applications/websites/livechat/responses>` `/helpdesk` to create a ticket "
-"a ticket without leaving the chat window. The transcript from the "
+"without leaving the chat window. The transcript from the conversation will "
-"conversation will be added to the new ticket, under the "
+"be added to the new ticket, under the :guilabel:`Description` tab."
-":guilabel:`Description` tab."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267
@@ -1551,7 +1684,7 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
 msgstr ":doc:`/applications/general/email_communication/email_servers`"
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293
-msgid ":doc:`/applications/websites/livechat/overview/get_started`"
+msgid ":doc:`/applications/websites/livechat`"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/reports.rst:3
@@ -1698,100 +1831,301 @@ msgstr "Acord privind nivelul de serviciilor (SLA)"
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:5
 msgid ""
-"Service Level Agreements (SLA) are commitments you make with your customers "
+"A Service Level Agreement (SLA) defines the level of service a customer can "
-"to outline how a service is delivered. It bolsters trust between you and "
+"expect from a supplier. SLAs provide a timeline that tells customers when "
-"your customers as it makes clear what needs to be done, to what standard, "
+"they can expect results, and keeps the support team on target."
-"and when."
 msgstr ""
-"Acordurile privind nivelul de servicii (SLA) sunt angajamente pe care vi le "
-"asumați față de clienții dvs. pentru a sublinia cum se livrează un serviciu."
-" Îmbunătățește încrederea dintre dvs. și clienții dvs. deoarece clarifică ce"
-" trebuie făcut, la ce standard și când."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:10
-msgid "Create your policies"
+msgid "Create a new SLA policy"
-msgstr "Crează politica ta"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst:13
-msgid ""
-"First, enable the feature on the settings of the team you would like "
-"policies to be applied, going to :menuselection:`Helpdesk --> Configuration "
-"--> Helpdesk Teams`."
 msgstr ""
-"În primul rând, activați funcția în setările echipei pe care doriți să se "
-"aplice politicile, mergând la :menuselection:`Helpdesk --> Configurare --> "
-"Echipe de asistenta`."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:15
+#: ../../content/applications/services/helpdesk/overview/sla.rst:12
 msgid ""
-"Create your policies through the team’s settings page or go to "
+"To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to "
-":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
+"the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`."
+" Select a team, scroll to the :guilabel:`Performance` section, and then "
+"check the selection box next to :guilabel:`SLA Policies` to enable it for "
+"that specific team."
 msgstr ""
-"Creați politica dvs. prin intermediul paginii de setări a echipei sau "
-"mergeți la :menuselection:`Helpdesk --> Configurare --> Politici SLA`."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
-msgid "View of an SLA form in Odoo Helpdesk"
+msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
-msgstr "Vizualizarea a unui formular SLA în Odoo Helpdesk"
+msgstr ""
-
+
-#: ../../content/applications/services/helpdesk/overview/sla.rst:23
+#: ../../content/applications/services/helpdesk/overview/sla.rst:22
-msgid ""
+msgid ""
-"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
+"The value indicated next to the :guilabel:`Working Hours` field is used to "
-" a ticket needs to have for the policy to be applied."
+"determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. "
+"By default, this is determined by the value set in the :guilabel:`Company "
+"Working Hours` field under :menuselection:`Settings app --> Employees --> "
+"Work Organization`."
 msgstr ""
-"Alegeți pentru **Echipă** este relevantă politica și **Prioritatea minimă** "
-"necesară unui tichet, pentru ca politica să fie aplicată."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:27
 msgid ""
-"**Target** is the stage a ticket needs to reach within the period defined to"
+"To create a new policy, click the smart button on the team`s settings page "
-" satisfy the SLA. The period is based on the ticket’s creation date, and a "
+"or go to :menuselection:`Helpdesk -->  Configuration --> SLA Policies`, and "
-"deadline is set on the ticket’s form once it matches an SLA policy rule. If "
+"click :guilabel:`New`. Start by entering a :guilabel:`Title` and a "
-"a ticket has more than one policy applied to it, the closest deadline of all"
+":guilabel:`Description` for the new policy, and proceed to fill out the form"
-" SLAs is the one considered."
+" using the steps below."
 msgstr ""
-"**Țintă** este stadiul în care un tichet trebuie să ajungă în perioada "
-"definită pentru a satisface SLA. Perioada este bazată pe data creării "
-"tichetului, iar o dată limită este setată pe formularul tichetului odată ce "
-"se potrivește cu o regulă a politicii SLA. Dacă un tichet are mai multe "
-"politici aplicate,  atunci cea mai apropiată dată limită dintre toate SLA "
-"este cea luată în considerare."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:29
+#: ../../content/applications/services/helpdesk/overview/sla.rst:33
+msgid "Define the criteria for an SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:35
 msgid ""
-"When a ticket has satisfied an SLA policy, the SLA tag appears in green and "
+"The :guilabel:`Criteria` section is used to identify what tickets this "
-"the deadline field is not shown anymore."
+"policy will be applied to. Fill out the following fields to adjust the "
+"selection criteria:"
 msgstr ""
-"Când un tichet a satisfăcut o politică SLA, eticheta SLA apare în verde și "
-"nu mai este afișat câmpul limită."
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+#: ../../content/applications/services/helpdesk/overview/sla.rst:38
-msgid "View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk"
+msgid ""
+":guilabel:`Team`: a policy can only be applied to one team. *This field is "
+"required.*"
 msgstr ""
-"Vizualizarea unui formular de tichet care evidențiază SLA satisfăcută în "
-"Odoo Helpdesk"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst:37
-msgid "SLA Analysis"
-msgstr "Analiza SLA"
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:39
 msgid ""
-"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply"
+":guilabel:`Priority`: the priority level for a ticket is identified by "
-" *Filters* and *Group by* to identify tickets that should be prioritized and"
+"selecting the number of stars representing the priority level on the kanban "
-" keep track of upcoming deadlines."
+"card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will "
+"only be applied once the priority level has been updated on the ticket to "
+"match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is"
+" made in this field, this policy will only apply to tickets marked as `Low "
+"Priority` (zero stars)."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:44
+msgid ""
+":guilabel:`Types`: ticket types can be helpful when indicating when a ticket"
+" is a customer question, that can be solved with a quick response, or an "
+"issue, that may require additional investigation. Multiple ticket types can "
+"be selected for this field. If no selection is made, this policy will apply "
+"to all ticket types."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:48
+msgid ""
+":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is "
+"about. Multiple tags can be applied to a single ticket."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:50
+msgid ""
+":guilabel:`Customers`: individual contacts or companies may be selected in "
+"this field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:51
+msgid ""
+":guilabel:`Sales Order Items`: this field is available only if a team has "
+"the *Timesheets* app enabled. This allows the ticket to tie directly to a "
+"specific line on a sales order, which must be indicated on the ticket in the"
+" :guilabel:`Sales Order Item` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:56
+msgid ""
+"Unless otherwise indicated, multiple selections can be made for each field. "
+"(i.e. multiple :guilabel:`Tags` can be included in a policy, but only one "
+":guilabel:`Priority` level)"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a blank SLA policy record"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:64
+msgid "Establish a target for an SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:66
+msgid ""
+"The :guilabel:`Target` is the stage a ticket needs to reach, and the time "
+"alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service "
+"Level Agreement)` policy. Any stage assigned to a team may be selected for "
+"the :guilabel:`Reach Stage` field. Time spent in stages selected in "
+":guilabel:`Excluding Stages` will not be included in the calculation of the "
+":abbr:`SLA (Service Level Agreement)` deadline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:73
+msgid ""
+"An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks "
+"the working time before a ticket is completed, and would have `Solved` as "
+"the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level "
+"Agreement)` was titled `2 Days to Start`, it tracks the working time before "
+"work on a ticket has begun, and would have `In Progress` as the "
+":guilabel:`Reach Stage`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:79
+msgid "Meeting SLA deadlines"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:81
+msgid ""
+"Once it is determined that a ticket fits the criteria of an :abbr:`SLA "
+"(Service Level Agreement)` policy, a deadline is calculated. The deadline is"
+" based on the creation date of the ticket, and the targeted working hours. "
+"The deadline is then added to the ticket, as well as a white tag indicating "
+"the name of the :abbr:`SLA (Service Level Agreement)` applied."
 msgstr ""
-"Mergi la :menuselection:`Helpdesk --> Raportare --> Analiza stării SLA`. "
-"Aplică *Filtre* și *Grupare după* pentru a identifica tichetele care ar "
-"trebui să fie prioritizate și urmărește termenele limită care se apropie."
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
 msgid ""
-"View of the SLA status analysis page emphasizing the group by option in Odoo"
+"View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo"
 " Helpdesk"
 msgstr ""
-"Vizualizarea paginii de analiză a stării SLA care evidențiază opțiunea de "
+
-"grupare după în Odoo Helpdesk"
+#: ../../content/applications/services/helpdesk/overview/sla.rst:91
+msgid ""
+"If a ticket fits the criteria for more than one :abbr:`SLA (Service Level "
+"Agreement)`, the earliest occurring deadline will be displayed on the "
+"ticket. Once that deadline has passed, the next deadline will be displayed."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:95
+msgid ""
+"Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the"
+" :abbr:`SLA (Service Level Agreement)` tag turns green, and the "
+":guilabel:`Deadline` field disappears from view on the."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:102
+msgid ""
+"If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket "
+"has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level "
+"Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level "
+"Agreement)` has failed, the red tag will stay on the ticket, even after the "
+"ticket is moved to the :guilabel:`Reach Stage`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid ""
+"View of a ticket's form with a failing and passing SLA in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:112
+msgid "Analyzing SLA performance"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:114
+msgid ""
+"The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA "
+"(Service Level Agreement)` is fulfilled, as well as the success rate of "
+"individual policies. Navigate to the report and corresponding pivot table by"
+" going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:120
+msgid "Using the Pivot view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:122
+msgid ""
+"By default, the report is displayed in a :guilabel:`Pivot` view, and is "
+"filtered to show the number of SLAs failed and the failure rate over the "
+"last 30 days, grouped by team."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:129
+msgid ""
+"To add the number of SLAs passed or in progress, click the "
+":guilabel:`Measures` button to reveal a drop-down menu of reporting "
+"criteria, and choose from the options available based on the measurements "
+"preferred. Whenever a measurement is picked, a check mark will appear in the"
+" drop-down menu to indicate that that measurement is included, and a "
+"corresponding new column will emerge in the pivot table to show the relevant"
+" calculations."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:135
+msgid ""
+"To add a group to a row or column, click the plus :guilabel:` + ` button "
+"next to :guilabel:`Total`, and then select one of the groups. To remove one,"
+" click the minus :guilabel:` - ` button and deselect."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:140
+msgid "Using the Graph view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:142
+msgid ""
+"The :guilabel:`Status Analysis` report can also be viewed as a "
+":guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between "
+"these views by selecting the appropriate icon at the top of the chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:148
+msgid "Bar Chart"
+msgstr "Grafic bare"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in bar view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:154
+msgid "Line Chart"
+msgstr "Grafic liniar"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in line view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:160
+msgid "Pie Chart"
+msgstr "Grafic tip pie"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in pie chart view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:167
+msgid ""
+"Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed "
+":guilabel:`Stacked`. This presents two or more groups to appear on top of "
+"each other instead of next to each other, making it easier to compare data."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:172
+msgid "Using the Cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:174
+msgid ""
+"The :guilabel:`Cohort` view is used to track the changes in data over a "
+"period of time. To display the :guilabel:`Status Analysis` report in a "
+":guilabel:`Cohort` view, click the icon in the top right corner above the "
+"chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:183
+msgid ":ref:`Reporting views <reporting/views>`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:184
+msgid ""
+":doc:`Allow customers to close their tickets "
+"</applications/services/helpdesk/advanced/close_tickets>`"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5
 msgid "Timesheet and Invoice"

locale/zh_CN/LC_MESSAGES/general.po

@@ -24,7 +24,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:53+0000\n"
 "Last-Translator: Emily Jia <eji@odoo.com>, 2023\n"
 "Language-Team: Chinese (China) (https://app.transifex.com/odoo/teams/41243/zh_CN/)\n"
@@ -351,11 +351,10 @@ msgid ""
 msgstr "因Azure云平台OAuth鉴权接口实现中的特殊需求，微软Azure云OAuth身份认证当前与Odoo不兼容."
 
 #: ../../content/applications/general/auth/azure.rst:9
-msgid ":doc:`/applications/general/calendars/outlook/outlook_calendar`"
+msgid ":doc:`../../productivity/calendar/outlook`"
 msgstr ""
 
 #: ../../content/applications/general/auth/azure.rst:10
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:67
 msgid ":doc:`/administration/maintain/azure_oauth`"
 msgstr ""
@@ -378,12 +377,10 @@ msgid ""
 msgstr "如果您的组织使用 Google Workforce，并且您希望组织内的员工使用其 Google 帐户连接到 Odoo，这将特别有用。"
 
 #: ../../content/applications/general/auth/google.rst:12
-msgid ""
+msgid ":doc:`../../productivity/calendar/google`"
-":doc:`/applications/general/calendars/google/google_calendar_credentials`"
 msgstr ""
 
 #: ../../content/applications/general/auth/google.rst:13
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
 #: ../../content/applications/general/email_communication/email_servers.rst:66
 msgid ":doc:`/administration/maintain/google_oauth`"
 msgstr ""
@@ -625,526 +622,6 @@ msgid ""
 "left blanked, the admin profile will be used as template."
 msgstr "在  **模板用户**  中，为创建的新配置文件指定模板。如果留空，管理员配置文件将用作模板。"
 
-#: ../../content/applications/general/calendars.rst:5
-msgid "Calendars"
-msgstr "日历"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:3
-msgid "Synchronize Google Calendar with Odoo"
-msgstr "同步谷歌日历"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5
-msgid ""
-"Synchronize Google Calendar with Odoo to see and manage meetings from both "
-"platforms (updates go in both directions). This integration helps organize "
-"your schedule so you never miss a meeting."
-msgstr ""
-"将 Google 日历与 Odoo 同步，以从两个平台查看和管理会议（双向更新）。 这种集成有助于组织您的日程安排，因此您不会错过任何会议。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9
-msgid ":doc:`/applications/general/auth/google`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:13
-msgid "Setup in Google"
-msgstr "在Google中设定"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:16
-msgid "Enable Google Calendar API"
-msgstr "允许Google日历API"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18
-msgid ""
-"Begin by creating a new Google API project and enabling the Google Calendar "
-"API. Then, go to the `Google API Console "
-"<https://console.developers.google.com>`_ and log into your Google account."
-msgstr ""
-"首先创建一个新的 Google API 项目并启用 Google Calendar API。 然后，转到 `Google API 控制台 "
-"<https://console.developers.google.com>`_ 并登录您的 Google 帐户。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22
-msgid ""
-"If this is your first time visiting this page, Google will prompt you to "
-"enter a country and agree to the Terms of Service. Select a country from the"
-" drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
-msgstr ""
-"如果这是您第一次访问此页面，Google 会提示您输入国家并同意服务条款。 从下拉列表中选择一个国家并同意: 缩写:`ToS（服务条款）`。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:26
-msgid ""
-"Next, click :guilabel:`Select a project` and select or create an API project"
-" to store credentials."
-msgstr "接下来，点击 :guilabel: ` Select a project ` 并选择或创建一个API项目来存储凭据。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Create a new API project to store credentials."
-msgstr "创建一个新的API项目来存储凭据。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:33
-msgid ""
-"Give the API Project a clear name like \"Odoo Sync\" so you can easily find "
-"it."
-msgstr "为 API 项目起一个清晰的名称，例如“Odoo Sync”，以便您轻松找到它。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
-msgid ""
-"Then, open the API Project and click :guilabel:`Enable APIs and Services`."
-msgstr "然后，打开API项目，点击 :guilabel:`Enable APIs and Services`。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable APIs and Services on the API Project."
-msgstr "在API项目中启用API和服务。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:41
-msgid ""
-"After that, search for *Google Calendar API* using the search bar and select"
-" :guilabel:`Google Calendar API` from the search results. Click "
-":guilabel:`Enable`."
-msgstr ""
-"之后，使用搜索栏搜索 *谷歌Calendar API*，并从搜索结果中选择 :guilabel:`Google Calendar API`。点击 "
-":guilabel:`Enable` 。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Enable the Google Calendar API."
-msgstr "启用谷歌日历API。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:49
-msgid "Create credentials"
-msgstr "创建凭据"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51
-msgid ""
-"Now that you have created your API project and enabled the Google Calendar "
-"API, you need to create credentials. Begin by clicking :guilabel:`Create "
-"Credentials`. Google will then guide you through four steps to create your "
-"API credentials."
-msgstr ""
-"现在您已经创建了API项目并启用了谷歌Calendar API，您需要创建凭证。首先点击 :guilabel:`Create "
-"Credentials`。按照向导通过四个步骤来创建API凭证。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
-msgid ""
-"In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google"
-" Calendar API` and :guilabel:`User Data` options. Then, click "
-":guilabel:`Next`."
-msgstr ""
-"在第一步中， :guilabel:`Credential Type` ，选择 :guilabel:`Google Calendar API` 和 "
-":guilabel:`User Data` 选项。然后,点击 :guilabel:`Next`。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Select Google Calendar API and User Data for the Credential Type."
-msgstr "为凭据类型选择谷歌日历API和用户数据。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:62
-msgid ""
-"In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the "
-":guilabel:`App name` field, select your email address for the "
-":guilabel:`User support email` field, and type your email address for the "
-":guilabel:`Developer contact information` section. Then, click "
-":guilabel:`Save and Continue`."
-msgstr ""
-"在第二步 :guilabel:`OAuth Consent Screen`中，在 :guilabel:`App name`字段中输入 *Odoo* ，在"
-" :guilabel:`User support email` 字段中选择电子邮件地址，在 :guilabel:`Developer contact "
-"information` 部分中输入你的电子邮件地址。然后，点击 :guilabel:`Save and Continue`。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
-msgid ""
-"Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and "
-"Continue`."
-msgstr "跳过第三步 :guilabel:`Scopes`，点击 :guilabel:`Save and Continue`。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
-msgid ""
-"In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website "
-"application` for the :guilabel:`Application Type` field and type *My Odoo "
-"Database* for the :guilabel:`Name`."
-msgstr ""
-"在最后一步，:guilabel: ' OAuth客户端ID '，为:guilabel: ' application Type "
-"'字段选择:guilabel: ' Website application '，为:guilabel: ' Name '字段选择*My Odoo "
-"Database*。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:72
-msgid ""
-"Under the :guilabel:`Authorized JavaScript Origins` section, click "
-":guilabel:`+ Add URI` and type your company's Odoo URL address."
-msgstr ""
-"在guilabel：`经授权JavaScript Origins`部分，单击guilabel：`+ Add URI`，并输入您公司的Odoo "
-"URL地址。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
-msgid ""
-"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ "
-"Add URI` and type your company's Odoo URL address followed by "
-"*/google_account/authentication*. Finally, click :guilabel:`Create` and "
-":guilabel:`Done`."
-msgstr ""
-"在guilabel：`经授权重新定向URIs`部分，单击guilabel：`+ Add URI`，并输入您公司的Odoo "
-"URL地址，后加*/google_account/authentication*。最后，单击guilabel：`创建`和guilabel：`完成`。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Add the authorized JavaScript origins and the authorized redirect URIs."
-msgstr "添加授权的 JavaScript 起源和授权的重定向 URI。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83
-msgid ""
-"After successfully creating a new API project, enabling the Google Calendar "
-"API, and generating the Google Calendar API credentials, you should now have"
-" a Client ID and Client Secret."
-msgstr ""
-"在成功创建新的 API 项目、启用 Google Calendar API 并生成 Google Calendar API 凭据后，您现在应该拥有一个 "
-"Client ID 和 Client Secret。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:87
-msgid "Client ID & Client Secret"
-msgstr "客户端ID和客户端密钥"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
-msgid ""
-"The **Client ID** and the **Client Secret** are both needed to connect "
-"Google Calendar to Odoo. Find the Client ID and the Client Secret by opening"
-" the Google Cloud Platform navigation menu and going to :menuselection:`API "
-"& Services --> Credentials --> OAuth 2.0 Client IDs`."
-msgstr ""
-"**客户ID**和**客户密码**均需将Google日历连接至Odoo需要。打开Google云端平台导航菜单，进入：菜单选择：`API和服务--> "
-"资格证书--> OAuth 2.0客户ID`。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:93
-msgid ""
-"Next, locate the credentials you just created for the Google Calendar API. "
-"Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page "
-"will redirect to the edit page, where you can view the Client ID and the "
-"Client Secret."
-msgstr ""
-"然后，找到您为Google日历API创建的凭据，单击guilabel：`编辑OAuth客户`（铅笔图标）。页面重定向至编辑页面，您可以查看客户ID和客户密码。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Click Edit OAuth Client to view the credential details."
-msgstr "单击 \"编辑OAuth客户端\"，查看证书的详细信息。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:102
-msgid "Setup in Odoo"
-msgstr "设置Odoo"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:104
-msgid ""
-"Once the Client ID and the Client Secret are located, open the Odoo database"
-" and go to :menuselection:`Settings --> General Settings --> Integrations "
-"--> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
-msgstr ""
-"找到客户端ID和客户端密码后，打开Odoo数据库，进入：菜单选择：`设置--> 一般设置--> 融合--> "
-"Google日历`。勾选guilabel：`Google日历`。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "The Google Calendar checkbox in General Settings."
-msgstr "常规设置中的谷歌日历复选框。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
-msgid ""
-"Next, copy and paste the Client ID and the Client Secret from the Google "
-"Calendar API Credentials page into their respective fields below the "
-":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:116
-msgid ""
-"Finally, open the Calendar module in Odoo and click on the "
-":guilabel:`Google` sync button to sync Google Calendar with Odoo."
-msgstr "最后，打开 Odoo 中的日历模块，点击:guilabel:`Google` 同步按钮，将 Google 日历与 Odoo 同步。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid ""
-"Click the Google sync button in Odoo Calendar to sync Google Calendar with "
-"Odoo."
-msgstr "点击Odoo日历中的谷歌同步按钮来将谷歌日历与Odoo同步。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:124
-msgid ""
-"The first time you sync your Google Calendar with Odoo, the page will "
-"redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` "
-"to authorize Odoo to access Google Calendar."
-msgstr ""
-"首次将您的 Google 日历与 Odoo 同步时，该页面将重定向到您的 Google 帐户。 "
-"点击:guilabel:`OK`和:guilabel:`Allow`授权Odoo访问谷歌日历。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Give Odoo permission to access Google Calendar."
-msgstr "给 Odoo 访问 Google 日历的权限。"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:131
-msgid "Now, Odoo Calendar is successfully synced with Google Calendar!"
-msgstr "现在，Odoo 日历已成功与 Google 日历同步！"
-
-#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst-1
-msgid "Successfully sync between Odoo and Google Calendar."
-msgstr "Odoo 与 Google 日历成功同步。"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
-msgid "Synchronize Outlook Calendar with Odoo"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5
-msgid ""
-"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping "
-"track of their tasks and appointments across all related applications."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9
-msgid ":doc:`/applications/general/auth/azure`"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:13
-msgid "Register the application with Microsoft Azure"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:15
-msgid ""
-"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account"
-" is needed. Creating an account is free for users who have never tried or "
-"paid for Azure. For more information, `click here "
-"<https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:19
-msgid ""
-"Refer to `Microsoft's documentation <https://docs.microsoft.com/en-"
-"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to"
-" set up an Azure AD Tenant (also called an *environment*), which is a "
-"representation of an organization to manage and register apps."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:23
-msgid ""
-"Then, `Register an Application <https://docs.microsoft.com/en-"
-"us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the "
-"appropriate :guilabel:`Supported account type`. Users who wish to connect "
-"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any "
-"organizational directory (Any Azure AD directory - Multitenant) and personal"
-" Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported "
-"account types`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:29
-msgid ""
-"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and "
-"copy the Odoo database URI (URL) followed by "
-"`/microsoft_account/authentication`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:33
-msgid ""
-"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` "
-"for the :guilabel:`Redirect URI`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid ""
-"The \"Supported account type\" and \"Redirect URI\" settings in the "
-"Microsoft Azure AD portal."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:40
-msgid ""
-"For more information on the restrictions and limitations of URIs, `check "
-"this page <https://docs. microsoft.com/en-us/azure/active-"
-"directory/develop/reply-url>`_."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:43
-msgid ""
-"Regarding the application credentials, the user *must* add a client secret, "
-"which allows Odoo to authenticate itself, requiring no interaction from the "
-"user's side. :guilabel:`Certificates` are optional."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:47
-msgid ""
-"To do add a client secret, click :guilabel:`Add a certificate or secret` and"
-" then click :guilabel:`New client secret`. Next, type a "
-":guilabel:`Description` and select when the client secret "
-":guilabel:`Expires`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:51
-msgid ""
-"Since resetting the synchronization can be tricky, Odoo recommends setting "
-"the maximum allowed expiration date for the client secret (24 months), so "
-"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to "
-"generate the client secret (:guilabel:`Secret ID`)."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:56
-msgid "Configuration in Odoo"
-msgstr "Odoo 中的配置"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:58
-msgid ""
-"In the Odoo database, go to :menuselection:`Settings --> General Settings "
-"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook Calendar\" setting activated in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:65
-msgid ""
-"From the Microsoft Azure portal, under the :guilabel:`Overview` section of "
-"the application, copy the :guilabel:`Application (Client) ID`, and paste it "
-"into the :guilabel:`Client ID` field in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client ID\" in the Microsoft Azure portal."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:72
-msgid ""
-"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` "
-"section, copy the :guilabel:`Client Secret Value` and paste it into the "
-":guilabel:`Client Secret` field in Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:79
-msgid ""
-"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, "
-"click :guilabel:`Save`."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:84
-msgid "Sync with Outlook"
-msgstr "与 Outlook 同步"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:88
-msgid ""
-"Odoo highly recommends testing the Outlook calendar synchronization on a "
-"test database and a test email address (that is not used for any other "
-"purpose) before attempting to sync the desired Outlook Calendar with the "
-"user's production database."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:92
-msgid ""
-"If the user has any past, present, or future events on their Odoo calendar "
-"before syncing their Outlook calendar, Outlook will treat the events pulled "
-"from Odoo's calendar during the sync as new events, causing an email "
-"notification to be sent from Outlook to all the event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:96
-msgid ""
-"To avoid unwanted emails being sent to all past, present, and future event "
-"attendees, the user must add the events from the Odoo calendar to the "
-"Outlook calendar before the first ever sync, delete the events from Odoo, "
-"and then start the sync."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:100
-msgid ""
-"Even after synchronizing the Odoo Calendar with the Outlook calendar, "
-"Outlook will still send a notification to all event participants every time "
-"an event is edited (created, deleted, unarchived, or event date/time "
-"changed), with no exceptions. This is a limitation that cannot be fixed from"
-" Odoo's side."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:105
-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/general/calendars/outlook/outlook_calendar.rst:112
-msgid ""
-"In summary, once a user synchronizes their Outlook calendar with the Odoo "
-"calendar:"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:114
-msgid ""
-"Creating an event in Odoo causes Outlook to send an invitation to all event "
-"attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:115
-msgid ""
-"Deleting an event in Odoo causes Outlook to send a cancellation to all event"
-" attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:116
-msgid ""
-"Unarchiving an event in Odoo causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:117
-msgid ""
-"Archiving an event in Odoo causes Outlook to send a cancellation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:118
-msgid ""
-"Adding a contact to an event causes Outlook to send an invitation to all "
-"event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:119
-msgid ""
-"Removing a contact from an event causes Outlook to send a cancellation to "
-"all event attendees."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:122
-msgid "Sync Odoo Calendar and Outlook"
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:124
-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 ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst-1
-msgid "The \"Outlook\" sync button in Odoo Calendar."
-msgstr ""
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:132
-msgid ""
-"The synchronization is a two-way process, meaning that events are reconciled"
-" in both accounts (Outlook and Odoo)."
-msgstr "同步是一个双向过程，这意味着事件在两个帐户（Outlook 和 Odoo）中进行协调。"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:136
-msgid ""
-"All users that want to use the synchronization simply need to :ref:`sync "
-"their calendar with Outlook <outlook_calendar/sync_with_outlook>`. The "
-"configuration of Microsoft's Azure account is only done once, as Azure AD "
-"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/general/calendars/outlook/outlook_calendar.rst:143
-msgid ":doc:`../../../productivity/mail_plugins/outlook`"
-msgstr ":doc:`../../../生产力/mail_plugins/展望`"
-
-#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:144
-msgid ":doc:`../google/google_calendar_credentials`"
-msgstr ":doc:`../谷歌/google_calendar_credentials`"
-
 #: ../../content/applications/general/developer_mode.rst:5
 msgid "Developer Mode (debug mode)"
 msgstr "开发人员模式（调试模式）"
@@ -4816,8 +4293,8 @@ msgstr ""
 "，查看要更改语言的用户列表，选择用户并点击左上角的 **编辑** 。可在用户偏好中更改之前已安装的语言，然后点击 **保存** 。"
 
 #: ../../content/applications/general/users/language.rst:61
-msgid ":doc:`../../websites/website/publish/translate`"
+msgid ":doc:`../../websites/website/configuration/translate`"
-msgstr ":doc:`../../网站/网站/发布/翻译`"
+msgstr ""
 
 #: ../../content/applications/general/users/manage_users.rst:3
 msgid "Manage users"

locale/zh_CN/LC_MESSAGES/services.po

@@ -9,18 +9,18 @@
 # 稀饭~~ <wangwhai@qq.com>, 2022
 # Mandy Choy <mnc@odoo.com>, 2022
 # Jeffery CHEN <jeffery9@gmail.com>, 2022
-# Martin Trigaux, 2023
 # Emily Jia <eji@odoo.com>, 2023
 # diaojiaolou <124412206@qq.com>, 2023
+# Martin Trigaux, 2023
 # 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 16.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-04-06 08:12+0000\n"
+"POT-Creation-Date: 2023-04-13 05:55+0000\n"
 "PO-Revision-Date: 2022-10-04 12:54+0000\n"
-"Last-Translator: diaojiaolou <124412206@qq.com>, 2023\n"
+"Last-Translator: Martin Trigaux, 2023\n"
 "Language-Team: Chinese (China) (https://app.transifex.com/odoo/teams/41243/zh_CN/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -324,80 +324,215 @@ msgstr ""
 "`优惠券 <https://www.odoo.com/slides/slide/coupon-programs-640?fullscreen=1>`_"
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3
-msgid "Allow customers to close their tickets"
+msgid "Closing tickets"
-msgstr "允许客户关闭他们的工单"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5
 msgid ""
-"Allowing customers to close their own tickets gives them autonomy and "
+"Once work has been completed on a *Helpdesk* ticket in Odoo, there are "
-"minimizes misunderstandings around when an issue is considered solved or "
+"several ways it can be closed. Manually closing solved tickets keeps the "
-"not. This results in operational capacity for support teams, and higher "
+"pipeline up to date, while automatically closing inactive tickets prevents "
-"satisfaction for the customer."
+"unnecessary blocking issues. Allowing customers to close their own tickets "
-msgstr ""
+"minimizes confusion around whether an issue is considered solved or not. "
-
+"This results in increased operational capacity for support teams, and higher"
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:10
+" customer satisfaction."
-msgid "Enable ticket closing"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12
+msgid "Manually close solved tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14
 msgid ""
-"Start by navigating to :menuselection:`Helpdesk --> Configuration --> "
+"As work on a ticket progresses, it is moved along to the next stage in the "
-"Helpdesk Teams` and choose the appropriate team. Then click :guilabel:`Edit`"
+"pipeline. Once the issue is solved, the ticket is moved to a *folded* stage."
-" and enable :guilabel:`Ticket closing` by checking the field box."
+" This marks the ticket as *closed*."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17
+msgid ""
+"To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and "
+"click on a team to open the pipeline. Hover over a stage's heading, and then"
+" click the gear icon that appears in the top-right corner of that stage's "
+"kanban column."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid "Ticket closing feature in Odoo Helpdesk."
+msgid ""
+"View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage"
+" option."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:19
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26
 msgid ""
-"To designate which stage the ticket migrates to once it is closed, navigate "
+"Clicking the gear icon also displays the option to :guilabel:`Fold` the "
-"to the ticket pipeline by going to :menuselection:`Helpdesk --> Overview` "
+"stage. This setting folds the stage *temporarily* to simplify the kanban "
-"and clicking :guilabel:`Tickets` on the team's card."
+"view. This does *not* close the tickets in this stage. It also does not "
+"permanently fold the stage. If a stage needs to be folded so the tickets can"
+" be marked as closed, continue following the steps below."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:23
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31
 msgid ""
-"There are two options: create a new Kanban stage or work with an existing "
+"From the menu that appears, select :guilabel:`Edit Stage`. This will open "
-"one. For both scenarios, click the :guilabel:`Settings (gear)` icon next to "
+"the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` "
-"the stage name, select :guilabel:`Edit Stage`, and enable :guilabel:`Closing"
+"towards the top of the window, and then :guilabel:`Save & Close` to confirm "
-" Stage`. After checking the field box, click :guilabel:`Save` to finish."
+"the changes. Now, tickets that reach this stage will be considered as "
+"*closed*."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:29
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
-msgid ""
+msgid "Stage settings page."
-"If a closing stage is not specified, by default, the ticket is moved to the "
-"last stage in the kanban. If more than one stage is set as a closing stage, "
-"the ticket is placed in the first closing stage column."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:33
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41
+msgid "Automatically close inactive tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43
 msgid ""
-"With the ticket closing settings now complete, customers can now view the "
+"Tickets that are inactive for a set period of time can be automatically "
-"option to :guilabel:`Close this ticket` when they log into their portal."
+"closed. At that point, they will be moved to a folded stage."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46
+msgid ""
+"Go to the team's settings page by going to :menuselection:`Helpdesk --> "
+"Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable"
+" :guilabel:`Automatic Closing`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49
+msgid ""
+"If one of the team's stages is set to be folded in the kanban view, it will "
+"be the default selection in the :guilabel:`Move to Stage` field. If the team"
+" has more than one folded stage, the stage that occurs first in the pipeline"
+" will be the default. If no stage is folded, the default selection will be "
+"the last stage in the pipeline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54
+msgid ""
+"The :guilabel:`After days of inactivity` field defaults to `7`, but can be "
+"adjusted if necessary."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57
+msgid ""
+"The :guilabel:`After days of inactivity` field does **not** take the working"
+" calendar into account when tracking the amount of time a ticket has been "
+"inactive."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60
+msgid ""
+"If only certain stages should be used to track days of inactivity, they can "
+"be added to the :guilabel:`In Stages` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64
+msgid "A team's pipeline is created with the following stages:"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66
+msgid "`New`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67
+msgid "`In Progress`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68
+msgid "`Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69
+msgid "`Closed`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71
+msgid ""
+"Tickets can linger in the :guilabel:`Customer Feedback stage`, because once "
+"an issue is solved, customers may not respond immediately. At that point, "
+"the tickets can be closed automatically. However, tickets in the "
+":guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due "
+"to assignment or workload issues. Closing these tickets automatically would "
+"result in issues going unsolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77
+msgid ""
+"Therefore, the :guilabel:`Automatic Closing` settings would be configured as"
+" below\\:\\"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79
+msgid ":guilabel:`Automatic Closing`: *checked*"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80
+msgid ":guilabel:`Move to Stage`: `Solved`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81
+msgid ":guilabel:`After``7`:guilabel:`days of inactivity`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82
+msgid ":guilabel:`In Stages`: `Customer Feedback`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0
+msgid "Example of Automatic Closing settings."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89
+msgid "Allow customers to close their own tickets"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91
+msgid ""
+"Enabling the :guilabel:`Closure by Customers` setting allows customers to "
+"close their own ticket(s) when they determine that their issue has been "
+"resolved."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94
+msgid ""
+"Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams`"
+" and select a team. On the team's settings page, scroll to the "
+":guilabel:`Self-Service` section and check the box for :guilabel:`Closure by"
+" Customers`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
+msgid "Customer closing setting in Odoo Helpdesk."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102
+msgid ""
+"Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` "
+"button will be available for customers when they view their ticket through "
+"the customer portal."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
 msgid "Customer view of ticket closing in Odoo Helpdesk."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:40
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110
-msgid "Get reports on tickets closed by customers"
+msgid ""
+"Customers are able to view their tickets by clicking the :guilabel:`View the"
+" ticket` link they receive by email. The link is included in the "
+":guilabel:`Request Acknowledgment` template, which is added to the first "
+"stage of a team by default. This link does not require a customer to have "
+"access to the portal to view or respond to their ticket."
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:42
+#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115
 msgid ""
-"To analyze the tickets that have been closed by customers, go to "
+"Customers with access to the portal will be able to view their tickets under"
-":menuselection:`Helpdesk --> Reporting --> Tickets`. Then, click on the "
+" :menuselection:`My Account --> Tickets`."
-":guilabel:`Filters` menu and choose :guilabel:`Add Custom filter`. Next, set"
-" the custom filter parameters to :guilabel:`Closed by partner` and "
-":guilabel:`is true`. Finally, click :guilabel:`Apply`."
-msgstr ""
-
-#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1
-msgid ""
-"Filter for tickets closed by customers on Odoo Helpdesk's reporting page."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview.rst:5
@@ -903,7 +1038,6 @@ msgid ""
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/ratings.rst:51
-#: ../../content/applications/services/helpdesk/overview/sla.rst:47
 msgid ":doc:`../advanced/close_tickets`"
 msgstr ":doc:`../advanced/close_tickets`"
 
@@ -1143,7 +1277,7 @@ msgid ""
 "The *Live Chat* feature allows website visitors to connect directly with a "
 "support agent or chatbot. During these conversations, *Helpdesk* tickets can"
 " be instantly created by using the :doc:`response command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk`."
+"</applications/websites/livechat/responses>` `/helpdesk`."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125
@@ -1394,10 +1528,9 @@ msgstr ""
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261
 msgid ""
 "During the conversation, an operator can use the shortcut :doc:`command "
-"</applications/websites/livechat/overview/responses>` `/helpdesk` to create "
+"</applications/websites/livechat/responses>` `/helpdesk` to create a ticket "
-"a ticket without leaving the chat window. The transcript from the "
+"without leaving the chat window. The transcript from the conversation will "
-"conversation will be added to the new ticket, under the "
+"be added to the new ticket, under the :guilabel:`Description` tab."
-":guilabel:`Description` tab."
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267
@@ -1458,7 +1591,7 @@ msgid ":doc:`/applications/general/email_communication/email_servers`"
 msgstr ":doc:`/applications/general/email_communication/email_servers`"
 
 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293
-msgid ":doc:`/applications/websites/livechat/overview/get_started`"
+msgid ":doc:`/applications/websites/livechat`"
 msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/reports.rst:3
@@ -1574,80 +1707,302 @@ msgstr "服务级别协议（SLA）"
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:5
 msgid ""
-"Service Level Agreements (SLA) are commitments you make with your customers "
+"A Service Level Agreement (SLA) defines the level of service a customer can "
-"to outline how a service is delivered. It bolsters trust between you and "
+"expect from a supplier. SLAs provide a timeline that tells customers when "
-"your customers as it makes clear what needs to be done, to what standard, "
+"they can expect results, and keeps the support team on target."
-"and when."
-msgstr "服务级别协议（SLA）是您对客户做出的概述服务交付方式的承诺。 它说明了需要完成的工作，达到的标准和时间，从而增强了您与客户之间的信任。"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst:10
-msgid "Create your policies"
-msgstr "建立您的政策"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst:13
-msgid ""
-"First, enable the feature on the settings of the team you would like "
-"policies to be applied, going to :menuselection:`Helpdesk --> Configuration "
-"--> Helpdesk Teams`."
-msgstr "首先，在您希望应用政策的团队的设置上启用该功能，进入 :menuselection:`服务台 --> 设置 --> 服务台团队`。"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst:15
-msgid ""
-"Create your policies through the team’s settings page or go to "
-":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
-msgstr "通过小组的设置页面创建政策，或转到 :menuselection:`服务台 --> 设置 --> 服务级别协议政策`。"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst-1
-msgid "View of an SLA form in Odoo Helpdesk"
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:23
+#: ../../content/applications/services/helpdesk/overview/sla.rst:10
+msgid "Create a new SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:12
 msgid ""
-"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
+"To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to "
-" a ticket needs to have for the policy to be applied."
+"the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`."
-msgstr "选择与该政策相关的  **** ，以及要应用该政策所需的  **低优先**  。"
+" Select a team, scroll to the :guilabel:`Performance` section, and then "
+"check the selection box next to :guilabel:`SLA Policies` to enable it for "
+"that specific team."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a team page in Helpdesk focusing on the SLA Policies setting"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:22
+msgid ""
+"The value indicated next to the :guilabel:`Working Hours` field is used to "
+"determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. "
+"By default, this is determined by the value set in the :guilabel:`Company "
+"Working Hours` field under :menuselection:`Settings app --> Employees --> "
+"Work Organization`."
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:27
 msgid ""
-"**Target** is the stage a ticket needs to reach within the period defined to"
+"To create a new policy, click the smart button on the team`s settings page "
-" satisfy the SLA. The period is based on the ticket’s creation date, and a "
+"or go to :menuselection:`Helpdesk -->  Configuration --> SLA Policies`, and "
-"deadline is set on the ticket’s form once it matches an SLA policy rule. If "
+"click :guilabel:`New`. Start by entering a :guilabel:`Title` and a "
-"a ticket has more than one policy applied to it, the closest deadline of all"
+":guilabel:`Description` for the new policy, and proceed to fill out the form"
-" SLAs is the one considered."
+" using the steps below."
 msgstr ""
-" ****  是工单在定义的满足服务级别协议的期限内需要达到的阶段。 "
-"该期限基于工单的创建日期，并且一旦工单符合服务级别协议政策规则，便会在工单表单上设置截止日期。 "
-"如果工单应用了一项以上的政策，则所有服务级别协议接近的最后期限为所考虑的期限。"
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:29
+#: ../../content/applications/services/helpdesk/overview/sla.rst:33
+msgid "Define the criteria for an SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:35
 msgid ""
-"When a ticket has satisfied an SLA policy, the SLA tag appears in green and "
+"The :guilabel:`Criteria` section is used to identify what tickets this "
-"the deadline field is not shown anymore."
+"policy will be applied to. Fill out the following fields to adjust the "
-msgstr "当工单满足服务级别协议策略时，SLA标签将显示为绿色，并且截止日期字段不再显示。"
+"selection criteria:"
-
-#: ../../content/applications/services/helpdesk/overview/sla.rst-1
-msgid "View of a ticket’s form emphasizing a satisfied SLA in Odoo Helpdesk"
 msgstr ""
 
-#: ../../content/applications/services/helpdesk/overview/sla.rst:37
+#: ../../content/applications/services/helpdesk/overview/sla.rst:38
-msgid "SLA Analysis"
+msgid ""
-msgstr "分析服务级别协议"
+":guilabel:`Team`: a policy can only be applied to one team. *This field is "
+"required.*"
+msgstr ""
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst:39
 msgid ""
-"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply"
+":guilabel:`Priority`: the priority level for a ticket is identified by "
-" *Filters* and *Group by* to identify tickets that should be prioritized and"
+"selecting the number of stars representing the priority level on the kanban "
-" keep track of upcoming deadlines."
+"card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will "
+"only be applied once the priority level has been updated on the ticket to "
+"match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is"
+" made in this field, this policy will only apply to tickets marked as `Low "
+"Priority` (zero stars)."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:44
+msgid ""
+":guilabel:`Types`: ticket types can be helpful when indicating when a ticket"
+" is a customer question, that can be solved with a quick response, or an "
+"issue, that may require additional investigation. Multiple ticket types can "
+"be selected for this field. If no selection is made, this policy will apply "
+"to all ticket types."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:48
+msgid ""
+":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is "
+"about. Multiple tags can be applied to a single ticket."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:50
+msgid ""
+":guilabel:`Customers`: individual contacts or companies may be selected in "
+"this field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:51
+msgid ""
+":guilabel:`Sales Order Items`: this field is available only if a team has "
+"the *Timesheets* app enabled. This allows the ticket to tie directly to a "
+"specific line on a sales order, which must be indicated on the ticket in the"
+" :guilabel:`Sales Order Item` field."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:56
+msgid ""
+"Unless otherwise indicated, multiple selections can be made for each field. "
+"(i.e. multiple :guilabel:`Tags` can be included in a policy, but only one "
+":guilabel:`Priority` level)"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a blank SLA policy record"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:64
+msgid "Establish a target for an SLA policy"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:66
+msgid ""
+"The :guilabel:`Target` is the stage a ticket needs to reach, and the time "
+"alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service "
+"Level Agreement)` policy. Any stage assigned to a team may be selected for "
+"the :guilabel:`Reach Stage` field. Time spent in stages selected in "
+":guilabel:`Excluding Stages` will not be included in the calculation of the "
+":abbr:`SLA (Service Level Agreement)` deadline."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:73
+msgid ""
+"An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks "
+"the working time before a ticket is completed, and would have `Solved` as "
+"the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level "
+"Agreement)` was titled `2 Days to Start`, it tracks the working time before "
+"work on a ticket has begun, and would have `In Progress` as the "
+":guilabel:`Reach Stage`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:79
+msgid "Meeting SLA deadlines"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:81
+msgid ""
+"Once it is determined that a ticket fits the criteria of an :abbr:`SLA "
+"(Service Level Agreement)` policy, a deadline is calculated. The deadline is"
+" based on the creation date of the ticket, and the targeted working hours. "
+"The deadline is then added to the ticket, as well as a white tag indicating "
+"the name of the :abbr:`SLA (Service Level Agreement)` applied."
 msgstr ""
-"转到 :menuselection:`服务台 --> 报告 --> 服务级别协议状态分析` 。 应用 *过滤器* 和 *分组依据* "
-"来确定应优先处理的票证，并跟踪即将到来的截止日期。"
 
 #: ../../content/applications/services/helpdesk/overview/sla.rst-1
 msgid ""
-"View of the SLA status analysis page emphasizing the group by option in Odoo"
+"View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo"
 " Helpdesk"
 msgstr ""
 
+#: ../../content/applications/services/helpdesk/overview/sla.rst:91
+msgid ""
+"If a ticket fits the criteria for more than one :abbr:`SLA (Service Level "
+"Agreement)`, the earliest occurring deadline will be displayed on the "
+"ticket. Once that deadline has passed, the next deadline will be displayed."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:95
+msgid ""
+"Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the"
+" :abbr:`SLA (Service Level Agreement)` tag turns green, and the "
+":guilabel:`Deadline` field disappears from view on the."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:102
+msgid ""
+"If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket "
+"has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level "
+"Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level "
+"Agreement)` has failed, the red tag will stay on the ticket, even after the "
+"ticket is moved to the :guilabel:`Reach Stage`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid ""
+"View of a ticket's form with a failing and passing SLA in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:112
+msgid "Analyzing SLA performance"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:114
+msgid ""
+"The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA "
+"(Service Level Agreement)` is fulfilled, as well as the success rate of "
+"individual policies. Navigate to the report and corresponding pivot table by"
+" going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:120
+msgid "Using the Pivot view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:122
+msgid ""
+"By default, the report is displayed in a :guilabel:`Pivot` view, and is "
+"filtered to show the number of SLAs failed and the failure rate over the "
+"last 30 days, grouped by team."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in Odoo Helpdesk"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:129
+msgid ""
+"To add the number of SLAs passed or in progress, click the "
+":guilabel:`Measures` button to reveal a drop-down menu of reporting "
+"criteria, and choose from the options available based on the measurements "
+"preferred. Whenever a measurement is picked, a check mark will appear in the"
+" drop-down menu to indicate that that measurement is included, and a "
+"corresponding new column will emerge in the pivot table to show the relevant"
+" calculations."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:135
+msgid ""
+"To add a group to a row or column, click the plus :guilabel:` + ` button "
+"next to :guilabel:`Total`, and then select one of the groups. To remove one,"
+" click the minus :guilabel:` - ` button and deselect."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:140
+msgid "Using the Graph view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:142
+msgid ""
+"The :guilabel:`Status Analysis` report can also be viewed as a "
+":guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between "
+"these views by selecting the appropriate icon at the top of the chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:148
+msgid "Bar Chart"
+msgstr "柱状图"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in bar view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:154
+msgid "Line Chart"
+msgstr "线状图"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in line view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:160
+msgid "Pie Chart"
+msgstr "饼图"
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:0
+msgid "View of the SLA status analysis report in pie chart view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:167
+msgid ""
+"Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed "
+":guilabel:`Stacked`. This presents two or more groups to appear on top of "
+"each other instead of next to each other, making it easier to compare data."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:172
+msgid "Using the Cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:174
+msgid ""
+"The :guilabel:`Cohort` view is used to track the changes in data over a "
+"period of time. To display the :guilabel:`Status Analysis` report in a "
+":guilabel:`Cohort` view, click the icon in the top right corner above the "
+"chart."
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst-1
+msgid "View of the SLA status analysis report in cohort view"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:183
+msgid ":ref:`Reporting views <reporting/views>`"
+msgstr ""
+
+#: ../../content/applications/services/helpdesk/overview/sla.rst:184
+msgid ""
+":doc:`Allow customers to close their tickets "
+"</applications/services/helpdesk/advanced/close_tickets>`"
+msgstr ""
+
 #: ../../content/applications/services/helpdesk/timesheet_and_invoice.rst:5
 msgid "Timesheet and Invoice"
 msgstr "工时单和开票"