# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-03-18 13:48+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../content/applications/general.rst:3
msgid "Miscellaneous"
msgstr ""

#: ../../content/applications/general/apps_modules.rst:3
msgid "Apps and modules"
msgstr ""

#: ../../content/applications/general/apps_modules.rst:5
msgid "You can :ref:`install <general/install>`, :ref:`upgrade <general/upgrade>` and :ref:`uninstall <general/uninstall>` all apps and modules from the :menuselection:`Apps` dashboard."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:8
msgid "By default, an *Apps* filter is applied. If you want to search for modules, click on *Filters* and select *Extra*."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:16
msgid "Odoo is *not a smartphone*, and its apps shouldn't be installed or uninstalled carelessly. Apply caution when adding or removing apps and modules on your database since this may impact your subscription costs."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:0
msgid "**Installing or uninstalling apps and managing users is up to you.**"
msgstr ""

#: ../../content/applications/general/apps_modules.rst:0
msgid "As the administrator of your database, you are responsible for its usage, as you know best how your organization works."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:0
msgid "**Odoo apps have dependencies.**"
msgstr ""

#: ../../content/applications/general/apps_modules.rst:0
msgid "Installing some apps and features with dependencies may also install additional apps and modules that are technically required, even if you won't actively use them."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:0
msgid "**Test app installation/removal on a duplicate of your database.**"
msgstr ""

#: ../../content/applications/general/apps_modules.rst:0
msgid "This way, you can know what app dependencies may be required or what data may be erased."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:32
msgid "Install apps and modules"
msgstr ""

#: ../../content/applications/general/apps_modules.rst:34
msgid "Go to :menuselection:`Apps`, and click on the *Install* button of the app you want to install."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:37
msgid "If the module you are looking for is not listed, you can **update the app list**."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:39
msgid "To do so, activate the :ref:`developer mode <developer-mode>`, then go to :menuselection:`Apps --> Update Apps List` and click on *Update*."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:45
msgid "Upgrade apps and modules"
msgstr ""

#: ../../content/applications/general/apps_modules.rst:47
msgid "On some occasions, new improvements or app features are added to :doc:`supported versions of Odoo </administration/maintain/supported_versions>`. To be able to use them, you must **upgrade** your app."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:50
msgid "Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you want to upgrade, then on *Upgrade*."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:56
msgid "Uninstall apps and modules"
msgstr ""

#: ../../content/applications/general/apps_modules.rst:58
msgid "Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you want to uninstall, then on *Uninstall*."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:64
msgid "Some apps have dependencies, meaning that one app requires another. Therefore, uninstalling one app may uninstall multiple apps and modules. Odoo warns you which dependant apps and modules are affected by it."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:71
msgid "To complete the uninstallation, click on *Confirm*."
msgstr ""

#: ../../content/applications/general/apps_modules.rst:74
msgid "Uninstalling an app also uninstalls all its dependencies and permanently erases their data."
msgstr ""

#: ../../content/applications/general/auth.rst:5
msgid "Authentication"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:3
msgid "Two-factor Authentication"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:5
msgid "Two-factor authentication (\"2FA\") is a good way to improve the security of an account, to make it less likely that an other person will manage to log in instead of you."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:9
msgid "Practically, it means storing a secret inside an *authenticator* (usually your cell phone) and exchanging a code from the authenticator when you try to log in."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:13
msgid "This means an attacker needs *both* to have guessed (or found) your password and to access (or steal) your authenticator, a more difficult proposition than either one or the other."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:18
msgid "Requirements"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:20
msgid "These lists are just examples, they are not endorsements of any specific software."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:23
msgid "If you don't already have one, you will need to choose an authenticator."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:26
msgid "Phone-based authenticators are the easiest and most common so we will assume you'll pick and install one on your phone, examples include `Authy <https://authy.com/>`_, `FreeOTP <https://freeotp.github.io/>`_, `Google Authenticator <https://support.google.com/accounts/answer/1066447?hl=en>`_, `LastPass Authenticator <https://lastpass.com/auth/>`_, `Microsoft Authenticator <https://www.microsoft.com/en-gb/account/authenticator?cmp=h66ftb_42hbak>`_, ...; password managers also commonly include :abbr:`2FA (two-factor authentication)` support e.g. `1Password <https://support.1password.com/one-time-passwords/>`_, `Bitwarden <https://bitwarden.com/help/article/authenticator-keys/>`_, ..."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:39
msgid "For the sake of demonstration we will be using Google Authenticator (not because it is any good but because it is quite common)."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:43
msgid "Setting up two-factor authentication"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:45
msgid "Once you have your authenticator of choice, go to the Odoo instance you want to setup :abbr:`2FA (two-factor authentication)`, then open :guilabel:`Preferences` (or :guilabel:`My Profile`):"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:52
msgid "Open the :guilabel:`Account Security` tab, then click the :guilabel:`Enable two-factor authentication` button:"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:58
msgid "Because this is a security-sensitive action, you will need to input your password:"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:64
msgid "After which you will see this screen with a barcode:"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:69
msgid "In most applications, you can simply *scan the barcode* via the authenticator of your choice, the authenticator will then take care of all the setup:"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:78
msgid "If you can not scan the screen (e.g. because you are doing this set-up on the same phone as the authenticator application), you can click the provided link, or copy the secret to manually set-up your authenticator:"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:89
msgid "Once this is done, the authenticator should display a *verification code* with some useful identifying information (e.g. the domain and login for which the code is):"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:96
msgid "You can now input the code into the :guilabel:`Verification Code` field, then click the :guilabel:`Enable two-factor authentication` button."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:100
msgid "Congratulation, your account is now protected by two-factor authentication!"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:107
msgid "Logging in"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:109
msgid "You should now :guilabel:`Log out` to follow along."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:111
msgid "On the login page, input the username and password of the account for which you set up :abbr:`2FA (two-factor authentication)`, rather than immediately enter Odoo you will now get a second log-in screen:"
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:118
msgid "Get your authenticator, input the code it provides for the domain and account, validate, and you're now in."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:121
msgid "And that's it. From now on, unless you disable :abbr:`2FA (two-factor authentication)` you will have a two-step log-in process rather than the old one-step process."
msgstr ""

#: ../../content/applications/general/auth/2fa.rst:125
msgid "Don't lose your authenticator, if you do, you will need an *Odoo Administrator* to disable :abbr:`2FA (two-factor authentication)` on the account."
msgstr ""

#: ../../content/applications/general/auth/azure.rst:3
msgid "OAuth"
msgstr ""

#: ../../content/applications/general/auth/azure.rst:5
msgid "Due to specific requirements in Azure's OAuth implementation, Microsoft Azure OAuth identification is NOT compatible with Odoo at the moment."
msgstr ""

#: ../../content/applications/general/auth/google.rst:3
msgid "Google Sign-In Authentication"
msgstr ""

#: ../../content/applications/general/auth/google.rst:5
msgid "The **Google Sign-In Authentication** is a useful function that allows your users to sign in to Odoo with their Google account."
msgstr ""

#: ../../content/applications/general/auth/google.rst:8
msgid "This is particularly helpful if your organization uses Google Workforce and you want the employees within your organization to connect to Odoo with their Google Accounts."
msgstr ""

#: ../../content/applications/general/auth/google.rst:14
#: ../../content/applications/general/voip/axivox.rst:16
#: ../../content/applications/general/voip/onsip.rst:13
msgid "Configuration"
msgstr ""

#: ../../content/applications/general/auth/google.rst:16
msgid "The integration of the Google sign-in function requires configuration both on Google and on Odoo."
msgstr ""

#: ../../content/applications/general/auth/google.rst:21
msgid "Google API Dashboard"
msgstr ""

#: ../../content/applications/general/auth/google.rst:23
msgid "Go to the `Google API Dashboard <https://console.developers.google.com/>`_."
msgstr ""

#: ../../content/applications/general/auth/google.rst:24
msgid "Make sure the right project is opened. If you don't have a project yet, click on *Create Project*, fill out the project name and other details of your company, and click on *Create*."
msgstr ""

#: ../../content/applications/general/auth/google.rst:32
msgid "Choose the name of your own company from the drop-down menu."
msgstr ""

#: ../../content/applications/general/auth/google.rst:37
msgid "OAuth consent screen"
msgstr ""

#: ../../content/applications/general/auth/google.rst:39
msgid "On the left side menu, click on :menuselection:`OAuth consent screen`."
msgstr ""

#: ../../content/applications/general/auth/google.rst:45
msgid "Choose one of the options **(Internal / External)** as instructed, and click on *Create*."
msgstr ""

#: ../../content/applications/general/auth/google.rst:51
msgid "Fill out your details and domain info, then click on *Save and Continue*."
msgstr ""

#: ../../content/applications/general/auth/google.rst:52
msgid "On the **Scopes** page, leave all fields as is, and click on *Save and Continue*."
msgstr ""

#: ../../content/applications/general/auth/google.rst:57
msgid "Credentials"
msgstr ""

#: ../../content/applications/general/auth/google.rst:59
msgid "On the left side menu, click on :menuselection:`Credentials`."
msgstr ""

#: ../../content/applications/general/auth/google.rst:65
msgid "Click on *Create Credentials* and select **OAuth client ID**."
msgstr ""

#: ../../content/applications/general/auth/google.rst:71
msgid "Select **Web Application** as the Application type. Now configure the allowed pages on which you will be redirected."
msgstr ""

#: ../../content/applications/general/auth/google.rst:74
msgid "In order to achieve this, in the **Authorized redirect URIs** field, enter your database's domain immediately followed by ``/auth_oauth/signin``. For example: ``https://mydomain.odoo.com/auth_oauth/signin``, then click on *Create*."
msgstr ""

#: ../../content/applications/general/auth/google.rst:85
msgid "Google Authentication on Odoo"
msgstr ""

#: ../../content/applications/general/auth/google.rst:90
msgid "Retrieve the Client ID"
msgstr ""

#: ../../content/applications/general/auth/google.rst:92
msgid "Once you have done the previous steps, two keys are generated on the Google API Dashboard: *Client ID* and *Client Secret*. Copy the *Client ID*."
msgstr ""

#: ../../content/applications/general/auth/google.rst:102
msgid "Odoo activation"
msgstr ""

#: ../../content/applications/general/auth/google.rst:104
msgid "Go to :menuselection:`Odoo General Settings --> Integrations` and activate **OAuth Authentication**."
msgstr ""

#: ../../content/applications/general/auth/google.rst:108
msgid "You may have to log in again after this step."
msgstr ""

#: ../../content/applications/general/auth/google.rst:110
msgid "Go back to :menuselection:`General Settings --> Integrations`, activate **Google Authentication**, then fill out the *Client ID* with the key from the Google API Dashboard, and *Save*."
msgstr ""

#: ../../content/applications/general/auth/google.rst:121
msgid "Log in to Odoo with Google"
msgstr ""

#: ../../content/applications/general/auth/google.rst:123
msgid "To link your Google account to your Odoo profile, click on *Log in with Google* when you are asked to choose a new password."
msgstr ""

#: ../../content/applications/general/auth/google.rst:130
msgid "Existing users must :ref:`reset their password <users/reset-password>` to access the *reset password* page, while new users can directly click on *Log in with Google* instead of choosing a new password."
msgstr ""

#: ../../content/applications/general/auth/google.rst:135
msgid "`Google Cloud Platform Console Help - Setting up OAuth 2.0 <https://support.google.com/cloud/answer/6158849>`_"
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:3
msgid "Sign in with LDAP"
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:5
msgid "Install the LDAP module in General Settings."
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:7
msgid "Click on **Create** in Setup your LDAP Server."
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:15
msgid "Choose the company about to use the LDAP."
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:20
msgid "In **Server Information**, enter the IP address of your server and the port it listens to."
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:22
msgid "Tick **User TLS** if your server is compatible."
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:27
msgid "In **Login Information**, enter ID and password of the account used to query the server. If left empty, the server will be queried anonymously."
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:32
msgid "In **Process Parameter**, enter the domain name of your LDAP server in LDAP nomenclature (e.g. ``dc=example,dc=com``)."
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:34
msgid "In **LDAP filter**, enter ``uid=%s``"
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:39
msgid "In **User Information**, tick *Create User* if you want Odoo to create a User profile the first time someone log in with LDAP."
msgstr ""

#: ../../content/applications/general/auth/ldap.rst:41
msgid "In **Template User**, indicate a template for the new profiles created. If 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 "Odoo is perfectly integrated with Google Calendar so that you can see & manage your meetings from both platforms (updates go through both directions)."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
msgid "Setup in Google"
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:11
msgid "Go to `Google APIs platform <https://console.developers.google.com>`__ to generate Google Calendar API credentials. Log in with your Google account."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:14
msgid "Go to the API & Services page."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:19
msgid "Search for *Google Calendar API* and select it."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:27
msgid "Enable the API."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:32
msgid "Select or create an API project to store the credentials if not yet done before. Give it an explicit name (e.g. Odoo Sync)."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
msgid "Create credentials."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:40
msgid "Select *Web browser (Javascript)* as calling source and *User data* as kind of data."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:46
msgid "Then you can create a Client ID. Enter the name of the application (e.g. Odoo Calendar) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance URL followed by '/google_account/authentication'."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
msgid "Go through the Consent Screen step by entering a product name (e.g. Odoo Calendar). Feel free to check the customizations options but this is not mandatory. The Consent Screen will only show up when you enter the Client ID in Odoo for the first time."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:60
msgid "Finally you are provided with your **Client ID**. Go to *Credentials* to get the **Client Secret** as well. Both of them are required in Odoo."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
msgid "Setup in Odoo"
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
msgid "Install the **Google Calendar** App from the *Apps* menu or by checking the option in :menuselection:`Settings --> General Settings`."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
msgid "Go to :menuselection:`Settings --> General Settings` and enter your **Client ID** and **Client Secret** in Google Calendar option."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:81
msgid "The setup is now ready. Open your Odoo Calendar and sync with Google. The first time you do it you are redirected to Google to authorize the connection. Once back in Odoo, click the sync button again. You can click it whenever you want to synchronize your calendar."
msgstr ""

#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
msgid "As of now you no longer have excuses to miss a meeting!"
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
msgid "Synchronization with Outlook's Calendar"
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:5
msgid "Synchronizing your **main** Outlook Calendar with Odoo is useful to keep track of your tasks and appointments, and across all related applications."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:9
msgid "Register your application with the Microsoft identity platform"
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:13
msgid "In order to be able to sync your Outlook Calendar with Odoo's Calendar, a Microsoft Azure account is needed. The creation of an account is free for users that 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:15
msgid "Following, `Set up an Azure AD Tenant <https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-create-new-tenant>`_, also called environment, which is a representation of an organization, to manage and register apps."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:17
msgid "Ultimately, `Register an Application <https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app>`_, choosing the appropriate supported account type."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:20
msgid "When configuring your platform settings, choose *Web*."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:0
msgid "For the **Redirect URI restrictions**, copy your Odoo database URI followed by ``/microsoft_account/authentication``. Example:"
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:0
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:37
msgid "Regarding credentials, you *must* **Add a client secret**, called *Client Secret* in Odoo, which allows Odoo to authenticate itself, requiring no interaction from your side. *Certificates* are optional."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:42
msgid "Configuration in Odoo"
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:44
msgid "Go to general *Settings* and activate the *Outlook Calendar* feature."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:50
msgid "From your Azure portal, under *Overview*, copy your *Application (client) ID*, and paste it to *Client ID* in Odoo."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:57
msgid "Going back to your Azure portal, now under *Certificates & secrets*, copy your *Client Secret Value* and paste it to *Client Secret* in Odoo."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:67
msgid "Sync with Outlook"
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:0
msgid "Odoo Calendar sends a confirmation email at the creation of an event to its attendees. But, on the **first** sync, Outlook will also send confirmation emails of all scheduled events (including past ones)."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:0
msgid "To avoid this situation, we recommend *archiving all past events, and removing yourself from future ones in Odoo Calendar before the first sync*. This will prevent events from being created in Outlook, and therefore, no redundant emails will be sent during the first synchronization. After the sync, events will only send one confirmation email."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:82
msgid "Go to the *Calendar* application and *Sync with Outlook*. You are asked to log in to your account, if you are not already, and grant the required permissions."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:89
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:97
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' are unique, and represent an organization that helps you to manage a specific instance of Microsoft cloud services for your internal and external users."
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:103
msgid ":doc:`../../../sales/crm/optimize/outlook_extension`"
msgstr ""

#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:104
msgid ":doc:`../google/google_calendar_credentials`"
msgstr ""

#: ../../content/applications/general/developer_mode.rst:5
msgid "Developer Mode (debug mode)"
msgstr ""

#: ../../content/applications/general/developer_mode.rst:7
msgid "The developer mode (or debug mode) gives you access to extra and advanced tools."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:10
msgid "Activate through the Settings"
msgstr ""

#: ../../content/applications/general/developer_mode.rst:12
msgid "Go to :menuselection:`Settings --> Activate the developer mode`."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:19
msgid "*Activate the developer mode (with assets)* is used by developers; *Activate the developer mode (with tests assets)* is used by developers and testers."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:22
msgid "Once activated, the *Deactivate the developer mode* option becomes available."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:25
msgid "Activate through a browser extension"
msgstr ""

#: ../../content/applications/general/developer_mode.rst:28
msgid "Go to the settings and extensions of your web browser, and search for *Odoo Debug*. Once the extension is installed, a new icon will be shown on your toolbar."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:30
msgid "For the *Odoo Debug* extension, a single click enables a normal version of the mode, while a double click enables it with assets. To deactivate it, use a single click."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:37
msgid "Activate through the URL"
msgstr ""

#: ../../content/applications/general/developer_mode.rst:39
msgid "In the URL add ``?debug=1`` or ``?debug=true`` after *web*."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:46
msgid "Developers: type ``?debug=assets`` and activate the mode with assets."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:49
msgid "Locate the mode tools"
msgstr ""

#: ../../content/applications/general/developer_mode.rst:51
msgid "The Developer mode tools can be accessed from the *Open Developer Tools* button, located on the header of your pages."
msgstr ""

#: ../../content/applications/general/email_communication.rst:5
msgid "Email Communication"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:3
msgid "Sending emails with Odoo"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:6
msgid "Using your email domain in Odoo"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:8
msgid "Documents in Odoo (a CRM opportunity, a sales order, an invoice ...) have a discussion thread, called *chatter*."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:11
msgid "When you post a message in the chatter, this message is sent by email to the followers of the document. If a follower replies to the message, the reply updates the chatter, and Odoo relays the reply to the followers."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:15
msgid "Emails from your users to partners (customers, vendors) are sent from the email address of your users. Similarly, emails from partners to users are sent from the email address of the partners. This allows you to recognize at a glance who sent an email relayed by Odoo."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:19
msgid "If your database is hosted on our cloud (Odoo Online or Odoo.sh), it is not necessary to add an outgoing email server to send emails from your custom domain. You can enjoy this feature by using the default Odoo email server."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:24
msgid "The Odoo server is subject to a daily email limit to prevent abuse. The default limit is 200 emails sent per day for databases with an Enterprise subscription. This limit can be increased under certain conditions. See our :doc:`FAQ <faq>` or contact support for more information."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:29
msgid "However, it is recommended that you configure your domain name to ensure that emails from your users reach your partners, rather than being considered spam."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:32
msgid "For the same reason, we recommend that you always give your users an email address from a domain you manage, rather than a generic email address (gmail.com, outlook.com, etc.)."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:38
msgid "Be SPF compliant"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:40
msgid "The Sender Policy Framework (SPF) protocol allows the owner of a domain name to specify which servers are allowed to send email from that domain. When a server receives an incoming email, it checks whether the IP address of the sending server is on the list of allowed IPs according to the SPF record of the sender."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:46
msgid "The SPF verification is performed on the domain mentioned in the Return-Path field of the email. In the case of an email sent by Odoo, this domain corresponds to the value of the `mail.catchall.domain` key in the database system parameters."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:50
msgid "See the :ref:`documentation on incoming emails <email_communication/inbound_messages>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:52
msgid "The SPF policy of a domain is set using a TXT record. How to create or modify a TXT record depends on the provider hosting the DNS zone of your domain name. In order for the verification to work properly, each domain can only have one SPF record."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:56
msgid "If your domain name does not yet have an SPF record, the content of the record to create is as follows:"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:59
msgid "``v=spf1 include:_spf.odoo.com ~all``"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:61
msgid "If your domain name already has an SPF record, you need to update this record (and do not create a new one)."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:66
msgid "If your TXT record is `v=spf1 include:_spf.google.com ~all`, you need to edit it to add `include:_spf.odoo.com`: `v=spf1 include:_spf.odoo.com include:_spf.google.com ~all`"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:69
msgid "You can check if your SPF record is valid with a free tool like `MXToolbox SPF <https://mxtoolbox.com/spf.aspx>`_."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:75
msgid "Enable DKIM"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:77
msgid "The DomainKeys Identified Mail (DKIM) allows you to authenticate your emails with a digital signature."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:79
msgid "When sending an email, the Odoo server includes a unique DKIM signature in the headers. The recipient's server decrypts this signature using the DKIM record in your domain name. If the signature and the key contained in the record match, this guarantees that your message is authentic and has not been altered during transport."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:84
msgid "To enable DKIM, you must add a CNAME record to the DNS zone of your domain name:"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:86
msgid "``odoo._domainkey IN CNAME odoo._domainkey.odoo.com.``"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:89
msgid "If your domain name is `mycompany.com`, you need to create a subdomain `odoo._domainkey.mycompany.com` whose canonical name is `odoo._domainkey.odoo.com.`."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:92
msgid "How to create or modify a CNAME record depends on the provider hosting the DNS zone of your domain name. The most common providers are list below."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:95
msgid "You can check if your DKIM record is valid with a free tool like `DKIM Core <https://dkimcore.org/tools/>`_. If a selector is asked, enter `odoo`."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:99
msgid "Check your DMARC policy"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:101
msgid "The Domain-based Message Authentication, Reporting & Conformance (DMARC) is a protocol that unifies SPF and DKIM. The instructions contained in the DMARC record of a domain name tell the destination server what to do with an incoming email that fails the SPF and/or DKIM check."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:105
msgid "There are three DMARC policies: - ``p=none`` - ``p=quarantine`` - ``p=reject``"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:110
msgid "``p=quarantine`` and ``p=reject`` instruct the server that receives an email to quarantine that email or ignore it if the SPF and/or DKIM check fails."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:113
msgid "If your domain name uses DMARC and has defined one of these policies, it is therefore imperative to be SPF compliant or to enable DKIM."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:117
msgid "Yahoo or AOL are examples of email providers with a DMARC policy set to ``p=reject``. We strongly advise against using an *@yahoo.com* or *@aol.com* address for your users. These emails will never reach their recipient."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:121
msgid "``p=none`` is used for the domain owner to receive reports about entities using their domain. It should not impact the deliverability if the DMARC check fails."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:124
msgid "You can check the DMARC record of a domain name with a tool like `MXToolbox DMARC <https://mxtoolbox.com/DMARC.aspx>`_."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:127
msgid "If one of your partners, customer or vendor, uses DMARC and has defined one of these policies, the Odoo server cannot relay emails from this partner to your users."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:130
msgid "You need to :ref:`handle user notifications in Odoo <discuss_app/notification_preferences>`, or replace the email address of the partner with a default email address."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:136
msgid "SPF, DKIM & DMARC documentation of common providers"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:138
msgid "`OVH DNS <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/>`_"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:139
msgid "`OVH SPF <https://docs.ovh.com/us/en/domains/web_hosting_the_spf_record/>`_"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:140
msgid "`GoDaddy TXT record <https://www.godaddy.com/help/add-a-txt-record-19232>`_"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:141
msgid "`GoDaddy SPF <https://www.godaddy.com/help/add-an-spf-record-19218>`_"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:142
msgid "`GoDaddy DKIM <https://www.godaddy.com/help/add-a-cname-record-19236>`_"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:143
msgid "`NameCheap <https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-do-i-add-txtspfdkimdmarc-records-for-my-domain/>`_"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:144
msgid "`CloudFlare DNS <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:145
msgid "`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:146
msgid "`Azure DNS <https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal>`_"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:148
msgid "To fully test your configuration, the tool `Mail-Tester <https://www.mail-tester.com/>`_ will give you a full overview of the content and configuration you have in one email sent! Mail-Tester can also be used for other lesser known providers."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:153
msgid "Use a default email address"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:155
msgid "To force the email address from which emails are sent, you need to create one of these two keys in the System Parameters of the database:"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:158
msgid "If ``mail.force.smtp.from`` is set, all outgoing emails are sent from the given address. This is a requirement to use `Outlook with Odoo <https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365#option-1-authenticate-your-device-or-application-directly-with-a-microsoft-365-or-office-365-mailbox-and-send-mail-using-smtp-auth-client-submission>`_."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:160
msgid "If ``mail.dynamic.smtp.from`` is set, the from email address is replaced by the given one if the domain does not match the domain set in `mail.catchall.domain`."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:163
msgid "You access the **System Parameters** in :ref:`developer mode <developer-mode>` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:3
msgid "Send and Receive Emails in Odoo with an Email Server"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:6
msgid "If you are a user of Odoo Online or Odoo.sh..."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:8
msgid "You have nothing to do! **Odoo sets up its own mail servers for your database.** Outgoing and incoming emails work out-of-the-box!"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:11
msgid "Unless you plan to send large batches of mass mailing that could require the use of an external mail server, simply enjoy your new Odoo database."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:16
msgid "Scope of this documentation"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:18
msgid "This document is **mainly dedicated to Odoo on-premise users** who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online <https://www.odoo.com/trial>`_ & `Odoo.sh <https://www.odoo.sh>`_."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:24
msgid "If no one in your company is used to manage email servers, we strongly recommend that you opt for those Odoo hosting solutions. Their email system works instantly and is monitored by professionals. Nevertheless you can still use your own email servers if you want to manage your email server's reputation yourself."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:30
msgid "You will find here some useful information on how to integrate your own email solution with Odoo."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:34
msgid "Office 365 email servers don't easily allow to send external emails from hosts like Odoo. Refer to `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`_ to make it work."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:39
msgid "How to manage outbound messages"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:40
msgid "As a system admin, go to :menuselection:`Settings --> General Settings` and check *External Email Servers*. Then, click *Outgoing Mail Servers* to create one and reference the SMTP data of your email server. Once all the information has been filled out, click on *Test Connection*."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:45
msgid "Here is a typical configuration for a G Suite server."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:50
msgid "Then set your email domain name in the General Settings."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:53
msgid "If you get a ``[AUTHENTICATIONFAILED] Invalid credentials (Failure)`` warning when you *Test Connection* on a Gmail address, activate the *Less secure app access* option. A direct link can be `accessed here <https://myaccount.google.com/lesssecureapps?pli=1>`_."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:57
msgid "In addition to that, enable the IMAP setting on your Gmail account."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:61
msgid "Can I use an Office 365 server"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:62
msgid "You can use an Office 365 server if you run Odoo on-premise. Office 365 SMTP relays are not compatible with Odoo Online unless you configure Odoo to :ref:`force the outgoing \"From\" address <email_communication/default_from>` ."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:66
msgid "Please refer to `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`_ to configure a SMTP relay for your Odoo's IP address."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:71
msgid "How to use a G Suite server"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:72
msgid "You can use an G Suite server for any Odoo hosting type. To do so you need to setup the SMTP relay service. The configuration steps are explained in `Google documentation <https://support.google.com/a/answer/2956491?hl=en>`__."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:77
msgid "Restriction"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:78
msgid "Please note that port 25 is blocked for security reasons on our SaaS and Odoo.sh platform. Try using 465, 587, or 2525."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:84
msgid "Use a default \"From\" email address"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:86
msgid "Sometimes, an email's \"From\" (outgoing) address can belong to a different domain, and that can be a problem."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:89
msgid "For example, if a customer with address *mary@customer.example.com* responds to a message, Odoo will try to redistribute that same email to other subscribers in the thread. But if the domain *customer.example.com* forbids that kind of usage for security, the Odoo's redistributed email would get rejected by some recipients' mail servers."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:95
msgid "To avoid those kind of problems, you should make sure all emails use a \"From\" address from your authorized domain."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:98
msgid "If your MTA supports `SRS (Sender Rewriting Scheme) <https://en.wikipedia.org/wiki/Sender_Rewriting_Scheme>`_, you can enable it to handle these situations. However, that is more complex and requires more technical knowledge that is not meant to be covered by this documentation."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:103
msgid "Instead, you can also configure Odoo to do something similar by itself:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:105
#: ../../content/applications/general/email_communication/email_servers.rst:159
msgid "Set your domain name in the General Settings."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:110
msgid "In developer mode, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:113
msgid "Add one system parameter from these:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:115
msgid "If you want *all* your outgoing messages to use the same \"From\" address, use the key ``mail.force.smtp.from`` and set that address as value (such as ``outgoing@mycompany.example.com``)."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:119
msgid "If you want to keep the original \"From\" address for emails that use your same domain, but change it for emails that use a different domain, use the key ``mail.dynamic.smtp.from`` and set as value the email address that should be used in those cases (such as ``outgoing@mycompany.example.com``)."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:128
msgid "How to manage inbound messages"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:130
msgid "Odoo relies on generic email aliases to fetch incoming messages."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:132
msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the catchall alias (**catchall@**)."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:136
msgid "**Bounced messages** are routed to **bounce@** in order to track them in Odoo. This is especially used in `Odoo Email Marketing <https://www.odoo.com/page/email-marketing>`__ to opt-out invalid recipients."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:140
msgid "**Original messages**: Several business objects have their own alias to create new records in Odoo from incoming emails:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:143
msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM <https://www.odoo.com/page/crm>`__),"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:145
msgid "Support Channel (to create Tickets in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`__),"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:147
msgid "Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page/project-management>`__),"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:149
msgid "Job Positions (to create Applicants in `Odoo Recruitment <https://www.odoo.com/page/recruitment>`__),"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:151
msgid "etc."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:153
msgid "Depending on your mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in your mail server."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:157
msgid "Create the corresponding email addresses in your mail server (catchall@, bounce@, sales@, etc.)."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:164
msgid "If you use Odoo on-premise, create an *Incoming Mail Server* in Odoo for each alias. You can do it from the General Settings as well. Fill out the form according to your email provider’s settings. Leave the *Actions to Perform on Incoming Mails* blank. Once all the information has been filled out, click on *TEST & CONFIRM*."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:173
msgid "If you use Odoo Online or Odoo.sh, We do recommend to redirect incoming messages to Odoo's domain name rather than exclusively use your own email server. That way you will receive incoming messages without delay. Indeed, Odoo Online is fetching incoming messages of external servers once per hour only. You should set redirections for all the email addresses to Odoo's domain name in your email server (e.g. *catchall@mydomain.ext* to *catchall@mycompany.odoo.com*)."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:183
msgid "All the aliases are customizable in Odoo."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:181
msgid "Object aliases can be edited from their  respective configuration view. To edit catchall and bounce aliases, you first need to activate the :ref:`developer mode <developer-mode>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:185
msgid "Then go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & * mail.bounce.alias*)."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:191
msgid "By default inbound messages are fetched every 5 minutes in Odoo on-premise. You can change this value in :ref:`developer mode <developer-mode>`. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:198
msgid "Set up different dedicated servers for transactional and mass mails"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:200
msgid "Odoo is subject to a :ref:`daily email limit <email_communication/daily_limit_mail>` to prevent abuse. However, if needed, you can use a separate Mail Transfer Agent (MTA) servers for transactional e-mails and mass mailings. Example: use Odoo's own mail server for transactional e-mails, and Sendgrid, Amazon SES, or Mailgun for mass mailings. Another alternative is to use Postmark for transactional e-mails, and Amazon SES or Sendgrid for mass mailings."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:208
msgid "A default outgoing email server is already configured. You should not create an alternative one unless you want to use a specific external outgoing email server for technical reasons."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:211
msgid "To do this, you should first activate the :ref:`developer mode <developer-mode>` and then go to :menuselection:`Settings --> Technical --> Outgoing` e-mail servers. There you have to create two e-mail MTA server settings. One for transactional e-mails and one for mass mail servers. Be sure to mark the priority of transactional e-mail servers as low as the mass email servers."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers.rst:216
msgid "Now, go to :menuselection:`Email Marketing --> Settings` and enable *Dedicated Server*. With these settings, Odoo uses the server with the lower priority for transactional emails, and the server here selected for mass mails. Note that in this case, you have to set your domain's Sender Policy Framework (SPF) records to include both transactional and mass mail servers. If your server resides with xxxx.odoo.com, the available options are Sendinblue and Mailchimp, as your e-mails would be originated from the xxxx.odoo.com domain."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:3
msgid "Email Templates"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:5
msgid "We all know writing good emails is vital to get a high response rate, but you do not want to rewrite the same structure every time, do you? That is where email templates come in. Without the need to rewrite the entire email structure every time, you save time to focus on the content. Multiple templates also let you deliver the right message to the right audience, improving their overall experience with the company."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:12
msgid "Enable it and understand a few concepts"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:14
msgid "The :ref:`Developer mode <developer-mode>` must be activated). Then, go to :menuselection:`Settings --> Technical --> Templates`. A view of the existing templates is shown."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:18
msgid "It is highly recommended not to change the content in existing templates unless the user has prior knowledge about placeholders."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:21
msgid "To add a new one, click on *Create* and choose the type of document this template is used with. In the example below, the template would be sent to job applicants."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:30
msgid "Under *Email Configuration*, fields such as *From*, *To (Emails)*, *To (Partners)*, require placeholders. If the *From* field is not set, the default value is the author’s email alias, if configured, or email address."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:32
msgid "Under *Advanced Settings*, if an *Outgoing Mail Server* is not set, the one with the highest priority is used."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:34
msgid "The option *Auto Delete* permanently deletes the emails after they are sent, saving space in your database."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:37
msgid "Writing content including placeholder expressions"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:39
msgid "A placeholder is a string of characters that temporarily takes the place of the final data. With email templates, for example, placeholders let you put dynamic content in order to personalize the email for the recipient."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:43
msgid "A common use is to use it to indicate the name of the recipient in the newsletter so that each recipient gets a personalized newsletter."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:46
msgid "Placeholders and more specifically fields that are available for a template will depend on the template you modify. One way to see the fields that are available is to check the Dynamic Placeholder Generator tab."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:52
msgid "Under the tab *Dynamic Placeholder Generator*, look for the *Field* you would like to use."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:57
msgid "Next, copy the *Placeholder Expression* and paste it in the *Body* of the email, under the *Content* tab, using - essentially - the *Code View*."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:63
msgid "Deactivate the *Code View* option by simply clicking on it again, and easily design the message. Click on *Preview* to check how the email looks before sending it."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:70
msgid "Using functions with placeholders"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:72
msgid "Functions can be used along with your placeholders in order to format the data as you'd like within your mail templates, for example, the time format can be changed using a function such as ``format_time``."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:76
msgid "In order to use functions, you have to know the available fields to format. To know that, you have to check the fields (the properties) of the object that are available to be used."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:80
msgid "Checking the fields (properties) available on the object"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:82
msgid "To check the **fields available**, click on the link next to Applies to. For the example we use the Portal: new user template, so we click on Portal user Config."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:89
msgid "By clicking on the link, you are redirected to the model, in this case the ``Portal user Config`` model that lists all the fields that you can use within your mail template."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:96
msgid "As a side note, you can also see the fields that are available by accessing the dynamic placeholder generator, as described :ref:`previously <email_communication/dynamic_placeholder_generator>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:99
msgid "See below an example with the email field that was added in the template and its result as well as some other placeholders already present by default."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:107
msgid "Using fields with functions"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:109
msgid "Now that you know the *fields* that can be used, you can use one of them with a function. For this example, we add the creation date, *create_date* field to the body of the template ‘Portal: new user’ along with the ``format_date`` function so that the user knows when he was invited."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:117
msgid "As you can see we use the placeholder `${}` with the ``format_date`` function which uses as a parameter the field create_date available on the current object, this gives the following line of code ``${format_date(object.create_date)}``."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:122
msgid "It's really important to check that the preview is working, if it's broken your template might appear totally blank when previewing it. We also recommend not changing the content in existing templates unless you have prior knowledge. We highly recommend duplicating the template and apply your changes within this one."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:127
msgid "Find below the result of the e-mail received in the recipient's mailbox with the modifications applied."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:134
msgid "Still by using the ``format_date`` function, you have the possibility to adapt the format of the date just in a specific email by specifying the formatting of the date as a second parameter. If not specified, the format used by default is the one defined in the settings of the language. More information on how to access these parameters can be found :ref:`here <email_communication/usable_functions>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:139
msgid "In order to adapt the date format, the piece of code used in the above example ``${format_date(object.create_date)}`` becomes ``${format_date(object.create_date, date_format='dd -- MM -- YYYY')}`` here dd is the day, MM the month and YYYY the year."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:143
msgid "Here is the result once the function is adapted in the template."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:152
msgid "Functions used by default within email templates"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:154
msgid "To format your data, many functions can be used, here are some examples."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:157
msgid "**This list of functions is not exhaustive**, meaning that all functions that are available aren't listed in the below list, for more functions, we invite you to check the `babel <http://babel.pocoo.org/en/latest/api/dates.html>`_ documentation, last but not least, modifications on the templates are considered as customization and isn’t covered by our support."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:162
msgid "For the following examples, we will introduce mostly some date functions. By default, the format of the date used is the one defined in the settings of the language."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:165
msgid "These settings can only be accessed when the :ref:`developer mode <developer-mode>` is enabled. Once developer is enabled go to :menuselection:`Settings --> Translations --> Languages` and click on one of the languages to see all the settings such as the time format or date format used by the language."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:170
msgid "**format_date()** - formats the date (without the time)."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:172
msgid "Can be found on the template `Purchase Order: Send PO`:"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:178
#: ../../content/applications/general/email_communication/email_template.rst:193
msgid "The result will look like this:"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:184
msgid "**format_datetime()** - formats the datetime, defining a specific timezone, in this case Central European Time (CET)."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:187
msgid "Can be found on the template `Event: Registration`."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:199
msgid "**format_time()** - Similar to the format_datetime function except It's used only for the time, not a date."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:202
msgid "**format_amount()** - Formats a number, an amount to display the currency depending on the display setting that has been defined on the currency (the :ref:`debug mode <developer-mode>` must be activated to see this feature) :menuselection:`Accounting --> Configuration --> Currencies` (before or after the amount depending on the convention)."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:211
msgid "Which will look like this:"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:218
msgid "Defining a default reply to on your mail template"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:220
msgid "Although the field *reply to* is available within the mail templates, **this field is only used for mass mailing** mode (this means when sending templates on what we call bulk emailing). You can send emails in bulk in almost every app that has a list view. Select the records you want and click on the action button. If you have an option to send an email, you will see a mail composer with possible values to define:"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:230
msgid "You can also define them by default on the template:"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:236
msgid "Because of this, setting a value in this field is useless as the value defined will be totally ignored. The default *reply-to* value is the default catchall email address to ensure a communication between your customer and your Odoo database. For more information about the way the catchall works, please check :ref:`how to manage inbound messages <email_communication/inbound_messages>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:242
msgid "Transactional emails and corresponding URL for each company"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:244
msgid "When using Odoo, multiple events trigger the sending of automated emails. These emails are known as transactional emails and sometimes contain links pointing to your Odoo database."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:247
msgid "By default, links generated by the database use the dynamic web.base.url key defined in the system parameters. More information about this :ref:`parameter <domain-name/web-base-url>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:250
msgid "If the website application isn't installed, the web.base.url key will always be the default parameter used to generate all the links."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:253
msgid "It’s important to know that this key can only have a single value, meaning that in a multi-website/company database environment, even if you have a specific domain name for each website, the links generated to share a document or within a transactional email might remain the same, whatever the website/company related to the sending of the email/document."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:258
msgid "This is not always the case as some Odoo applications have a link established in the database with the website application, meaning that in this case, if a specific domain is defined for the websites, the URL generated in the email template will use the domain defined on the corresponding website of the company."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:264
msgid "A document shared using the documents application will always use the web.base.url key, as the document shared isn't associated with any particular website. Meaning that the URL will always be the same (the web.base.url key value), whatever the company it's shared from, this is a known limitation!"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:269
msgid "On the other hand, sales orders made by a customer on one of your Odoo e-commerce websites have a link established with the website from which the order was made. As a result, the e-mail sent for the sales orders uses the domain name defined for the corresponding website to generate the links."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:273
msgid "For more information about how to configure your domains, we invite you to check :doc:`our domain name documentation </administration/maintain/domain_names>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:277
msgid "Updating translations within email templates"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:279
msgid "Email templates are automatically translated. Changing the translations shouldn’t be necessary. However, if for a specific reason you’d like to change some of the translations, this can be done."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:282
msgid "Like any modification in the code, keep in mind that modifications that aren’t done correctly (for example modifications leading to bad syntax) can break the template, as a result, the template will appear blank."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:286
msgid "In order to edit your translations, follow these steps from the template."
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:288
msgid "Click on the edit button, then on the language button"
msgstr ""

#: ../../content/applications/general/email_communication/email_template.rst:294
msgid "A pop-up window with the different languages installed on the database will be displayed. From here, editing the translations will be possible. Don't forget to hit the save button to preserve your changes."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:3
msgid "FAQ"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:5
msgid "This document contains an explanation of the most recurring mailing concerns."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:7
msgid "We will start by addressing issues of outgoing emails (ex: my client has not received my email), and then, of incoming emails (ex: I do not receive responses from my customers in the database)."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:11
msgid "Outgoing emails"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:16
msgid "What do you have to check if your email is not sent?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:18
msgid "The first indicator showing you that the email has not been sent is the red envelope next to the date and time of the message."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:26
msgid "Common error messages"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:31
msgid "You reached your daily limit:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:37
msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, and sometimes even per minute. This is the same for Odoo, we have to limit our customers to prevent our e-mail servers from being blacklisted."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:41
msgid "Here are the default limits for new databases:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:43
msgid "200 emails/day for Odoo Online and Odoo.sh databases with an active subscription,"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:45
msgid "50 emails/day for one-app free and trial databases,"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:47
msgid "in case of migration, your daily limit might be reset to 50 emails a day."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:49
msgid "In case you hit the limit, you can:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:51
msgid "Ask our support team to increase your daily limit. We will analyze the situation of your database depending on (non-exhaustive list):"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:54
msgid "How many users in your database,"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:55
msgid "Which apps are installed,"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:56
msgid "Your bounce rate: the percentage of email addresses that did not receive your emails because it was returned by a mail server on its way to the final recipient. You can contact the `support <https://www.odoo.com/help>`_."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:60
msgid "Use your own outgoing email server to be independent of Odoo’s mail limit (please refer to :doc:`the corresponding documentation </applications/general/email_communication/email_servers>`),"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:62
msgid "Wait until 11pm UTC for the reset and click on the retry button: The :ref:`Developer mode <developer-mode>` must be activated. Then, go to :menuselection:`Settings --> Technical --> Emails`"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:70
msgid "The daily limit is global to your database and can rise quickly! By default an internal message, a notification, a note, etc. counts as an email in your daily limit if it notifies someone."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:73
msgid "You can mitigate this by receiving your :ref:`notifications in Odoo <discuss_app/notification_preferences>` instead of by emails."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:77
msgid "SMTP Error"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:79
msgid "You can find out why an email wasn't transmitted successfully by reviewing the Simple Mail Transport Protocol (SMTP) error messages. SMTP is a protocol to describe the email structure and transmit it over the Internet, and the error messages generated by email services are helpful tools to diagnose and troubleshoot email problems."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:85
msgid "No Error"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:87
msgid "Odoo is not always capable of providing information for the reason it failed. The different providers implement a personalized policy of the bounce emails and it is not always possible for Odoo to interpret it correctly."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:91
msgid "If you have this problem on a recurring basis with the same client or the same domain, please do not hesitate to contact `Odoo Support <https://www.odoo.com/help>`_ for help in finding a reason."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:94
msgid "Note: in such case, one of the most common reasons is related to :ref:`SPF <email_communication/spf_compliant>` and/or :ref:`DKIM <email_communication/DKIM_compliant>` configuration."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:98
msgid "Why is my email sent late?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:100
msgid "It may happen that you schedule an email campaign but it is not sent on time. We know that we use a delayed job to send emails that we consider as not urgent (Newsletters concept such as mass mailing, marketing automation, events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. We use that policy in order to avoid cluttering the mail servers and prioritize the communication."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:106
msgid "The emails considered urgent (communication from one person to another one such as Sales Orders, Invoices, Purchase Orders, etc.) are sent directly."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:113
msgid "By default, the Mass Mailing cron runs every 60 minutes. So, you should wait maximum an hour before the campaign is actually sent."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:117
msgid "Incoming emails"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:119
msgid "When you have an issue with incoming emails, there might not be an indication per se in Odoo. This is the client who tries to contact a database who will get a bounce (most of the time 550: mailbox unavailable)."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:124
msgid "Emails are not received"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:126
msgid "Depending on the platform you are using:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:128
msgid "The **Odoo.sh** users can find their live logs on the folder :file:`~/logs/`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:130
msgid "The folder :file:`~/logs/` (preferably accessed by the command line) of an Odoo.sh contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM UTC. The two last days are not compressed, while the older ones are, in order to gain space. The naming of the files for Today and Yesterday are :file:`odoo.log` and :file:`odoo.log.1`. For the following, they are named with their dates and compressed. See the Odoo.sh documentation about :ref:`logs <odoosh/logs>`. Use the command ``grep`` and ``zgrep`` (for the compressed ones) to search through the files."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:138
msgid "The **SaaS** users won’t have access to their logs. However you can still contact `Odoo Support <https://www.odoo.com/help>`_ , if you have a recurring issue with the same client or domain."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:143
msgid "Get help from support"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:145
msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:148
msgid "The **EML** of the email, stating for *Electronic Mail*, is the file format containing all the technical information required for an investigation. The documentation of your own email provider might help you on how to get your EML files. Once you get the EML of the email, adding it in the attachment of your ticket is the most efficient way for us to investigate. The support will mainly focus on redundant issues."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:155
msgid "`Gmail documentation <https://support.google.com/mail/answer/29436>`_"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:157
msgid "`Outlook documentation <https://support.microsoft.com/en-us/office/view-internet-message-headers-in-outlook-cd039382-dc6e-4264-ac74-c048563d212c#tab=Web>`_"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:160
msgid "The exact flow you are following in order to normally receive those emails in Odoo. Here are examples of questions whose answers can be useful:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:163
msgid "Is this simply a reply from an email going out from Odoo ?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:165
msgid "Are you using an incoming email server or somehow redirecting?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:167
msgid "Can you provide us with an example of an email that has been correctly forwarded ?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:169
msgid "Providing answers to the following questions:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:171
msgid "Is it a generic issue or is it specific to a use case? If yes, which one exactly?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:173
msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database and display the :ref:`red envelope <red_envelop>`."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:3
msgid "Export and import data"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:8
msgid "Export data from Odoo"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:10
msgid "When working with a database, it sometimes is necessary to export your data in a distinct file. Doing so can help to do reporting over your activities (even if Odoo offers a precise and easy reporting tool with each available application)."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:14
msgid "With Odoo, you can export the values from any field in any record. To do so, activate the list view on the items that need to be exported, click on *Action*, and, then, on *Export*."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:22
msgid "Pretty simple, this action still comes with some specificities. In fact, when clicking on *Export*, a pop-up window appears with several options for the data to export:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:30
msgid "With the *I want to update data* option ticked, the system only shows the fields which can be imported. This is very helpful in case you want to update existing records. Basically, this works like a filter. Leaving the box unticked gives way more field options because it shows all the fields, not just the ones which can be imported."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:36
msgid "When exporting, you can choose between two formats: .csv and .xls. With .csv, items are separated with a comma, while .xls holds information about all the worksheets in a file, including both content and formatting."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:39
msgid "Those are the items you may want to export. Use the arrows to display more sub-field options. Of course, you can use the search bar to find specific fields more easily. To use the search option more efficiently, display all the fields by clicking on all the arrows!"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:44
msgid "The + button is there to add fields to the \"to export\" list."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:45
msgid "The \"handles\" next to the selected fields allow you to move the fields up and down to change the order in which they must be displayed in the exported file."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:48
msgid "The trashcan is there if you need to remove fields."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:49
msgid "For recurring reports, it might be interesting to save export presets. Select all the needed ones and click on the template bar. There, click on *New template* and give a name to yours. The next time you need to export the same list, simply select the related template."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:56
msgid "It’s good to keep the field’s external identifier in mind. For example, *Related Company* is equal to *parent_id*. Doing so helps export only what you would like to import next."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:63
msgid "Import data into Odoo"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:66
msgid "How to start"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:68
msgid "You can import data on any Odoo's business object using either Excel (.xlsx) or CSV (.csv) formats: contacts, products, bank statements, journal entries and even orders!"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:72
msgid "Open the view of the object you want to populate and click on :menuselection:`Favorites --> Import records`."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:78
msgid "There you are provided with templates you can easily populate with your own data. Such templates can be imported in one click; The data mapping is already done."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:83
msgid "How to adapt the template"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:85
msgid "Add, remove and sort columns to fit at best your data structure."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:86
msgid "We advise to not remove the **ID** one (see why in the next section)."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:87
#: ../../content/applications/general/export_import_data.rst:376
msgid "Set a unique ID to every single record by dragging down the ID sequencing."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:92
msgid "When you add a new column, Odoo might not be able to map it automatically if its label doesn't fit any field in Odoo. Don't worry! You can map new columns manually when you test the import. Search the list for the corresponding field."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:100
msgid "Then, use this field's label in your file in order to make it work straight on the very next time."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:104
msgid "How to import from another application"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:106
msgid "In order to re-create relationships between different records, you should use the unique identifier from the original application and map it to the **ID** (External ID) column in Odoo. When you import another record that links to the first one, use **XXX/ID** (XXX/External ID) to the original unique identifier. You can also find this record using its name but you will be stuck if at least 2 records have the same name."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:114
msgid "The **ID** will also be used to update the original import if you need to re-import modified data later, it's thus good practice to specify it whenever possible."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:120
msgid "I cannot find the field I want to map my column to"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:122
msgid "Odoo tries to find with some heuristic, based on the first ten lines of the files, the type of field for each column inside your file. For example if you have a column only containing numbers, only the fields that are of type *Integer* will be displayed for you to choose from. While this behavior might be good and easy for most cases, it is also possible that it goes wrong or that you want to map your column to a field that is not proposed by default."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:131
msgid "If that happens, you just have to check the ** Show fields of relation fields (advanced)** option, you will then be able to choose from the complete list of fields for each column."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:139
msgid "Where can I change the date import format?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:141
msgid "Odoo can automatically detect if a column is a date, and it will try to guess the date format from a set of most commonly used date formats. While this process can work for many date formats, some date formats will not be recognized. This can cause confusion due to day-month inversions; it is difficult to guess which part of a date format is the day and which part is the month in a date such as '01-03-2016'."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:147
msgid "To view which date format Odoo has found from your file you can check the **Date Format** that is shown when clicking on **Options** under the file selector. If this format is incorrect you can change it to your liking using the *ISO 8601* to define the format."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:152
msgid "If you are importing an excel (.xls, .xlsx) file, you can use date cells to store dates as the display of dates in excel is different from the way it is stored. That way you will be sure that the date format is correct in Odoo whatever your locale date format is."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:157
msgid "Can I import numbers with currency sign (e.g.: $32.00)?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:159
msgid "Yes, we fully support numbers with parenthesis to represent negative sign as well as numbers with currency sign attached to them. Odoo also automatically detect which thousand/decimal separator you use (you can change those under **options**). If you use a currency symbol that is not known to Odoo, it might not be recognized as a number though and it will crash."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:164
msgid "Examples of supported numbers (using thirty-two thousands as an example):"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:166
msgid "32.000,00"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:167
msgid "32000,00"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:168
msgid "32,000.00"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:169
msgid "-32000.00"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:170
msgid "(32000.00)"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:171
msgid "$ 32.000,00"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:172
msgid "(32000.00 €)"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:174
msgid "Example that will not work:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:176
msgid "ABC 32.000,00"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:177
msgid "$ (32.000,00)"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:180
msgid "What can I do when the Import preview table isn't displayed correctly?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:182
msgid "By default the Import preview is set on commas as field separators and quotation marks as text delimiters. If your csv file does not have these settings, you can modify the File Format Options (displayed under the Browse CSV file bar after you select your file)."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:186
msgid "Note that if your CSV file has a tabulation as separator, Odoo will not detect the separations. You will need to change the file format options in your spreadsheet application. See the following question."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:191
msgid "How can I change the CSV file format options when saving in my spreadsheet application?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:193
msgid "If you edit and save CSV files in spreadsheet applications, your computer's regional settings will be applied for the separator and delimiter. We suggest you use OpenOffice or LibreOffice Calc as they will allow you to modify all three options (in :menuselection:`'Save As' dialog box --> Check the box 'Edit filter settings' --> Save`)."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:198
msgid "Microsoft Excel will allow you to modify only the encoding when saving (in :menuselection:`'Save As' dialog box --> click 'Tools' dropdown list --> Encoding tab`)."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:202
msgid "What's the difference between Database ID and External ID?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:204
msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When you want to import such fields, Odoo will have to recreate links between the different records. To help you import such fields, Odoo provides three mechanisms. You must use one and only one mechanism per field you want to import."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:209
msgid "For example, to reference the country of a contact, Odoo proposes you 3 different fields to import:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:211
msgid "Country: the name or code of the country"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:212
msgid "Country/Database ID: the unique Odoo ID for a record, defined by the ID postgresql column"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:213
msgid "Country/External ID: the ID of this record referenced in another application (or the .XML file that imported it)"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:216
msgid "For the country Belgium, you can use one of these 3 ways to import:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:218
msgid "Country: Belgium"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:219
msgid "Country/Database ID: 21"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:220
msgid "Country/External ID: base.be"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:222
msgid "According to your need, you should use one of these 3 ways to reference records in relations. Here is when you should use one or the other, according to your need:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:225
msgid "Use Country: This is the easiest way when your data come from CSV files that have been created manually."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:227
msgid "Use Country/Database ID: You should rarely use this notation. It's mostly used by developers as it's main advantage is to never have conflicts (you may have several records with the same name, but they always have a unique Database ID)"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:230
msgid "Use Country/External ID: Use External ID when you import data from a third party application."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:232
msgid "When you use External IDs, you can import CSV files with the \"External ID\" column to define the External ID of each record you import. Then, you will be able to make a reference to that record with columns like \"Field/External ID\". The following two CSV files give you an example for Products and their Categories."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:237
msgid ":download:`CSV file for categories <export_import_data/External_id_3rd_party_application_product_categories.csv>`."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:240
msgid ":download:`CSV file for Products <export_import_data/External_id_3rd_party_application_products.csv>`."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:244
msgid "What can I do if I have multiple matches for a field?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:246
msgid "If for example you have two product categories with the child name \"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other Products/Sellable\"), your validation is halted but you may still import your data. However, we recommend you do not import the data because they will all be linked to the first 'Sellable' category found in the Product Category list (\"Misc. Products/Sellable\"). We recommend you modify one of the duplicates' values or your product category hierarchy."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:252
msgid "However if you do not wish to change your configuration of product categories, we recommend you use make use of the external ID for this field 'Category'."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:256
msgid "How can I import a many2many relationship field (e.g. a customer that has multiple tags)?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:258
msgid "The tags should be separated by a comma without any spacing. For example, if you want your customer to be linked to both tags 'Manufacturer' and 'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column of your CSV file."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:262
msgid ":download:`CSV file for Manufacturer, Retailer <export_import_data/m2m_customers_tags.csv>`"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:266
msgid "How can I import a one2many relationship (e.g. several Order Lines of a Sales Order)?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:268
msgid "If you want to import sales order having several order lines; for each order line, you need to reserve a specific row in the CSV file. The first order line will be imported on the same row as the information relative to order. Any additional lines will need an additional row that does not have any information in the fields relative to the order. As an example, here is ``purchase.order_functional_error_line_cant_adpat.CSV`` file of some quotations you can import, based on demo data."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:275
msgid ":download:`File for some Quotations <export_import_data/purchase.order_functional_error_line_cant_adpat.csv>`."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:277
msgid "The following CSV file shows how to import purchase orders with their respective purchase order lines:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:280
msgid ":download:`Purchase orders with their respective purchase order lines <export_import_data/o2m_purchase_order_lines.csv>`."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:282
msgid "The following CSV file shows how to import customers and their respective contacts:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:284
msgid ":download:`Customers and their respective contacts <export_import_data/o2m_customers_contacts.csv>`."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:287
msgid "Can I import several times the same record?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:289
msgid "If you import a file that contains one of the column \"External ID\" or \"Database ID\", records that have already been imported will be modified instead of being created. This is very useful as it allows you to import several times the same CSV file while having made some changes in between two imports. Odoo will take care of creating or modifying each record depending if it's new or not."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:294
msgid "This feature allows you to use the Import/Export tool of Odoo to modify a batch of records in your favorite spreadsheet application."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:298
msgid "What happens if I do not provide a value for a specific field?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:300
msgid "If you do not set all fields in your CSV file, Odoo will assign the default value for every non defined fields. But if you set fields with empty values in your CSV file, Odoo will set the EMPTY value in the field, instead of assigning the default value."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:305
msgid "How to export/import different tables from an SQL application to Odoo?"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:307
msgid "If you need to import data from different tables, you will have to recreate relations between records belonging to different tables. (e.g. if you import companies and persons, you will have to recreate the link between each person and the company they work for)."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:311
msgid "To manage relations between tables, you can use the \"External ID\" facilities of Odoo. The \"External ID\" of a record is the unique identifier of this record in another application. This \"External ID\" must be unique across all the records of all objects, so it's a good practice to prefix this \"External ID\" with the name of the application or table. (like 'company_1', 'person_1' instead of '1')"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:317
msgid "As an example, suppose you have a SQL database with two tables you want to import: companies and persons. Each person belong to one company, so you will have to recreate the link between a person and the company he work for. (If you want to test this example, here is a :download:`dump of such a PostgreSQL database <export_import_data/database_import_test.sql>`)"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:322
msgid "We will first export all companies and their \"External ID\". In PSQL, write the following command:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:328
msgid "This SQL command will create the following CSV file:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:337
msgid "To create the CSV file for persons, linked to companies, we will use the following SQL command in PSQL:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:343
msgid "It will produce the following CSV file:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:353
msgid "As you can see in this file, Fabien and Laurence are working for the Bigees company (company_1) and Eric is working for the Organi company. The relation between persons and companies is done using the External ID of the companies. We had to prefix the \"External ID\" by the name of the table to avoid a conflict of ID between persons and companies (person_1 and company_1 who shared the same ID 1 in the original database)."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:359
msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two CSV files, you will have 4 contacts and 3 companies. (the firsts two contacts are linked to the first company). You must first import the companies and then the persons."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:364
msgid "How to adapt an import template"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:366
msgid "Import templates are provided in the import tool of the most common data to import (contacts, products, bank statements, etc.). You can open them with any spreadsheets software (Microsoft Office, OpenOffice, Google Drive, etc.)."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:372
msgid "How to customize the file"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:374
msgid "Remove columns you don't need. We advise to not remove the *ID* one (see why here below)."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:381
msgid "When you add a new column, Odoo might not be able to map it automatically if its label doesn't fit any field of the system. If so, find the corresponding field using the search."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:388
msgid "Then, use the label you found in your import template in order to make it work straight away the very next time you try to import."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:392
msgid "Why an “ID” column"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:394
msgid "The **ID** (External ID) is an unique identifier for the line item. Feel free to use the one of your previous software to ease the transition to Odoo."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:397
msgid "Setting an ID is not mandatory when importing but it helps in many cases:"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:399
msgid "Update imports: you can import the same file several times without creating duplicates;"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:400
msgid "Import relation fields (see here below)."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:403
msgid "How to import relation fields"
msgstr ""

#: ../../content/applications/general/export_import_data.rst:405
msgid "An Odoo object is always related to many other objects (e.g. a product is linked to product categories, attributes, vendors, etc.). To import those relations you need to import the records of the related object first from their own list menu."
msgstr ""

#: ../../content/applications/general/export_import_data.rst:409
msgid "You can do it using either the name of the related record or its ID. The ID is expected when two records have the same name. In such a case add \" / ID\" at the end of the column title (e.g. for product attributes: Product Attributes / Attribute / ID)."
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:3
msgid "In-App Purchase (IAP)"
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:5
msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows you to send SMS Text Messages or to send Invoices by post directly from my database."
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:9
msgid "Buying Credits"
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:11
msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult my current balance or to recharge my account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`."
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:19
msgid "If I am on Odoo Online (SAAS) and have the Enterprise version, I benefit from free credits to test our IAP features."
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:23
msgid "IAP accounts"
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:25
msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service and database. By default, IAP accounts are common to all companies, but can be restricted to specific ones. Activate the :ref:`developer mode <developer-mode>`, then go to :menuselection:`Technical Settings --> IAP Account`."
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:34
msgid "IAP Portal"
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:36
msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low."
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:44
msgid "Get notified when credits are low"
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:46
msgid "To be notified when it’s time to recharge my credits, I’ll go to my IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and mark the Receive threshold warning option. Then, I’ll provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!"
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:56
msgid "IAP services available"
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:58
msgid "Different services are available depending on the hosting type of your Database:"
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:60
msgid "*Odoo Online (SAAS)*: only the IAP services provided by Odoo can be used (i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);"
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:62
msgid "*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party apps can be used."
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:66
msgid "Offering my own services"
msgstr ""

#: ../../content/applications/general/in_app_purchase.rst:68
msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: :doc:`In-App Purchase </developer/misc/api/iap>`."
msgstr ""

#: ../../content/applications/general/users.rst:7
msgid "Users & Companies"
msgstr ""

#: ../../content/applications/general/users.rst:9
msgid "Odoo defines a *user* as someone who has access to a database to perform daily tasks. You can add as many users as you need and, in order to restrict the type of information each user can access, rules can be applied. Users and access rights can be added and changed at any point."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:3
msgid "Access Rights"
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:5
msgid "Activate the :ref:`developer mode <developer-mode>`, then go to :menuselection:`Settings --> Users & Companies --> Groups`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:9
msgid "Groups"
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:14
msgid "When choosing the groups the user can have access under :ref:`Access Rights <users/add-individual>`, details of the rules and inheritances of that group are not shown, so this is when the menu *Groups* comes along. *Groups* are created to define rules to models within an application."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:16
msgid "Under *Users*, have a list of the current ones. The ones with administrative rights are shown in black."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:22
msgid "*Inherited* means that users added to this application group are automatically added to the following ones. In the example below, users who have access to the group *Administrator* of *Sales* also have access to *Website/Restricted Editor* and *Sales/User: All Documents*."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:32
msgid "Remember to always test the settings being changed in order to ensure that they are being applied to the needed and right users."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:35
msgid "The *Menus* tab is where you define which menus (models) the user can have access to."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:42
msgid "*Access Rights* rules are the first level of rights. The field is composed of the object name, which is the technical name given to a model. For each model, enable the following options as appropriate:"
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:45
msgid "*Read*: the values of that object can be only seen by the user."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:46
msgid "*Write*: the values of that object can be edited by the user."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:47
msgid "*Create*: values for that object can be created by the user."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:48
msgid "*Delete*: the values of that object can be deleted by the user."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:55
msgid "As a second layer of editing and visibility rules, *Record Rules* can be formed. They overwrite, or refine, the *Access Rights*."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:58
msgid "A record rule is written using a *Domain*. Domains are conditions used to filter or searching data. Therefore, a domain expression is a list of conditions. For each rule, choose among the following options: *Read*, *Write*, *Create* and *Delete* values."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:65
msgid "Making changes in access rights can have a big impact on the database. For this reason, we recommend you to contact your Odoo Business Analyst or our Support Team, unless you have knowledge about Domains in Odoo."
msgstr ""

#: ../../content/applications/general/users/companies.rst:3
msgid "Companies"
msgstr ""

#: ../../content/applications/general/users/companies.rst:5
msgid "A centralized management environment allows you to select multiple companies simultaneously and set their specific warehouses, customers, equipment, and contacts. It provides you the ability to generate reports of aggregated figures without switching interfaces, which facilitates daily tasks and the overall management process."
msgstr ""

#: ../../content/applications/general/users/companies.rst:11
msgid "Manage companies and records"
msgstr ""

#: ../../content/applications/general/users/companies.rst:13
msgid "Go to :menuselection:`Settings --> Manage Companies` and fill in the form with your company’s information. If a *Parent Company* is selected, records are shared between the two companies (as long as both environments are active)."
msgstr ""

#: ../../content/applications/general/users/companies.rst:22
msgid "Activate the :ref:`developer mode <developer-mode>` to choose a *Favicon* for each of your companies, and easily identify them by the browser tabs. Set your favicons’ files size to 16x16 or 32x32 pixels. JPG, PNG, GIF, and ICO are extensions accepted."
msgstr ""

#: ../../content/applications/general/users/companies.rst:31
msgid "Switch between or select multiple companies by enabling their selection boxes to activate them. The grayed company is the one which environment is in use. To switch environments, click on the company’s name. In the example below, the user has access to three companies, two are activated, and the environment in use is of *JS Store US*."
msgstr ""

#: ../../content/applications/general/users/companies.rst:40
msgid "Data such as Products, Contacts, and Equipment can be shared or set to be shown for a specific company only. To do so, on their forms, choose between:"
msgstr ""

#: ../../content/applications/general/users/companies.rst:43
msgid "*A blank field*: the record is shared within all companies."
msgstr ""

#: ../../content/applications/general/users/companies.rst:44
msgid "*Adding a company*: the record is visible to users logged in to that specific company."
msgstr ""

#: ../../content/applications/general/users/companies.rst:51
msgid "Employees' access"
msgstr ""

#: ../../content/applications/general/users/companies.rst:53
msgid "Once companies are created, manage your employees' :doc:`Access Rights <access_rights>` for *Multi Companies*."
msgstr ""

#: ../../content/applications/general/users/companies.rst:62
msgid "If a user has multiple companies *activated* on his database, and he is **editing** a record, the editing happens on the record's related company."
msgstr ""

#: ../../content/applications/general/users/companies.rst:65
msgid "Example: if editing a sale order issued under JS Store US while working on the JS Store Belgium environment, the changes are applied under JS Store US (the company from which the sale order was issued)."
msgstr ""

#: ../../content/applications/general/users/companies.rst:66
msgid "When **creating** a record, the company taken into account is:"
msgstr ""

#: ../../content/applications/general/users/companies.rst:68
msgid "The current company (the one active) or,"
msgstr ""

#: ../../content/applications/general/users/companies.rst:69
msgid "No company is set (on products and contacts’ forms for example) or,"
msgstr ""

#: ../../content/applications/general/users/companies.rst:70
msgid "The company set is the one linked to the document (the same as if a record is being edited)."
msgstr ""

#: ../../content/applications/general/users/companies.rst:73
msgid "Documents’ format"
msgstr ""

#: ../../content/applications/general/users/companies.rst:75
msgid "To set documents' formats according to each company, *activate* and *select* the respective one and, under *Settings*, click on *Configure Document Layout*."
msgstr ""

#: ../../content/applications/general/users/companies.rst:83
msgid "Inter-Company Transactions"
msgstr ""

#: ../../content/applications/general/users/companies.rst:85
msgid "First, make sure each one of your companies is properly set in relation to:"
msgstr ""

#: ../../content/applications/general/users/companies.rst:87
msgid ":doc:`Chart of Accounts <../../finance/accounting/getting_started/initial_configuration/chart_of_accounts>`"
msgstr ""

#: ../../content/applications/general/users/companies.rst:89
msgid ":doc:`Taxes <../../finance/accounting/taxation/taxes/default_taxes>`"
msgstr ""

#: ../../content/applications/general/users/companies.rst:90
msgid ":doc:`Fiscal Positions <../../finance/accounting/taxation/taxes/fiscal_positions>`"
msgstr ""

#: ../../content/applications/general/users/companies.rst:91
msgid ":doc:`Journals <../../finance/accounting/bank/setup/bank_accounts>`"
msgstr ""

#: ../../content/applications/general/users/companies.rst:92
msgid ":doc:`Fiscal Localizations <../../finance/accounting/fiscal_localizations/overview/fiscal_localization_packages>`"
msgstr ""

#: ../../content/applications/general/users/companies.rst:94
msgid ":doc:`Pricelists <../../sales/sales/products_prices/prices/pricing>`"
msgstr ""

#: ../../content/applications/general/users/companies.rst:96
msgid "Now, activate the *Inter-Company Transactions* option under *Settings*. With the respective company *activated* and *selected*, choose if you would like operations between companies to be synchronized at an invoice/bills level or at a sales/purchase orders level."
msgstr ""

#: ../../content/applications/general/users/companies.rst:104
msgid "**Synchronize invoice/bills**: generates a bill/invoice when a company confirms a bill/invoice for the selected company."
msgstr ""

#: ../../content/applications/general/users/companies.rst:107
msgid "*Example:* an invoice posted on JS Store Belgium, for JS Store US, automatically creates a vendor bill on the JS Store US, from the JS Store Belgium."
msgstr ""

#: ../../content/applications/general/users/companies.rst:114
msgid "**Synchronize sales/purchase order**: generates a drafted purchase/sales order using the selected company warehouse when a sales/purchase order is confirmed for the selected company. If instead of a drafted purchase/sales order you rather have it validated, enable *Automatic Validation*."
msgstr ""

#: ../../content/applications/general/users/companies.rst:118
msgid "*Example:* when a sale order for JS Store US is confirmed on JS Store Belgium, a purchase order on JS Store Belgium is automatically created (and confirmed if the *Automatic Validation* feature was enabled)."
msgstr ""

#: ../../content/applications/general/users/companies.rst:127
msgid "Products have to be configured as *Can be sold* and must be shared between the companies."
msgstr ""

#: ../../content/applications/general/users/companies.rst:130
msgid "Remember to test all workflows as an user other than the administrator."
msgstr ""

#: ../../content/applications/general/users/companies.rst:133
msgid ":doc:`Multi-company Guidelines </developer/howtos/company>`"
msgstr ""

#: ../../content/applications/general/users/companies.rst:134
msgid ":doc:`../../finance/accounting/others/multicurrencies/how_it_works`"
msgstr ""

#: ../../content/applications/general/users/language.rst:3
msgid "Change language"
msgstr ""

#: ../../content/applications/general/users/language.rst:5
msgid "Odoo provides you with the option to manage Odoo in different languages, and each user can use Odoo in his own language ."
msgstr ""

#: ../../content/applications/general/users/language.rst:9
msgid "Load your desired language"
msgstr ""

#: ../../content/applications/general/users/language.rst:11
msgid "The first thing to do is to load your desired language on your Odoo instance."
msgstr ""

#: ../../content/applications/general/users/language.rst:14
msgid "From the general dashboard click on the **Settings** app; on the top left of the page select :menuselection:`Translations --> Load a Translation`, select a language to install and click on **LOAD.**"
msgstr ""

#: ../../content/applications/general/users/language.rst:23
msgid "If you check the \"Websites to translate\" checkbox you will have the option to change the navigation language on your website."
msgstr ""

#: ../../content/applications/general/users/language.rst:27
msgid "Change your language"
msgstr ""

#: ../../content/applications/general/users/language.rst:29
msgid "You can change the language to the installed language by going to the drop-down menu at the top right side of the screen, choose **Preferences**."
msgstr ""

#: ../../content/applications/general/users/language.rst:36
msgid "Then change the Language setting to your installed language and click **SAVE.**"
msgstr ""

#: ../../content/applications/general/users/language.rst:42
msgid "Open a new menu to view the changes."
msgstr ""

#: ../../content/applications/general/users/language.rst:45
msgid "Change another user's language"
msgstr ""

#: ../../content/applications/general/users/language.rst:47
msgid "Odoo also gives you the possibility for each user to choose his preferred language."
msgstr ""

#: ../../content/applications/general/users/language.rst:50
msgid "To change the language for a different user, choose :menuselection:`Users --> Users` from the Settings app. Here you have a list of all users and you can choose the user who you'd like to change the language for. Select the user and click on **Edit** in the top left corner. Under Preferences you can change the Language to any previously installed language and click **SAVE.**"
msgstr ""

#: ../../content/applications/general/users/language.rst:61
msgid ":doc:`../../websites/website/publish/translate`"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:3
msgid "Manage users"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:5
msgid "Odoo defines a **user** as someone who has access to a database to perform daily tasks. You can add as many users as you need and, in order to restrict the type of information each user can access, rules can be applied. Users and access rights can be added and changed at any point."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:10
msgid ":doc:`language`"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:11
msgid ":doc:`access_rights`"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:16
msgid "Add individual users"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:18
msgid "Go to :menuselection:`Settings --> Manage Users` and click on *Create*."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:27
msgid "Fill in the form with the needed information. Under the tab :doc:`Access Rights <access_rights>` choose the group within each application the user can have access to."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:28
msgid "The list of applications shown is based on the applications installed on the database."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:34
msgid "When you are done editing the page and have *Saved* it, an invitation email is automatically sent to the user. The user must click on it to accept the invitation and create a login."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:42
msgid "Remember that subscription prices follow the number of users. Refer to our `pricing page <https://www.odoo.com/pricing>`_ for more information."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:46
msgid "With the :ref:`developer mode <developer-mode>` activated, *User Types* can be selected."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:53
msgid "The *Portal* and *Public* options do not allow you to choose access rights. Members have specific ones (such as record rules and restricted menus) and usually do not belong to the usual Odoo groups."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:60
msgid "Deactivate users"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:62
msgid "Go to :menuselection:`Settings --> Users & Companies --> Users`, open the user you want to deactivate, click on *Action*, and then on *Archive*."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:66
msgid "**Never** deactivate the main user (*admin*)."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:71
msgid "Passwords management"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:76
msgid "Reset passwords"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:81
msgid "Enable password resets from login page"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:83
msgid "It is possible to enable password resets directly from the login page."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:85
msgid "To do so, go to :menuselection:`Settings --> Permissions`, activate **Password Reset** and *Save*."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:94
msgid "Send reset instructions to users"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:96
msgid "Go to :menuselection:`Settings --> Users & Companies --> Users`, select the user out of the list and click on *Send Password Reset Instructions* on its user form. An email is automatically sent to them."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:101
msgid "The *Send Password Reset Instructions* button only appears if the Odoo invitation email has already been confirmed by the user."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:104
msgid "This email contains all the instructions needed to reset the password, along with a link redirecting the user to an Odoo login page."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:114
msgid "Change users’ passwords"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:116
msgid "Go to :menuselection:`Settings --> Users  & Companies --> Users` and select a user to access its form. Click on the *Action* button and select *Change Password*."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:123
msgid "Enter a new password and confirm by clicking on *Change Password*."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:126
msgid "This operation only modifies the password of the users locally and does not affect their odoo.com account. If you want to change the odoo.com password, you can :ref:`send the password reset instructions <users/reset-password-email>`."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:130
msgid "Click on *Change Password* one more time. You are then redirected to an Odoo login page where you can reaccess your database using your new password."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:136
msgid "Multi Companies"
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:138
msgid "The *Multi Companies* field allows you to set to which of the multiple companies database you hold the user can have access."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:142
msgid "Note that if not handled correctly, it may be the source of a lot of inconsistent multi-company behaviors. Therefore, a good knowledge of Odoo is required. For technical explanations refer to :doc:`this </developer/howtos/company>` documentation."
msgstr ""

#: ../../content/applications/general/users/manage_users.rst:152
msgid ":doc:`companies`"
msgstr ""

#: ../../content/applications/general/voip.rst:5
msgid "VoIP (Voice over Internet Protocol)"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:3
msgid "Configure your VoIP Asterisk server for Odoo"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:6
msgid "Installing Asterisk server"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:9
msgid "Dependencies"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:11
msgid "Before installing Asterisk you need to install the following dependencies:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:13
msgid "wget"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:14
msgid "gcc"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:15
msgid "g++"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:16
msgid "ncurses-devel"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:17
msgid "libxml2-devel"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:18
msgid "sqlite-devel"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:19
msgid "libsrtp-devel"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:20
msgid "libuuid-devel"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:21
msgid "openssl-devel"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:22
msgid "pkg-config"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:24
msgid "In order to install libsrtp, follow the instructions below:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:35
msgid "You also need to install PJSIP, you can download the source `here <http://www.pjsip.org/download.htm>`_. Once the source directory is extracted:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:37
msgid "**Change to the pjproject source directory:**"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:43
msgid "**run:**"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:49
msgid "**Build and install pjproject:**"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:57
msgid "**Update shared library links:**"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:63
msgid "**Verify that pjproject is installed:**"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:69
msgid "**The result should be:**"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:86
msgid "Asterisk"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:88
msgid "In order to install Asterisk 13.7.0, you can download the source directly `there <http://downloads.asterisk.org/pub/telephony/asterisk/old-releases/asterisk-13.7.0.tar.gz>`_."
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:90
msgid "Extract Asterisk:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:96
msgid "Enter the Asterisk directory:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:102
msgid "Run the Asterisk configure script:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:108
msgid "Run the Asterisk menuselect tool:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:114
msgid "In the menuselect, go to the resources option and ensure that res_srtp is enabled. If there are 3 x’s next to res_srtp, there is a problem with the srtp library and you must reinstall it. Save the configuration (press x). You should also see stars in front of the res_pjsip lines."
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:116
msgid "Compile and install Asterisk:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:122
msgid "If you need the sample configs you can run 'make samples' to install the sample configs. If you need to install the Asterisk startup script you can run 'make config'."
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:125
msgid "DTLS Certificates"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:127
msgid "After you need to setup the DTLS certificates."
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:133
msgid "Enter the Asterisk scripts directory:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:139
msgid "Create the DTLS certificates (replace pbx.mycompany.com with your ip address or dns name, replace My Super Company with your company name):"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:146
msgid "Configure Asterisk server"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:148
msgid "For WebRTC, a lot of the settings that are needed MUST be in the peer settings. The global settings do not flow down into the peer settings very well. By default, Asterisk config files are located in /etc/asterisk/. Start by editing http.conf and make sure that the following lines are uncommented:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:158
msgid "Next, edit sip.conf. The WebRTC peer requires encryption, avpf, and icesupport to be enabled. In most cases, directmedia should be disabled. Also under the WebRTC client, the transport needs to be listed as ‘ws’ to allow websocket connections. All of these config lines should be under the peer itself; setting these config lines globally might not work:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:186
msgid "In the sip.conf and rtp.conf files you also need to add or uncomment the lines:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:193
msgid "Lastly, set up extensions.conf:"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:202
msgid "Configure Odoo VOIP"
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:204
msgid "In Odoo, the configuration should be done in the user's preferences."
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:210
msgid "The SIP Login/Browser's Extension is the number you configured previously in the sip.conf file (in our example: 1060)."
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:212
msgid "The SIP Password is the secret you chose in the sip.conf file."
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:214
msgid "The extension of your office's phone is not a required field but it is used if you want to transfer your call from Odoo to an external phone also configured in the sip.conf file."
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:217
msgid "The configuration should also be done in the General Settings under the \"Integrations\" section."
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:222
msgid "The PBX Server IP should be the same as the IP you define in the http.conf file."
msgstr ""

#: ../../content/applications/general/voip/asterisk.rst:224
msgid "The WebSocket should be: ws://localhost:XXXX/ws where \"localhost\" needs to be the same as the IP defined previously and \"XXXX\" needs to be the port defined in the http.conf file."
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:3
msgid "Use VoIP services in Odoo with Axivox"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:6
#: ../../content/applications/general/voip/onsip.rst:6
msgid "Introduction"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:8
msgid "Odoo VoIP can be set up to work together with `Axivox <https://www.axivox.com/>`_. In that case, an :doc:`Asterisk server <asterisk>` is not necessary as the infrastructure is hosted and managed by Axivox."
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:12
msgid "To use this service, `contact Axivox <https://www.axivox.com/contact/>`_ to open an account. Before doing so, verify that Axivox covers your area and the areas you wish to call."
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:18
msgid "Go to :menuselection:`Apps` and install the **VoIP Module**."
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:24
msgid "Go to :menuselection:`Settings --> General Settings --> Integrations`, and fill out the **Asterisk (VoIP)** field:"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:27
msgid "**PBX Server IP**: set the domain created by Axivox for your account (e.g., *yourcompany.axivox.com*)"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:29
msgid "**WebSocket**: type in ``wss://pabx.axivox.com:3443``"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:30
msgid "**VoIP Environment**: set as *Production*"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:37
msgid "Configure the VOIP user in the Odoo's user"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:39
msgid "Go to :menuselection:`Settings --> Users & Companies --> Users`, then open the user's form you want to configure. Under the **Preferences** tab, fill out the section **PBX Configuration**:"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:42
msgid "**SIP Login / Browser's Extension**: the Axivox *username*"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:43
msgid "**SIP Password**: the Axivox *SIP Password*"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:50
msgid "You can find all this information by logging in at https://manage.axivox.com/, selecting the user you want to configure, and referring to the fields as pictured below."
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:58
msgid "Phone Calls"
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:60
msgid "You can make phone calls by clicking on the phone icon in the navigation bar."
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:62
msgid "You can also receive phone calls. Odoo rings and displays a notification."
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:65
msgid "Your number is the one provided by Axivox."
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:72
msgid "If you see a *Missing Parameter* message in the **Odoo softphone**, refresh your Odoo window and try again."
msgstr ""

#: ../../content/applications/general/voip/axivox.rst:80
msgid "If you see an *Incorrect Number* message in the Odoo softphone, make sure to use the international format, leading with the plus (+) sign followed by the international country code. E.g., +16506913277 (where +1 is the international prefix for the United States)."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:3
msgid "Use VoIP services in Odoo with OnSIP"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:8
msgid "Odoo VoIP can be set up to work together with OnSIP (www.onsip.com). In that case, the installation and setup of an Asterisk server is not necessary as the whole infrastructure is hosted and managed by OnSIP."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:10
msgid "You will need to open an account with OnSIP to use this service. Before doing so, make sure that your area and the areas you wish to call are covered by the service. After opening an OnSIP account, follow the configuration procedure below."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:15
msgid "Go to Apps and install the module **VoIP OnSIP**."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:20
msgid "Go to Settings/General Settings. In the section Integrations/Asterisk (VoIP), fill in the 3 fields:"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:22
msgid "**OnSIP Domain** is the domain you chose when creating an account on www.onsip.com. If you don't know it, log in to https://admin.onsip.com/ and you will see it in the top right corner of the screen."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:23
msgid "**WebSocket** should contain wss://edge.sip.onsip.com"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:24
msgid "**Mode** should be Production"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:29
msgid "Go to **Settings/Users**. In the form view of each VoIP user, in the Preferences tab, fill in the section **PBX Configuration**:"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:31
msgid "**SIP Login / Browser's Extension**: the OnSIP 'Username'"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:32
msgid "**OnSIP authorization User**: the OnSIP 'Auth Username'"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:33
msgid "**SIP Password**: the OnSIP 'SIP Password'"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:34
msgid "**Handset Extension**: the OnSIP 'Extension'"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:36
msgid "You can find all this information by logging in at https://admin.onsip.com/users, then select the user you want to configure and refer to the fields as pictured below."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:41
msgid "You can now make phone calls by clicking the phone icon in the top right corner of Odoo (make sure you are logged in as a user properly configured in Odoo and in OnSIP)."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:45
msgid "If you see a *Missing Parameters* message in the Odoo softphone, make sure to refresh your Odoo window and try again."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:52
msgid "If you see an *Incorrect Number* message in the Odoo softphone, make sure to use the international format, leading with the plus (+) sign followed by the international country code. E.g.: +16506913277 (where +1 is the international prefix for the United States)."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:57
msgid "You can now also receive phone calls. Your number is the one provided by OnSIP. Odoo will ring and display a notification."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:63
msgid "OnSIP on Your Cell Phone"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:65
msgid "In order to make and receive phone calls when you are not in front of your computer, you can use a softphone app on your cell phone in parallel of Odoo VoIP. This is useful for on-the-go calls, but also to make sure to hear incoming calls, or simply for convenience. Any SIP softphone will work."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:67
msgid "On Android and iOS, OnSIP has been successfully tested with `Grandstream Wave <https://play.google.com/store/apps/details?id=com.grandstream.wave>`_. When creating an account, select OnSIP in the list of carriers. You will then have to configure it as follows:"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:69
msgid "**Account name**: OnSIP"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:70
msgid "**SIP Server**: the OnSIP 'Domain'"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:71
msgid "**SIP User ID**: the OnSIP 'Username'"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:72
msgid "**SIP Authentication ID**: the OnSIP 'Auth Username'"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:73
msgid "**Password**: the OnSIP 'SIP Password'"
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:75
msgid "Aside from initiating calls from Grandstream Wave on your phone, you can also initiate calls by clicking phone numbers in your browser on your PC. This will make Grandstream Wave ring and route the call via your phone to the other party. This approach is useful to avoid wasting time dialing phone numbers. In order to do so, you will need the Chrome extension `OnSIP Call Assistant <https://chrome.google.com/webstore/detail/onsip-call-assistant/pceelmncccldedfkcgjkpemakjbapnpg?hl=en>`_."
msgstr ""

#: ../../content/applications/general/voip/onsip.rst:79
msgid "The downside of using a softphone on your cell phone is that your calls will not be logged in Odoo as the softphone acts as an independent separate app."
msgstr ""