NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
d6f5e74971
documentation/locale/sources/general.pot
Martin Trigaux (mat) e7e79a70bd [I18N] *: export 15.0 translations 
closes 

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
2024-03-05 14:17:23 +00:00

6622 lines
345 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# 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 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-03-05 13:22+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:-1
msgid "Add \"Extra\" filter in Odoo Apps"
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:51
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:57
msgid "Uninstall apps and modules"
msgstr ""
#: ../../content/applications/general/apps_modules.rst:59
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:65
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 dependent apps and modules are affected by it."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:72
msgid "To complete the uninstallation, click on *Confirm*."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:75
msgid "Uninstalling an app also uninstalls all its dependencies and permanently erases their data."
msgstr ""
#: ../../content/applications/general/auth.rst:5
#: ../../content/applications/general/auth/azure.rst:79
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 "Microsoft Azure sign-in authentication"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:5
msgid "The Microsoft Azure OAuth sign-in authentication is a useful function that allows Odoo users to sign in to their database with their Microsoft Azure account."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:8
msgid "This is particularly helpful if the organization uses Azure Workspace, and wants employees within the organization to connect to Odoo using their Microsoft Accounts."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:12
msgid "Databases hosted on Odoo.com should not use OAuth login for the owner or administrator of the database as it would unlink the database from their Odoo.com account. If OAuth is set up for that user, the database will no longer be able to be duplicated, renamed, or otherwise managed from the Odoo.com portal."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:19
msgid ":doc:`../../productivity/calendar/outlook`"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:20
#: ../../content/applications/general/email_communication/email_servers.rst:69
msgid ":doc:`/administration/maintain/azure_oauth`"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:23
#: ../../content/applications/general/auth/google.rst:24
#: ../../content/applications/general/voip/axivox/axivox_config.rst:17
#: ../../content/applications/general/voip/onsip.rst:18
msgid "Configuration"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:25
msgid "Integrating the Microsoft sign-in function requires configuration on Microsoft and Odoo."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:28
msgid "Odoo System Parameter"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:30
msgid "First activate the :ref:`developer mode <developer-mode>`, and then go to :menuselection:`Settings --> Technical --> System Parameters`."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:33
msgid "Click :guilabel:`Create` and on the new/blank form that appears, add the following system parameter `auth_oauth.authorization_header` to the :guilabel:`Key` field, and set the :guilabel:`Value` to `1`. Then click :guilabel:`Save` to finish."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:38
msgid "Microsoft Azure dashboard"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:41
msgid "Create a new application"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:43
msgid "Now that the system parameters in Odoo have been set up, it's time to create a corresponding application inside of Microsoft Azure. To get started creating the new application, go to `Microsoft's Azure Portal <https://portal.azure.com/>`_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise, log in with a personal :guilabel:`Microsoft account`."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:50
msgid "A user with administrative access to the *Azure Settings* must connect and perform the following configuration steps below."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:53
msgid "Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` (formally *Azure Active Directory*). The location of this link is usually in the center of the page."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:56
msgid "Now, click on the :guilabel:`Add (+)` icon, located in the top menu, and then select :guilabel:`App registration` from the drop-down menu. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` field to `Odoo Login OAuth` or a similarly recognizable title. Under the :guilabel:`Supported account types` section select the option for :guilabel:`Accounts in this organizational directory only (Default Directory only - Single tenant)`."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:63
msgid "The :guilabel:`Supported account types` can vary by Microsoft account type and end use of the OAuth. For example: Is the login meant for internal users within one organization or is it meant for customer portal access? The above configuration is used for internal users in an organization."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:68
msgid "Choose :guilabel:`Personal Microsoft accounts only` if the target audience is meant for portal users. Choose :guilabel:`Accounts in this organizational directory only (Default Directory only - Single tenant)` if the target audience is company users."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:72
msgid "Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input `https://<odoo base url>/auth_oauth/signin` in the :guilabel:`URL` field. The Odoo base :abbr:`URL (Uniform Resource Locator)` is the canonical domain at which your Odoo instance can be reached (e.g. *mydatabase.odoo.com* if you are hosted on Odoo.com) in the :guilabel:`URL` field. Then, click :guilabel:`Register`, and the application is created."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:81
msgid "Edit the new app's authentication by clicking on the :guilabel:`Authentication` menu item in the left menu after being redirected to the application's settings from the previous step."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:84
msgid "Next, the type of *tokens* needed for the OAuth authentication will be chosen. These are not currency tokens but rather authentication tokens that are passed between Microsoft and Odoo. Therefore, there is no cost for these tokens; they are used merely for authentication purposes between two :abbr:`APIs (application programming interfaces)`. Select the tokens that should be issued by the authorization endpoint by scrolling down the screen and check the boxes labeled: :guilabel:`Access tokens (used for implicit flows)` and :guilabel:`ID tokens (used for implicit and hybrid flows)`."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:-1
msgid "Authentication settings and endpoint tokens."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:96
msgid "Click :guilabel:`Save` to ensure these settings are saved."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:99
msgid "Gather credentials"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:101
msgid "With the application created and authenticated in the Microsoft Azure console, credentials will be gathered next. To do so, click on the :guilabel:`Overview` menu item in the left-hand column. Select and copy the :guilabel:`Application (client) ID` in the window that appears. Paste this credential to a clipboard / notepad, as this credential will be used in the Odoo configuration later."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:106
msgid "After finishing this step, click on :guilabel:`Endpoints` on the top menu and click the *copy icon* next to :guilabel:`OAuth 2.0 authorization endpoint (v2)` field. Paste this value in the clipboard / notepad."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:-1
msgid "Application ID and OAuth 2.0 authorization endpoint (v2) credentials."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:115
msgid "Odoo setup"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:117
msgid "Finally, the last step in the Microsoft Azure OAuth configuration is to configure some settings in Odoo. Navigate to :menuselection:`Settings --> Integrations --> OAuth Authentication` and check the box to activate the OAuth login feature. Click :guilabel:`Save` to ensure the progress is saved. Then, sign in to the database once the login screen loads."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:122
msgid "Once again, navigate to :menuselection:`Settings --> Integrations --> OAuth Authentication` and click on :guilabel:`OAuth Providers`. Now, select :guilabel:`New` in the upper-left corner and name the provider `Azure`."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:126
msgid "Paste the :guilabel:`Application (client) ID` from the previous section into the :guilabel:`Client ID` field. After completing this, paste the new :guilabel:`OAuth 2.0 authorization endpoint (v2)` value into the :guilabel:`Authorization URL` field."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:130
msgid "For the :guilabel:`UserInfo URL` field, paste the following :abbr:`URL (Uniform Resource Locator)`: `https://graph.microsoft.com/oidc/userinfo`"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:133
msgid "In the :guilabel:`Scope` field, paste the following value: `openid profile email`. Next, the Windows logo can be used as the CSS class on the login screen by entering the following value: `fa fa-fw fa-windows`, in the :guilabel:`CSS class` field."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:137
msgid "Check the box next to the :guilabel:`Allowed` field to enable the OAuth provider. Finally, add `Microsoft Azure` to the :guilabel:`Login button label` field. This text will appear next to the Windows logo on the login page."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:-1
msgid "Odoo provider setup in the Settings application."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:145
msgid ":guilabel:`Save` the changes to complete the OAuth authentication setup in Odoo."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:148
msgid "User experience flows"
msgstr ""
#: ../../content/applications/general/auth/azure.rst:150
msgid "For a user to log in to Odoo using Microsoft Azure, the user must be on the :menuselection:`Odoo password reset page`. This is the only way that Odoo is able to link the Microsoft Azure account and allow the user to log in."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:155
msgid "Existing users must :ref:`reset their password <users/reset-password>` to access the :menuselection:`Odoo password reset page`. New Odoo users must click the new user invitation link that was sent via email, then click on :guilabel:`Microsoft Azure`. Users should not set a new password."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:160
msgid "To sign in to Odoo for the first time using the Microsoft Azure OAuth provider, navigate to the :menuselection:`Odoo password reset page` (using the new user invitation link). A password reset page should appear. Then, click on the option labeled :guilabel:`Microsoft Azure`. The page will redirect to the Microsoft login page."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:-1
msgid "Microsoft Outlook login page."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:169
msgid "Enter the :guilabel:`Microsoft Email Address` and click :guilabel:`Next`. Follow the process to sign in to the account. Should :abbr:`2FA (Two Factor Authentication)` be turned on, then an extra step may be required."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:-1
msgid "Enter Microsoft login credentials."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:177
msgid "Finally, after logging in to the account, the page will redirect to a permissions page where the user will be prompted to :guilabel:`Accept` the conditions that the Odoo application will access their Microsoft information."
msgstr ""
#: ../../content/applications/general/auth/azure.rst:-1
msgid "Accept Microsoft conditions for permission access to your account information."
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 Odoo users to sign in to their database with their Google account."
msgstr ""
#: ../../content/applications/general/auth/google.rst:8
msgid "This is particularly helpful if the organization uses Google Workspace, and wants employees within the organization to connect to Odoo using their Google Accounts."
msgstr ""
#: ../../content/applications/general/auth/google.rst:12
msgid "Databases hosted on Odoo.com should not use Oauth login for the owner or administrator of the database as it would unlink the database from their Odoo.com account. If Oauth is set up for that user, the database will no longer be able to be duplicated, renamed or otherwise managed from the Odoo.com portal."
msgstr ""
#: ../../content/applications/general/auth/google.rst:18
msgid ":doc:`/applications/productivity/calendar/google`"
msgstr ""
#: ../../content/applications/general/auth/google.rst:19
#: ../../content/applications/general/email_communication/email_servers.rst:68
msgid ":doc:`/administration/maintain/google_oauth`"
msgstr ""
#: ../../content/applications/general/auth/google.rst:26
msgid "The integration of the Google sign-in function requires configuration both on Google *and* Odoo."
msgstr ""
#: ../../content/applications/general/auth/google.rst:31
msgid "Google API Dashboard"
msgstr ""
#: ../../content/applications/general/auth/google.rst:33
msgid "Go to the `Google API Dashboard <https://console.developers.google.com/>`_."
msgstr ""
#: ../../content/applications/general/auth/google.rst:34
msgid "Make sure the right project is opened. If there isn't a project yet, click on :guilabel:`Create Project`, fill out the project name and other details of the company, and click on :guilabel:`Create`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:0
msgid "Filling out the details of a new project."
msgstr ""
#: ../../content/applications/general/auth/google.rst:43
msgid "Choose the name of the company from the drop-down menu."
msgstr ""
#: ../../content/applications/general/auth/google.rst:48
msgid "OAuth consent screen"
msgstr ""
#: ../../content/applications/general/auth/google.rst:50
msgid "On the left side menu, click on :menuselection:`OAuth consent screen`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:0
msgid "Google OAuth consent selection menu."
msgstr ""
#: ../../content/applications/general/auth/google.rst:56
msgid "Choose one of the options (:guilabel:`Internal` / :guilabel:`External`), and click on :guilabel:`Create`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:0
msgid "Choice of a user type in OAuth consent."
msgstr ""
#: ../../content/applications/general/auth/google.rst:64
msgid "*Personal* Gmail Accounts are only allowed to be **External** User Type, which means Google may require an approval, or for *Scopes* to be added on. However, using a *Google WorkSpace* account allows for **Internal** User Type to be used."
msgstr ""
#: ../../content/applications/general/auth/google.rst:68
msgid "Note, as well, that while the API connection is in the *External* testing mode, then no approval is necessary from Google. User limits in this testing mode is set to 100 users."
msgstr ""
#: ../../content/applications/general/auth/google.rst:71
msgid "Fill out the required details and domain info, then click on :guilabel:`Save and Continue`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:72
msgid "On the :menuselection:`Scopes` page, leave all fields as is, and click on :guilabel:`Save and Continue`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:74
msgid "Next, if continuing in testing mode (*External*), add the email addresses being configured under the :guilabel:`Test users` step by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A summary of the app registration appears."
msgstr ""
#: ../../content/applications/general/auth/google.rst:77
msgid "Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:82
msgid "Credentials"
msgstr ""
#: ../../content/applications/general/auth/google.rst:84
msgid "On the left side menu, click on :menuselection:`Credentials`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:0
msgid "Credentials button menu."
msgstr ""
#: ../../content/applications/general/auth/google.rst:90
msgid "Click on :guilabel:`Create Credentials`, and select :guilabel:`OAuth client ID`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:0
msgid "OAuth client id selection."
msgstr ""
#: ../../content/applications/general/auth/google.rst:96
msgid "Select :guilabel:`Web Application` as the :guilabel:`Application Type`. Now, configure the allowed pages on which Odoo will be redirected."
msgstr ""
#: ../../content/applications/general/auth/google.rst:99
msgid "In order to achieve this, in the :guilabel:`Authorized redirect URIs` field, enter the database's domain immediately followed by `/auth_oauth/signin`. For example: `https://mydomain.odoo.com/auth_oauth/signin`, then click on :guilabel:`Create`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:103
msgid "Now that the *OAuth client* has been created, a screen will appear with the :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the :guilabel:`Client ID` for later, as it will be necessary for the configuration in Odoo, which will be covered in the following steps."
msgstr ""
#: ../../content/applications/general/auth/google.rst:110
msgid "Google Authentication on Odoo"
msgstr ""
#: ../../content/applications/general/auth/google.rst:115
msgid "Retrieve the Client ID"
msgstr ""
#: ../../content/applications/general/auth/google.rst:117
msgid "Once the previous steps are complete, two keys are generated on the Google API Dashboard: :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the :guilabel:`Client ID`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:-1
msgid "Google OAuth Client ID generated."
msgstr ""
#: ../../content/applications/general/auth/google.rst:127
msgid "Odoo activation"
msgstr ""
#: ../../content/applications/general/auth/google.rst:129
msgid "Go to :menuselection:`Odoo General Settings --> Integrations` and activate :guilabel:`OAuth Authentication`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:133
msgid "Odoo may prompt the user to log-in again after this step."
msgstr ""
#: ../../content/applications/general/auth/google.rst:135
msgid "Go back to :menuselection:`General Settings --> Integrations --> OAuth Authentication`, activate the selection and :guilabel:`Save`. Next, return to :menuselection:`General Settings --> Integrations --> Google Authentication` and activate the selection. Then fill out the :guilabel:`Client ID` with the key from the Google API Dashboard, and :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:0
msgid "Filling out the client id in Odoo settings."
msgstr ""
#: ../../content/applications/general/auth/google.rst:145
msgid "Google OAuth2 configuration can also be accessed by clicking on :guilabel:`OAuth Providers` under the :guilabel:`OAuth Authentication` heading in :menuselection:`Integrations`."
msgstr ""
#: ../../content/applications/general/auth/google.rst:151
msgid "Log in to Odoo with Google"
msgstr ""
#: ../../content/applications/general/auth/google.rst:153
msgid "To link the Google account to the Odoo profile, click on :guilabel:`Log in with Google` when first logging into Odoo."
msgstr ""
#: ../../content/applications/general/auth/google.rst:0
msgid "Reset password screen with \"Log in with Google\" button."
msgstr ""
#: ../../content/applications/general/auth/google.rst:161
msgid "Existing users must :ref:`reset their password <users/reset-password>` to access the :menuselection:`Reset Password` page, while new users can directly click on :guilabel:`Log in with Google`, instead of choosing a new password."
msgstr ""
#: ../../content/applications/general/auth/google.rst:166
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 Lightweight Directory Access Protocol (LDAP) module in General Settings."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:7
msgid "Click on **Create** in Setup the :abbr:`LDAP (Lightweight Directory Access Protocol)` Server."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:-1
msgid "LDAP Authentication checkbox highlighted in the integrations settings on Odoo."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:-1
msgid "Create highlighted in the LDAP server settings."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:17
msgid "Choose the company using the LDAP."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:-1
msgid "Select the company drop-down menu highlighted in LDAP setup."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:23
msgid "In **Server Information**, enter the IP address of the server and the port it listens to."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:25
msgid "Tick **Use TLS** if the server is compatible."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:-1
msgid "LDAP server settings highlighted in LDAP server setup on Odoo."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:31
msgid "In **Login Information**, enter ID and password of the account used to query the server. If left empty, the server queries anonymously."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:-1
msgid "Login information highlighted in LDAP server setup on Odoo."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:38
msgid "In **Process Parameter**, enter the domain name of the LDAP server in :abbr:`LDAP (Lightweight Directory Access Protocol)` nomenclature (e.g. ``dc=example,dc=com``)."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:41
msgid "In **LDAP filter**, enter ``uid=%s``"
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:-1
msgid "Process parameter highlighted in LDAP server setup on Odoo."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:47
msgid "In **User Information**, tick *Create User* if Odoo should create a User profile the first time someone logs in with :abbr:`LDAP (Lightweight Directory Access Protocol)`."
msgstr ""
#: ../../content/applications/general/auth/ldap.rst:50
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/auth/ldap.rst:-1
msgid "User information highlighted on LDAP server setup on Odoo."
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) unlocks access to extra and advanced tools in Odoo. There are several ways to activate the developer mode: through the :ref:`settings <general/developer_mode/settings>`, the :ref:`browser extension <general/developer_mode/browser-extension>`, through the :ref:`command palette <general/developer_mode/command-palette>` or the :ref:`URL <general/developer_mode/url>`."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:17
msgid "Activate through the Settings"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:19
msgid "The debug mode can be activated in the Odoo database settings. Go to :menuselection:`Settings --> General Settings --> Developer Tools` and click on :guilabel:`Activate the developer mode`. At least one application needs to be installed for the :guilabel:`Developer Tools` section to appear in the :guilabel:`Settings` module."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:-1
msgid "Overview of the debug options under settings in Odoo."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:29
msgid ":guilabel:`Activate the developer mode (with assets)` is used by developers; :guilabel:`Activate the developer mode (with tests assets)` is used by developers and testers."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:32
msgid "Once activated, the :guilabel:`Deactivate the developer mode` option becomes available."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:37
msgid "Activate through the browser extension"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:39
msgid "Within a web browser, navigate to the browser settings and extensions and search for the `Odoo Debug` extension. Once the extension is installed, a new icon will be shown on the browser's toolbar."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:43
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:-1
msgid "View of Odoo's debug icon in a Google Chrome toolbar."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:53
msgid "Activate through the command palette"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:55
msgid "In Odoo, the command palette tool has a command to activate the debug mode. First, open the command palette tool with the keyboard shortcut `ctrl+k` and then type `debug`. A command will show up to activate the debug mode."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:-1
msgid "Command palette with debug command."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:66
msgid "Activate through the URL"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:68
msgid "The debug mode can also be activated by adding an extra query string to the database's URL. In the URL, add `?debug=1` or `?debug=true` after `/web`. To deactivate the debug mode, change the value to `?debug=0` instead."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:-1
msgid "Overview of a URL with the debug mode command added."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:77
msgid "Additional modes are available for developers: `?debug=assets` enables the :ref:`assets mode <frontend/framework/assets_debug_mode>`, and `?debug=tests` enables the :ref:`tests mode <frontend/framework/tests_debug_mode>`."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:84
msgid "Locate the developer mode tools"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:86
msgid "Once developer mode is activated, the developer mode tools can be accessed from the :guilabel:`Open Developer Tools` button, the bug icon located in the header of the Odoo database."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:-1
msgid "Overview of a console page and the debug icon being shown in Odoo."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:93
msgid "This menu contains additional tools that are useful to understand or edit technical data, such as the views or actions of a page. On a page that has filters, actions, and view options, the developer mode tools contain some useful menu items such as:"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:97
msgid ":guilabel:`Edit Action`"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:98
msgid ":guilabel:`Manage Filters`"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:99
msgid "Edit the current view (e.g. Kanban, List, Graph, etc.)"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:100
msgid "See the :guilabel:`Fields View Get`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:3
msgid "Digest Emails"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:5
msgid "**Digest Emails** are periodic snapshots sent to your organization via email that include high-level information about how your business is performing."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:8
msgid "Navigate to Digest Emails by going to :menuselection:`Settings --> General Settings --> Statistics`, then activate the **Digest Emails** feature and click on save."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:-1
msgid "Digest Emails section inside General Settings."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:15
msgid "You can control a variety of settings for your Digest Emails, such as:"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:17
msgid "which KPIs are shared in the Digest"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:18
msgid "how often Digest Emails are sent"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:19
msgid "who in your organization receives Digest Emails"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:20
msgid "creating custom Digest Email templates"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:21
msgid "adding additional KPIs (Studio required)"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:24
msgid "By default, Digest Email is *enabled*, and *Your Odoo Periodic Digest* serves as the primary template, which includes all KPI measurements across your Odoo database and is sent daily to administrators."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:31
msgid "Customize *Your Odoo Periodic Digest*"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:33
msgid "To customize the default Digest Email (*Your Odoo Periodic Digest*), go to :menuselection:`Settings --> General Settings --> Statistics --> Digest Email`, select *Your Odoo Periodic Digest* and click on the *external link* next to the dropdown selection."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:37
msgid "A popup window appears and presents a variety of editable settings, which include:"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:39
msgid "**Digest Title** - what you want your Digest Email to be called"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:40
msgid "**Periodicity** - control the regimen in how often Digest Emails are sent"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:41
msgid "**KPIs** - check/uncheck each calculated KPI that appears in Digest Emails"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:42
msgid "**Recipients** - add/remove users who receive your Digest Emails"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:43
msgid "**Custom** - add your own KPIs (Studio required)"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:-1
msgid "Customize default Digest Email settings and custom KPIs."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:52
msgid "Custom digest emails"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:54
msgid "To do so, click on **Configure Digest Emails** and then **Create**."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:56
msgid "From there, give your Digest Email a title, specify periodicity, and choose your desired KPIs and recipients fields as needed."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:59
msgid "After you click **Save**, your new custom Digest Email is available as a selection in the **General Settings** dropdown menu."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:65
msgid "Custom KPIs with Studio"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:67
msgid "For either *Your Odoo Periodic Digest* or your own custom Digest Email, you can add your own KPIs by using Odoo Studio."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:70
msgid "To begin, click the **Toggle Studio** icon or click the **Recipients** tab and then the ellipses :menuselection:`… icon --> Add Custom Field` to edit the template or add additional fields."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:73
msgid "In order to create additional fields, you must create two fields on the digest object:"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:75
msgid "create a boolean field called `kpi_myfield` and display it in the KPIs tab"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:76
msgid "create a computed field called `kpi_myfield_value` that computes your customized KPI"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:77
msgid "select your KPI(s) in the KPIs tab."
msgstr ""
#: ../../content/applications/general/digest_emails.rst:80
msgid "Computed values reference table"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:83
msgid "LABEL"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:83
msgid "VALUE"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:85
msgid "Connected Users"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:85
msgid "`kpi_res_users_connected_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:87
msgid "Messages Sent"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:87
msgid "`kpi_mail_message_total_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:89
msgid "New Leads"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:89
msgid "`kpi_crm_lead_created_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:91
msgid "Opportunities Won"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:91
msgid "`kpi_crm_opportunities_won_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:93
msgid "Open Tasks"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:93
msgid "`kpi_project_task_opened_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:95
msgid "Tickets Closed"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:95
msgid "`kpi_helpdesk_tickets_closed_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:97
msgid "% of Happiness"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:97
msgid "`kpi_livechat_rating_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:99
msgid "Conversations handled"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:99
msgid "`kpi_livechat_conversations_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:101
msgid "Time to answer (sec)"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:101
msgid "`kpi_livechat_response_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:103
msgid "All Sales"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:103
msgid "`kpi_all_sale_total_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:105
msgid "eCommerce Sales"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:105
msgid "`kpi_website_sale_total_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:107
msgid "Revenue"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:107
msgid "`kpi_account_total_revenue_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:109
msgid "Bank & Cash Moves"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:109
msgid "`kpi_account_bank_cash_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:111
msgid "POS Sales"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:111
msgid "`kpi_pos_total_value`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:113
msgid "New Employees"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:113
msgid "`kpi_hr_recruitment_new_colleagues_value`"
msgstr ""
#: ../../content/applications/general/email_communication.rst:5
msgid "Email Communication"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:3
msgid "Configure DNS records to send emails in Odoo"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:6
msgid "SPAM labels overview"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:8
msgid "Sometimes, emails from Odoo are misclassified by the different email providers and end up in spam folders. At the moment, some settings are out of Odoo's control, notably the way the different email providers classify Odoo's emails according to their own restriction policy and/or limitations."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:12
msgid "It is standard in Odoo that emails are received from ``\"name of the author\" <notifications@mycompany.odoo.com>``. In other words this can be translated to: ``\"name of the author\" <{ICP.mail.from.filter}@{mail.catchall.domain}>``. In this case ICP stands for `ir.config.parameters`, which are the System Parameters. Deliverability is greatly improved with the :ref:`notifications configuration <email_servers/notifications>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:18
msgid "In order for servers to accept emails from Odoo on a more regular basis, one of the solutions is for customers to create rules within their own mailbox. A filter can be added to the email inbox so that when email is received from Odoo (`notifications@mycompany.odoo.com`) it is moved to the inbox. It is also possible to add the Odoo database domain onto a safe senders list or whitelist on the receiving domain."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:24
msgid "If an Odoo email server appears on a blacklist, notify Odoo via a `new help ticket <https://www.odoo.com/help>`_ and the support team will work to get the servers removed from the blacklist."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:28
msgid "Should the Odoo database be using a custom domain for sending emails from Odoo there are three records that should be implemented on the custom domain's DNS to ensure deliverability of email. This includes setting records for :abbr:`SPF (Sender Policy Framework)`, :abbr:`DKIM (DomainKeys Identified Mail)` and :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)`. Ultimately though, it is up to the discretion of the final receiving mailbox."
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 emails 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 sender's :abbr:`SPF (Sender Policy Framework)` record."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:46
msgid "The :abbr:`SPF (Sender Policy Framework)` 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 "The :abbr:`SPF (Sender Policy Framework)` policy of a domain is set using a TXT record. The way to create or modify a TXT record depends on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. In order for the verification to work properly, each domain can only have one :abbr:`SPF (Sender Policy Framework)` record."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:55
msgid "If the domain name does not yet have a :abbr:`SPF (Sender Policy Framework)` record, create one using the following input: `v=spf1 include:_spf.odoo.com ~all`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:58
msgid "If the domain name already has a :abbr:`SPF (Sender Policy Framework)` record, the record must be updated (and do not create a new one)."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:63
msgid "If the TXT record is `v=spf1 include:_spf.google.com ~all`, 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:66
msgid "Check if the :abbr:`SPF (Sender Policy Framework)` record is valid with a free tool like `MXToolbox SPF <https://mxtoolbox.com/spf.aspx>`_."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:72
msgid "Enable DKIM"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:74
msgid "The DomainKeys Identified Mail (DKIM) allows a user to authenticate emails with a digital signature."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:77
msgid "When sending an email, the Odoo server includes a unique :abbr:`DKIM (DomainKeys Identified Mail)` signature in the headers. The recipient's server decrypts this signature using the :abbr:`DKIM (DomainKeys Identified Mail)` record in the database's domain name. If the signature and the key contained in the record match, this guarantees that the message is authentic and has not been altered during transport."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:83
msgid "To enable :abbr:`DKIM (DomainKeys Identified Mail)`, add a :abbr:`CNAME (Canonical Name)` record to the :abbr:`DNS (Domain Name System)` zone of the 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 the domain name is `mycompany.com`, make sure 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 "The way to create or modify a :abbr:`CNAME (Canonical Name)` record depends on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. The most common providers are :ref:`listed below <email_communication/SPFDKIM_common_providers>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:96
msgid "Check if the :abbr:`DKIM (DomainKeys Identified Mail)` 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:100
msgid "Check the DMARC policy"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:102
msgid "The Domain-based Message Authentication, Reporting, & Conformance (DMARC) record is a protocol that unifies :abbr:`SPF (Sender Policy Framework)` and :abbr:`DKIM (DomainKeys Identified Mail)`. The instructions contained in the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record of a domain name tell the destination server what to do with an incoming email that fails the :abbr:`SPF (Sender Policy Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:110
msgid "DMARC: TXT record"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:112
msgid "`v=DMARC1; p=none;`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:114
msgid "There are three :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policies:"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:117
msgid "`p=none`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:118
#: ../../content/applications/general/email_communication/email_domain.rst:171
msgid "`p=quarantine`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:119
msgid "`p=reject`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:121
msgid "`p=quarantine` and `p=reject` instruct the server that receives an email to quarantine that email or ignore it if the :abbr:`SPF (Sender Policy Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check fails."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:125
msgid "If the domain name uses :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` and has defined one of these policies, the domain must be :abbr:`SPF (Sender Policy Framework)` compliant or enable :abbr:`DKIM (DomainKeys Identified Mail)`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:130
msgid "Yahoo or AOL are examples of email providers with a :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policy set to `p=reject`. Odoo strongly advises against using an *@yahoo.com* or *@aol.com* address for the database users. These emails will never reach their recipient."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:135
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 :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` check fails."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:139
msgid ":abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` records are comprised of tags in the form of :abbr:`DNS (Domain Name System)` records. These tags/parameters allow for reporting, such as :abbr:`RUA (Reporting URI of aggregate reports)` and :abbr:`RUF (Reporting URI for forensic reports)`, along with more precise specification like :abbr:`PCT (Percentage of messages subjected to filtering)`, :abbr:`P (Policy for organizational domain)`, :abbr:`SP (Policy for subdomains of the OD)` :abbr:`ADKIM (Alignment mode for DKIM)` & :abbr:`ASPF (Alignment mode for SPF)`. For best practice, the the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policy should not start out being too restrictive."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:148
msgid "The following chart displays available tags:"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:154
msgid "Tag Name"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:155
msgid "Purpose"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:156
msgid "Example"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:157
msgid "v"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:158
msgid "Protocol version"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:159
msgid "`v=DMARC1`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:160
msgid "pct"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:161
msgid "Percentage of messages subjected to filtering"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:162
msgid "`pct=20`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:163
msgid "ruf"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:164
msgid "Reporting URI for forensic reports"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:165
msgid "`ruf=mailto:authfail@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:166
msgid "rua"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:167
msgid "Reporting URI of aggregate reports"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:168
msgid "`rua=mailto:aggrep@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:169
msgid "p"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:170
msgid "Policy for organizational domain"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:172
msgid "sp"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:173
msgid "Policy for subdomains of the OD"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:174
msgid "`sp=reject`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:175
msgid "adkim"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:176
msgid "Alignment mode for DKIM"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:177
msgid "`adkim=s`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:178
msgid "aspf"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:179
msgid "Alignment mode for SPF"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:180
msgid "`aspf=r`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:182
msgid "Check the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` 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:186
msgid "`DMARC.org is another great resource to learn about DMARC records. <https://dmarc.org/overview/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:192
msgid "SPF, DKIM & DMARC documentation of common providers"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:194
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:195
msgid "`OVH SPF <https://docs.ovh.com/us/en/domains/web_hosting_the_spf_record/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:196
msgid "`GoDaddy TXT record <https://www.godaddy.com/help/add-a-txt-record-19232>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:197
msgid "`GoDaddy SPF <https://www.godaddy.com/help/add-an-spf-record-19218>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:198
msgid "`GoDaddy DKIM <https://www.godaddy.com/help/add-a-cname-record-19236>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:199
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:201
msgid "`CloudFlare DNS <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:202
msgid "`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:203
msgid "`Azure DNS <https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:205
msgid "To fully test the configuration, use the `Mail-Tester <https://www.mail-tester.com/>`_ tool, which gives a full overview of the content and configuration in one sent email. Mail-Tester can also be used to configure records for other, lesser-known providers."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:210
msgid "`Using Mail-Tester to set SPF Records for specific carriers <https://www.mail-tester.com/spf/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:5
msgid "Send and receive emails in Odoo with an email server"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:8
msgid "Odoo Online or Odoo.sh users"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:10
msgid "Since **Odoo sets up its own mail servers for the database**, outgoing and incoming emails already work out-of-the-box. So for **Odoo Online** and **Odoo.sh** customers, nothing needs to be configured!"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:14
msgid "Unless an external mail server is required to send large batches of mass emails, simply use the standard online Odoo database normally since it has already been pre-configured to send email."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:18
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 the :doc:`FAQ <faq>` or contact support for more information."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:24
msgid "Scope of this documentation"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:26
msgid "This document is **mainly dedicated to Odoo on-premise databases** 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>`_ and `Odoo.sh <https://www.odoo.sh>`_. Incoming and outgoing servers must be configured for on-premise databases."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:31
msgid "The following sections below contain information on how to integrate an external email server with Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:35
msgid "If no one in the company is employed to manage email servers, Odoo Online and Odoo.sh are strongly recommended. In these Odoo hosting types email sending and receiving works instantly and is monitored by professionals. Nevertheless, a company can use their own email server if they want to manage the email server's reputation themselves. For more information see :doc:`Configure DNS records to send emails in Odoo <email_domain>`"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:44
msgid "Default notifications system"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:46
msgid "Documents in Odoo (such as a CRM opportunity, a sales order, an invoice, etc.) have a discussion thread, called *chatter*."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:49
msgid "When a database user posts a message in the chatter, this message is sent by email to the followers of the document as a notification (except to the sender). If a follower replies to the message, the reply updates the chatter, and Odoo relays another reply to the followers as a notification. Messages sent back to the chatter from users or external users will appear in the chatter from their respective email, or as the name listed in their *Contacts* record."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:55
msgid "These notifications are sent using a default from address. For more information see :ref:`Use a default email address <email_communication/default>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:59
msgid "Manage outbound messages"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:61
msgid "As a system admin, go to :menuselection:`Settings --> General Settings --> Discuss` in Odoo, and enable the :guilabel:`Custom Email Servers` option. Then, click :guilabel:`Save`. Next, click :guilabel:`Outgoing Email Servers` and click :guilabel:`Create` to create a new outgoing mail server record in Odoo. Reference the SMTP data of the external email server. Once all the information has been filled out, click :guilabel:`Test Connection`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:72
msgid "Ensuring the outgoing domain has :abbr:`SPF (Sender Policy Framework)`, :abbr:`DKIM (DomainKeys Identified Mail)` and :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` set up on the :abbr:`DNS (Domain Name System)` will improve deliverability. For more information see :doc:`email_domain`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:80
msgid "Port restriction"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:82
msgid "Note that port 25 is blocked for security reasons on the Odoo Online and Odoo.sh platforms. Try using ports 465, 587, or 2525 instead."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:88
msgid "Use a default \"From\" email address"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:90
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:93
msgid "For example, if a customer with the email address `mary\\@customer.example.com` responds to a message, Odoo will try to redistribute that same email to the other subscribers in the thread. However, if the domain `customer.example.com` forbids that kind of usage for security, the email that Odoo is trying to redistribute would get rejected by some recipients' email servers."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:98
msgid "To avoid that problem, Odoo sends all emails using a \"From\" address from the same authorized domain."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:101
msgid "Access the :guilabel:`System Parameters` by activating :ref:`developer mode <developer-mode>` and going to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:104
msgid "To force the email address from which emails are sent, a combination of the following keys needs to be set in the system parameters of the database:"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:107
msgid "`mail.default.from`: accepts the local part or a complete email address as value"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:108
msgid "`mail.default.from_filter`: accepts a domain name or a full email address as value"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:111
msgid "The `mail.default.from_filter` works only for `odoo-bin` configurations or the default Odoo email server, otherwise this parameter can be set using the `from_filter` field on `ir.mail_server`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:114
msgid "The field can be a domain name or an entire email address, or it can remain empty. If the sender's email address does not match this set filter, then the email will be encapsulated using a combination of the two system parameters: `mail.default.from` and `mail.catchall.domain`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:119
msgid "In the following example, the from email address is replaced with the combination of the the two system parameters (`mail.default.from` and `mail.catchall.domain`). This is the default\\ notifications configuration in Odoo: ``“Admin” <admin@example.com>`` => ``“Admin” <notifications@mycompany.com>``."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:124
msgid "In other words if the email address of the author does not match `mail.default.from_filter`, the email address is replaced by `mail.default.from` (if it contains a full email address) or a combination of `mail.default.from` and `mail.catchall.domain`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:128
msgid "If the `from_filter` contains a full email address, and if the `mail.default.from` is the same as this address, then all of the email addresses that are different from `mail.default.from` will be encapsulated in `mail.default.from`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:135
msgid "Utilizing the \"From\" filter on an outgoing email server"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:137
msgid "The :guilabel:`FROM Filtering` field allows for the use of a specific outgoing email server depending on the :guilabel:`From` email address or domain that Odoo is sending on behalf of. This setting can be used to improve the deliverability or sending success rate of emails sent from the database. Setting the :guilabel:`FROM Filtering` field can also be used to send from different domains in a multi-company environment. Access this field in Odoo by navigating to :menuselection:`Settings --> Discuss --> Custom Mail Servers --> Outgoing Mail Servers --> New`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:-1
msgid "Outgoing email server settings and the FROM filter settings."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:148
msgid "When an email is sent from Odoo while the :guilabel:`FROM Filtering` field is set, an email server is chosen in the following sequence:"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:151
msgid "First, Odoo searches for an email server that has the same :guilabel:`FROM Filtering` value as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` value (email address) is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `test\\@example.com` are returned."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:155
msgid "However, if no email servers are found that use the :guilabel:`From` value, then Odoo searches for an email server that has the same *domain* as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` email address is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `example.com` are returned."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:161
msgid "If no email servers are found after checking for the domain, then Odoo returns all email servers that do not have any :guilabel:`FROM Filtering` value(s) set."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:164
msgid "Should this query return no results, then Odoo performs a search for an email server using the system parameter: `mail.default.from`. First, the email address listed attempts to match an email server, and then the domain attempts to find a match. If no email server is found, Odoo returns the first outgoing email server (sorted by priority)."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:170
msgid "If several email servers are found, then Odoo uses the first one according to its priority. For example, if there are two email servers, one with a priority of `10` and the other with a priority of `20`, then the email server with a priority of `10` is used first."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:177
msgid "Set up different dedicated servers for transactional and mass emails"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:179
msgid "In Odoo a separate email server can be used for transactional emails and mass mailings. Example: Use Postmark or SendinBlue for transactional emails, and Amazon SES, Mailgun, Sendgrid or :doc:`Mailjet </administration/maintain/mailjet_api>` for mass mailings."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:184
msgid "A default outgoing email server is already configured. Do not create an alternative one unless a specific external outgoing email server is needed for technical reasons."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:187
msgid "To do this, first activate the :ref:`developer mode <developer-mode>`, and then go to :menuselection:`Settings --> Technical --> Outgoing` email servers. There, create two outgoing email server settings; one for the transactional emails and one for the mass mailing server. Make sure to give priority to the transactional server over the mass mailing server by providing a lower priority number for the transactional email server."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:193
msgid "Now, go to :menuselection:`Email Marketing --> Settings` and enable :guilabel:`Dedicated Server`. Choose the appropriate email 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, the domain's Sender Policy Framework (SPF) records must be set to include both transactional and mass mail servers."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:200
msgid ":doc:`email_domain`"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:205
msgid "Manage inbound messages"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:207
msgid "Odoo relies on generic email aliases to fetch incoming messages."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:209
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 alias of the model if there is any or by the catchall alias (**catchall@**). Replies to messages of models that don't have a custom alias will use the catchall alias (`catchall@mycompany.odoo.com`). The catchall address, however, does not have another action attached to it like other aliases might, it is only used to collect replies."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:214
msgid "**Bounced messages** are used as a Return-Path. One example this is especially useful for is in `Odoo Email Marketing <https://www.odoo.com/page/email-marketing>`__. In this case bounces are opt-out based on if the email bounced too many times (5) in the last month and the bounces are separated by one week. This is done to avoid blacklisting someone because of a mail server error. If these circumstances are met then the email is considered invalid and is blacklisted. A log note is added on the contact under :guilabel:`Blacklisted Email Addresses` on the :guilabel:`Email Marketing Configuration Menu`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:222
msgid "Messages that bounce in the chatter (outside of Email Marketing) will populate a red envelope indicating the failed delivery. This can be helpful to know that a Sales Order or an Invoice did not reach its final destination."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:225
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:228
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:230
msgid "Support channel (to create *Tickets* in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`_)"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:231
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:233
msgid "Job positions (to create *Applicants* in `Odoo Recruitment <https://www.odoo.com/page /recruitment>`_)"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:236
msgid "Depending on the 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 the mail server."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:239
msgid "Create the corresponding email addresses in the mail server (**catchall@**, **bounce@**, **sales@**, etc.)."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:241
msgid "Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> General Settings --> Discuss`. Changing the :guilabel:`Alias Domain` will change the catchall's domain for the database."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:244
msgid "If the database's hosting type is Odoo on-premise, create an :guilabel:`Incoming Mail Server` in Odoo for each alias. To create a new incoming server go to: :menuselection:`Settings --> Discuss --> Custom Mail Servers --> Incoming Mail Servers --> New` Fill out the form according to the email provider's settings. Leave the :guilabel:`Actions to Perform on Incoming Mails` field blank. Once all the information has been filled out, click on :guilabel:`TEST & CONFIRM`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:0
msgid "Incoming mail server configuration on Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:254
msgid "If the database's hosting type is Odoo Online or Odoo.sh, redirecting or forwarding incoming messages to Odoo's domain name instead of the external email server is recommended. That way, incoming messages can be received without delay. Redirections for all email addresses should be set to Odoo's domain name in the email server (e.g. `catchall\\@mydomain.ext` to `catchall\\@mycompany.odoo.com`)."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:260
msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their respective configuration view by navigating to :menuselection:`Settings --> Technical Menu --> Email --> Aliases`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:264
msgid "To edit catchall and bounce aliases, first activate the :ref:`developer mode <developer-mode>`. Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (`mail.catchall.alias` & `mail.bounce.alias`). These types of changes should be completed prior to the database going live. If a customer replies after a change is made then the system will not recognize the old alias and the reply won't be received."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:270
msgid "By default, inbound messages are fetched every 5 minutes for on-premise databases."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:273
msgid "This value can be changed in :ref:`developer mode <developer-mode>`. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for :guilabel:`Mail: Fetchmail Service`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:3
msgid "Email templates"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:5
msgid "Email templates are saved emails that are used repeatedly to send emails from the database. They allow users to send quality communications, without having to compose the same text repeatedly."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:8
msgid "Creating different templates that are tailored to specific situations lets users choose the right message for the right audience. This increases the quality of the message and the overall engagement rate with the customer."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:13
msgid "Email templates in Odoo use QWeb or XML, which allows for editing emails in their final rendering, making customizations more robust, without having to edit any code whatsoever. This means that Odoo can use a Graphical User Interface (GUI) to edit emails, which edits the backend code. When the received email is read by the end user's program different formatting and graphics will appear in the final form of it."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:19
msgid "Access email templates in :ref:`developer mode <developer-mode>` by navigating to :menuselection:`Settings app --> Technical menu --> Email --> Email Templates`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:23
msgid "Editing email templates"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:25
msgid "The *powerbox* feature can be used when working with email templates. This feature provides the ability to directly edit the formatting and text in an email template, as well as the ability to add links, buttons, appointment options, or images."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:29
msgid "Additionally, the XML/HTML code of the email template can be edited directly, via the :guilabel:`</>` icon."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:32
msgid "*Dynamic placeholders* (text that references fields within Odoo to auto-fill information on the template) are available for the :guilabel:`Email Configuration` fields, the :guilabel:`Subject`, and the :guilabel:`Language`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:37
msgid "Powerbox"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:39
msgid "The *powerbox* feature is an enriched text editor with various formatting, layout, and text options. It can also be used to add XML/HTML features in an email template. The powerbox feature is activated by typing a forward slash `/` in the body of the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:43
msgid "When a forward slash `/` is typed in the body of an email template, a drop-down menu appears with the following options:"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:46
msgid ":guilabel:`Basic Blocks`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:48
msgid ":guilabel:`Heading 1`: Big section heading."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:49
msgid ":guilabel:`Heading 2`: Medium section heading."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:50
msgid ":guilabel:`Heading 3`: Small section heading."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:51
msgid ":guilabel:`Text`: Paragraph block."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:52
msgid ":guilabel:`Bulleted list`: Create a simple bulleted list."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:53
msgid ":guilabel:`Numbered list`: Create a list with numbering."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:54
msgid ":guilabel:`Checklist`: Track tasks with a checklist."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:55
msgid ":guilabel:`Table`: Insert a table."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:56
msgid ":guilabel:`Switch direction`: Switch the text's direction."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:57
msgid ":guilabel:`Separator`: Insert a horizontal rule separator."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:58
msgid ":guilabel:`Quote`: Add a blockquote section."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:59
msgid ":guilabel:`Code`: Add a code section."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:60
msgid ":guilabel:`Appointment`: Add a specific appointment."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:61
msgid ":guilabel:`Calendar`: Schedule an appointment."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:63
msgid ":guilabel:`Navigation`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:65
msgid ":guilabel:`Link`: Add a link."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:66
msgid ":guilabel:`Button`: Add a button."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:68
msgid ":guilabel:`Medias`"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:70
msgid ":guilabel:`Image`: Insert an image."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:73
msgid "To use any of these options, click on the desired feature from the powerbox drop-down menu. To format existing text with a text-related option (e.g. :guilabel:`Heading 1`, :guilabel:`Switch direction`, etc.), highlight the text, then type in the activator key (forward slash) `/`, and select the desired option from the drop-down menu."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:0
msgid "Powerbox feature in the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:83
msgid "XML/HTML code editor"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:85
msgid "To access the XML/HTML editor for an email template, first enter :ref:`developer mode <developer-mode>`. Then, click the :guilabel:`</>` icon in the upper-right corner of the template, and proceed to edit the XML/HTML. To return to the standard text editor, click the :guilabel:`</>` icon again."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "HTML editor in the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:95
msgid "The XML/HTML editor should be accessed with caution as this is the backend code of the template. Editing the code can cause the email template to break immediately or when upgrading the database."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:100
msgid "Dynamic placeholders"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:102
msgid "*Dynamic placeholders* reference certain fields within the Odoo database to produce unique data in the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:106
msgid "Many companies like to customize their emails with a personalized piece of customer information to grab attention. This can be accomplished in Odoo by referencing a field within a model by inserting a dynamic placeholder. For example, a customer's name can be referenced in the email from the :guilabel:`Customer` field on the :guilabel:`Sales Order` model. The dynamic placeholder for this field is: `{{ object.partner_id }}`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:112
msgid "Dynamic placeholders are encoded to display fields from within the database. Dynamic placeholders can **only** be used in the fields present in the :guilabel:`Email Configuration` tab, the :guilabel:`Subject` of the email, and the :guilabel:`Language`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:116
msgid "Dynamic placeholders can be used with the following fields on an email template:"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:118
msgid ":guilabel:`Subject` (:guilabel:`Content` tab)"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:119
msgid ":guilabel:`From` (:guilabel:`Email Configuration` tab)"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:120
msgid ":guilabel:`To (Emails)` (:guilabel:`Email Configuration` tab)"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:121
msgid ":guilabel:`To (Partners)` (:guilabel:`Email Configuration` tab)"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:122
msgid ":guilabel:`CC` (:guilabel:`Email Configuration` tab)"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:123
msgid ":guilabel:`Reply-To` (:guilabel:`Email Configuration` tab)"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:124
msgid ":guilabel:`Language` (:guilabel:`Advanced Settings` tab)"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:126
msgid "The :guilabel:`Dynamic Placeholder Generator`, which is the last tab on the email template, creates placeholders for the aforementioned fields. Dynamic placeholders may also be inserted in the HTML code, but this task is out of the scope of Odoo Support."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:130
msgid "To use the *Dynamic Placeholder Generator*, navigate to the :guilabel:`Dynamic Placeholder Generator` tab. Select the field that the dynamic placeholder should reference using the :guilabel:`Field` drop-down menu. Should a :guilabel:`Sub-Model` or :guilabel:`Sub-Field` need to be specified, set those by selecting the corresponding drop-down menu. These fields should be set automatically after setting the :guilabel:`Field`, although in some instances these fields will remain empty. The dynamic placeholder will appear in the :guilabel:`Placeholder Expression` field. Copy and paste the placeholder expression into the appropriate field in the tabs of the email template, as listed in the bulleted list above."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:140
msgid "Each unique combination of :guilabel:`Fields`, :guilabel:`Sub-models` and :guilabel:`Sub-fields` creates a different dynamic placeholder. Imagine it as a combination to the field that is being created."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:144
msgid "To search the available fields, simply click the drop-down menu next to :guilabel:`Field` and select one, or click :guilabel:`Search More` to select from all of the available fields for the model that the email template is created for."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:149
msgid ":doc:`../../productivity/studio/models_modules_apps`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:152
msgid "These fields can also be accessed in :ref:`developer mode <developer-mode>`. On a contact form (or other relevant form in Odoo), navigate to the information that should be referenced in the dynamic placeholder, and hover over the field name. A box of backend information will reveal itself with the specific Odoo :guilabel:`Field` name in the backend. Search for this field in the :guilabel:`Field` drop-down menu in the email template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:0
msgid "Backend information box of fields on a model."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:163
msgid ":ref:`Views and fields in the developer documentation <developer/fields>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:166
msgid "Customizing email templates are out of the scope of Odoo Support."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:169
msgid "Default reply on email templates"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:171
msgid "Under the :guilabel:`Email Configuration` tab on an email template, there is a :guilabel:`Reply To` field. In this field, add email addresses to which replies are redirected when sending emails en masse using this template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:176
msgid "A Add multiple email addresses by adding a comma `,` between the addresses or dynamic placeholders."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Reply-to field on template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:183
msgid "The :guilabel:`Reply To` field is **only** used for mass mailing (sending emails in bulk). Bulk emails can be sent in almost every Odoo application that has a list view option."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:186
msgid "To send mass mails, while in :guilabel:`list` view, check the boxes next to the desired records where the emails are to be sent, click the :guilabel:`Action` button (represented by a :guilabel:`⚙️ (gear)` icon), and select the desired email option from the :guilabel:`Action` drop-down menu. Email options can vary by the particular list view and application."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:191
msgid "If it is possible to send an email, a mail composer pop-up window appears, with values that can be defined and customized. This option will be available on the :guilabel:`Action` button on pages where emails can be sent in bulk---for example, on the :guilabel:`Customers` page of the CRM app. This action occurs throughout the Odoo database."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Email composer in mass mailing mode with reply-to highlighted."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:201
msgid "Transactional emails and corresponding URLs"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:203
msgid "In Odoo, multiple events can trigger the sending of automated emails. These emails are known as *transactional emails*, and sometimes contain links redirecting to the Odoo database."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:206
msgid "By default, links generated by the database use the dynamic `web.base.url` key defined in the system parameters. For more information about this, see :ref:`system parameters <domain-name/web-base-url>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:210
msgid "If the *Website* application is not 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:214
msgid "The `web.base.url` key can only have a single value, meaning that, in a multi-website or multi-company database environment, even if there is a specific domain name for each website, the links generated to share a document (or the links within a transactional email) may remain the same, regardless of which website/company is related to the sending of the email/document."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:220
msgid "If the :guilabel:`Value` of the :guilabel:`web.base.url` system parameter is equal to `https://www.mycompany.com` and there are two separate companies in Odoo with different website URLs: `https://www.mycompany2.com` and `https://www.mycompany1.com`, the links created by Odoo to share a document, or send a transactional email, come from the domain: `https://www.mycompany.com`, regardless of which company sends the document or email."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:226
msgid "This is not always the case, as some Odoo applications (*eCommerce*, for example) have a link established in the database with the *Website* application. In that case, if a specific domain is defined for the website, the URL generated in the email template uses the domain defined on the corresponding website of the company."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:232
msgid "When a customer makes a purchase on an Odoo *eCommerce* website, the order has an established link with that website. As a result, the links in the confirmation email sent to the customer use the domain name for that specific website."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:237
msgid "A document shared using the *Documents* application will **always** use the `web.base.url` key, as the document shared is not associated with any particular website. This means that the URL will always be the same (the `web.base.url` key value), no matter what company it's shared from. This is a known limitation."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:242
msgid "For more information about how to configure domains, check out the :doc:`domain name documentation </administration/maintain/domain_names>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:246
msgid "Updating translations within email templates"
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:248
msgid "In Odoo, email templates are automatically translated for all users in the database for all of the languages installed. Changing the translations shouldn't be necessary. However, if for a specific reason, some of the translations need to be changed, it can be done."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:253
msgid "Like any modification in the code, if translation changes are not done correctly (for example, modifications leading to bad syntax), it can break the template, and as a result, the template will appear blank."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:257
msgid "In order to edit translations, first enter :ref:`developer mode <developer-mode>`. Then, on the email template, click on the :guilabel:`Edit` button, and then click on the language button, represented by the initials of the language currently being used (e.g. :guilabel:`EN` for English)."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Edit the language of a template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:266
msgid "If there aren't multiple languages installed and activated in the database, or if the user does not have administration access rights, the language button will not appear."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:269
msgid "A pop-up window with the different languages installed on the database appears. From this pop-up, editing of translations is possible. When the desired changes have been made, click the :guilabel:`Save` button to save the changes."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:-1
msgid "Translation of the body of the Appointment Booked template."
msgstr ""
#: ../../content/applications/general/email_communication/email_template.rst:278
msgid "When editing the translations, the default language set in the database appears in **bold**."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:3
msgid "Email issues"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:5
msgid "This document contains an explanation of the most recurring emailing issues in Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:8
msgid "Outgoing emails"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:13
msgid "Email is not sent"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:15
msgid "The first indicator showing that an email has not been sent is the presence of a red :guilabel:`✉️ (envelope)` icon, next to the date and time of the message, located in the chatter."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:-1
msgid "Red envelope icon displayed in chatter."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:22
msgid "Unsent emails also appear in the Odoo email queue. In :ref:`developer mode <developer-mode>`, the email queue can be accessed by going to :menuselection:`Settings app --> Technical menu --> Email --> Emails`. Unsent emails appear in turquoise, while sent emails appear in grey."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:27
msgid "Common error messages"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:32
msgid "Daily limit reached"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:-1
msgid "Warning in Odoo upon email limit reached."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:38
msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, or sometimes, per minute. This is the same for Odoo, which limits a customer's sending to prevent Odoo's email servers from being blacklisted."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:42
msgid "Here are the default limits for new databases:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:44
msgid "**200 emails per day** for Odoo Online and Odoo.sh databases with an active subscription."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:45
msgid "**20 emails per day** for one-app free databases."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:46
msgid "**50 emails per day** for trial databases."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:47
msgid "In the case of migration, the daily limit might be reset to 50 emails per day."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:49
msgid "If the daily limit is reached:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:51
msgid "Contact the Odoo support team, who may increase the daily limit depending on the following factors:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:54
msgid "How many users are in the 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 "The bounce rate: the percentage of email addresses that did not receive emails because they were returned by a mail server on its way to the final recipient."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:59
msgid "Use an external outgoing email server to be independent of Odoo's mail limit (refer to the corresponding :doc:`email documentation </applications/general/email_communication/email_servers>`)."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:62
msgid "Wait until 11 PM (UTC) for the daily limit to reset, and retry sending the email. In :ref:`developer mode <developer-mode>`, go to :menuselection:`Settings app --> Technical menu --> Email --> Emails`, then click the :guilabel:`Retry` button next to an unsent email."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:67
msgid "The daily email limit is comprehensive to the database. By default, any internal message, notification, logged note, etc. counts as an email in the daily limit if it notifies someone via email. This can be mitigated by receiving :ref:`notifications in Odoo <discuss_app/notification_preferences>`, instead of emails."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:73
msgid "SMTP error"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:75
msgid "Simple Mail Transport Protocol (SMTP) error messages explain why an email wasn't transmitted successfully. :abbr:`SMTP (Simple Mail Transport Protocol)` is a protocol to describe the email structure, and transmits data from messages over the Internet. The error messages generated by email services are helpful tools to diagnose and troubleshoot email problems."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:81
msgid "This is an example of a 554 SMTP permanent delivery error: `554: delivery error: Sorry, your message to ------@yahoo.com cannot be delivered. This mailbox is disabled (554.30). - mta4471.mail.bf1.yahoo.com --- Below this line is a copy of the message.`"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:85
msgid "The debug menu can be used to investigate SMTP sending issues from a database. To access the menu, :ref:`developer mode <developer-mode>` must be activated. Once activated, navigate to the :menuselection:`Debug Menu` in the top right of the menu bar (the :guilabel:`🐞 (bug)` icon), :menuselection:`Debug Menu --> Manage Messages`"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:90
msgid "The :guilabel:`Manage Messages` menu opens a list of all the messages sent in a particular record. Within each message there is information on sending, including the type, and subtype, of the message."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:94
msgid "Other information includes to whom the message was sent, and whether Odoo received a bounce-back message from an email server."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:-1
msgid "Manage messages menu option on the debug menu."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:102
msgid "A user must be on a view in Odoo that has a chatter in order for the :guilabel:`Manage Messages` menu option to appear."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:106
msgid "No error populated"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:108
msgid "Odoo is not always capable of providing information for the reason it failed. The different email providers implement a personalized policy of bounced emails, and it is not always possible for Odoo to interpret it correctly."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:112
msgid "If this is a recurring problem with the same client, or the same domain, 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:116
msgid "One of the most common reasons for an email failing to send with no error message is related to :ref:`SPF <email_communication/spf_compliant>` and/or :ref:`DKIM <email_communication/DKIM_compliant>` configuration. Also, check to make sure the `mail.bounce.alias` is defined in the *system parameters*. Access system parameters in :ref:`developer mode <developer-mode>` by navigating to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:124
msgid "Email is sent late"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:126
msgid "Email campaigns send at a scheduled time, using a delay pre-programed in the database. Odoo uses a delayed task to send emails that are considered \"not urgent\" (newsletter formats, such as: mass mailing, marketing automation, and events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. Odoo uses that policy in order to avoid cluttering the mail servers and, instead, prioritizes individual communication. This **cron** is called :guilabel:`Mail: Email Queue Manager`, and can be accessed in :ref:`developer mode <developer-mode>` by going to :menuselection:`Settings app --> Technical menu --> Automation --> Scheduled Actions`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:-1
msgid "Email scheduled to be sent later."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:140
msgid "What is a **cron**? A cron is an action that Odoo runs in the background to execute particular code to complete a task."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:144
msgid "By default, the *Mass Mailing cron* runs every 60 minutes. This can be changed to no less than 5 minutes. However, running the action every 5 minutes would bog down the Odoo database (stress the system), so this is not recommended. To edit the mass mailing cron, select the scheduled action :guilabel:`Mail: Email Queue Manager`, and proceed to make any necessary adjustments."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:149
msgid "Emails that are considered urgent (communication from one person to another, such as sales orders, invoices, purchase orders, etc.) are sent immediately."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:153
msgid "Incoming emails"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:155
msgid "When there is an issue with incoming emails, there might not be an indication, per se, in Odoo. It is the sending email client, who tries to contact a database, that will get a bounce-back message (most of the time a :guilabel:`550: mailbox unavailable` error message)."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:160
msgid "Email is not received"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:162
msgid "The steps that should be taken depend on the Odoo platform where the database is hosted."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:164
msgid "**Odoo.sh** users can find their live logs on the folder :file:`~/logs/`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:166
msgid "Logs are a stored collection of all the tasks completed in a database. They are a text-only representation, complete with timestamps of every action taken on the Odoo database. This can be helpful to track emails leaving the database. Failure to send can also be seen by logs that indicate that the message tried to send repeatedly. Logs will show every action to the email servers from the database."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:172
msgid "The folder :file:`~/logs/` (accessed by the command line or on the Odoo.sh dashboard) of an Odoo.sh database contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM (UTC)."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:177
msgid "The two most recent days (today and yesterday) are not compressed, while the older ones are, in order to save space. The naming of the files for today and yesterday are respectively: :file:`odoo.log` and :file:`odoo.log.1`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:181
msgid "For the following days, they are named with their dates, and then compressed. Use the command :command:`grep` and :command:`zgrep` (for the compressed ones) to search through the files."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:185
msgid "For more information on logs and how to access them via the Odoo.sh dashboard, see :ref:`this administration documentation <odoosh/logs>`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:188
msgid "For more information on accessing logs via the command line visit :ref:`this developer documentation <reference/cmdline/server/logging>`."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:191
msgid "**Odoo Online** users won't have access to the logs. However `Odoo Support <https://www.odoo.com/help>`_ can be contacted if there is a recurring issue with the same client or domain."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:196
msgid "Get help from Odoo support"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:198
msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful when reaching out to the Odoo Support team about an issue:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:201
msgid "Send a copy of the email headers. The `.EML` file (or **headers**) of the email is the file format containing all the technical information required for an investigation. The documentation from the email provider might explain how to access the EML file/header files. Once the headers of the email are obtained, adding it into the Odoo Support ticket is the most efficient way for the Odoo Support team to investigate."
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:208
msgid "`Gmail documentation on headers <https://support.google.com/mail/answer/29436>`_"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:209
msgid "`Outlook documentation on headers <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:212
msgid "Explain the exact flow that is being followed 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:215
msgid "Is this a notification message from a reply being received in Odoo?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:216
msgid "Is this a message being sent from the Odoo database?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:217
msgid "Is there an incoming email server being used, or is the email somehow being redirected?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:218
msgid "Is there an example of an email that has been correctly forwarded?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:220
msgid "Provide answers to the following questions:"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:222
msgid "Is it a generic issue, or is it specific to a use case? If specific to a use case, which one exactly?"
msgstr ""
#: ../../content/applications/general/email_communication/faq.rst:224
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/email_communication/faq.rst:228
msgid "The bounce system parameter needs to be set in the technical settings in order for the database to correctly receive bounce messages. To access this setting, go to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`. Then select the parameter name :guilabel:`mail.bounce.alias` and set the value to `bounce` if it isn't already set."
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:-1
msgid "view of the different things to enable/click to export data"
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:-1
msgid "overview of all the options to take into account when exporting data in Odoo"
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/geolocation.rst:3
msgid "Geolocation"
msgstr ""
#: ../../content/applications/general/geolocation.rst:5
msgid "You can locate contacts or places and generate routes on a map in Odoo."
msgstr ""
#: ../../content/applications/general/geolocation.rst:-1
msgid "Map displaying a contact's location."
msgstr ""
#: ../../content/applications/general/geolocation.rst:10
msgid "To use the feature, open the :guilabel:`Settings` app, and, under the :guilabel:`Integrations`, section, activate :guilabel:`Geo Localization`. Then, choose between using the OpenStreetMap or Google Places API."
msgstr ""
#: ../../content/applications/general/geolocation.rst:14
msgid "**OpenStreetMap**"
msgstr ""
#: ../../content/applications/general/geolocation.rst:16
msgid "OpenStreetMap is a free, open geographic database updated and maintained by volunteers. To use it, select :guilabel:`Open Street Map`."
msgstr ""
#: ../../content/applications/general/geolocation.rst:20
msgid "OpenStreetMap might not always be accurate. You can `join the OpenStreetMap community <https://www.openstreetmap.org/fixthemap>`_ to fix any issues encountered."
msgstr ""
#: ../../content/applications/general/geolocation.rst:23
msgid "**Google Places API map**"
msgstr ""
#: ../../content/applications/general/geolocation.rst:25
msgid "The Google Places API map provides detailed info on places, businesses, and points of interest. It supports location-based features like search, navigation, and recommendations."
msgstr ""
#: ../../content/applications/general/geolocation.rst:29
msgid "Using the Google Places API could require `payment to Google <https://mapsplatform.google.com/pricing/>`_."
msgstr ""
#: ../../content/applications/general/geolocation.rst:32
msgid "To use it, select :guilabel:`Google Place Map` and enter your API :guilabel:`Key`"
msgstr ""
#: ../../content/applications/general/geolocation.rst:-1
msgid "Google Places API key"
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 your 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 your current balance or to recharge your account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:19
msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free credits to test our IAP features."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst: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. 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 "An IAP account can be disabled by appending `+disabled` to its token. Reverting this change will re-enable the account."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:38
msgid "IAP Portal"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:40
msgid "The IAP Portal is a platform regrouping your IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, you can view your current balance, recharge your credits and set a reminder when your balance falls below a threshold."
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:48
msgid "Get notified when credits are low"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:50
msgid "To be notified when it’s time to recharge your credits, you can go to your IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and check the Receive threshold warning option. Then, you can provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent by email!"
msgstr ""
#: ../../content/applications/general/users.rst:5
msgid "Users and companies"
msgstr ""
#: ../../content/applications/general/users.rst:7
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:-1
msgid "View of a group’s form emphasizing the tab users in Odoo"
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:-1
msgid "View of a group’s form emphasizing the tab inherited in Odoo"
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:-1
msgid "View of a group’s form emphasizing the tab menus in Odoo"
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:-1
msgid "View of a group’s form emphasizing the tab access rights in Odoo"
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:-1
msgid "View of a group’s form emphasizing the tab record rules in Odoo"
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:-1
msgid "Overview of a new company's form in Odoo"
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:0
msgid "View of a web browser and the favicon for a specific company chosen in Odoo"
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:-1
msgid "View of the companies menu through the main dashboard in Odoo"
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:-1
msgid "View of a product's form emphasizing the company field in Odoo Sales"
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:-1
msgid "View of an user form emphasizing the multi companies field under the access rights tabs\n"
"in Odoo"
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:-1
msgid "View of the settings page emphasizing the document layout field in Odoo"
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/get_started/chart_of_accounts>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:88
msgid ":doc:`Taxes <../../finance/accounting/taxes>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:89
msgid ":doc:`Fiscal Positions <../../finance/accounting/taxes/fiscal_positions>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:90
msgid ":doc:`Journals <../../finance/accounting/bank>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:91
msgid ":doc:`Fiscal Localizations <../../finance/fiscal_localizations>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:92
msgid ":doc:`Pricelists <../../sales/sales/products_prices/prices/pricing>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:94
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:-1
msgid "View of the settings page emphasizing the inter company transaction field in Odoo"
msgstr ""
#: ../../content/applications/general/users/companies.rst:102
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:105
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:-1
msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo"
msgstr ""
#: ../../content/applications/general/users/companies.rst:112
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:116
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:-1
msgid "View of the purchase created on JS Store US from JS Store Belgium in Odoo"
msgstr ""
#: ../../content/applications/general/users/companies.rst:125
msgid "Products have to be configured as *Can be sold* and must be shared between the companies."
msgstr ""
#: ../../content/applications/general/users/companies.rst:128
msgid "Remember to test all workflows as an user other than the administrator."
msgstr ""
#: ../../content/applications/general/users/companies.rst:131
msgid ":doc:`Multi-company Guidelines </developer/howtos/company>`"
msgstr ""
#: ../../content/applications/general/users/companies.rst:132
msgid ":doc:`../../finance/accounting/get_started/multi_currency`"
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/configuration/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:-1
msgid "View of the settings page emphasizing the manage users field in Odoo"
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:-1
msgid "View of a user’s form emphasizing the access rights tab in Odoo"
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:-1
msgid "View of a user’s form with a notification that the invitation email has been sent in Odoo"
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:-1
msgid "View of a user’s form in developer mode emphasizing the user type field in Odoo"
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:-1
msgid "Enabling Password Reset in Odoo Settings"
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:-1
msgid "Example of an email with a password reset link for an Odoo account"
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:-1
msgid "Change another user's password on Odoo"
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:-1
msgid "View of a user’s form emphasizing the multi companies field in Odoo"
msgstr ""
#: ../../content/applications/general/users/manage_users.rst:152
msgid ":doc:`companies`"
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:3
msgid "Odoo.com account changes"
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:5
msgid "This documentation is dedicated to edits made to an Odoo.com account. The following processes describe how to delete an Odoo.com account, and how to change the password on an Odoo.com account."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:9
msgid "Delete Odoo.com account"
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:11
msgid "To delete an Odoo.com account, start by clicking the profile icon in the upper-right corner (represented by the username and icon) to reveal a drop-down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, which reveals the user portal."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:15
msgid "From the user portal, the delete option can be accessed by going to :menuselection:`My Account --> Edit Security Settings --> Delete Account`. It can also be accessed by going to `https://www.odoo.com/my/home <https://www.odoo.com/my/home>`_."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:20
msgid "Deleting an Odoo account is irreversible. Be careful performing this action, as the Odoo.com account is **not** retrievable once deleted."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:23
msgid "Upon clicking the :guilabel:`Delete Account` button, a pop-up window appears, requesting confirmation for the account deletion."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:-1
msgid "Clicking on the Delete Account button will populate a window verifying the change."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:30
msgid "To confirm the deletion, enter the :guilabel:`Password` and the :guilabel:`Login` for the account being deleted. Then, click the :guilabel:`Delete Account` button to confirm the deletion."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:34
msgid "Odoo.com account password change"
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:36
msgid "To change an Odoo.com account password, first login into the Odoo.com user account from the Odoo.com login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon next to the profile icon. Then, select :guilabel:`My Account`, and a portal dashboard appears."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:41
msgid "To change the Odoo.com password, click on the :guilabel:`Edit Security Settings` link, below the :menuselection:`Account Security` section. Next, make the necessary changes by typing in the current :guilabel:`Password`, :guilabel:`New Password`, and verify the new password. Lastly, click on :guilabel:`Change Password` to complete the password change."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:47
msgid "If a customer would like to change the login, contact Odoo support `here <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:51
msgid "Passwords for Odoo.com users and portal users remain separate, even if the same email address is used."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:55
#: ../../content/applications/general/users/portal.rst:143
msgid "Add two-factor authentication"
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:57
msgid "To add two-factor authentication, login into the Odoo.com user account from the Odoo.com login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon next to the :guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal dashboard appears."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:62
msgid "If the user would like to turn on two-factor authentication (2FA) for Odoo.com access, click on the :guilabel:`Edit Security Settings` link below the :menuselection:`Account Security` section."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:65
msgid "Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA (two-factor authentication)`. Then, confirm the current password in the :guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. Following that, activate :abbr:`2FA (two-factor authentication)` in a :abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, etc.), by scanning the :guilabel:`QR code` or entering a :guilabel:`Verification Code`."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:71
msgid "Finally, click on :guilabel:`Enable two-factor authentication` to complete the setup."
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:74
msgid "Under :guilabel:`My Account` Odoo.com users can also access the following:"
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:76
msgid ":guilabel:`My Partner dashboard`"
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:77
msgid ":guilabel:`My In-App Services`"
msgstr ""
#: ../../content/applications/general/users/odoo_account.rst:78
msgid ":guilabel:`My Apps Dashboard`"
msgstr ""
#: ../../content/applications/general/users/portal.rst:3
msgid "Portal access"
msgstr ""
#: ../../content/applications/general/users/portal.rst:7
msgid "Portal access is given to users who need the ability to view certain documents or information within an Odoo database."
msgstr ""
#: ../../content/applications/general/users/portal.rst:10
msgid "Some common use cases for providing portal access include allowing customers to read/view any or all of the following in Odoo:"
msgstr ""
#: ../../content/applications/general/users/portal.rst:13
msgid "leads/opportunities"
msgstr ""
#: ../../content/applications/general/users/portal.rst:14
msgid "quotations/sales orders"
msgstr ""
#: ../../content/applications/general/users/portal.rst:15
msgid "purchase orders"
msgstr ""
#: ../../content/applications/general/users/portal.rst:16
msgid "invoices & bills"
msgstr ""
#: ../../content/applications/general/users/portal.rst:17
msgid "projects"
msgstr ""
#: ../../content/applications/general/users/portal.rst:18
msgid "tasks"
msgstr ""
#: ../../content/applications/general/users/portal.rst:19
msgid "timesheets"
msgstr ""
#: ../../content/applications/general/users/portal.rst:20
msgid "tickets"
msgstr ""
#: ../../content/applications/general/users/portal.rst:21
msgid "signatures"
msgstr ""
#: ../../content/applications/general/users/portal.rst:22
msgid "subscriptions"
msgstr ""
#: ../../content/applications/general/users/portal.rst:25
msgid "Portal users only have read/view access, and will not be able to edit any documents in the database."
msgstr ""
#: ../../content/applications/general/users/portal.rst:29
msgid "Provide portal access to customers"
msgstr ""
#: ../../content/applications/general/users/portal.rst:31
msgid "From the main Odoo dashboard, select the :guilabel:`Contacts` application. If the contact is not yet created in the database, click on the :guilabel:`Create` button, enter the details of the contact, and then click :guilabel:`Save`. Otherwise, choose an existing contact, and then click on the :guilabel:`Action` drop-down menu located at the top-center of the interface."
msgstr ""
#: ../../content/applications/general/users/portal.rst:-1
msgid "Use the Contacts application to give portal access to users."
msgstr ""
#: ../../content/applications/general/users/portal.rst:40
msgid "Then select :guilabel:`Grant portal access`. A pop-up window appears, listing three fields:"
msgstr ""
#: ../../content/applications/general/users/portal.rst:42
msgid ":guilabel:`Contact`: the recorded name of the contact in the Odoo database"
msgstr ""
#: ../../content/applications/general/users/portal.rst:43
msgid ":guilabel:`Email`: the contact's email address that they will use to log into the portal"
msgstr ""
#: ../../content/applications/general/users/portal.rst:44
msgid ":guilabel:`In Portal`: whether or not the user has portal access"
msgstr ""
#: ../../content/applications/general/users/portal.rst:46
msgid "To grant portal access, first enter the contact's :guilabel:`Email` they will use to log into the portal. Then, check the box under the :guilabel:`In Portal` column. Optionally, add text to the invitation message the contact will receive. Then click :guilabel:`Apply` to finish."
msgstr ""
#: ../../content/applications/general/users/portal.rst:-1
msgid "An email address and corresponding checkbox for the contact need to be filled in before\n"
"sending a portal invitation."
msgstr ""
#: ../../content/applications/general/users/portal.rst:55
msgid "An email will be sent to the specified email address, indicating that the contact is now a portal user for that Odoo database."
msgstr ""
#: ../../content/applications/general/users/portal.rst:59
msgid "To grant portal access to multiple users at once, navigate to a company contact, then click :menuselection:`Action --> Grant portal access` to view a list of all of the company's related contacts. Check the box under the :guilabel:`In Portal` column for all the contacts that need portal access, then click :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/general/users/portal.rst:65
msgid "At any time, portal access can be revoked by navigating to the contact, clicking :menuselection:`Action --> Grant portal access`, and then unselecting the checkbox under the :guilabel:`In Portal` column and clicking :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/general/users/portal.rst:72
msgid "Change portal username"
msgstr ""
#: ../../content/applications/general/users/portal.rst:74
msgid "There may be times when a portal user wants to change their user login. This can be done by any user in the database with administrator access rights. The following process outlines the necessary steps to change the portal user login."
msgstr ""
#: ../../content/applications/general/users/portal.rst:79
msgid ":doc:`See the documentation on setting access rights </applications/general/users/access_rights>`."
msgstr ""
#: ../../content/applications/general/users/portal.rst:82
msgid "First, navigate to :menuselection:`Settings app --> Users`. Then, under :guilabel:`Filters`, select :guilabel:`Portal Users`, or select :guilabel:`Add Custom Filter` and set the following configuration :guilabel:`Groups` > :guilabel:`contains` > `portal`. After making this selection, search for (and open) the portal user that needs to be edited."
msgstr ""
#: ../../content/applications/general/users/portal.rst:87
msgid "Next, click :guilabel:`Edit` (if necessary), click into the :guilabel:`Email Address` field, and proceed to make any necessary changes to this field. The :guilabel:`Email Address` field is used to log into the Odoo portal."
msgstr ""
#: ../../content/applications/general/users/portal.rst:92
msgid "Changing the :guilabel:`Email Address` (or login) only changes the *username* on the customer's portal login."
msgstr ""
#: ../../content/applications/general/users/portal.rst:95
msgid "In order to change the contact email, this change needs to take place on the contact template in the *Contacts* app. Alternatively, the customer can change their email directly from the portal, but the login **cannot** be changed. :ref:`See change customer info <portal/custinfo>`."
msgstr ""
#: ../../content/applications/general/users/portal.rst:100
msgid "Customer portal changes"
msgstr ""
#: ../../content/applications/general/users/portal.rst:102
msgid "There may be times when the customer would like to make changes to their contact information, password/security, or payment information attached to the portal account. This can be performed by the customer from their portal. The following process is how a customer can change their contact information."
msgstr ""
#: ../../content/applications/general/users/portal.rst:110
msgid "Change customer info"
msgstr ""
#: ../../content/applications/general/users/portal.rst:112
msgid "First enter the username and password (login) into the database login page to access the portal user account. A portal dashboard will appear upon successfully logging in. Portal documents from the various installed Odoo applications will appear with the number count of each."
msgstr ""
#: ../../content/applications/general/users/portal.rst:117
msgid ":ref:`Portal access documentation <portal/main>`."
msgstr ""
#: ../../content/applications/general/users/portal.rst:119
msgid "Next, navigate to the upper-right corner of the portal, and click the :guilabel:`Edit` button, next to the :guilabel:`Details` section. Then, change the pertinent information, and click :guilabel:`Confirm`."
msgstr ""
#: ../../content/applications/general/users/portal.rst:124
msgid "Change password"
msgstr ""
#: ../../content/applications/general/users/portal.rst:126
#: ../../content/applications/general/users/portal.rst:145
#: ../../content/applications/general/users/portal.rst:162
msgid "First enter the username and password (login) into the database login page to access the portal user account. A portal dashboard will appear upon successfully logging in."
msgstr ""
#: ../../content/applications/general/users/portal.rst:129
msgid "If the customer would like to change their password for portal access, click on the :guilabel:`Edit Security Settings` link, below the :guilabel:`Account Security` section. Then, make the necessary changes, by typing in the current :guilabel:`Password`, :guilabel:`New Password`, and verify the new password. Lastly, click on :guilabel:`Change Password` to complete the password change."
msgstr ""
#: ../../content/applications/general/users/portal.rst:135
msgid "If a customer would like to change the login, as documented above, contact the Odoo database point-of-contact. :ref:`See above documentation on changing the portal username <portal/login>`."
msgstr ""
#: ../../content/applications/general/users/portal.rst:139
msgid "Passwords for portal users and Odoo.com users remain separate, even if the same email address is used."
msgstr ""
#: ../../content/applications/general/users/portal.rst:148
msgid "If the customer would like to turn on two-factor authentication (2FA) for portal access, click on the :guilabel:`Edit Security Settings` link, below the :guilabel:`Account Security` section."
msgstr ""
#: ../../content/applications/general/users/portal.rst:151
msgid "Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA (two-factor authentication)`. Confirm the current portal password in the :guilabel:`Password` field. Then, click on :guilabel:`Confirm Password`. Next, activate :abbr:`2FA (two-factor authentication)` in a :abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, etc.), by scanning the :guilabel:`QR code` or entering a :guilabel:`Verification Code`."
msgstr ""
#: ../../content/applications/general/users/portal.rst:157
msgid "Finally, click :guilabel:`Enable two-factor authentication` to complete the setup."
msgstr ""
#: ../../content/applications/general/users/portal.rst:160
msgid "Change payment info"
msgstr ""
#: ../../content/applications/general/users/portal.rst:165
msgid "If the customer would like to manage payment options, navigate to the :guilabel:`Manage payment methods` in the menu on the right. Then, add the new payment information, and select :guilabel:`Add new card`."
msgstr ""
#: ../../content/applications/general/voip.rst:7
msgid "VoIP (Voice over Internet Protocol)"
msgstr ""
#: ../../content/applications/general/voip.rst:10
msgid "For more information, reference the `Odoo eLearning (video tutorials) on VoIP <https://www.odoo.com/slides/voip-voice-over-ip-315>`_"
msgstr ""
#: ../../content/applications/general/voip/axivox.rst:5
msgid "Axivox configuration"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:3
msgid "VoIP services in Odoo with Axivox"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:6
#: ../../content/applications/general/voip/onsip.rst:6
msgid "Introduction"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:8
msgid "Odoo VoIP (Voice over Internet Protocol) can be set up to work together with `Axivox <https://www.axivox.com/>`_. In that case, an Asterisk server is **not** necessary, as the infrastructure is hosted and managed by Axivox."
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.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 the company's area, along with the areas the company's users wish to call."
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:19
msgid "To configure Axivox in Odoo, go to the :menuselection:`Apps` application, and search for `VoIP`. Then, install the :guilabel:`VoIP` module."
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:22
msgid "Next, go to :menuselection:`Settings app --> General Settings --> Integrations section`, and fill out the :guilabel:`Asterisk (VoIP)` field:"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:25
msgid ":guilabel:`OnSIP Domain`: set the domain created by Axivox for the account (e.g., `yourcompany.axivox.com`)"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:27
msgid ":guilabel:`WebSocket`: type in `wss://pabx.axivox.com:3443`"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:28
msgid ":guilabel:`VoIP Environment`: set as :guilabel:`Production`"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:-1
msgid "Integration of Axivox as VoIP provider in an Odoo database."
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:35
msgid "Access the domain on the Axivox administrative panel by navigating to `https://manage.axivox.com/ <https://manage.axivox.com/>`_. After logging into the portal, go to :menuselection:`Users --> Edit (next to any user) --> SIP Identifiers tab --> Domain`."
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:40
msgid "Configure VoIP user in Odoo"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:42
msgid "Next, the user is configured in Odoo, which **must** take place for every Axivox/Odoo user using VoIP."
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:45
msgid "In Odoo, go to :menuselection:`Settings app --> Users & Companies --> Users`, then open the desired user's form to configure :abbr:`VoIP (Voice over Internet Protocol)`. Under the :guilabel:`Preferences` tab, fill out the :guilabel:`VOIP Configuration` section:"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:49
msgid ":guilabel:`SIP Login` / :guilabel:`Browser's Extension`: (Axivox) :guilabel:`SIP username`"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:50
msgid ":guilabel:`Handset Extension`: SIP external phone extension"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:51
msgid ":guilabel:`SIP Password`: (Axivox) :guilabel:`SIP Password`"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:52
msgid ":guilabel:`Mobile call`: method to make calls on a mobile device"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:53
msgid ":guilabel:`OnSIP authorization User`: (Axivox) :guilabel:`SIP username`"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:54
msgid ":guilabel:`Always Redirect to Handset`: option to always transfer phone calls to handset"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:55
msgid ":guilabel:`Reject All Incoming Calls`: option to reject all incoming calls"
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:-1
msgid "Integration of Axivox user in the Odoo user preference."
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:62
msgid "Access the domain on the Axivox administrative panel by navigating to `https://manage.axivox.com/ <https://manage.axivox.com/>`_. After logging into the portal, go to :menuselection:`Users --> Edit (next to the user) --> SIP Identifiers tab --> SIP username / SIP password`."
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:0
msgid "SIP credentials in the Axivox manager."
msgstr ""
#: ../../content/applications/general/voip/axivox/axivox_config.rst:71
msgid "When entering the :guilabel:`SIP Password` into the user's :guilabel:`Preferences` tab, this value **must** be typed out manually and **not** pasted in. Pasting in causes a `401 server rejection error`."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:3
msgid "Call queues"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:5
msgid "A call queue is a system that organizes and routes incoming calls. When customers call a business, and all of the agents are busy, the call queue lines up the callers in sequential order, based on the time they called in."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:9
msgid "The callers then wait on hold to be connected to the next available call center agent."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:11
msgid "Implementing a call queue system reduces stress for employees, and helps build brand trust with customers. Many companies use call queues to set expectations with customers, and to distribute the workload equally amongst employees."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:15
msgid "This document covers the process required to configure call queues (with advanced settings), as well as how to log into a call queue from the Odoo database."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:19
msgid ":ref:`voip/axivox/music_on_hold`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:22
msgid "Add a queue"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:24
msgid "To add a call queue in Axivox, navigate to the `Axivox management console <https://manage.axivox.com>`_. In the left menu, click :guilabel:`Queues`. Next, click :guilabel:`Add a queue`. Doing so reveals a blank :guilabel:`New queue` form with various fields to fill out."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:30
msgid "Name"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:32
msgid "Once the :guilabel:`New queue` page appears, enter the :guilabel:`Name` of the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:35
msgid "Internal extension"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:37
msgid "Choose an :guilabel:`Internal extension` for the queue. This is a number to be dialed by users of the database to reach the login prompt for the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:41
msgid "Strategy"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:43
msgid "Next, is the :guilabel:`Strategy` field. This field determines the call routing of received calls into this queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:46
msgid "The following choices are available in the :guilabel:`Strategy` drop-down menu:"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:48
msgid ":guilabel:`Call all available agents`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:49
msgid ":guilabel:`Calls the agent who has received the call for the longest time`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:50
msgid ":guilabel:`Calls the agent who has received the least call`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:51
msgid ":guilabel:`Call a random agent`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:52
msgid ":guilabel:`Call agents one after the other`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:53
msgid ":guilabel:`Call agents one after the other starting with the first in the list`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:55
msgid "Choose a strategy that best meets the company's needs for customers in the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:58
msgid "Maximum waiting time in seconds"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:60
msgid "In the :guilabel:`Maximum waiting time in seconds` field, determine the longest time a customer waits in the queue before going to a voicemail, or wherever else they are directed to in a dial plan. Enter a time in seconds."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:65
msgid "Maximum duration of ringing at an agent"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:67
msgid "In the :guilabel:`Maximum duration of ringing at an agent` field, determine the longest time an individual agent's line rings before moving on to another agent, or moving to the next step in the dial plan. Enter a time in seconds."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:72
msgid "For more information on dial plans, visit:"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:74
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:36
msgid ":doc:`dial_plan_basics`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:75
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:37
msgid ":doc:`dial_plan_advanced`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:78
msgid "Adding agents"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:80
msgid "The final two fields on the :guilabel:`New queue` form revolve around adding agents. Adding :guilabel:`Static agents` and :guilabel:`Dynamic agents` are two pre-configured methods for adding agents onto the call queue during the configuration."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:87
msgid "Static agents"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:89
msgid "When :guilabel:`Static agents` are added, these agents are automatically added to the queue without the need to log in to receive calls."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:95
msgid "Dynamic agents"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:97
msgid "When :guilabel:`Dynamic agents` are added, these agents have the ability to log into this queue. They are **not** logged-in automatically, and **must** log in to receive calls."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:100
msgid "Be sure to :guilabel:`Save` the changes, and click :guilabel:`Apply changes` in the upper-right corner to implement the change in production."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:104
msgid "Agent connection"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:106
msgid "There are three ways call agents can connect to an Axivox call queue:"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:108
msgid "Dynamic agents connect automatically."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:109
msgid "Manager logs in specific agent(s), via the `Axivox management console <https://manage.axivox.com>`_."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:111
msgid "Agent connects to the queue in Odoo, via the *VoIP* widget."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:114
msgid "See the documentation on setting :ref:`voip/axivox/dynamic-agents` in the `Axivox management console <https://manage.axivox.com>`_."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:118
msgid "Connect via Axivox queue"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:120
msgid "After the initial configuration of the call queue is completed, with the changes saved and implemented, a manager can log into the `Axivox management console <https://manage.axivox.com>`_ and connect dynamic agents to the queue manually."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:124
msgid "To connect an agent, click :guilabel:`Queues`, located in the left-hand column. Doing so reveals the :guilabel:`Queues` dashboard, with a few different columns listed:"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:127
msgid ":guilabel:`Name`: name of the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:128
msgid ":guilabel:`Extension`: number of the extension to be dialed to reach the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:129
msgid ":guilabel:`Agent Connection`: number to dial to log into the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:130
msgid ":guilabel:`Agent disconnection`: number to dial to log out of the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:131
msgid ":guilabel:`Connected Agents`: name of agent connected to the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:133
msgid "The following buttons are also available on the :guilabel:`Queues` dashboard:"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:135
msgid ":guilabel:`Connect an agent`: manually connect an agent to the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:136
msgid ":guilabel:`Report`: run a report on the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:137
msgid ":guilabel:`Delete`: delete the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:138
msgid ":guilabel:`Edit`: make changes to the settings of the queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:140
msgid "When agents are connected to the queue, or are live with a customer, they are displayed under the :guilabel:`Connected Agents` column."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:143
msgid "If they are static agents, they **always** show up as connected."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:145
msgid "Connect an agent by clicking the orange button labeled, :guilabel:`Connect an agent`. Then, select the desired agent's name from the drop-down menu, and click :guilabel:`Connect`."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:-1
msgid "Call queue with connected agents column highlighted and connect an agent and report buttons\n"
"highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:154
msgid "For more information on static and dynamic agents, see this documentation:"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:156
msgid ":ref:`voip/axivox/static-agents`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:157
msgid ":ref:`voip/axivox/dynamic-agents`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:160
msgid "Report"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:162
msgid "Click :guilabel:`Report` to check on the reporting for a particular queue, in order to see who connected when, and what phone calls came in and out of the queue. This information is showcased on a separate :guilabel:`Queue report` page, when the green :guilabel:`Report` button is clicked."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:166
msgid "Reports can be customized by date in the :guilabel:`Period` field, and specified in the :guilabel:`From` and :guilabel:`to` fields. The information can be organized by :guilabel:`Event type`, and :guilabel:`Call ID`."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:170
msgid "When the custom configurations have been entered, click :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:172
msgid "Each report can be exported to a :abbr:`CSV (comma separated value)` file for further use and analysis, via the :guilabel:`Export to CSV` button."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:175
msgid "When the :guilabel:`Event type` field is clicked, a drop-down menu appears with the following options:"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:178
msgid ":guilabel:`The caller quit`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:179
msgid ":guilabel:`An agent is connecting`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:180
msgid ":guilabel:`An agent is disconnecting`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:181
msgid ":guilabel:`The call was terminated (agent hangs up)`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:182
msgid ":guilabel:`The call was terminated (caller hangs up)`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:183
msgid ":guilabel:`The caller is connected to an agent.`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:184
msgid ":guilabel:`Someone is entering the queue`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:185
msgid ":guilabel:`The caller exits the queue (no agent is connected)`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:186
msgid ":guilabel:`The caller exits the queue (timeout)`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:187
msgid ":guilabel:`No one is answering`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:188
msgid ":guilabel:`No one is answering, the caller hangs up`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:189
msgid ":guilabel:`Transfer`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:190
msgid ":guilabel:`Blind Transfer`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:-1
msgid "Event types in the Axivox queue reporting feature."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:196
msgid "There is no limit to how many options can be selected from the :guilabel:`Event type` drop-down menu."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:199
msgid "Clicking :guilabel:`Check all` selects all the available options from the drop-down menu, and clicking :guilabel:`Uncheck all` removes all selections from the drop-down menu."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:202
msgid "To select an individual :guilabel:`Event type`, click on the desired option in the drop-down menu."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:-1
msgid "Axivox queue report with result, event type, and period highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:209
msgid "Connect to queue on Odoo"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:211
msgid "Dynamic agents can connect manually to the Axivox call queue from the Odoo *VoIP* widget, once the *VoIP* app is configured for the individual user in Odoo."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:215
msgid ":doc:`axivox_config`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:217
msgid "To access the Odoo *VoIP* widget, click the :guilabel:`📞 (phone)` icon in the upper-right corner of the screen, from any window within Odoo."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:221
msgid "For more information on the Odoo *VoIP* widget, see this documentation: :doc:`../voip_widget`"
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:223
msgid "For an agent to connect to the call queue, simply dial the :guilabel:`Agent connection` number, and press the green call button :guilabel:`📞 (phone)` icon in the *VoIP* widget. Then, the agent hears a short, two-second message indicating the agent is logged in. The call automatically ends (disconnects)."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:228
msgid "To view the connected agents in a call queue, navigate to the `Axivox management console <https://manage.axivox.com>`_, and click :guilabel:`Queues`, located in the left-hand column."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:231
msgid "Then, click the green :guilabel:`Refresh` button at the top of the :guilabel:`Connected agents` column. Any agent (static or dynamic) that is connected to the queue currently, appears in the column next to the queue they are logged into."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:235
msgid "To log out of the queue, open the Odoo *VoIP* widget, dial the :guilabel:`Agent disconnection` number, and press the green call button :guilabel:`📞 (phone)` icon. The agent is disconnected from the queue after a short, two-second message."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:239
msgid "To manually log a dynamic agent out of a call queue, navigate to the `Axivox management console <https://manage.axivox.com>`_, and click :guilabel:`Queues`, located in the left-hand column. Then, click the green :guilabel:`Refresh` button at the top of the :guilabel:`Connected agents` column."
msgstr ""
#: ../../content/applications/general/voip/axivox/call_queues.rst:243
msgid "To disconnect an agent manually, click the red :guilabel:`Disconnect` button, and they are immediately disconnected. This can be helpful in situations where agents forget to log out at the end of the day."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:3
msgid "Conference calls"
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:5
msgid "Conference calls help employees connect quickly and efficiently, so matters can be discussed in an open forum of sorts. Attendees can be limited, via a sign-in code. That way, confidential matters stay private."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:9
msgid "This document covers the configuration of conference calls in Axivox for use in Odoo *VoIP*."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:12
msgid "Add a virtual conference"
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:14
msgid "To add a virtual conference room, navigate to the `Axivox management console <https://manage.axivox.com>`_. After logging in, click on :guilabel:`Conferences` in the menu on the left."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:18
msgid "Next, click the green button labeled, :guilabel:`Add a conference`, and a :guilabel:`New conference` form appears."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:-1
msgid "New conference form on Axivox."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:25
msgid "From here, fill in the :guilabel:`Name` field, and set an :guilabel:`Internal extension`."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:27
msgid "The internal extension is what everyone in the network uses to quickly dial into the conference call, instead of typing in the whole phone number."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:31
msgid "Pick a number between three and five digits long, making it easy to remember and dial."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:33
msgid "Next, set the :guilabel:`Access code`, if the conference room requires security. This is a password to get into the conference, once the extension for the conference is dialed. Immediately after dialing the extension, a digital receptionist prompts for the :guilabel:`Access code`."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:37
msgid "In the :guilabel:`Administrator extension` field, click the drop-down menu, and select the user's extension that manages the call."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:40
msgid "Finally, in the :guilabel:`Wait for the administrator to start the conference` field, click the drop-down menu, and select :guilabel:`Yes` or :guilabel:`No`."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:43
msgid "Should the selection be :guilabel:`Yes`, then nobody is allowed to utilize the virtual conference room until the administrator is present, and logged into the conference call."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:46
msgid "When all fields are filled in, be sure to :guilabel:`Save` the configuration. Then, click :guilabel:`Apply changes` in the upper-right corner to implement the change in production."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:49
msgid "Upon doing so, the conference is added, and the Axivox administrator has the option to :guilabel:`Delete` or :guilabel:`Edit` the conference from the Axivox :guilabel:`Conference` main dashboard."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:53
msgid "To invite an Axivox user to a specific conference call, click :guilabel:`Invite` to the right of the desired conference, and proceed to enter the extension or phone number of the invitee in the pop-up window that appears."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:57
msgid "Once the extension or number is added into the :guilabel:`Please enter the phone number of the person you want to invite` field, click the green :guilabel:`Invite` button, and the recipient immediately receives a phone call, automatically linking them to the conference."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:66
#: ../../content/applications/general/voip/axivox/manage_users.rst:32
msgid "Incoming numbers"
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:68
msgid "To open a conference to a wider audience, an Axivox conference can be linked to *Incoming numbers*."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:70
msgid "To do that, log into the `Axivox management console <https://manage.axivox.com>`_, and click :guilabel:`Incoming numbers` in the menu on the left."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:73
msgid "On the :guilabel:`Incoming numbers` dashboard, click :guilabel:`Edit` to the far-right of the :guilabel:`Number` to which the conference should be attached."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:76
msgid "Then, under the first field, labeled, :guilabel:`Destination type for voice call`, click the drop-down menu, and select :guilabel:`Conference`."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:79
msgid "Next, in the :guilabel:`Conference` field, click the drop-down menu, and select the specific conference that should be attached to this incoming number."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:82
msgid "Now, whenever this incoming number is dialed, the caller is let into the conference, if there is not an :guilabel:`Access code` required. If there *is* an :guilabel:`Access code` required, the caller is then prompted to enter the :guilabel:`Access code` to enter the conference."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:87
msgid "Start call in Odoo"
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:89
msgid "Anywhere in the Odoo database, open the *VoIP* widget, by clicking the :guilabel:`📞 (phone)` icon, located in the upper-right corner. Then, dial the specific extension number for the conference, and click the :guilabel:`📞 (phone)` icon."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:-1
msgid "Connecting to a conference extension using the Odoo VoIP widget."
msgstr ""
#: ../../content/applications/general/voip/axivox/conference_calls.rst:97
msgid "Once the digital receptionist answers, enter the :guilabel:`Access code` (if needed), and press the :guilabel:`# (pound)` icon/key."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:3
msgid "Advanced dial plans"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:5
msgid "Typically, companies have a lot of incoming calls every day, but many do not want their teams to answer calls 24 hours a day, 7 days a week."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:8
msgid "By using Axivox advanced dial plan features, the process can be automated, and routing can be set up for all scenarios. This way, customers are never left waiting, or frustrated, because they cannot get in touch with anyone."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:12
msgid "By utilizing the advanced elements in dial plans, companies can automate call routing for certain days or times, like company holidays. Companies can also allow callers to enter extensions themselves, and get transferred automatically using a digital receptionist. This way, an administrative team does **not** have to be available around the clock."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:17
msgid "There is even the option to route callers, depending on where they are calling from in the world, thus maximizing efficiency."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:21
msgid "For more information on basic dial plans, and how to add elements, visit :doc:`dial_plan_basics`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:24
msgid "Using a browser add-on for spelling may hinder the use of the visual editor in dial plans. Do **not** use a translator with the Axivox management console."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:28
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:160
msgid "Advanced elements"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:30
msgid "In Axivox dial plans (as described in :doc:`dial_plan_basics`), there are two advanced elements that can be used."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:33
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:164
msgid ":guilabel:`Record`: recording feature is enabled (requires plan change, enabled in Axivox settings)."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:35
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:166
msgid ":guilabel:`Caller ID`: replace the caller ID by the called number or free text."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:37
msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console <https://manage.axivox.com>`_."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:40
msgid "Next, click on the :guilabel:`Visual Editor` button to the right of the desired dial plan to edit it. Finally, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1
msgid "Visual editor for a dial plan in Axivox, with Add and the dispatcher element highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:48
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:99
msgid "For more information, visit :ref:`voip/axivox/dial_plans`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:51
msgid "The :guilabel:`Record` element records calls that are routed through this element, and requires an additional plan change in Axivox."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:54
msgid "To enable recording on Axivox, navigate to :guilabel:`Settings` in the `Axivox management console <https://manage.axivox.com>`_. Then, go to the :guilabel:`Recording` drop-down menu, near the bottom of the page. From there, select :guilabel:`Enabled` from the drop-down menu to enable recording using the :guilabel:`Record` element in a dial plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:60
msgid "If the :guilabel:`Recording` drop-down menu is unavailable and unable to change, then consult Axivox to enable the feature."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:63
msgid "The :guilabel:`Caller ID` element allows for the replacement of the caller ID downstream, after routing."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:66
msgid "Upon adding the :guilabel:`Caller ID` element to the dial plan, and double-clicking it to configure it, two options appear."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:69
msgid "The first is a :guilabel:`Free text` field, where any text can be input to replace the caller ID. The second option is :guilabel:`Replace the caller ID by the called number`. This option replaces the caller's ID with the :guilabel:`Incoming number`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:74
msgid "A company may want to use the :guilabel:`Caller ID` element to replace the :guilabel:`Incoming number`, so employees, or outside transfers, cannot see the number, and information is kept private."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:79
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:135
msgid "Basic routing elements"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:81
msgid "Basic routing elements in Axivox dial plans provide extension-based routing. This can be done by adding either a *Menu* to numerically link the dial-by-numbers to an action, or by using a *Digital Receptionist* to automatically route or listen for an extension, based on a key input from the caller."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:86
msgid "The main difference between the two elements is that the *Digital Receptionist* does **not** need to be pre-configured numerically with actions. Instead, it acts as a virtual receptionist."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:89
msgid ":guilabel:`Menu`: add a dial-by-number directory and configured downstream actions (not terminal). For example, a dial-by-numbers function could feature an element, wherein clicking '2' takes the caller to the element linked to '2' on the Menu element in the dial plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:92
msgid ":guilabel:`Digital Receptionist`: attach a virtual dispatcher to listen for extensions."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:94
msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console <https://manage.axivox.com>`_. Next, click on the :guilabel:`Visual Editor` button to the right of the dial plan, to edit the dial plan. Then, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:102
msgid "Digital receptionist scenario"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:104
msgid "The *Digital Receptionist* element is a listen-feature that accurately routes callers through a dial plan, based on the extension they enter, via the key pad."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:107
msgid "Set a *Digital Receptionist* to eliminate the need of a team, or live receptionist, to be on-call all the time. With that element in place, calls now reach their destination, without a real person interjecting."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:111
msgid "After adding the :guilabel:`Digital Receptionist` element to a dial plan, connect the appropriate endpoints, and double-click on the element to set the :guilabel:`Timeout` on the :guilabel:`receptionist` pop-up window that appears."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:115
msgid "The :guilabel:`Timeout` can be set in `5` second increments, from `5` seconds to `60` seconds."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:118
msgid "The :guilabel:`Digital Receptionist` element **requires** a :guilabel:`Play a file` element on either side of it, to explain what action to take, and when a wrong extension is entered."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:122
msgid "While customizing a dial plan in a :guilabel:`Dialplan Editor` pop-up window, add a :guilabel:`Menu` element, with a :guilabel:`Greeting message` that might read, `Press star to dial an extension`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:126
msgid "Then, on the :guilabel:`Menu` element, for the :guilabel:`* (star)` option, link a :guilabel:`Play a file` element, that plays an :guilabel:`Audio message` saying, 'Enter the extension of the person you are trying to reach'."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:130
msgid "Following the first :guilabel:`Play a file` element, add the :guilabel:`Digital Receptionist` element, followed by another :guilabel:`Play a file` element, which states, 'That is not a valid extension'."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:134
msgid "This last element is in place to close the loop, should the caller not enter a correct extension."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:136
msgid "Finally, this last :guilabel:`Play a file` element is looped back into the :guilabel:`Menu` element."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:0
msgid "A digital receptionist element highlighted in an example dial plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:144
msgid "Dial plan elements can be configured by double-clicking them, and selecting different features of the Axivox console to them."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:147
msgid "For example, an :guilabel:`Audio message` needs to be made, and then selected in a :guilabel:`Play a file` or :guilabel:`Menu` element."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:150
msgid "For more information, see this documentation :ref:`voip/axivox/audio_messages`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:153
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:147
msgid "Advanced routing elements"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:155
msgid "Advanced routing elements route calls automatically as they are received into the incoming number(s). This can be configured using geo-location, whitelisting, or time-based variables. Calls pass through a filter prior to their final destination, and are routed, based on the set variable(s)."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:160
msgid "The following are advanced routing elements:"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:162
msgid ":guilabel:`Dispatcher`: create a call filter to route traffic, based on the geo-location of the caller ID."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:164
msgid ":guilabel:`Access List`: create a tailored access list, with VIP customer preference."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:165
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:154
msgid ":guilabel:`Time Condition`: create time conditions to route incoming traffic around holidays, or other sensitive time-frames."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:169
msgid "Whitelisting is a technical term used to create a list of allowed numbers. Conversely, blacklisting is used to create a list of denied numbers."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:172
msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console <https://manage.axivox.com>`_. Next, click on the :guilabel:`Visual Editor` button to the right of the dial plan, to edit the dial plan. Then, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`. For more information, visit :ref:`voip/axivox/dial_plans`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:179
msgid "Dispatcher scenario"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:181
msgid "A *Dispatcher* element is a dial plan feature that directs calls, based on region or geo-location. In most cases, the :guilabel:`Dispatcher` element in a dial plan is linked to the :guilabel:`Start` element, in order to filter or screen calls as they come into an incoming number."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:185
msgid "Double-click the :guilabel:`Dispatcher` element in the :guilabel:`Dialplan Editor` pop-up window to configure it."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:188
msgid "This element checks numbers (routed through this element), according to regular expressions. To add a regular expression, click :guilabel:`Add a line` on the bottom of the :guilabel:`Dispatcher` pop-up window."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:192
msgid "Then, under :guilabel:`Name`, enter a recognizable name to identify this expression. This is the name that appears in the :guilabel:`Dispatcher` element on the dial plan showcased in the :guilabel:`Dialplan Editor` pop-up window."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:196
msgid "In the :guilabel:`Regular expression` field, enter the country code, or area code, which Axivox should route for incoming calls. This is especially helpful when a company would like to filter their customers to certain queues, or users based on the customer's geo-location."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:200
msgid "To specify all numbers behind a certain country code, or area code, include `\\d+` after the country code, or country code + area code."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1
msgid "Dispatcher configuration panel, with name, regular expression and add a line highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:208
msgid "`02\\\\d+`: validates the numbers starting with `02`"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:209
msgid "`00\\\\d+`: validates all numbers beginning with `00`"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:210
msgid "`0052\\\\d+` validates all numbers beginning with `0052` (Mexico country code)"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:211
msgid "`001716\\\\d+`: validates all numbers beginning with `001716` (USA country code + Western New York area code)"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:215
msgid "A regular expression (shortened to \"regex\" or \"regexp\"), sometimes referred to as a \"rational expression,\" is a sequence of characters that specifies a match pattern in text. In other words, a match is made within the given range of numbers."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:219
msgid "When the desired configurations are complete on the :guilabel:`Dispatcher` pop-up window, be sure to click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:222
msgid "Upon doing so, the :guilabel:`Dispatcher` element appears with different routes available to configure, based on the :guilabel:`Regular Expressions` that were set."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:225
msgid "Attach these routes to any :guilabel:`New element` in the :guilabel:`Dialplan Editor` pop-up window."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:227
msgid "By default, there is an :guilabel:`Unknown` path that appears on the :guilabel:`Dispatcher` element after setting at least one :guilabel:`Regular Expression`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:230
msgid "Calls follow this route/path when their number does not match any :guilabel:`Regular Expression` set on the :guilabel:`Dispatcher` element."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1
msgid "Dial plan with dispatcher element highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:238
msgid "Time condition scenario"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:240
msgid "When a :guilabel:`Time Condition` element is added to a dial plan, it has a simple :guilabel:`True` and :guilabel:`False` routing."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:243
msgid "After adding the :guilabel:`Time Condition` element to a dial plan, double-click it to configure the variables. :guilabel:`Hour/Minute`, :guilabel:`Days of the week`, :guilabel:`Day of the month`, and :guilabel:`Month` can all be configured."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:247
msgid "If the time which the caller contacts the incoming number matches the set time conditions, then the :guilabel:`True` path is followed, otherwise the :guilabel:`False` path is followed."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:251
msgid "For a company that is closed yearly for the American Independence Day holiday (July 4th) the following time conditions should be set:"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:254
msgid ":guilabel:`Hour/Minute` - `0:0 to 23:59`"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:255
msgid ":guilabel:`Day of the week` - `All to All`"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:256
msgid ":guilabel:`Day of the month` - `From 4 to 4`"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:257
msgid ":guilabel:`Month` - `July`"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:259
msgid "The :guilabel:`Time Condition` element is especially useful for holidays, weekends, and to set working hours. When a caller reaches a destination where they can be helped, either with a real person or voicemail, this reduces wasted time and hangups."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1
msgid "Time condition element set in a dial plan on Axivox. Time condition is highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:268
msgid "To set the :guilabel:`Timezone` that the :guilabel:`Time Condition` operates under, navigate to `Axivox management console <https://manage.axivox.com>`_, and click :guilabel:`Settings` in the menu on the left. Then, set the :guilabel:`Timezone` using the second field from the bottom, by clicking the drop-down menu."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:274
msgid "Access list scenario"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:276
msgid "An *Access List* element in a dial plan allows for the routing of certain numbers, and disallows (denies) other numbers."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:279
msgid "After adding an :guilabel:`Access List` element to a dial plan, it can be configured by double-clicking on the element directly in the :guilabel:`Dialplan Editor` pop-up window."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:282
msgid "Two fields appear where regular expressions can based in the :guilabel:`Allow` and :guilabel:`Deny` fields of the :guilabel:`Access List` pop-up window."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:286
msgid "For a very important customer, their number can be set in the :guilabel:`Allow` field, and these callers can be sent directly to management."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:290
msgid "A regular expression (shortened to \"regex\" or \"regexp\"), sometimes also referred to as a \"rational expression,\" is a sequence of characters that specifies a match pattern in text."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1
msgid "Access list element configuration with the allow/deny fields highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:298
msgid "`2\\\\d\\\\d`: validates numbers from `200 to 299`"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:299
msgid "`02\\\\d*`: validates all numbers beginning with `02`"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:300
msgid "`0017165551212`: validates the number (`0017165551212`)"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:302
msgid "After setting the :guilabel:`Allow` and :guilabel:`Deny` fields with regular expressions or numbers, click :guilabel:`Save` on the :guilabel:`Access List` pop-up window."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:305
msgid "Then, on the :guilabel:`Access list` element in the dial plan, three paths (or routes) are available to link to further actions."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:308
msgid "Unknown calls can be routed through the regular menu flow by adding a :guilabel:`Menu` element, and connecting it to the :guilabel:`Unknown` path. :guilabel:`Refused` calls can be routed to the :guilabel:`Hang up` element. Lastly, :guilabel:`Authorized` callers can be sent to a specific extension or queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1
msgid "Access list element highlighted in an example dial plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:318
msgid "Switches"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:320
msgid "A *Switch* element in Axivox is a simple activated/deactivated route action."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:322
msgid "These can be activated or chosen quickly, allowing for quick routing changes, without altering the dial plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:325
msgid "Alternate routes can be configured, so that in a moments notice, they can be switched to. This could be for new availability, or to adjust traffic flow for any number of reasons."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:328
msgid "Axivox allows for a simple on/off switch, and a multi-switch, which can have several paths to choose from."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:331
msgid ":guilabel:`Switch`: a manual on/off control that can divert traffic, based on whether it is opened (on) or closed (off)."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:333
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:156
msgid ":guilabel:`Multi-Switch`: a mechanism to create paths, and turn them on and off, to divert incoming calls."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:337
msgid "Basic switch"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:339
msgid "A :guilabel:`Switch` can be set in the `Axivox management console <https://manage.axivox.com>`_ by navigating to :guilabel:`Switches` in the left menu. To create a new switch click :guilabel:`Add a switch` from the :guilabel:`Switches` dashboard, configure a :guilabel:`Name` for it, and click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:344
msgid "Then, toggle the desired switch to either :guilabel:`On` or :guilabel:`Off`, from the :guilabel:`State` column on the :guilabel:`Switches` dashboard."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:347
msgid "This :guilabel:`On` / :guilabel:`Off` state automatically routes traffic in a dial plan, in which this switch is set."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:350
msgid "The traffic travels to the :guilabel:`Active` route when :guilabel:`On` is toggled in the switch. The call traffic travels to the :guilabel:`Inactive` route when :guilabel:`Off` is toggled in the switch."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:354
msgid "Changes can be made on the fly, just be sure to click :guilabel:`Apply changes` to implement the them."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:358
msgid "Add a switch to dial plan"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:360
msgid "To add a :guilabel:`Switch` to a dial plan, navigate to `Axivox management console <https://manage.axivox.com>`_, and click on :guilabel:`Dial plans` in the left menu. Then, click :guilabel:`Visual Editor` next to the desired dial plan to open the :guilabel:`Dialplan Editor` pop-up window."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:365
msgid "Then, from the :guilabel:`New element` drop-down menu, select :guilabel:`Switch`, and then click :guilabel:`Add`. Double-click on the element to further configure the :guilabel:`Switch` element."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1
msgid "Switch configuration in a dial plan, with inactive and active routes highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:373
msgid "Multi-switch"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:375
msgid "A *Multi-Switch* element in Axivox is a switch where multiple paths can be configured, and switched between."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:378
msgid "To configure and set a :guilabel:`Multi-Switch` element, navigate to `Axivox management console <https://manage.axivox.com>`_. Then, click on the :guilabel:`Switches` menu item in the left menu."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:381
msgid "Toggle to the :guilabel:`Multi-switch` tab to create, or set, a pre-configured :guilabel:`Multi-Switch` element."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:384
msgid "To create a new :guilabel:`Multi-Switch`, click :guilabel:`Create new`. Then, enter a :guilabel:`Name` for the element, and then enter the :guilabel:`Available choice`. Enter one :guilabel:`Available choice` per line. Do **not** duplicate any entries."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:388
msgid "Remember to click :guilabel:`Save` when done."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:390
msgid "To select the :guilabel:`State` of the :guilabel:`Multi-Switch`, click the drop-down menu next to the :guilabel:`Multi-Switch` name, under the :guilabel:`Multi-switch` tab on the :guilabel:`Switches` dashboard."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:394
msgid "The :guilabel:`State` chosen is the route that is followed in the dial plan. The :guilabel:`State` can be edited on the fly, just be sure to click :guilabel:`Apply changes`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:398
msgid "Add a multi-switch to dial plan"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:400
msgid "To add a :guilabel:`Multi-Switch` element to a dial plan, navigate to `Axivox management console <https://manage.axivox.com>`_, and click :guilabel:`Dial plans` in the left menu."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:403
msgid "Then, select or create a dial plan. Next, click :guilabel:`Visual Editor` on the desired dial plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:405
msgid "On the :guilabel:`Dialplan Editor` pop-up window that appears, click on the :guilabel:`New element` drop-down menu, and select :guilabel:`Multi-Switch`. Then, click :guilabel:`Add`. Double-click on the element to further configure the :guilabel:`Switch` element."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1
msgid "Multi-switch configuration in a dial plan, with chosen route highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:3
msgid "Dial plan basics"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:5
msgid "When someone calls a business, they might need to get in contact with customer support, a sales team, or even a person's direct line. The caller might also be in search of some information about the business, such as store hours. Or, they might want to leave a voicemail, so someone from the company can call them back. With dial plans in Axivox, a company can manage how incoming calls like this are handled."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:11
msgid "Using proper call architecture through a dial plan, callers get directed to the right people, or to the right information, in a quick, efficient manner."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:14
msgid "This document covers the basic configuration of dial plans in Axivox."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:17
msgid "For more information on advanced dial plans, visit :doc:`dial_plan_advanced`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:20
msgid "Using a browser add-on for spelling may hinder the use of the visual editor in dial plans. Do not use a translator with the Axivox management console."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:26
msgid "Dial plans"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:28
msgid "Access dial plans by navigating to `Axivox management console <https://manage.axivox.com>`_, and clicking on :guilabel:`Dial plans` from the menu on the left."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:31
msgid "To add a new dial plan from the :guilabel:`Dial plan` page, click the green button labeled, :guilabel:`Add a new dial plan`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:35
msgid "Axivox has no limit to the number of dial plans that can be created. These can be added, and improved upon, at any time. This allows for sandboxes to be created with many different configurations."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:-1
msgid "Dial plan dashboard with the edit features and Add a dial plan button highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:43
msgid "To edit an existing dial plan, choose one of the following options to the right of the saved dial plan:"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:46
msgid ":guilabel:`Delete`: this action deletes the attached dial plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:47
msgid ":guilabel:`Edit`: this action allows the user to edit the dial plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:48
msgid ":guilabel:`Visual Editor`: this action opens a visual editor window, where the dial plan architecture can be viewed and edited."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:50
msgid ":guilabel:`Duplicate`: this action duplicates the dial plan, and puts it at the bottom of the list, with an extension of one number (+1) larger than the original extension."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:54
msgid "Dialplan editor (visual editor)"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:56
msgid "When the :guilabel:`Visual Editor` button is clicked for a dial plan on the :guilabel:`Dial plan` page, a pop-up :guilabel:`Dialplan Editor` window appears."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:59
msgid "This pop-up window is the primary place where the architecture, or structure, of the dial plan is configured. In this window, a :abbr:`GUI (graphical user interface)` appears, where various dial plan elements can be configured and linked together."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:-1
msgid "Visual editor for an example dial plan, with the new element, Add, and Save buttons\n"
"highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:69
msgid "New dial plans come blank with :guilabel:`New element` options for the user to :guilabel:`Add` and :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:72
msgid "The method for saving in the :guilabel:`Dialplan Editor` is different from saving any other edits in the Axivox management console because the :guilabel:`Save` button **must** be pressed before closing the :menuselection:`Visual editor`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:76
msgid "Then, before these changes can take place on the Axivox platform, the user **must** click :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`Dial plan` page."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:79
msgid "From the :guilabel:`Dialplan Editor` pop-up window, users can add a new element to the dial plan. To do that, open the :guilabel:`New element` drop-down menu, and select the desired element. Then, click :guilabel:`Add`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:83
msgid "Doing so adds that element to the visual editor display of the dial plan being modified. This element can be moved where desired amongst the other elements present in the dial plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:86
msgid "Connect elements in the dial plan by clicking and dragging outward from the :guilabel:`(open circle)` icon on the right side of the element. Doing so reveals an :guilabel:`(arrow)` icon. Proceed to drag this :guilabel:`(arrow)` icon to the desired element in the dial plan that it is meant to connect with."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:91
msgid "Connect the :guilabel:`(arrow)` icon to the circle on the left side of the desired element."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:93
msgid "Calls displayed in the dial plan flow from left-to-right in the element."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:95
msgid "In order to further configure a :guilabel:`New element`, double-click on the element inside the dial plan, to reveal a subsequent pop-up window, wherein additional customizations can be entered."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:98
msgid "Each element has a different configuration pop-up window that appears when double-clicked."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:101
msgid "All elements **must** have a final destination in the dial plan in order to close a loop. This can be accomplished by implementing the :guilabel:`Hang up` element, or looping the element back to a :guilabel:`Menu` element or :guilabel:`Digital Receptionist` element elsewhere in the dial plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:0
msgid "Dial plan, shown with highlight looping open end back to the beginning of the menu\n"
"element."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:111
msgid "Once all desired dial plan elements and configurations are complete, remember to click :guilabel:`Save` before exiting the :guilabel:`Dialplan Editor` pop-up window. Then, click :guilabel:`Apply changes` on the :guilabel:`Dial plans` page to ensure they are implemented into Axivox production."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:117
msgid "Dial plan elements"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:119
msgid "The following elements are available in the :guilabel:`New element` drop-down menu, while designing a dial plan in the :guilabel:`Dialplan Editor` pop-up window."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:123
msgid "Basic elements"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:125
msgid "These are the basic elements that are used in simple dial plans in Axivox:"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:127
msgid ":guilabel:`Call`: call an extension or queue."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:128
msgid ":guilabel:`Play a file`: play an audio file or voice greeting."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:129
msgid ":guilabel:`Voicemail`: forward to a voicemail (terminal)."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:130
msgid ":guilabel:`Hang up`: hang up the call (terminal)."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:131
msgid ":guilabel:`Queue`: attach a call queue with a group of users to answer a call."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:132
msgid ":guilabel:`Conference`: add a conference room for a caller to connect to."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:137
msgid "Routing elements change or route the path of a caller, these are some basic routing elements used in Axivox:"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:140
msgid ":guilabel:`Menu`: add a dial-by-number directory and configure downstream actions (not terminal)."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:141
msgid ":guilabel:`Switch`: attach a manual on/off control that can divert traffic based on whether it is opened (On) or closed (Off)."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:143
msgid ":guilabel:`Digital Receptionist`: attach a virtual dispatcher to listen for extensions to connect to."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:149
msgid "These are the more advanced elements that route calls in Axivox:"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:151
msgid ":guilabel:`Dispatcher`: create a call filter to route traffic based on the geo-location of the caller ID."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:153
msgid ":guilabel:`Access List`: create a tailored access list with VIP customer preference."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:162
msgid "The following are more advanced elements (not routing) in Axivox:"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:169
msgid "Dial plan elements can be configured by double-clicking them, and linking different aspects of the Axivox console to them."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:173
msgid "Attach to incoming number"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:175
msgid "To attach an existing dial plan to an incoming number, go to `Axivox management console <https://manage.axivox.com>`_ , and click on :guilabel:`Incoming numbers`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:178
msgid "Next, click :guilabel:`Edit` next to the number to which the dial plan should be attached."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:180
msgid "Doing so reveals a separate page wherein that number's dial plan can be modified. To do that, select :guilabel:`Dial plan` from the :guilabel:`Destination type for voice call` field drop-down menu. Then, choose the desired dial plan from the :guilabel:`Dial plan` field that appears."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:184
msgid "With that in place, that means when that specific number calls in, the configured dial plan is activated, and runs through the prompts to properly route the caller."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:187
msgid "Finally, :guilabel:`Save` the changes, and click :guilabel:`Apply changes` in the upper-right corner."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:191
msgid "Basic dial plan scenario"
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:193
msgid "The following showcases a basic dial plan scenario for call routing, where additional elements can be added to expand the setup. This basic dial plan scenario includes the following linked elements :menuselection:`Start --> Play a file --> Menu --> (Hang-up, Calls, Queues, Conferences) --> (Voicemail, Hang-up)`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:-1
msgid "Basic dial plan configuration."
msgstr ""
#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:203
msgid "This setup does **not** include any basic or advanced call routing. For more information on call routing, reference this documentation: :doc:`dial_plan_advanced`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:3
msgid "Dynamic caller ID"
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:5
msgid "*Caller ID* identifies the caller when they make a phone call. It allows the recipient of the call to see what number the caller is calling from. Caller ID shows users and clients who is calling, so they can choose to pick up or decline the call."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:9
msgid "Axivox offers a dynamic caller ID option to choose which number is displayed on outgoing calls."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:11
msgid "International numbers can be purchased to do business transactions internationally, via a phone call, from a number that has an area code or country code of the destination being called. By displaying a local number, this can increase customer engagement."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:15
msgid "Some companies have many employees making calls from a call center. These employees are not always available to receive a return phone call from a prospective customer. In this case, :abbr:`VoIP (Voice over Internet Protocol)` can be configured in such a way that dynamic caller ID shows the main company phone number, so any number of employees in the group can answer the call. This way, a call is never missed."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:24
msgid "Default outgoing number"
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:26
msgid "In Axivox a *default number* can be set. This is a company's main number. This means, when anyone from the company (user/employee) calls a number outside the company, the default outgoing number shows up automatically on the caller ID."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:30
msgid "If someone from outside the company tries to call back a user/employee, they are then funneled back through the main line (default number). If there is a dial plan set up, they are prompted to make selections. This is especially helpful in cases where employees change positions frequently, or if they leave the company."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:39
msgid "To access the default number, go to the `Axivox management console <https://manage.axivox.com>`_, and log in. Then, click into :guilabel:`Settings` in the left menu, and navigate to :guilabel:`Default outgoing number`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:43
msgid "From here, change the :guilabel:`Default outgoing number` by clicking the drop-down menu, and making a selection from the incoming phone numbers available on Axivox."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:46
msgid "Be sure to :guilabel:`Save` the changes, then click :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`General Settings` page to implement the change."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:49
msgid "The :guilabel:`Default outgoing number` is what shows up by default in the Axivox management portal. However, the outgoing number can also be configured differently at the user level."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:53
msgid "Users"
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:55
msgid "To configure the outgoing number at the user level, log in to the `Axivox management console <https://manage.axivox.com>`_. Next, click :guilabel:`Users` from the menu on the left, and then click :guilabel:`Edit` to the right of the user that is to be configured."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:59
msgid "Under :guilabel:`Outgoing number`, click the drop-down menu to select either the :guilabel:`Default outgoing number` (as specified here: :ref:`voip/axivox/dynamic-caller-id-default`), or any of the incoming numbers on the Axivox account."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:63
msgid "Choosing the :guilabel:`Default` selection in the :guilabel:`Outgoing number` drop-down menu ensures this user has the :guilabel:`Default outgoing number` shown on their caller ID when making calls."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:66
msgid "If a specific number is chosen, and that number is assigned to this user under :guilabel:`Incoming numbers` (in the Axivox console's menu on the left), that means this user has a direct line for customers to reach them."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:70
msgid "Once the desired changes are complete, be sure to click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement the change."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:74
msgid "By default, when creating a new user in Axivox, the :guilabel:`Outgoing number` is automatically set to :guilabel:`Default`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:78
msgid "Advanced options"
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:80
msgid "To access the :guilabel:`Advanced options`, navigate to the :guilabel:`Settings` option in the menu on the left of the `Axivox management console <https://manage.axivox.com>`_. Then, click :guilabel:`Advanced options` to the right of :guilabel:`Default outgoing number`."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:84
msgid "By default, there are not any advanced rules set. To create one, click the green :guilabel:`+ (plus)` icon. Doing so reveals a line with two blank fields. From here, different caller IDs can be set up, depending on what location the user/employee is calling from."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:88
msgid "To create a rule, first set the :guilabel:`Destination prefix` in the first empty field. This is the country code, complete with zero(s) in front of it. Then, in the second empty field, select the phone number that should be used for calling out from that country code."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:93
msgid "Check the box for :guilabel:`Apply advanced rules even for users with a default outgoing number configured` to allow these rules to take precedent over all other outgoing configurations."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:97
msgid "The order of the rules can be modified by dragging-and-dropping them into another order. The first matching rule is applied."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:101
msgid "For example, a company wants all users/employees to utilize the configured number for Great Britain when calling from the `0044` country code (Great Britain)."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:104
msgid "To accomplish that, simply type in `0044` into the :guilabel:`Destination prefix` field, and select the number starting with the `+44` country code. Order the rules as necessary, and select the checkbox to supersede all other rules, if needed."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:0
msgid "Advanced options for the default outgoing number."
msgstr ""
#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:112
msgid "Once the desired configurations are complete, be sure to click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement the change."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:3
msgid "Manage users in Axivox"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:5
msgid "Managing Axivox :abbr:`VoIP (Voice over Internet Protocol)` users is an important part of setting up :abbr:`VoIP (Voice over Internet Protocol)` in an Odoo database. Each Axivox user has a unique name, phone number and/or extension, and a voicemail. This way, they can be reached in a variety of convenient ways."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:10
msgid "Axivox users are organized in a simple, straightforward way in the Axivox console, so an administrator can manage users quickly and easily."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:14
msgid "This documentation covers how to configure everything through a provider called, Axivox. Depending on the chosen VoIP provider, the processes to manage users may be different."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:18
msgid "Overview"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:20
msgid "Begin at the Axivox management console by navigating to `https://manage.axivox.com <https://manage.axivox.com>`_. Log in with the appropriate administrator credentials."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:24
msgid "Actions in the Axivox management console **must** be double-saved, in order for the changes to take effect. To save any changes, click :guilabel:`Save` in the individualized changes screen. Then, to implement those changes, click the :guilabel:`Apply Changes` button in the upper-right corner of the console."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:34
msgid "Incoming numbers are all the numbers a company is paying to use to receive calls."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:36
msgid "Click on :menuselection:`Incoming numbers` from the menu on the left of the Axivox management console. Doing so reveals the :guilabel:`Incoming numbers` page, where all the incoming numbers are listed, along with their :guilabel:`Destination` and SMS information."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:40
msgid "The :guilabel:`Destination` determines the action that is taken, or the path the caller follows when dialing said numbers."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:43
msgid "To edit the :guilabel:`Destination`, click the :guilabel:`Edit` button to the far-right of the incoming number line to be modified. Then, on the :guilabel:`Edit number` page that appears, the :guilabel:`Destination type for voice call` can be changed."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:47
msgid "The options available in the :guilabel:`Destination type for voice call` drop-down menu are as follows:"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:50
msgid ":guilabel:`Not configured`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:51
msgid ":guilabel:`Extension`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:52
msgid ":guilabel:`Dial plan`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:53
msgid ":guilabel:`Voicemail`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:54
msgid ":guilabel:`Hang up`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:55
msgid ":guilabel:`Conference`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:57
msgid "Depending on the selection made in the :guilabel:`Destination type for voice call` drop-down menu, a second, selection-specific drop-down menu is populated with further configuration options. Additionally, more fields are revealed, based on the selection made in the :guilabel:`Destination type for voice call` drop-down menu."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:62
msgid "Once the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement them."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:66
msgid "New users"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:68
msgid "Every employee using :abbr:`VoIP (Voice over Internet Protocol)` at the company needs an Axivox user account associated with them."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:71
msgid "To view existing users in the Axivox management console, click :guilabel:`Users` from the menu on the left of the console. Every user has a :guilabel:`Number`, :guilabel:`Name`, option for a :guilabel:`Voicemail`, and an :guilabel:`Outgoing number` specified."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:75
msgid "To create a new user in the Axivox console, click :guilabel:`Add a user` to reveal a :guilabel:`New user` form. The following tabs are available for configuring the new user:"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:78
msgid ":guilabel:`General`: basic information, including the extension of the user, can be set."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:79
msgid ":guilabel:`Forwardings`: internal forwards on 'no answer' or busy signals."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:80
msgid ":guilabel:`Follow Me`: external forward configuration."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:81
msgid ":guilabel:`Keys`: set hot-keys within the :abbr:`VoIP (Voice over Internet Protocol)` system."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:82
msgid ":guilabel:`SIP Identifiers`: :abbr:`SIP (Session Initiation Protocol)` username and password for external configuration."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:84
msgid ":guilabel:`Permissions`: set access rights for users in the Axivox management console."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:87
msgid "General tab"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:89
msgid "Under the :guilabel:`General` tab of the :guilabel:`New user` form, in the :guilabel:`Extension` field, input an extension that is unique to the user. This is the number internal users dial to reach a specific employee."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:93
msgid "In the :guilabel:`Name` field, input the employee name."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:95
msgid "Next, fill out the :guilabel:`Email address of the user` field. A valid email address for the employee should be added here, where the user receives business emails."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:98
msgid "In the :guilabel:`GSM number` field, enter an alternative number at which the user can be reached. Be sure to include the country code."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:102
#: ../../content/applications/general/voip/onsip.rst:135
msgid "A country code is a locator code that allows access to the desired country's phone system. The country code is dialed first, prior to the target number. Each country in the world has its own specific country code."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:106
#: ../../content/applications/general/voip/onsip.rst:146
msgid "For a list of comprehensive country codes, visit: `https://countrycode.org <https://countrycode.org>`_."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:-1
msgid "General tab layout in the Axivox management console."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:113
msgid "In the :guilabel:`Voicemail` field, select either :guilabel:`Yes` or :guilabel:`No` from the drop-down menu."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:116
msgid "In the :guilabel:`Directory` field, the administrator has the option to leave it blank, by making no changes, or selecting :guilabel:`Default` from the drop-down menu. The :guilabel:`Directory` is used in the *Digital Receptionist* feature element of a dial-plan."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:120
msgid "At the bottom of the :guilabel:`General` tab, there are two separate options with selection boxes."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:122
msgid "The first option is :guilabel:`This user can receive multiple calls at the same time`. By selecting this option, users are able to receive calls when on another call."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:125
msgid "The second option, :guilabel:`This user must log-in to call`, provides the option to make it mandatory for the user to log in."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:129
msgid "If a company uses physical VoIP phones on desks, and wants their employees to be able to log in from *any* phone or desk in the office, they would make the selection for :guilabel:`This user must log-in to call`."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:133
msgid "Once the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:139
msgid "Forwardings tab"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:141
msgid "Under the :guilabel:`Forwardings` tab of the :guilabel:`New user` form, a company can decide what happens if someone calls a user, and the call is not answered."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:145
msgid "Forwardings are disabled when the :guilabel:`Follow Me` option is enabled."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:147
msgid "For example, under the :guilabel:`Forwarding on no answer` field, when the button for :guilabel:`Add a destination` is selected, the option to add a specific user or phone number is revealed. After entering the :guilabel:`Destination`, a specific time frame can be selected by sliding the :guilabel:`seconds bar` to the desired ring time."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:152
msgid "Additional :guilabel:`Destinations` can be added on with different ring times."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:155
msgid "Ring times can be staggered, so the call is forwarded to another user after the first user does not pick up the call. The option to :guilabel:`Send to voicemail as a last resort` is available to the administrator, should the :guilabel:`Destinations` not pick up."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:159
msgid "Under the :guilabel:`Forwarding on busy` field, an administrator can :guilabel:`Add a destination`. When clicked, they can then set the :guilabel:`Destination` (user) and time frame. Should the original user's :abbr:`VoIP (Voice over Internet Protocol)` extension, or incoming number, be busy, the call is forwarded to the destination(s)."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:-1
msgid "Manage forwarding calls to different users or phone numbers in the Forwardings tab."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:168
msgid "When the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the page."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:172
msgid "Follow Me tab"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:174
msgid "When the :guilabel:`Follow Me` option is selected, under the :guilabel:`Follow Me` tab of the :guilabel:`New user` form, no :menuselection:`Forwardings` can be made."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:177
msgid "Also, when the :guilabel:`Follow Me` option is selected, the :guilabel:`Add a destination` button can be selected to add users, or a destination phone number, to the original user's account. That way, these added numbers ring when a call is received."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:181
msgid "After entering the :guilabel:`Destination`, a specific time frame can be made by sliding the :guilabel:`seconds bar` to the desired ring time. Additional :guilabel:`Destinations` can be added with different ring times."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:186
msgid "The original user's :abbr:`VoIP (Voice over Internet Protocol)` number does **not** ring with this option selected. Ring times can also be staggered, so the call is forwarded to another user after the first user does not pick up the call."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:-1
msgid "Ring destinations like different users or phone numbers from the Follow Me tab."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:195
msgid "The Odoo mobile app, or another :abbr:`SIP (Session Initiation Protocol)` mobile client, allows for simultaneous ringing of the user's extension or incoming number. For more information, visit the :doc:`VoIP Mobile Integrations <../devices_integrations>` documentation."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:199
#: ../../content/applications/general/voip/axivox/manage_users.rst:345
msgid "Once all desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:203
msgid "Keys tab"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:205
msgid "Under the :guilabel:`Keys` tab of the :guilabel:`New user` form, speed dial actions for the user can be configured. Some more advanced options are available, as well."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:208
msgid "The following options are available to set to numerical values `1-20`."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:210
msgid "These actions can be set on each number:"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:212
msgid ":guilabel:`Not configured`: the default action, which is nothing."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:213
msgid ":guilabel:`BLF (Busy lamp fields)`: this action shows the status of other users' phones connected to the Axivox phone system. This is primarily used on a desk-phone."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:215
msgid ":guilabel:`Quick Call`: this action allows for a speed-dial of an external number."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:216
msgid ":guilabel:`Line`: this action allows the user to call another user."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:217
msgid ":guilabel:`Switch`: this action allows the user to switch between calls from a desk-phone."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:218
msgid ":guilabel:`Pickup`: this action allows the user to pick up an incoming call from a desk-phone."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:-1
msgid "Manage user page with Keys tab highlighted and number 2 key drop-down menu selected (with\n"
"highlight)"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:225
#: ../../content/applications/general/voip/axivox/manage_users.rst:313
msgid "Once all the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:229
msgid "Many of the preceding options have secondary options available, as well, that can be used to link a user, or external phone number. These **must** be filled out in conjunction with the initial action."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:234
msgid "The :guilabel:`Number of keys` field can be changed by entering in the desired numerical value in the :guilabel:`Number of keys` field, located at the top of the :guilabel:`Keys` tab of the :guilabel:`New user` form."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:239
msgid "SIP Identifiers tab"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:241
msgid "*SIP*, which stands for Session Initiation Protocol telephony, allows one to make and receive calls through an internet connection. The :guilabel:`SIP Identifiers` tab on the :guilabel:`New user` form, contains credentials needed to configure Axivox users in Odoo and/or a different :abbr:`SIP (Session Initiation Protocol)` mobile client."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:247
msgid "See the documentation on configuring Axivox, using the SIP identifiers:"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:249
msgid ":doc:`Use VoIP services in Odoo with Axivox <axivox_config>`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:250
msgid ":doc:`Axivox Mobile Integrations <../devices_integrations>`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:252
msgid "Under the :guilabel:`SIP Identifiers` tab, the :guilabel:`SIP username` field represents the user's information that was entered in the :guilabel:`Extension` field, under the :guilabel:`General` tab."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:255
msgid "The :guilabel:`Domain` field is assigned to the company by the Axivox representative."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:257
msgid "The value in the :guilabel:`SIP Password` field is unique for every Axivox user. This value is used to sign into Axivox on Odoo, and for any mobile :abbr:`SIP (Session Initiation Protocol)` clients."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:-1
msgid "Important credentials used for external configurations of Axivox VoIP."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:264
msgid "The value listed in the :guilabel:`Address of the proxy server` field is typically: `pabx.axivox.com`, but is subject to change by Axivox, so be sure to check the :guilabel:`SIP Identifiers` tab for the most accurate value."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:268
msgid "Once all desired configurations have been made, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:272
msgid "Permissions tab"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:274
msgid "Under the :guilabel:`Permissions` tab of a :guilabel:`New user` form, a :guilabel:`Username` and :guilabel:`Password` can be entered for the user."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:277
msgid "Beneath those fields, the following permissions can be granted to Axivox users for portal access:"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:279
msgid ":guilabel:`User portal access`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:280
msgid ":guilabel:`User management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:281
msgid ":guilabel:`Administrator access`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:282
msgid ":guilabel:`Phone management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:283
msgid ":guilabel:`User group management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:284
msgid ":guilabel:`Phone number management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:285
msgid ":guilabel:`Dial plan management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:286
msgid ":guilabel:`Pickup group management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:287
msgid ":guilabel:`Switch management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:288
msgid ":guilabel:`Conference management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:289
msgid ":guilabel:`Queue management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:290
msgid ":guilabel:`Voicemail management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:291
msgid ":guilabel:`Audio messages management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:292
msgid ":guilabel:`Music on hold management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:293
msgid ":guilabel:`Directory management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:294
msgid ":guilabel:`Call list`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:295
msgid ":guilabel:`Connected user list`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:296
msgid ":guilabel:`Global settings`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:297
msgid ":guilabel:`Apply changes button`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:298
msgid ":guilabel:`Invoice download`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:299
msgid ":guilabel:`Invoice details`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:300
msgid ":guilabel:`Blacklist management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:301
msgid ":guilabel:`Conference participant management`"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:303
msgid "To access credentials for the Axivox user portal, navigate to the top of the :menuselection:`Permissions` tab. Then, copy the :guilabel:`Username`, and enter the correct :guilabel:`Password` for the individual user. There is a minimum of 8 characters for a user password."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:309
msgid "These are the same permissions granted to the Axivox administrator that are listed in the menu on the left in the Axivox management console. Should a selection state :guilabel:`No`, or :guilabel:`No access`, then the menu option does **not** populate for the user."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:316
msgid "Upon finishing the setup for a new user, an :ref:`voip/axivox/incoming_number` can be linked."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:-1
msgid "Manage a user page, with the permissions tab highlighted, along with the first permission\n"
"highlighted indicating a no selection."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:326
msgid "User groups"
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:328
msgid "A user group is a grouping of Axivox users that can be linked to a queue for call center capability."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:331
msgid "To begin using user groups, navigate to `https://manage.axivox.com <https://manage.axivox.com>`_."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:333
msgid "Then, log in with the appropriate administrator credentials. From the menu on the left of the Axivox administrative panel, click into :guilabel:`User Groups`."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:336
msgid "To add a user group from the :guilabel:`User Groups` page, click :guilabel:`Add a group`."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:338
msgid "Next, name the group, by entering text into the :guilabel:`Name` field. Then, add a member to the group by typing the first few letters of the user's name into the :guilabel:`Members` field. The user populates in a drop-down menu below the field. Then, click on the desired user, and they are added to the user group."
msgstr ""
#: ../../content/applications/general/voip/axivox/manage_users.rst:343
msgid "Repeat this process to add more users to the group."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:3
msgid "Voicemails and audio messages"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:7
msgid "Managing voicemail is an important part of any business. A company needs to access their messages with ease, and stay on top of any missed calls. Recording audio messages, like thanking a caller for reaching out, or directing them to the right extension, is also a great way to personalize the business interaction, and set the tone with the customer."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:12
msgid "This document covers the configuration of both voicemail and audio messages in the Axivox administrative portal."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:18
msgid "Set global language"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:20
msgid "To start using voicemails and audio messages with Axivox, the global language should be set in the Axivox admin portal settings. To do that, navigate to `manage.axivox.com <axivox_admin_>`_. After logging into the portal, go to :menuselection:`Settings --> Global language (e.g.: voicemail messages,...)`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:25
msgid "From here, set the language to either: :guilabel:`Francais`, :guilabel:`English`, :guilabel:`Espanol`, or :guilabel:`Deutsch`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:28
msgid "Then, click :guilabel:`Save`, followed by :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`General Settings` page to implement the change into production."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:34
msgid "Activate voicemail"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:36
msgid "In order for a user to utilize voicemail in Axivox, the voicemail feature **must** be turned on in the Axivox administrative portal. To begin using voicemail with a user, navigate to `manage.axivox.com <axivox_admin_>`_. Then, log in with the appropriate administrator credentials."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:40
msgid "On the left menu of the Axivox administrative panel, click into :guilabel:`Users`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:42
msgid "Then, click into the specific user the voicemail should be activated for. Under the section marked, :guilabel:`Voicemail`, open the drop-down menu, and click on :guilabel:`Yes`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:45
msgid "Lastly, :guilabel:`Save` the change, then click :guilabel:`Apply changes` in the upper-right corner of the screen."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:49
msgid "Voicemail"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:51
msgid "The next step is to set up the individual voicemail boxes on the Axivox administrative portal. To access the portal, visit `manage.axivox.com <axivox_admin_>`_ and log in. Then, navigate to :menuselection:`Voicemails`, located in the menu on the left."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:55
msgid "If the voicemail option was activated in the user profile, using this process :ref:`voip/axivox/activate_voicemail`, then a voicemail is automatically created on the :guilabel:`Voicemails` page."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:60
msgid "It should be noted that some of the administrative portal language is in French, as Axivox is a Belgian company. The global language is still set to one of the four options as seen here: :ref:`voip/axivox/global_language`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:65
msgid "Manually create voicemail"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:67
msgid "To manually create a new voicemail box, click :guilabel:`Add a voicemail` on the :guilabel:`Voicemails` page. Or, edit an existing voicemail box, by clicking :guilabel:`Edit` to the far-right of an existing voicemail box on the :guilabel:`Voicemails` page."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:72
msgid "Suppose a sales or support team needs a general voicemail box. The voicemail would need to be created manually, and attached to an incoming number."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:75
msgid "The new, manually-created voicemail box should be attached to an incoming number, so it can receive messages. To do so, navigate to :menuselection:`Incoming numbers`, located in the menu on the left. Then, click :guilabel:`Edit` to the far-right of the specific number the voicemail should be linked to."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:80
msgid "In the :guilabel:`Destination type for voice call` field, click the drop-down menu, and select :guilabel:`Voicemail`. Then, open the drop-down menu on the next line labeled, :guilabel:`Voicemail`, and select the manually-created voicemail box."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:85
msgid "If an incoming number is capable of receiving SMS/text messages, an additional field, :guilabel:`Destination email address for Incoming SMS`, is present."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:88
msgid "To determine whether an incoming number is capable of receiving SMS/text messages, click :guilabel:`Incoming numbers` from the menu on the left, then check the :guilabel:`SMS compatible` column for the incoming number."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:92
msgid "Then, if applicable, in the field labeled, :guilabel:`Destination email address for Incoming SMS`, enter an email to which incoming text messages sent to the incoming number can be received. Some incoming numbers (US +1) in Axivox are capable of receiving text messages from individuals and automated numbers."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:97
msgid "Should this field be left empty, the default destination address is used, instead (as previously set in the beginning of the process for manually creating a voicemail)."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:100
msgid "Once all desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the screen to implement the change into production."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:104
msgid "Notifications"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:106
msgid "Now, whenever a voicemail is received on any of the automatically pre-configured or manually-linked voicemail boxes, an email is sent to the user's email address, as listed in the :guilabel:`Voicemails` page, or in the user's Axivox profile."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:110
msgid "This information can be accessed by navigating to :menuselection:`Users` in the left menu, and clicking :guilabel:`Edit` next to the specific user in question."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:116
msgid "Forwarding to voicemail"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:118
msgid "In Axivox, there are also numerous forwarding settings for a user. To access these forwarding settings, go to `manage.axivox.com <axivox_admin_>`_ and log in."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:121
msgid "Next, navigate to :menuselection:`Users`, located in the menu on the left."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:123
msgid "From there, click into the specific user the forwarding should be added to. Then, open the :guilabel:`Forwardings` tab."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:126
msgid "If the user is busy on another call, or away from the phone, there is an option present in this tab to :guilabel:`Send to voicemail as a last resort`, located in the :guilabel:`Forwarding on no answer` and :guilabel:`Forwarding on busy` fields."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:-1
msgid "Send to voicemail as a last resort options highlighted on the Forwardings tab of the user."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:134
msgid "If the :guilabel:`Send to voicemail as a last resort` box is ticked, when the forwarding actions stated in each section are not successful, the caller is routed to the voicemail set on the particular user."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:139
msgid "For more information on forwarding and transfers, visit :ref:`voip/axivox/forwardings_tab`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:141
msgid "When all the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the screen to implement the change."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:147
msgid "Audio messages"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:149
msgid "It is possible to add audio messages *before* a customer's call is even taken, to inform them about the waiting time for deliveries, the availability of a product, or any other important promotional messages."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:153
msgid "To record an audio message in Axivox, navigate to `manage.axivox.com <axivox_admin_>`_ and log in."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:155
msgid "Next, click on :guilabel:`Audio messages` in the menu on the left. From the :guilabel:`Audio messages` page, click :guilabel:`Add a message`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:158
msgid "Type in a :guilabel:`Name`, and click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:160
msgid "Upon clicking :guilabel:`Save`, the browser redirects back to the main :guilabel:`Audio messages` page, where the newly-created message can be found on the list."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:163
msgid "There are two different ways to make the audio message. The user could either record the message over the phone, or type the message (in text), and select a computer-generated speaker to read the message."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:168
msgid "Record audio message"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:170
msgid "To record an audio message over the phone, click the orange button labeled, :guilabel:`Record/Listen`, located to the right of the desired message on the list to record, on the :guilabel:`Audio messages` page."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:174
msgid "When clicked, a :guilabel:`Record / listen to a message` pop-up window appears. From here, the message is then recorded, via one of the extensions that is associated with the user. Under :guilabel:`Extension to use for message management` field, click the drop-down menu, and select the extension where Axivox should call to record the message."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:179
msgid "Then, click :guilabel:`OK` to begin the call."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:182
msgid "The user **must** be active in the production database with :abbr:`VoIP (Voice over Internet Protocol)` configured. To configure :abbr:`VoIP (Voice over Internet Protocol)` for a user, see this documentation: :doc:`axivox_config`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:186
msgid "Upon connecting to the Axivox audio recorder management line, a recorded French-speaking operator provides the following options:"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:189
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:199
msgid "Press `1` to record a message."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:190
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:200
msgid "Press `2` to listen to the current message."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:192
msgid "Press either `1` or `2`, depending on whether or not there is already a message present in the system for this particular audio message that requires a review, before recording a new one."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:195
msgid "Record the new audio message after pressing `1`, then press `#` to end the recording."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:197
msgid "The French-speaking operator returns to the line presenting the first set of questions again:"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:202
msgid "Press `#` to end the call."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:205
msgid "Write audio message"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:207
msgid "To type the message, and select a computerized speaker to say the text, navigate to the :menuselection:`Audio messages` in the menu on the left."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:210
msgid "From the :guilabel:`Audio messages` page, select the blue button labeled, :guilabel:`Text message`, next to the corresponding audio message :guilabel:`Name` that the message should be attached to."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:213
msgid "Doing so reveals a :guilabel:`Convert text to message` pop-up window."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:215
msgid "From the :guilabel:`Convert to text message` pop-up window, click the drop-down menu next to the field labeled, :guilabel:`Voice`, and select an option for the :guilabel:`Text` to be read in."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:218
msgid "After the :guilabel:`Voice` selection has been made, and the message has been written in the :guilabel:`Text` field, click :guilabel:`Generate` to process the audio file."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:221
msgid "The text is read in the same language it is written in the :guilabel:`Text` field. Should the language differ in the :guilabel:`Voice` field, then an accent is used by the computerized speaker."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:224
msgid "Finally, when these steps are complete, click :guilabel:`Save` to save the audio message."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:226
msgid "To implement the changes, click :guilabel:`Apply changes` in the upper-right corner of the screen."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:-1
msgid "Convert text to message window with voice, text, generate button and save highlighted."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:233
msgid "To set a greeting or audio message in a dial plan element double-click on the element. This could be a :guilabel:`Play a file` element, or a :guilabel:`Menu` element, in which the caller should encounter an urgent message, or a dial-by-number directory."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:237
msgid "For more information on dial plans see this documentation: :doc:`dial_plan_basics` or :doc:`dial_plan_advanced`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:243
msgid "Music on-hold"
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:245
msgid "Axivox has the option to add custom hold music to the call whenever a caller is waiting for their call to be answered. To add hold music to the Axivox administrative portal, navigate to the `manage.axivox.com <axivox_admin_>`_, and log in."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:249
msgid "Then, click on :guilabel:`Music on hold` from the menu on the left, and a :guilabel:`Change the music on hold` pop-up window appears."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:252
msgid "On the :guilabel:`Change the music on hold` pop-up window, click the :guilabel:`Choose File` button to select an MP3 (MPEG Audio Layer 3) or WAV (Waveform Audio File Format ) file to be uploaded."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:256
msgid "Only :abbr:`MP3 (MPEG Audio Layer 3)` or :abbr:`WAV (Waveform Audio File Format)` files can be uploaded to the Axivox administrative portal."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:259
msgid "Once the file is selected, the :guilabel:`Progression` bar shows an upload status. When this activity completes, the window can be closed, by clicking :guilabel:`Close`."
msgstr ""
#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:262
msgid "When the desired changes are complete, click :guilabel:`Apply changes` in the upper-right corner of the screen."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:3
msgid "Devices and integrations"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:5
msgid ":abbr:`VoIP (Voice over Internet Protocol)` can be used on many different devices, such as a computer, tablet, mobile phone, and many more. This is helpful in that it reduces costs, and employees can work from anywhere in the world, so long as they have a broadband internet connection."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:9
msgid "Odoo *VoIP* is SIP (Session Initiation Protocol) compatible, which means it can be used with *any* :abbr:`SIP (Session Initiation Protocol)` compatible application."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:12
msgid "This document covers the process of setting up Odoo *VoIP* across different devices and integrations."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:15
msgid "Odoo is fully-integrated with all Odoo apps, allowing users to click into any app, and schedule a call as an activity in the chatter."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:19
msgid "For example, in the *CRM* app, a user can click into an opportunity, and click on :guilabel:`Activities` in the chatter."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:22
msgid "Next, they can choose :guilabel:`Call`, and under :guilabel:`Due Date`, they can select a date."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:24
msgid "Once they click :guilabel:`Save`, an activity shows up in the chatter."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:26
msgid "Should the :guilabel:`Due Date` be for today's date, the activity shows up in the :abbr:`VoIP (Voice over Internet Protocol)` widget."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:0
msgid "View of CRM leads and the option to schedule an activity for Odoo Discuss."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:34
msgid "Odoo VoIP (laptop/desktop computer)"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:36
msgid "The Odoo *VoIP* (Voice over Internet Protocol) module and widget can be used from any browser on a laptop or desktop device. Simply click on the :guilabel:`📞 (phone)` icon in the upper-right corner, while in the Odoo database, and the widget appears."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:41
msgid "To see how to use the :abbr:`VoIP (Voice over Internet Protocol)` widget on a desktop/laptop computer, check out this documentation: :doc:`voip_widget`."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:45
msgid "Odoo VoIP (tablet/mobile device)"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:47
msgid "The Odoo *VoIP* app can be used on tablets and mobile phones, through the Odoo Android or Apple IOS applications. Additionally, a mobile web browser can be used to access the database."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:51
msgid "Odoo Android and Apple IOS applications are no longer being maintained by Odoo on the Android and Apple portals. This means Odoo support only handles limited scopes of Odoo Android or Apple IOS support tickets."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:56
msgid "While outgoing calls can be placed using Odoo on a mobile device, be aware that Odoo is **not** a full :abbr:`VoIP (Voice over Internet Protocol)` application, and does **not** ring on incoming calls. If the user needs to be reachable on a mobile device at all times, an app, like Zoiper, should be used. Apps like that stay connected in the background at all times."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:61
msgid "For more information, see this documentation: :ref:`voip/zoiper`."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:63
msgid "While in the mobile application on a mobile device/tablet, access the Odoo *VoIP* widget, by tapping on the :guilabel:`📞 (phone)` icon in the upper-right corner. The widget appears in the lower-left corner."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:67
msgid "When first making a call from the tablet using the mobile application, the user is prompted to :guilabel:`Allow` the database to use the microphone. Click :guilabel:`Allow` when prompted to continue with the call using the microphone."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:71
msgid "This step is **necessary**, whether using the mobile Odoo application or web browser."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:-1
msgid "Allow the database to access the microphone."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:77
msgid "Odoo then asks how to make the call. The two options are : :guilabel:`VOIP` or :guilabel:`Phone` (should the tablet be enabled for calling). Click the box next to :guilabel:`Remember ?` should this decision be the default moving forward."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:-1
msgid "Window prompt to choose whether to use VOIP or the devices phone to make the call."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:85
msgid "Here is the layout of what the Odoo *VoIP* app looks like on a mobile device:"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:-1
msgid "Layout of what the VoIP app looks like on the a mobile device."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:94
msgid "Zoiper Lite"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:96
msgid "*Zoiper Lite* is a free :abbr:`VoIP (Voice over Internet Protocol)` :abbr:`SIP (Session Initiation Protocol)` dialer with voice and video."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:99
msgid "To start using the *Zoiper* app, download it to the device, via the `Zoiper download page <https://www.zoiper.com/en/voip-softphone/download/current>`_."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:102
msgid "A mobile device is the most common installation, and this document covers how to set up on the *Zoiper* IOS application. Screenshots and steps may differ depending on the set up conditions."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:105
msgid "After installing the *Zoiper* application on the mobile phone, open the application, and tap on :guilabel:`Settings`. Navigate to :menuselection:`Accounts`, and tap on the :guilabel:`+ (plus)` icon to add an account."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:109
msgid "If the :abbr:`VoIP (Voice over Internet Protocol)` account is already set up, then click :guilabel:`Yes`. This means an account username and password has already been produced."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:-1
msgid "Zoiper account setup, shown in the view from a mobile device."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:116
msgid "Next, tap on :guilabel:`Select a provider`. On the screen that populates, tap :guilabel:`Country`, in the upper-right corner, to narrow the providers down to a specific country. Choose the country for the provider that is being configured, then find the :guilabel:`Provider`, and select it."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:121
msgid "If the provider being configured is *Axivox*, then select :guilabel:`Belgium`. Then, choose :guilabel:`Axivox` as the provider."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:-1
msgid "Zoiper account setup, choosing the provider."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:128
msgid "Under :abbr:`SIP (Session Initiation Protocol)` options, enter the :guilabel:`Account name`, :guilabel:`Domain`, :guilabel:`Username`, and :guilabel:`Password`. All this information varies, based on the account."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:133
msgid "To access this information, via the *Axivox* portal, navigate to :menuselection:`Users --> Choose user --> Edit --> SIP Identifiers tab`. The :guilabel:`SIP username`, :guilabel:`Domain`, :guilabel:`SIP password`, and :guilabel:`Address of the proxy server` are all present in this tab."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:141
msgid "Zoiper Field"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:142
msgid "Axivox Field"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:143
msgid "Account name"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:144
msgid "*Can be anything*"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:145
#: ../../content/applications/general/voip/devices_integrations.rst:146
msgid "Domain"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:147
msgid "Username"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:148
msgid "SIP username"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:149
msgid "Password"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:150
msgid "SIP password"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:152
msgid "Once this account information is entered, click the green :guilabel:`Register` button at the top of the screen. Once the registration information is checked, *Zoiper* populates a message, stating :guilabel:`Registration Status: OK`."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:156
msgid "At this point, *Zoiper* is now set up to make phone calls using the :abbr:`VoIP (Voice over Internet Protocol)` service."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:-1
msgid "Zoiper account setup, registration successful."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:164
msgid "Linphone"
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:166
msgid "*Linphone* is an open-source :abbr:`VoIP (Voice over Internet Protocol)` :abbr:`SIP (Session Initiation Protocol)` softphone, used for voice, video, messaging (group and individual), as well as conference calls."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:170
msgid "To start using the *Linphone* app, download it to the device, via the `Linphone download page <https://new.linphone.org/technical-corner/linphone?qt-technical_corner=2#qt-technical_corner>`_."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:173
msgid "A mobile device is the most common installation, and this document covers how to set up the *Linphone* IOS application. Screenshots and steps may differ depending on the circumstances."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:176
msgid "To begin configuring *Linphone* for use with a :abbr:`SIP (Session Initiation Protocol)` provider, first open *Linphone*, and an assistant screen appears."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:179
msgid "From this screen, select :guilabel:`Use SIP Account`. Then, on the following screen, enter the :guilabel:`Username`, :guilabel:`Password`, :guilabel:`Domain`, and :guilabel:`Display Name`. Once complete, press :guilabel:`Login`."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:183
msgid "At this point, *Linphone* is ready to start making calls, once there is a green button at the top of the application screen that reads, :guilabel:`Connected`."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:-1
msgid "Linphone account setup, registration successful."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:191
msgid "*Linphone* makes a variety of applications for mobile and desktop devices in operating systems, such as Windows, Linux, Apple, and Android. Because *Linphone* is an open-source project, many new updates are released on a regular basis."
msgstr ""
#: ../../content/applications/general/voip/devices_integrations.rst:195
msgid "See `Linphone's wiki-documentation page <https://wiki.linphone.org/xwiki/wiki/public/view/Linphone/>`_."
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 <https://www.onsip.com/>`_. OnSIP is a VoIP provider. An account is needed with OnSIP in order to use this service."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:11
msgid "Before setting up an account with OnSIP, make sure the company's home area, and the areas that will be called, are covered by OnSIP services."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:14
msgid "After opening an OnSIP account, follow the configuration procedure below to configure it on an Odoo database."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:20
msgid "To configure the Odoo database to connect to OnSIP services, first navigate to the :menuselection:`Apps application` from the main Odoo dashboard. Then, remove the default `Apps` filter from the :guilabel:`Search...` bar, and search for `VoIP OnSIP`."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:24
msgid "Next, install the :guilabel:`VOIP OnSIP` module."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:-1
msgid "View of OnSIP app in the app search results."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:31
msgid "Odoo VoIP setting"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:33
msgid "After installing the *VOIP OnSIP* module, go to the :menuselection:`Settings app`, scroll down to the :guilabel:`Integrations` section, and locate the :guilabel:`Asterisk (VoIP)` fields. Then, proceed to fill in those three fields with the following information:"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:37
msgid ":guilabel:`OnSIP Domain`: the domain that was assigned when creating an account on `OnSIP <https://www.onsip.com/>`_."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:39
msgid ":guilabel:`WebSocket`: `wss://edge.sip.onsip.com`"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:40
msgid ":guilabel:`VoIP Environment`: :guilabel:`Production`"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:-1
msgid "VoIP configuration settings in Odoo Settings app."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:47
msgid "To access the OnSIP domain, navigate to `OnSIP <https://www.onsip.com/>`_ and log in. Then, click the :guilabel:`Administrators` link in the top-right of the page."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:50
msgid "Next, in the left menu, click :guilabel:`Users`, and then select any user. By default, the selected user opens on the :guilabel:`User Info` tab."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:53
msgid "Click on the :guilabel:`Phone Settings` tab to reveal OnSIP configuration credentials (first column)."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:0
msgid "Domain setting revealed (highlighted) on administrative panel of OnSIP management\n"
"console."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:62
msgid "Odoo user setting"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:64
msgid "Next, the user needs to be set up in Odoo. Every user associated with an OnSIP user **must** also be configured in the Odoo user's settings/preferences."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:67
msgid "To do that, navigate to :menuselection:`Settings app --> Manage Users --> Select the User`."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:69
msgid "On the user form, click :guilabel:`Edit` to configure the user's OnSIP account. Then, click the :guilabel:`Preferences` tab, and scroll to the :guilabel:`VoIP Configuration` section."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:72
msgid "In this section, fill in the fields with OnSIP credentials."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:74
msgid "Fill in the following fields with the associated credentials listed below:"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:76
msgid ":guilabel:`SIP Login` / :guilabel:`Browser's Extension` = OnSIP :guilabel:`Username`"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:77
msgid ":guilabel:`OnSIP authorization User` = OnSIP :guilabel:`Auth Username`"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:78
msgid ":guilabel:`Handset Extension` = OnSIP :guilabel:`Ext.` (extension without the `x`)"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:79
msgid ":guilabel:`SIP Password` = OnSIP :guilabel:`SIP Password`"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:-1
msgid "OnSIP user credentials with username, auth username, SIP password, and extension\n"
"highlighted."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:87
msgid "The OnSIP extension can be found in the *User* banner line above the tabs."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:89
msgid "When these steps are complete, click :guilabel:`Save` on the user form in Odoo to save the configurations."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:92
msgid "Once saved, Odoo users can make phone calls by clicking the :guilabel:`📞 (phone)` icon in the top-right corner of Odoo."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:96
msgid "Additional setup and troubleshooting steps can be found on `OnSIP's knowledge base <https://support.onsip.com/hc/en-us>`_."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:100
msgid "Incoming calls"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:102
msgid "The Odoo database also receives incoming calls that produce pop-up windows in Odoo. When those call pop-up windows appear, click the green :guilabel:`📞 (phone)` icon to answer the call."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:105
msgid "To ignore the call, click the red :guilabel:`📞 (phone)` icon."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:-1
msgid "Incoming call shown in the Odoo VoIP widget."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:113
msgid ":doc:`voip_widget`"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:116
#: ../../content/applications/general/voip/voip_widget.rst:32
msgid "Troubleshooting"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:119
msgid "Missing parameters"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:121
msgid "If a *Missing Parameters* message appears in the Odoo widget, make sure to refresh the Odoo browser window (or tab), and try again."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:-1
msgid "Missing parameter message in the Odoo VoIP widget."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:129
msgid "Incorrect number"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:131
msgid "If an *Incorrect Number* message appears in the Odoo widget, make sure to use the international format for the number. This means leading with the :guilabel:`+ (plus)` sign, followed by the international country code."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:139
msgid "For example, `+16505555555` (where `+1` is the international prefix for the United States)."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:-1
msgid "Incorrect number message populated in the Odoo VoIP widget."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:150
msgid "OnSIP on mobile phone"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:152
msgid "In order to make and receive phone calls when the user is not in front of Odoo on their computer, a softphone app on a mobile phone can be used in parallel with Odoo *VoIP*."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:155
msgid "This is useful for convenient, on-the-go calls, and to make sure incoming calls are heard. Any SIP softphone will work."
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:159
msgid ":doc:`devices_integrations`"
msgstr ""
#: ../../content/applications/general/voip/onsip.rst:160
msgid "`OnSIP App Download <https://www.onsip.com/app/download>`_"
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:3
msgid "Make, receive, transfer, and forward calls"
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:5
msgid "Calling prospective clients, customers, or colleagues is an essential part of any business. A company also needs to be available when customers call, in order to build trust and make connections."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:9
msgid "This document covers how to make, receive, transfer, and forward calls with Odoo *VoIP*."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:12
msgid "Make calls"
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:14
msgid "Starting on the Odoo dashboard, a call can be made by opening the phone widget in the the upper-right corner, which is represented by a :guilabel:`📞 (phone)` icon."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:17
msgid "Then, a user can click on the :guilabel:`Contacts` tab, and click into any contact in the database to make a call."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:20
msgid "Additionally, one can also use the :guilabel:`Search bar` in the :guilabel:`VOIP` pop-up window to find any desired contact."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:-1
msgid "Using the VoIP phone widget to make calls."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:27
msgid "To manually make a call, click the :guilabel:`⌨️ (keyboard)` icon, and proceed to manually key in the desired number. Do not forget to lead with the :guilabel:`+ (plus)` icon, followed by the international country code."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:32
msgid "For the United States of America, the country code and :guilabel:`+ (plus)` icon, would look like this: `+1`. If one were to dial Belgium, the number would be prefixed by `+32`, and for Great Britain it would be `+44`."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:36
msgid "After entering the full number, with the required :guilabel:`+ (plus)` icon prefix and country code, click the green :guilabel:`📞 (phone)` icon to start the call. When finished, click the red :guilabel:`📞 (phone)` icon to end the call."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:45
msgid "Receive calls"
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:47
msgid "An incoming call automatically opens the *VoIP* widget, when a user is using the Odoo database. Should the database be open in another tab, a sound plays (the sound **must** be activated on the device)."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:51
msgid "Once back to the tab, the calling screen of the *VoIP* phone widget appears."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:53
msgid "Click the green :guilabel:`📞 (phone)` icon to pick up the call, or the red :guilabel:`📞 (phone)` icon to reject the call."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:-1
msgid "Incoming call on the VoIP widget, with the call answer and call reject buttons highlighted."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:61
msgid "Add to call queue"
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:63
msgid "All the contacts and customers that need to be called can be seen in one place with the Odoo *VoIP* phone widget, under the :guilabel:`Next activities` tab."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:-1
msgid "VoIP widget with next activities highlighted, showing tasks below."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:70
msgid "To add a call to the :guilabel:`Next activities` tab, click the green :guilabel:`📞 (phone)` icon, while in kanban view of the *CRM* application."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:73
msgid "To remove them from the call queue, hover over the opportunity that has a call scheduled, and click the red :guilabel:`📞 (phone)` icon that appears with the :guilabel:`- (minus)` icon."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:76
msgid "When navigating back to the *VoIP* phone widget, **only** the calls that are scheduled immediately for that day appear in the queue under the :guilabel:`Next Activities` tab of the *VoIP* pop-up widget."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:-1
msgid "Adding a call to the next activities tab in the VoIP phone widget."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:84
msgid "The :guilabel:`Next Activities` tab of the *VoIP* phone widget is integrated with the following Odoo apps: *CRM*, *Project*, and *Helpdesk*."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:87
msgid "A call can be added in the chatter of records within those applications."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:89
msgid "To manually add a call, via the chatter, click :guilabel:`Activities` (next to the :guilabel:`🕗 (clock)` icon). Under :guilabel:`Activity Type`, select :guilabel:`Call` from the drop-down menu that appears."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:93
msgid "Next, set a :guilabel:`Due Date`, and add a :guilabel:`Summary`."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:95
msgid "Lastly, change the :guilabel:`Assigned to` field to the person that should make the call. Whomever is set in this last field (:guilabel:`Assigned to`) has this call show up in their :guilabel:`Next Activities` call queue in the Odoo *VoIP* phone widget."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:100
msgid "Only calls for the immediate day (today's date) appear in the :guilabel:`Next Activities` tab of the *VoIP* phone widget for that specific user."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:103
msgid "If specified, click :guilabel:`Save` or :guilabel:`Open Calendar` to complete the scheduling of the call."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:107
msgid "Transfer calls"
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:109
msgid "A call can be transferred from one user to another in the Odoo *VoIP* phone widget. However, this can **only** occur after speaking to the caller first. Without picking up the call in the Odoo *VoIP* phone widget, the only way to transfer a call is automatically though the provider console/portal."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:115
msgid "For more information on transfers, visit :ref:`voip/axivox/forwardings_tab`."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:117
msgid "To transfer a call within the Odoo *VoIP* phone widget, first, answer the call using the green :guilabel:`📞 (phone)` icon."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:120
msgid "Once the incoming call is answered, click the :guilabel:`↔ (left-right arrow)` icon. Then, enter the extension of the user the call should be forwarded to. Finally, click :guilabel:`Transfer` to route the call to that phone number."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:125
msgid "To find the extension for a user, consult the :abbr:`VoIP (Voice over Internet Protocol)` administrator, or, if the user has *Settings* access rights to *Administration*, navigate to :menuselection:`Settings App --> Manage Users --> Select the user --> Preferences --> VOIP --> VoIP username / Extension number`."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:130
msgid "For more information on access rights, visit: :doc:`../users/access_rights`."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:-1
msgid "Transferring a call within the phone widget, with the transfer buttons highlighted."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:137
msgid "Forward calls"
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:139
msgid "To forward a call within the Odoo *VoIP* phone widget, first, answer the call using the green :guilabel:`📞 (phone)` icon. Once the incoming call is answered, click the :guilabel:`↔ (left-right arrow)` icon."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:143
msgid "Then, enter the full phone number of the user the call should be forwarded to. Finally, click :guilabel:`Transfer` to route the call to that phone number."
msgstr ""
#: ../../content/applications/general/voip/transfer_forward.rst:147
msgid "For more information on forwarding, visit :ref:`voip/axivox/forwardings_tab`."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:3
msgid "VoIP widget"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:5
msgid "The *VoIP* widget is an add-on made available to Odoo users through the *VoIP* module. It is used to incorporate virtual telephony into the database. The widget is the control center for making and managing calls in Odoo."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:10
msgid "Phone calls"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:12
msgid "To make phone calls while in the Odoo database, click the :guilabel:`📞 (phone)` icon, located in the top navigation bar."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:15
msgid "When clicked, a :guilabel:`VOIP` pop-up widget appears in the lower-left corner of the Odoo database. The widget allows users to freely navigate throughout the database, while making and receiving calls."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:19
msgid "When receiving calls in Odoo, the :guilabel:`VOIP` widget rings,and displays a notification. To close the widget, click the :guilabel:`X (close)` icon in the upper-right of the widget's screen."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:23
msgid "The :abbr:`VoIP (Voice over Internet Protocol)` number is the one provided by Axivox. It can be accessed by navigating to `https://manage.axivox.com/ <https://manage.axivox.com/>`_. After logging into the portal, go to :menuselection:`Users --> Outgoing number` (column)."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:-1
msgid "VoIP call in Odoo."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:35
msgid "If a *Missing Parameter* error message appears in the Odoo *VoIP* widget, refresh the Odoo window, and try again."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:0
msgid "\"Missing Parameter\" error message in the Odoo softphone."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:43
msgid "If an *Incorrect Number* error message appears in the Odoo *VoIP* widget, make sure to use the international format, leading with the :guilabel:`+ (plus)` sign, followed by the international country code."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:47
msgid "(E.g., +16506913277, where `+1` is the international prefix for the United States.)"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:0
msgid "\"Incorrect Number\" error message in the Odoo softphone."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:54
msgid "Tabs"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:56
msgid "In all, there are three tabs (:guilabel:`Recent`, :guilabel:`Next Activities`, and :guilabel:`Contacts`) present in the *VoIP* widget, which are used for managing calls and day-to-day activities in Odoo."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:61
msgid "Recent"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:63
msgid "Under the :guilabel:`Recent` tab of the *VoIP* widget, the call history for the user is available. This includes incoming and outgoing calls. Any number can be clicked to begin a call."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:67
msgid "Next activities"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:69
msgid "Under the :guilabel:`Next Activities` tab of the *VoIP* widget, a user can see any activities assigned to them, and which ones are due to be completed for the day."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:72
msgid "Click an activity from this tab to perform any actions including: Sending an email, accessing their contact, scheduling another activity, or accessing a linked record (such as a Sales Order, Lead/Opportunity, or Project Task)."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:76
msgid "The user can also mark the activity as complete, edit the details of the activity, or cancel it."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:78
msgid "To call the customer related to a scheduled activity, click the :guilabel:`📞 (phone)` icon, or click the :guilabel:`⌨️ (keyboard)` icon to dial another number for the customer."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:-1
msgid "Activity control center on the VoIP widget."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:85
msgid "Some other icons appear in the *VoIP* widget, categorized by two sections: :guilabel:`Document` and :guilabel:`Activity`."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:88
msgid "Under the :guilabel:`Document` section, from right to left:"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:90
msgid ":guilabel:`➣ (paper airplane)` icon: sends an email"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:91
msgid ":guilabel:`👤 (person icon)` icon: redirects to the contact card"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:92
msgid ":guilabel:`📄 (document)` icon: redirects to the attached record in Odoo"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:93
msgid ":guilabel:`🕓 (clock)` icon: schedule an activity"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:95
msgid "Under the :guilabel:`Activity` section, from left to right:"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:97
msgid ":guilabel:`✔️ (checkmark)` icon: mark activity as done"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:98
msgid ":guilabel:`✏️ (pencil)` icon: edit the activity"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:99
msgid ":guilabel:`✖️ (cancel)` icon: cancel the activity"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:102
msgid "Contacts"
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:104
msgid "Under the :guilabel:`Contacts` tab of the *VoIP* widget, a user can access a contact in the *Contacts* app."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:107
msgid "Any contact can easily be called by clicking into the contact from the *VoIP* widget's :guilabel:`Contacts` tab."
msgstr ""
#: ../../content/applications/general/voip/voip_widget.rst:110
msgid "A search feature is also available in the upper-right side of the widget, represented by a :guilabel:`🔍 (magnifying glass)` icon."
msgstr ""
Reference in New Issue View Git Blame Copy Permalink