documentation/locale/uk/LC_MESSAGES/general.po
2024-03-24 02:40:29 +01:00

8837 lines
338 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.
#
# Translators:
# Martin Trigaux, 2024
# Wil Odoo, 2024
# Alina Lisnenko <alina.lisnenko@erp.co.ua>, 2024
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-03-20 10:19+0000\n"
"PO-Revision-Date: 2021-11-02 08:47+0000\n"
"Last-Translator: Alina Lisnenko <alina.lisnenko@erp.co.ua>, 2024\n"
"Language-Team: Ukrainian (https://app.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (n % 10 ==0 || (n % 10 >=5 && n % 10 <=9) || (n % 100 >=11 && n % 100 <=14 )) ? 2: 3);\n"
#: ../../content/applications/general.rst:3
msgid "General settings"
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/supported_versions>`. To "
"be able to use them, you must **upgrade** your app."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:50
msgid ""
"Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you "
"want to upgrade, then on *Upgrade*."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:56
msgid "Uninstall apps and modules"
msgstr ""
#: ../../content/applications/general/apps_modules.rst:58
msgid ""
"Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you "
"want to uninstall, then on *Uninstall*."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:64
msgid ""
"Some apps have dependencies, meaning that one app requires another. "
"Therefore, uninstalling one app may uninstall multiple apps and modules. "
"Odoo warns you which dependent apps and modules are affected by it."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:71
msgid "To complete the uninstallation, click on *Confirm*."
msgstr ""
#: ../../content/applications/general/apps_modules.rst:74
msgid ""
"Uninstalling an app also uninstalls all its dependencies and permanently "
"erases their data."
msgstr ""
#: ../../content/applications/general/companies.rst:5
msgid "Companies"
msgstr "Компанії"
#: ../../content/applications/general/companies.rst:7
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/companies.rst:13
msgid "Manage companies and records"
msgstr ""
#: ../../content/applications/general/companies.rst:15
msgid ""
"Go to :menuselection:`Settings --> Manage Companies` and fill in the form "
"with your companys 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/companies.rst-1
msgid "Overview of a new company's form in Odoo"
msgstr ""
#: ../../content/applications/general/companies.rst:24
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/companies.rst:0
msgid ""
"View of a web browser and the favicon for a specific company chosen in Odoo"
msgstr ""
#: ../../content/applications/general/companies.rst:33
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 companys 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/companies.rst-1
msgid "View of the companies menu through the main dashboard in Odoo"
msgstr ""
#: ../../content/applications/general/companies.rst:42
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/companies.rst:45
msgid "*A blank field*: the record is shared within all companies."
msgstr ""
#: ../../content/applications/general/companies.rst:46
msgid ""
"*Adding a company*: the record is visible to users logged in to that "
"specific company."
msgstr ""
#: ../../content/applications/general/companies.rst-1
msgid "View of a product's form emphasizing the company field in Odoo Sales"
msgstr ""
#: ../../content/applications/general/companies.rst:53
msgid "Employees' access"
msgstr ""
#: ../../content/applications/general/companies.rst:55
msgid ""
"Once companies are created, manage your employees' :doc:`Access Rights "
"<users/access_rights>` for *Multi Companies*."
msgstr ""
#: ../../content/applications/general/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/companies.rst:64
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/companies.rst:67
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/companies.rst:68
msgid "When **creating** a record, the company taken into account is:"
msgstr ""
#: ../../content/applications/general/companies.rst:70
msgid "The current company (the one active) or,"
msgstr ""
#: ../../content/applications/general/companies.rst:71
msgid "No company is set (on products and contacts forms for example) or,"
msgstr ""
#: ../../content/applications/general/companies.rst:72
msgid ""
"The company set is the one linked to the document (the same as if a record "
"is being edited)."
msgstr ""
#: ../../content/applications/general/companies.rst:75
msgid "Documents format"
msgstr ""
#: ../../content/applications/general/companies.rst:77
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/companies.rst-1
msgid ""
"View of the settings page emphasizing the document layout field in Odoo"
msgstr ""
#: ../../content/applications/general/companies.rst:85
msgid "Inter-Company Transactions"
msgstr "Операції між компаніями"
#: ../../content/applications/general/companies.rst:87
msgid ""
"First, make sure each one of your companies is properly set in relation to:"
msgstr ""
#: ../../content/applications/general/companies.rst:89
msgid ""
":doc:`Chart of Accounts "
"<../finance/accounting/get_started/chart_of_accounts>`"
msgstr ""
#: ../../content/applications/general/companies.rst:90
msgid ":doc:`Taxes <../finance/accounting/taxes>`"
msgstr ""
#: ../../content/applications/general/companies.rst:91
msgid ":doc:`Fiscal Positions <../finance/accounting/taxes/fiscal_positions>`"
msgstr ""
#: ../../content/applications/general/companies.rst:92
msgid ":doc:`Journals <../finance/accounting/bank>`"
msgstr ""
#: ../../content/applications/general/companies.rst:93
msgid ":doc:`Fiscal Localizations <../finance/fiscal_localizations>`"
msgstr ""
#: ../../content/applications/general/companies.rst:94
msgid ":doc:`Pricelists <../sales/sales/products_prices/prices/pricing>`"
msgstr ""
#: ../../content/applications/general/companies.rst:96
msgid ""
"Now, activate the *Inter-Company Transactions* option under *Settings*. With"
" the respective company *activated* and *selected*, choose if you would like"
" operations between companies to be synchronized at an invoice/bills level "
"or at a sales/purchase orders level."
msgstr ""
#: ../../content/applications/general/companies.rst-1
msgid ""
"View of the settings page emphasizing the inter company transaction field in"
" Odoo"
msgstr ""
#: ../../content/applications/general/companies.rst:104
msgid ""
"**Synchronize invoice/bills**: generates a bill/invoice when a company "
"confirms a bill/invoice for the selected company."
msgstr ""
#: ../../content/applications/general/companies.rst:107
msgid ""
"*Example:* an invoice posted on JS Store Belgium, for JS Store US, "
"automatically creates a vendor bill on the JS Store US, from the JS Store "
"Belgium."
msgstr ""
#: ../../content/applications/general/companies.rst-1
msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo"
msgstr ""
#: ../../content/applications/general/companies.rst:114
msgid ""
"**Synchronize sales/purchase order**: generates a drafted purchase/sales "
"order using the selected company warehouse when a sales/purchase order is "
"confirmed for the selected company. If instead of a drafted purchase/sales "
"order you rather have it validated, enable *Automatic Validation*."
msgstr ""
#: ../../content/applications/general/companies.rst:118
msgid ""
"*Example:* when a sale order for JS Store US is confirmed on JS Store "
"Belgium, a purchase order on JS Store Belgium is automatically created (and "
"confirmed if the *Automatic Validation* feature was enabled)."
msgstr ""
#: ../../content/applications/general/companies.rst-1
msgid ""
"View of the purchase created on JS Store US from JS Store Belgium in Odoo"
msgstr ""
#: ../../content/applications/general/companies.rst:127
msgid ""
"Products have to be configured as *Can be sold* and must be shared between "
"the companies."
msgstr ""
#: ../../content/applications/general/companies.rst:130
msgid ""
"Remember to test all workflows as an user other than the administrator."
msgstr ""
#: ../../content/applications/general/companies.rst:133
msgid ":doc:`Multi-company Guidelines </developer/howtos/company>`"
msgstr ""
#: ../../content/applications/general/companies.rst:134
msgid ":doc:`../finance/accounting/get_started/multi_currency`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:3
msgid "Digest Emails"
msgstr "Електронні пошти дайджесту"
#: ../../content/applications/general/companies/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/companies/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/companies/digest_emails.rst-1
msgid "Digest Emails section inside General Settings."
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:15
msgid "You can control a variety of settings for your Digest Emails, such as:"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:17
msgid "which KPIs are shared in the Digest"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:18
msgid "how often Digest Emails are sent"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:19
msgid "who in your organization receives Digest Emails"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:20
msgid "creating custom Digest Email templates"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:21
msgid "adding additional KPIs (Studio required)"
msgstr ""
#: ../../content/applications/general/companies/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/companies/digest_emails.rst:31
msgid "Customize *Your Odoo Periodic Digest*"
msgstr ""
#: ../../content/applications/general/companies/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/companies/digest_emails.rst:37
msgid ""
"A popup window appears and presents a variety of editable settings, which "
"include:"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:39
msgid "**Digest Title** - what you want your Digest Email to be called"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:40
msgid ""
"**Periodicity** - control the regimen in how often Digest Emails are sent"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:41
msgid ""
"**KPIs** - check/uncheck each calculated KPI that appears in Digest Emails"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:42
msgid "**Recipients** - add/remove users who receive your Digest Emails"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:43
msgid "**Custom** - add your own KPIs (Studio required)"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst-1
msgid "Customize default Digest Email settings and custom KPIs."
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:52
msgid "Custom digest emails"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:54
msgid "To do so, click on **Configure Digest Emails** and then **Create**."
msgstr ""
#: ../../content/applications/general/companies/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/companies/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/companies/digest_emails.rst:65
msgid "Custom KPIs with Studio"
msgstr ""
#: ../../content/applications/general/companies/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/companies/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/companies/digest_emails.rst:73
msgid ""
"In order to create additional fields, you must create two fields on the "
"digest object:"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:75
msgid ""
"create a boolean field called `kpi_myfield` and display it in the KPIs tab"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:76
msgid ""
"create a computed field called `kpi_myfield_value` that computes your "
"customized KPI"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:77
msgid "select your KPI(s) in the KPIs tab."
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:80
msgid "Computed values reference table"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:83
msgid "LABEL"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:83
msgid "VALUE"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:85
msgid "Connected Users"
msgstr "Підключені користувачі"
#: ../../content/applications/general/companies/digest_emails.rst:85
msgid "`kpi_res_users_connected_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:87
msgid "Messages Sent"
msgstr "Повідомлення надіслані"
#: ../../content/applications/general/companies/digest_emails.rst:87
msgid "`kpi_mail_message_total_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:89
msgid "New Leads"
msgstr "Нові ліди"
#: ../../content/applications/general/companies/digest_emails.rst:89
msgid "`kpi_crm_lead_created_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:91
msgid "Opportunities Won"
msgstr "Впіймані нагоди"
#: ../../content/applications/general/companies/digest_emails.rst:91
msgid "`kpi_crm_opportunities_won_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:93
msgid "Open Tasks"
msgstr "Відкрити завдання"
#: ../../content/applications/general/companies/digest_emails.rst:93
msgid "`kpi_project_task_opened_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:95
msgid "Tickets Closed"
msgstr "Закриті заявки"
#: ../../content/applications/general/companies/digest_emails.rst:95
msgid "`kpi_helpdesk_tickets_closed_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:97
msgid "% of Happiness"
msgstr "% вдоволення"
#: ../../content/applications/general/companies/digest_emails.rst:97
msgid "`kpi_livechat_rating_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:99
msgid "Conversations handled"
msgstr "Оброблені розмови"
#: ../../content/applications/general/companies/digest_emails.rst:99
msgid "`kpi_livechat_conversations_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:101
msgid "Time to answer (sec)"
msgstr "Час на відповідь (сек)"
#: ../../content/applications/general/companies/digest_emails.rst:101
msgid "`kpi_livechat_response_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:103
msgid "All Sales"
msgstr "Усі продажі"
#: ../../content/applications/general/companies/digest_emails.rst:103
msgid "`kpi_all_sale_total_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:105
msgid "eCommerce Sales"
msgstr "Продажі електронної комерції"
#: ../../content/applications/general/companies/digest_emails.rst:105
msgid "`kpi_website_sale_total_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:107
msgid "Revenue"
msgstr "Дохід"
#: ../../content/applications/general/companies/digest_emails.rst:107
msgid "`kpi_account_total_revenue_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:109
msgid "Bank & Cash Moves"
msgstr "Банківські та готівкові переміщення"
#: ../../content/applications/general/companies/digest_emails.rst:109
msgid "`kpi_account_bank_cash_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:111
msgid "POS Sales"
msgstr "Продажі точки продажу"
#: ../../content/applications/general/companies/digest_emails.rst:111
msgid "`kpi_pos_total_value`"
msgstr ""
#: ../../content/applications/general/companies/digest_emails.rst:113
msgid "New Employees"
msgstr "Нові співробітники"
#: ../../content/applications/general/companies/digest_emails.rst:113
msgid "`kpi_hr_recruitment_new_colleagues_value`"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:3
msgid "Email templates"
msgstr "Шаблони електронних листів"
#: ../../content/applications/general/companies/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/companies/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/companies/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/companies/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/companies/email_template.rst:23
msgid "Editing email templates"
msgstr ""
#: ../../content/applications/general/companies/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/companies/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/companies/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/companies/email_template.rst:37
msgid "Powerbox"
msgstr ""
#: ../../content/applications/general/companies/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/companies/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/companies/email_template.rst:46
msgid ":guilabel:`Basic Blocks`"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:48
msgid ":guilabel:`Heading 1`: Big section heading."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:49
msgid ":guilabel:`Heading 2`: Medium section heading."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:50
msgid ":guilabel:`Heading 3`: Small section heading."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:51
msgid ":guilabel:`Text`: Paragraph block."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:52
msgid ":guilabel:`Bulleted list`: Create a simple bulleted list."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:53
msgid ":guilabel:`Numbered list`: Create a list with numbering."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:54
msgid ":guilabel:`Checklist`: Track tasks with a checklist."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:55
msgid ":guilabel:`Table`: Insert a table."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:56
msgid ":guilabel:`Switch direction`: Switch the text's direction."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:57
msgid ":guilabel:`Separator`: Insert a horizontal rule separator."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:58
msgid ":guilabel:`Quote`: Add a blockquote section."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:59
msgid ":guilabel:`Code`: Add a code section."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:60
msgid ":guilabel:`Appointment`: Add a specific appointment."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:61
msgid ":guilabel:`Calendar`: Schedule an appointment."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:63
msgid ":guilabel:`Navigation`"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:65
msgid ":guilabel:`Link`: Add a link."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:66
msgid ":guilabel:`Button`: Add a button."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:68
msgid ":guilabel:`Medias`"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:70
msgid ":guilabel:`Image`: Insert an image."
msgstr ""
#: ../../content/applications/general/companies/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/companies/email_template.rst:0
msgid "Powerbox feature in the email template."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:83
msgid "XML/HTML code editor"
msgstr ""
#: ../../content/applications/general/companies/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/companies/email_template.rst-1
msgid "HTML editor in the email template."
msgstr ""
#: ../../content/applications/general/companies/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/companies/email_template.rst:100
msgid "Dynamic placeholders"
msgstr ""
#: ../../content/applications/general/companies/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/companies/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/companies/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/companies/email_template.rst:116
msgid ""
"Dynamic placeholders can be used with the following fields on an email "
"template:"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:118
msgid ":guilabel:`Subject` (:guilabel:`Content` tab)"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:119
msgid ":guilabel:`From` (:guilabel:`Email Configuration` tab)"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:120
msgid ":guilabel:`To (Emails)` (:guilabel:`Email Configuration` tab)"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:121
msgid ":guilabel:`To (Partners)` (:guilabel:`Email Configuration` tab)"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:122
msgid ":guilabel:`CC` (:guilabel:`Email Configuration` tab)"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:123
msgid ":guilabel:`Reply-To` (:guilabel:`Email Configuration` tab)"
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:124
msgid ":guilabel:`Language` (:guilabel:`Advanced Settings` tab)"
msgstr ""
#: ../../content/applications/general/companies/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/companies/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/companies/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/companies/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/companies/email_template.rst:149
msgid ":doc:`/applications/studio/models_modules_apps`."
msgstr ""
#: ../../content/applications/general/companies/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/companies/email_template.rst:0
msgid "Backend information box of fields on a model."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:163
msgid ""
":ref:`Views and fields in the developer documentation <developer/fields>`."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:166
msgid "Customizing email templates are out of the scope of Odoo Support."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:169
msgid "Default reply on email templates"
msgstr ""
#: ../../content/applications/general/companies/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/companies/email_template.rst:176
msgid ""
"A Add multiple email addresses by adding a comma `,` between the addresses "
"or dynamic placeholders."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst-1
msgid "Reply-to field on template."
msgstr ""
#: ../../content/applications/general/companies/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/companies/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/companies/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/companies/email_template.rst-1
msgid "Email composer in mass mailing mode with reply-to highlighted."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:201
msgid "Transactional emails and corresponding URLs"
msgstr ""
#: ../../content/applications/general/companies/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/companies/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/companies/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/companies/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/companies/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/companies/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/companies/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/companies/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/companies/email_template.rst:242
msgid ""
"For more information about how to configure domains, check out the "
":doc:`domain name documentation "
"</applications/websites/website/configuration/domain_names>`."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:246
msgid "Updating translations within email templates"
msgstr ""
#: ../../content/applications/general/companies/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/companies/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/companies/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/companies/email_template.rst-1
msgid "Edit the language of a template."
msgstr ""
#: ../../content/applications/general/companies/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/companies/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/companies/email_template.rst-1
msgid "Translation of the body of the Appointment Booked template."
msgstr ""
#: ../../content/applications/general/companies/email_template.rst:278
msgid ""
"When editing the translations, the default language set in the database "
"appears in **bold**."
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/email_communication.rst:5
msgid "Email communication"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:3
msgid "Connect Microsoft Outlook 365 to Odoo using Azure OAuth"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:5
msgid ""
"Odoo is compatible with Microsoft's Azure OAuth for Microsoft 365. In order "
"to send and receive secure emails from a custom domain, all that is required"
" is to configure a few settings on the Azure platform and on the back end of"
" the Odoo database. This configuration works with either a personal email "
"address or an address created by a custom domain."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:11
msgid ""
"`Microsoft Learn: Register an application with the Microsoft identity "
"platform <https://learn.microsoft.com/azure/active-"
"directory/develop/quickstart-register-app>`_"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:15
msgid ":doc:`/applications/general/users/azure`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:16
msgid ":doc:`/applications/productivity/calendar/outlook`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:19
msgid "Setup in Microsoft Azure Portal"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:22
#: ../../content/applications/general/users/azure.rst:40
msgid "Create a new application"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:24
msgid ""
"To get started, 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 the personal "
":guilabel:`Microsoft account`. A user with administrative access to the "
"Azure Settings will need to connect and perform the following configuration."
" Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID`"
" (formally *Azure Active Directory*)."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:30
msgid ""
"Now, click on :guilabel:`Add (+)`, located in the top menu, and then select "
":guilabel:`App registration`. On the :guilabel:`Register an application` "
"screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. "
"Under the :guilabel:`Supported account types` section select "
":guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID "
"directory - Multitenant) and personal Microsoft accounts (e.g. Skype, "
"Xbox)`."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:36
msgid ""
"Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the "
"platform, and then input `https://<odoo base url>/microsoft_outlook/confirm`"
" in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at "
"which your Odoo instance can be reached in the URL field."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:41
msgid ""
"*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the "
"database's subdomain, assuming it's hosted on Odoo.com"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:44
msgid ""
"After the URL has been added to the field, :guilabel:`Register` the "
"application so it is created."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:47
msgid "API permissions"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:49
msgid ""
"The :guilabel:`API permissions` should be set next. Odoo will need specific "
"API permissions to be able to read (IMAP) and send (SMTP) emails in the "
"Microsoft 365 setup. First, click the :guilabel:`API permissions` link, "
"located in the left menu bar. Next, click on the :guilabel:`(+) Add a "
"Permission` button and select :guilabel:`Microsoft Graph` under "
":guilabel:`Commonly Used Microsoft APIs`. After, select the "
":guilabel:`Delegated Permissions` option."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:55
msgid ""
"In the search bar, search for the following :guilabel:`Delegated "
"permissions` and click :guilabel:`Add permissions` for each one:"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:58
msgid ":guilabel:`SMTP.Send`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:59
msgid ":guilabel:`IMAP.AccessAsUser.All`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:62
msgid "The :guilabel:`User.Read` permission will be added by default."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst-1
msgid ""
"API permissions needed for Odoo integration are listed under the Microsoft "
"Graph."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:69
msgid "Assign users and groups"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:71
msgid ""
"After adding the API permissions, navigate back to the :guilabel:`Overview` "
"of the :guilabel:`Application` in the top of the left sidebar menu."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:74
msgid ""
"Now, add users to this application. Under the :guilabel:`Essentials` "
"overview table, click on the link labeled :guilabel:`Managed Application in "
"Local Directory`, or the last option on the bottom right-hand side of the "
"table."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst-1
msgid ""
"Add users/groups by clicking the Managed application in local directory link for the\n"
"created application."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:83
msgid ""
"In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click "
"on :guilabel:`(+) Add User/Group`. Depending on the account, either a "
":guilabel:`Group` and a :guilabel:`User` can be added, or only "
":guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` "
"to be added."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:88
msgid ""
"Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None "
"Selected` and add the users or group of users that will be sending emails "
"from the :guilabel:`Microsoft account` in Odoo. :guilabel:`Add` the "
"users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to "
"the application."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:94
msgid "Create credentials"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:96
msgid ""
"Now that the Microsoft Azure app is set up, credentials need to be created "
"for the Odoo setup. These include the :guilabel:`Client ID` and "
":guilabel:`Client Secret`. To start, the :guilabel:`Client ID` can be copied"
" from the :guilabel:`Overview` page of the app. The :guilabel:`Client ID` or"
" :guilabel:`Application ID` is located under the :guilabel:`Display Name` in"
" the :guilabel:`Essentials` overview of the app."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst-1
msgid "Application/Client ID located in the Overview of the app."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:106
msgid ""
"Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this"
" value, click on :guilabel:`Certificates & Secrets` in the left sidebar "
"menu. Then, a :guilabel:`Client Secret` needs to be produced. In order to do"
" this, click on the :guilabel:`(+) New Client Secret` button."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:110
msgid ""
"A window on the right will populate with a button labeled :guilabel:`Add a "
"client secret`. Under :guilabel:`Description`, type in `Odoo Fetchmail` or "
"something recognizable, and then set the :guilabel:`expiration date`."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:115
msgid ""
"A new :guilabel:`Client Secret` will need to be produced and configured if "
"the first one expires. In this event, there could be an interruption of "
"service, so the expiration date should be noted and set to the furthest "
"possible date."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:119
msgid ""
"Next, click on :guilabel:`Add` when these two values are entered. A "
":guilabel:`Client Secret Value` and :guilabel:`Secret ID` will be created. "
"It is important to copy the :guilabel:`Value` or :guilabel:`Client Secret "
"Value` into a notepad as it will become encrypted after leaving this page. "
"The :guilabel:`Secret ID` is not needed."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst-1
msgid "Client Secret Value or Value in the app's credentials."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:128
msgid ""
"After these steps, the following items should be ready to be set up in Odoo:"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:130
msgid "A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:131
msgid "A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:133
msgid ""
"This completes the setup on the :guilabel:`Microsoft Azure Portal` side."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:136
#: ../../content/applications/general/email_communication/google_oauth.rst:111
msgid "Setup in Odoo"
msgstr "Налаштування в Odoo"
#: ../../content/applications/general/email_communication/azure_oauth.rst:139
msgid "Enter Microsoft Outlook credentials"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:141
msgid ""
"First, open the Odoo database and navigate to the :guilabel:`Apps` module. "
"Then, remove the :guilabel:`Apps` filter from the search bar and type in "
"`Outlook`. After that, install the module called :guilabel:`Microsoft "
"Outlook`."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:145
msgid ""
"Next, navigate to :menuselection:`Settings --> General Settings`, and under "
"the :guilabel:`Discuss` section, ensure that the checkbox for "
":guilabel:`Custom Email Servers` is checked. This populates a new option for"
" :guilabel:`Outlook Credentials`."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:149
msgid ":guilabel:`Save` the progress."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:151
msgid ""
"Then, copy and paste the :guilabel:`Client ID` (Application ID) and "
":guilabel:`Client Secret (Client Secret Value)` into the respective fields "
"and :guilabel:`Save` the settings."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst-1
msgid "Outlook Credentials in Odoo General Settings."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:159
#: ../../content/applications/general/email_communication/google_oauth.rst:127
msgid "Configure outgoing email server"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:161
msgid ""
"On the :guilabel:`General Settings` page, under the :guilabel:`Custom Email "
"Servers` setting, click the :guilabel:`Outgoing Email Servers` link to "
"configure the Microsoft account."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:164
msgid ""
"Then, create a new email server and check the box for :guilabel:`Outlook`. "
"Next, fill in the :guilabel:`Name` (it can be anything) and the Microsoft "
"Outlook email :guilabel:`Username`."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:167
msgid ""
"If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain "
"or email address <email_communication/default>`."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:170
msgid "Then, click on :guilabel:`Connect your Outlook account`."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:172
msgid ""
"A new window from Microsoft opens to complete the :guilabel:`authorization "
"process`. Select the appropriate email address that is being configured in "
"Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst-1
msgid "Permission page to grant access between newly created app and Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:179
msgid ""
"Then, allow Odoo to access the Microsoft account by clicking on "
":guilabel:`Yes`. After this, the page will navigate back to the newly "
"configured :guilabel:`Outgoing Mail Server` in Odoo. The configuration "
"automatically loads the :guilabel:`token` in Odoo, and a tag stating "
":guilabel:`Outlook Token Valid` appears in green."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst-1
msgid "Valid Outlook Token indicator."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:188
msgid ""
"Finally, click :guilabel:`Test Connection`. A confirmation message should "
"appear. The Odoo database can now send safe, secure emails through Microsoft"
" Outlook using OAuth authentication."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:194
msgid "Configuration with a single outgoing mail server"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:196
msgid ""
"Configuring a single outgoing server is the simplest configuration available"
" for Microsoft Azure and it doesn't require extensive access rights for the "
"users in the database."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:199
msgid ""
"A generic email address would be used to send emails for all users within "
"the database. For example it could be structured with a `notifications` "
"alias (`notifications@example.com`) or `contact` alias "
"(`contact@example.com`). This address must be set as the :guilabel:`FROM "
"Filtering` on the server. This address must also match the "
"`{mail.default.from}@{mail.catchall.domain}` key combination in the system "
"parameters."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:206
#: ../../content/applications/general/email_communication/azure_oauth.rst:247
msgid ""
"For more information on the from filter visit: "
":ref:`email_communication/default`."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:209
#: ../../content/applications/general/email_communication/azure_oauth.rst:254
msgid ""
"The :guilabel:`System Parameters` can be accessed by activating "
":ref:`developer-mode` in the :menuselection:`Settings --> Technical --> "
"Parameters --> System Parameters` menu."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:212
msgid ""
"When using this configuration, every email that is sent from the database "
"will use the address of the configured `notification` mailbox. However it "
"should be noted that the name of the sender will appear but their email "
"address will change:"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst-1
msgid "Name from real sender with static email."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:221
msgid "Single outgoing mail server configuration:"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:223
msgid ""
"Outgoing mail server **username** (login) = `notifications@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:224
msgid ""
"Outgoing mail server :guilabel:`FROM Filtering` = "
"`notifications@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:225
#: ../../content/applications/general/email_communication/azure_oauth.rst:279
msgid "`mail.catchall.domain` in system parameters = `example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:226
#: ../../content/applications/general/email_communication/azure_oauth.rst:280
msgid "`mail.default.from` in system parameters = `notifications`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:229
msgid "User-specific (multiple user) configuration"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:231
msgid ""
"In addition to a generic email server, individual email servers can be set "
"up for users in a database. These email addresses must be set as the "
":guilabel:`FROM Filtering` on each individual server for this configuration "
"to work."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:235
msgid ""
"This configuration is the more difficult of the two Microsoft Azure "
"configurations, in that it requires all users configured with email servers "
"to have access rights to settings in order to establish a connection to the "
"email server."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:240
#: ../../content/applications/general/iot/config/pos.rst:21
#: ../../content/applications/general/iot/config/troubleshooting.rst:456
msgid "Setup"
msgstr "Встановлення"
#: ../../content/applications/general/email_communication/azure_oauth.rst:242
msgid ""
"Each user should have a separate email server set up. The :guilabel:`FROM "
"Filtering` should be set so that only the user's email is sent from that "
"server. In other words, only a user with an email address that matches the "
"set :guilabel:`FROM Filtering` is able to use this server."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:249
msgid ""
"A :ref:`fallback server <azure_oauth/notifications>` must be setup to allow "
"for the sending of :guilabel:`notifications`. The :guilabel:`FROM Filtering`"
" for this server should have the value of the "
"`{mail.default.from}@{mail.catchall.domain}`."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:258
msgid ""
"The configuration for this transactional email server can work alongside an "
"outgoing mass-mailing email server. The :guilabel:`FROM Filtering` for the "
"mass-mailing email server can remain empty, but it's require to be added in "
"the settings of the *Email Marketing* application."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:263
msgid ""
"For more information on setting the mass-mailing email server visit "
":ref:`email_communication/mass_mails`."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:267
msgid "Multiple user outgoing mail server configuration:"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:270
msgid "User #1 mailbox"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:270
msgid "Outgoing mail server #1 **username** (login) = `john@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:271
msgid ""
"Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:273
msgid "User #2 mailbox"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:273
msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:274
msgid ""
"Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:276
msgid "Notifications mailbox"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:276
msgid ""
"Outgoing mail server #3 **username** (login) = `notifications@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:277
msgid ""
"Outgoing mail server #3 :guilabel:`FROM Filtering` = "
"`notifications@example.com`"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:279
msgid "System Parameters"
msgstr "Параметри системи"
#: ../../content/applications/general/email_communication/azure_oauth.rst:283
msgid "Configure incoming email server"
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:285
msgid ""
"The incoming account should be configured in a similar way to the outgoing "
"email account. Navigate to the :guilabel:`Incoming Mail Servers` in the "
":guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check"
" or Select the button next to :guilabel:`Outlook Oauth Authentication` and "
"enter the :guilabel:`Microsoft Outlook username`. Click on "
":guilabel:`Connect your Outlook account`. Odoo will state: "
":guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the "
"account. The account should be ready to receive email to the Odoo database."
msgstr ""
#: ../../content/applications/general/email_communication/azure_oauth.rst:293
msgid ":doc:`email_servers`"
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** that do "
"not 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 administrator, 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:68
msgid ":doc:`google_oauth`"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:69
msgid ":doc:`azure_oauth`"
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 <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 ""
"Odoo покладається на загальні псевдоніми електронної пошти, щоб отримувати "
"вхідні повідомлення."
#: ../../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 do not 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 will not 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_servers.rst:278
msgid "Allow alias domain system parameter"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:280
msgid ""
"Incoming aliases are set in the Odoo database to create records by receiving"
" incoming emails. To view aliases set in the Odoo database, first activate "
"the :ref:`developer mode <developer-mode>`. Then, go to "
":menuselection:`Settings app --> Technical --> Email section --> Aliases`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:284
msgid ""
"The following system parameter, `mail.catchall.domain.allowed`, set with "
"allowed alias domain values, separated by commas, filters out correctly "
"addressed emails to aliases. Setting the domain(s) for which the alias can "
"create a ticket, lead, opportunity, etc., eliminates false positives where "
"email addresses with only the prefix alias (not the domain) are present."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:289
msgid ""
"In some instances, matches have been made in the Odoo database when an email"
" is received with the same alias prefix and a different domain on the "
"incoming email address. This is true in the sender, recipient, and :abbr:`CC"
" (Carbon Copy)` email addresses of an incoming email."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:294
msgid ""
"When Odoo receives emails that have the name `commercial` prefix alias in "
"the sender, recipient, or :abbr:`CC (Carbon Copy)` email address(es) (e.g. "
"commercial@gmail.com, commercial@odoo.net), the database falsely treats the "
"email as the full `commercial` alias (with a different domain), and "
"therefore, creates a ticket/lead/opportunity/etc."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:299
msgid ""
"To add the `mail.catchall.domain.allowed` system parameter, first, activate "
"the :ref:`developer mode <developer-mode>`. Then, go to "
":menuselection:`Settings app --> Technical --> Parameters section --> System"
" Parameters`. Click :guilabel:`Create`. Then, type in "
"`mail.catchall.domain.allowed` for the :guilabel:`Key` field."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:304
msgid ""
"Next, for the :guilabel:`Value` field, add the domain(s) separated by "
"comma(s) (if plural domains). Manually :guilabel:`Save`, and the system "
"parameter takes immediate effect."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst-1
msgid ""
"mail.catchall.domain.allowed system parameter set with key and value "
"highlighted."
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/email_communication/google_oauth.rst:3
msgid "Connect Gmail to Odoo using Google OAuth"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:5
msgid ""
"Odoo is compatible with Google's OAuth for Gmail. In order to send secure "
"emails from a custom domain, all that is required is to configure a few "
"settings on Google's *Workspace* platform, as well as on the back end of the"
" Odoo database. This configuration works by using either a personal email "
"address or an address created by a custom domain."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:11
msgid ""
"For more information, visit `Google's documentation "
"<https://support.google.com/cloud/answer/6158849>`_ on setting up OAuth."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:15
msgid ":doc:`/applications/general/users/google`"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:16
#: ../../content/applications/general/users/google.rst:18
msgid ":doc:`/applications/productivity/calendar/google`"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:19
msgid "Setup in Google"
msgstr "Встановлення в Google"
#: ../../content/applications/general/email_communication/google_oauth.rst:22
msgid "Create a new project"
msgstr "Створіть новий проект"
#: ../../content/applications/general/email_communication/google_oauth.rst:24
msgid ""
"To get started, go to the `Google API Console "
"<https://console.developers.google.com>`_. Log in with your *Google "
"Workspace* account if you have one, otherwise log in with your personal "
"Gmail account (this should match the email address you want to configure in "
"Odoo)."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:28
msgid ""
"After that, click on :guilabel:`Create Project`, located on the far right of"
" the :guilabel:`OAuth consent screen`. If a project has already been created"
" in this account, then the :guilabel:`New Project` option will be located on"
" the top right under the :guilabel:`Select a project` drop-down menu."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:33
msgid ""
"On the :menuselection:`New Project` screen, rename the :guilabel:`Project "
"name` to `Odoo` and browse for the :guilabel:`Location`. Set the "
":guilabel:`Location` as the *Google Workspace organization*. If you are "
"using a personal Gmail account, then leave the :guilabel:`Location` as "
":guilabel:`No Organization`."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst-1
msgid "Project Name and Location for Google OAuth."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:42
msgid "Click on :guilabel:`Create` to finish this step."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:45
#: ../../content/applications/general/users/google.rst:48
msgid "OAuth consent screen"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:47
msgid ""
"If the page doesn't redirect to the :menuselection:`User Type` options, "
"click on :guilabel:`OAuth consent screen` in the left menu."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:50
msgid ""
"Under :guilabel:`User Type` options, select the appropriate :guilabel:`User "
"Type`, and then click on :guilabel:`Create` again, which will finally "
"navigate to the :menuselection:`Edit app registration` page."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:55
#: ../../content/applications/general/users/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/email_communication/google_oauth.rst:59
#: ../../content/applications/general/users/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/email_communication/google_oauth.rst:63
msgid "Edit app registration"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:65
msgid "Next we will configure the app registration of the project."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:67
msgid ""
"On the :guilabel:`OAuth consent screen` step, under the :guilabel:`App "
"information` section, enter `Odoo` in the :guilabel:`App name` field. Select"
" the organization's email address under the :guilabel:`User support` email "
"field."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:71
msgid ""
"Next, under :menuselection:`App Domain --> Authorized domains`, click on "
":guilabel:`Add Domain` and enter `odoo.com`."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:74
msgid ""
"After that, under the :guilabel:`Developer contact information` section, "
"enter the organization's email address. Google uses this email address to "
"notify the organization about any changes to your project."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:78
msgid ""
"Next, click on the :guilabel:`Save and Continue` button. Then, skip the "
":menuselection:`Scopes` page by scrolling to the bottom and clicking on "
":guilabel:`Save and Continue`."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:81
msgid ""
"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/email_communication/google_oauth.rst:85
msgid ""
"Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard` to "
"finish setting up the project."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:89
msgid "Create Credentials"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:91
msgid ""
"Now that the project is set up, credentials should be created, which "
"includes the *Client ID* and *Client Secret*. First, click on "
":guilabel:`Credentials` in the left sidebar menu."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:94
msgid ""
"Then, click on :guilabel:`Create Credentials` in the top menu and select "
":guilabel:`OAuth client ID` from the dropdown menu."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:97
msgid ""
"Under :guilabel:`Application Type`, select :guilabel:`Web Application` from "
"the dropdown menu."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:98
msgid "In the :guilabel:`Name` field, enter `Odoo`."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:99
msgid ""
"Under the :guilabel:`Authorized redirect URIs` label, click the button "
":guilabel:`ADD URI`, and then input "
"`https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1`"
" field. Be sure to replace the *yourdbname* part of the URL with the actual "
"Odoo database name."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:102
msgid ""
"Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID`"
" and :guilabel:`Client Secret`. Finally, copy each generated value for later"
" use when configuring in Odoo, and then navigate to the Odoo database."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst-1
msgid "Client ID and Client Secret for Google OAuth."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:114
msgid "Enter Google Credentials"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:116
msgid ""
"First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove "
"the :guilabel:`Apps` filter from the search bar and type in `Google`. "
"Install the module called :guilabel:`Google Gmail`."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:120
msgid ""
"Next, navigate to :menuselection:`Settings --> General Settings`, and under "
"the :guilabel:`Discuss` section, ensure that the checkbox for "
":guilabel:`Custom Email Servers` or :guilabel:`External Email Servers` is "
"checked. This populates a new option for :guilabel:`Gmail Credentials` or "
":guilabel:`Use a Gmail Sever`. Then, copy and paste the respective values "
"into the :guilabel:`Client ID` and :guilabel:`Client Secret` fields and "
":guilabel:`Save` the settings."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:129
msgid ""
"To configure the external Gmail account, return to the top of the "
":guilabel:`Custom Email Servers` setting and then click the "
":guilabel:`Outgoing Email Servers` link."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst-1
msgid "Configure Outgoing Email Servers in Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:136
msgid ""
"Then, click on :guilabel:`New` or :guilabel:`Create` to create a new email "
"server, and fill in the :guilabel:`Name`, :guilabel:`Description`, and the "
"email :guilabel:`Username` (if required)."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:139
msgid ""
"Next, click on :guilabel:`Gmail OAuth Authentication` or :guilabel:`Gmail` "
"(under the :guilabel:`Authenticate with` or :guilabel:`Connection` section)."
" Finally, click on :guilabel:`Connect your Gmail Account`."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:143
msgid ""
"A new window labeled :guilabel:`Google` opens to complete the authorization "
"process. Select the appropriate email address that is being configured in "
"Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:146
msgid ""
"If the email address is a personal account, then an extra step pops up, so "
"click :guilabel:`Continue` to allow the verification and connect the Gmail "
"account to Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:149
msgid ""
"Then, allow Odoo to access the Google account by clicking on "
":guilabel:`Continue` or :guilabel:`Allow`. After that, the page navigates "
"back to the newly configured outgoing email server in Odoo. The "
"configuration automatically loads the token in Odoo, and a tag stating "
":guilabel:`Gmail Token Valid` appears in green."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:158
msgid ""
"Finally, :guilabel:`Test the Connection`. A confirmation message should "
"appear. The Odoo database can now send safe, secure emails through Google "
"using OAuth authentication."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:162
msgid "Google OAuth FAQ"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:165
msgid "Production VS Testing Publishing Status"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:167
msgid ""
"Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` "
"(instead of :guilabel:`Testing`) will display the following warning message:"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst-1
msgid "OAuth is Limited to 100 Sensitive Scope Logins."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:174
msgid ""
"To correct this warning, navigate to the `Google API Platform "
"<https://console.cloud.google.com/apis/credentials/consent>`_. If the "
":guilabel:`Publishing status` is :guilabel:`In Production`, click "
":guilabel:`Back to Testing` to correct the issue."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:179
msgid "No Test Users Added"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:181
msgid ""
"If no test users are added to the OAuth consent screen, then a 403 access "
"denied error will populate."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst-1
msgid "403 Access Denied Error."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:188
msgid ""
"To correct this error, return to the :guilabel:`OAuth consent screen` under "
":guilabel:`APIs & Services` and add test user(s) to the app. Add the email "
"that you are configuring in Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:192
msgid "Gmail Module not updated"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:194
msgid ""
"If the *Google Gmail* module in Odoo has not been updated to the latest "
"version, then a :guilabel:`Forbidden` error message populates."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst-1
msgid ""
"Forbidden you don't have the permission to access the requested resource."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:201
msgid ""
"To correct this error, go to the :menuselection:`Apps` module and clear out "
"the search terms. Then, search for `Gmail` or `Google` and upgrade the "
":guilabel:`Google Gmail` module. Finally, click on the three dots on the "
"upper right of the module and select :guilabel:`Upgrade`."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:206
msgid "Application Type"
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:208
msgid ""
"When creating the credentials (OAuth *Client ID* and *Client Secret*), if "
":guilabel:`Desktop App` is selected for the :guilabel:`Application Type`, an"
" :guilabel:`Authorization Error` appears."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst-1
msgid "Error 400 Redirect URI Mismatch."
msgstr ""
#: ../../content/applications/general/email_communication/google_oauth.rst:215
msgid ""
"To correct this error, delete the credentials already created and create new"
" credentials, selecting :guilabel:`Web Application` for the "
":guilabel:`Application Type`. Then, under :guilabel:`Authorized redirect "
"URIs`, click :guilabel:`ADD URI` and type: "
"`https://yourdbname.odoo.com/google_gmail/confirm` in the field, being sure "
"to replace *yourdbname* in the URL with the Odoo database name."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:3
msgid "Mailjet API"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:5
msgid ""
"Odoo is compatible with Mailjet's :abbr:`API (Application Programming "
"Interface)` for mass mailing. Set up a dedicated mass mailing server through"
" Mailjet by configuring settings in the Mailjet account and the Odoo "
"database. In some circumstances, settings need to be configured on the "
"custom domain's :abbr:`DNS (Domain Name System)` settings as well."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:11
msgid "Set up in Mailjet"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:14
msgid "Create API credentials"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:16
msgid ""
"To get started, sign in to the `Mailjet Account Information "
"<https://app.mailjet.com/account>`_ page. Next, navigate to the "
":guilabel:`Senders & Domains` section and click on :guilabel:`SMTP and SEND "
"API Settings`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst-1
msgid ""
"SMTP and Send API Settings link in the Senders & Domains section of Mailjet."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:24
msgid ""
"Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration "
"settings onto a notepad. They can be found under the "
":guilabel:`Configuration (SMTP only)` section. The :abbr:`SMTP (Simple Mail "
"Transfer Protocol)` configuration settings include the server address, the "
"security option needed (Use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS "
"(Transport Layer Security)`), and the port number. The settings are needed "
"to configure Mailjet in Odoo, which is covered in the :ref:`last section "
"<maintain/mailjet-api/odoo-setup>`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:32
msgid ""
"`Mailjet: How can I configure my SMTP parameters? "
"<https://documentation.mailjet.com/hc/articles/360043229473>`_"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:36
msgid ""
"Odoo blocks `port 25` on Odoo Online and Odoo.sh databases. :ref:`See "
"reference here <email_servers/restriction>`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst-1
msgid "SMTP configuration from Mailjet."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:43
msgid ""
"Next, click on the button labeled :guilabel:`Retrieve your API credentials` "
"to retrieve the Mailjet API credentials."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:46
msgid ""
"Then, click on the eye icon to reveal the :guilabel:`API key`. Copy this key"
" to a notepad, as this serves as the :guilabel:`Username` in the Odoo "
"configuration. Next, click on the :guilabel:`Generate Secret Key` button to "
"generate the :guilabel:`Secret Key`. Copy this key to a notepad, as this "
"serves as the :guilabel:`Password` in the Odoo configuration."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:52
msgid "Add verified sender address(es)"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:54
msgid ""
"The next step is to add a sender address or a domain to the Mailjet account "
"settings so that the email address or domain is approved to send emails "
"using Mailjet's servers. First, navigate to the `Mailjet Account Information"
" <https://app.mailjet.com/account>`_ page. Next, click on the :guilabel:`Add"
" a Sender Domain or Address` link under the :guilabel:`Senders & Domains` "
"section."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst-1
msgid "Add a sender domain or address in the Mailjet interface."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:63
msgid ""
"Determine if a sender's email address or the entire domain needs to be added"
" to the Mailjet settings. It may be easier to configure the domain as a "
"whole if :abbr:`DNS (Domain Name System)` access is available. Jump to the "
":ref:`Add a domain <maintain/mailjet-api/add-domain>` section for steps on "
"adding the domain."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:69
msgid ""
"Either all email addresses of the Odoo database users who are sending emails"
" using Mailjet's servers need to be configured or the domain(s) of the "
"users' email addresses can be configured."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:72
msgid ""
"By default, the email address originally set up in the Mailjet account is "
"added as a trusted sender. To add another email address, click on the button"
" labeled :guilabel:`Add a sender address`. Then, add the email address that "
"is configured to send from the custom domain."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:76
msgid ""
"At minimum the following email addresses should be set up in the provider "
"and verified in Mailjet:"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:78
msgid "notifications\\@yourdomain.com"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:79
msgid "bounce\\@yourdomain.com"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:80
msgid "catchall\\@yourdomain.com"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:83
msgid ""
"Replace `yourdomain` with the custom domain for the Odoo database. If there "
"isn't one, then use the :guilabel:`mail.catchall.domain` system parameter."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:86
msgid ""
"After that, fill out the :guilabel:`Email Information` form, making sure to "
"select the appropriate email type: transactional email or mass emails. After"
" completing the form, an activation email is sent to the email address and "
"the trusted sender can be activated."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:90
msgid ""
"It is recommended to set up the :abbr:`SPF (Sender Policy "
"Framework)`/:abbr:`DKIM (DomainKeys Identified Mail)`/:abbr:`DMARC (Domain-"
"based Message Authentication, Reporting, and Conformance)` settings on the "
"domain of the sender."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:95
#: ../../content/applications/general/email_communication/mailjet_api.rst:162
msgid ""
"`Mailjet's SPF/DKIM/DMARC documentation "
"<https://documentation.mailjet.com/hc/articles/ 360042412734-Authenticating-"
"Domains-with-SPF-DKIM>`_"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:99
msgid ""
"If the database is not using a custom domain, then in order to verify the "
"sender's address, a temporary alias (of the three email addresses mentioned "
"above) should be set up in Odoo CRM to create a lead. Then, the database is "
"able to receive the verification email and verify the accounts."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:107
msgid "Add a domain"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:109
msgid ""
"By adding an entire domain to the Mailjet account, all the sender addresses "
"related to that domain are automatically validated for sending emails using "
"Mailjet servers. First, navigate to the `Mailjet Account Information "
"<https://app.mailjet.com/account>`_ page. Next, click on :guilabel:`Add a "
"Sender Domain or Address` link under the :guilabel:`Senders & Domains` "
"section. Then, click on :guilabel:`Add domain` to add the custom domain."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:116
msgid ""
"The domain needs to be added to the Mailjet account and then validated "
"through the :abbr:`DNS (Domain Name System)`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:119
msgid ""
"After that, fill out the :guilabel:`Add a new Domain` page on Mailjet and "
"click :guilabel:`Continue`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:122
msgid ""
"After adding the domain, a validation page will populate. Unless the Odoo "
"database is on-premise (in which case, choose :guilabel:`Option 1`), choose "
":guilabel:`Option 2: Create a DNS Record`. Copy the TXT record information "
"to a notepad and then navigate to the domain's :abbr:`DNS (Domain Name "
"System)` provider to complete validation."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst-1
msgid "The TXT record information to input on the domain's DNS."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:132
msgid "Setup in the domain's DNS"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:134
msgid ""
"After getting the TXT record information from the Mailjet account, add a TXT"
" record to the domain's :abbr:`DNS (Domain Name System)`. This process "
"varies depending on the :abbr:`DNS (Domain Name System)` provider. Consult "
"the provider for specific configuration processes. The TXT record "
"information consists of the :guilabel:`Host` and :guilabel:`Value`. Paste "
"these into the corresponding fields in the TXT record."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:141
msgid "Return to Mailjet account information"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:143
msgid ""
"After adding the TXT record to the domain's :abbr:`DNS (Domain Name "
"System)`, navigate back to the Mailjet account. Then, navigate to "
":menuselection:`Account Information --> Add a Sender Domain or Address`, "
"click the gear icon next to :guilabel:`Domain`, and select "
":guilabel:`Validate`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:147
msgid ""
"This action can also be done by going to the `Sender domains & addresses "
"<https://app.mailjet.com/ account/sender>`_ page on the Mailjet account "
"information and clicking on :guilabel:`Manage`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:150
msgid ""
"Next, click :guilabel:`Check Now` to validate the TXT record that was added "
"on the domain. A success screen will appear if the domain is configured "
"correctly."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst-1
msgid "Check DNS record in Mailjet."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:157
msgid ""
"After successfully setting up the domain, there is an option to "
":guilabel:`Authenticate this domain (SPF/DKIM)`. This button populates "
":abbr:`SPF (Sender Policy Framework)` & :abbr:`DKIM (DomainKeys Identified "
"Mail) records to input into the :abbr:`DNS (Domain Name System)` provider."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst-1
msgid "Authenticate the domain with SPF/DKIM records in Mailjet."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:172
msgid "Set up in Odoo"
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:174
msgid ""
"To complete the setup, navigate to the Odoo database and go to the "
":guilabel:`Settings`. With :ref:`developer-mode` turned on, go to the "
":menuselection:`Technical Menu --> Email --> Outgoing Mail Servers`. Then, "
"create a new outgoing server configuration by clicking on the "
":guilabel:`Create` button."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:179
msgid ""
"Next, input the `SMTP server` (in-v3.mailjet.com), `port number` (587 or "
"465), and `Security (SSL/TLS)` that was copied earlier from the Mailjet "
"account. They can also be found `here "
"<https://app.mailjet.com/account/setup>`_. It is recommended to use "
":abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)` "
"even though Mailjet may not require it."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:184
msgid ""
"For the :guilabel:`Username`, input the :guilabel:`API KEY`. For the "
":guilabel:`Password`, input the :guilabel:`SECRET KEY` that was copied from "
"the Mailjet account to the notepad earlier. These settings can be found on "
":menuselection:`Mailjet --> Account Settings --> SMTP and SEND API "
"Settings`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:189
msgid ""
"Then, if the Mailjet server is used for mass emailing, set the "
":guilabel:`Priority` value higher than that of any transactional email "
"server(s). Finally, save the settings and :guilabel:`Test the Connection`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst-1
msgid "Odoo outgoing email server settings."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:198
msgid ""
"In order for the notifications feature to work using Mailjet, there are "
"three settings that need to be set in Odoo."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:201
msgid ""
"The :guilabel:`From Filter` needs to be set on the server configuration. It "
"is recommended to set it as a domain and not a full email address. It should"
" match the domain in the two proceeding steps. More information can be "
"referenced :ref:`here <email_communication/from_filter>`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:205
msgid ""
"The :guilabel:`mail.default.from` system parameter must have the value "
"`notifications\\@yourdomain.com`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:207
msgid ""
"The :guilabel:`mail.default.from_filter` system parameter must have the "
"value `yourdomain.com`. Replace `yourdomain` with the custom domain for the "
"Odoo database. If there isn't one, then use the "
":guilabel:`mail.catchall.domain` system parameter."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:211
msgid ""
"For more information see :ref:`Using a default email address "
"<email_communication/default>`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:213
msgid ""
"The :guilabel:`System Parameters` can be accessed by activating the "
":ref:`developer mode <developer-mode>`."
msgstr ""
#: ../../content/applications/general/email_communication/mailjet_api.rst:216
msgid ""
"Once the setup is complete, the Odoo database is ready to use the Mailjet "
"email server for mass mailing or transactional emails!"
msgstr ""
#: ../../content/applications/general/integrations.rst:3
msgid "Integrations"
msgstr "Інтеграції"
#: ../../content/applications/general/integrations/geolocation.rst:3
msgid "Geolocation"
msgstr "Геолокація"
#: ../../content/applications/general/integrations/geolocation.rst:5
msgid ""
"You can locate contacts or places and generate routes on a map in Odoo."
msgstr ""
#: ../../content/applications/general/integrations/geolocation.rst-1
msgid "Map displaying a contact's location."
msgstr ""
#: ../../content/applications/general/integrations/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/integrations/geolocation.rst:14
msgid "**OpenStreetMap**"
msgstr ""
#: ../../content/applications/general/integrations/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/integrations/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/integrations/geolocation.rst:23
msgid "**Google Places API map**"
msgstr ""
#: ../../content/applications/general/integrations/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/integrations/geolocation.rst:29
msgid ""
"Using the Google Places API could require `payment to Google "
"<https://mapsplatform.google.com/pricing/>`_."
msgstr ""
#: ../../content/applications/general/integrations/geolocation.rst:32
msgid ""
"To use it, select :guilabel:`Google Place Map` and enter your API "
":guilabel:`Key`"
msgstr ""
#: ../../content/applications/general/integrations/geolocation.rst-1
msgid "Google Places API key"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:5
msgid "Mail Plugins"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:13
msgid ""
"Mail Plugins are connectors that bridge your mailbox with your Odoo "
"database. With them, you can interact with your Odoo database directly from "
"your mailbox by:"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:16
msgid "Creating leads and centralizing prospects' emails into the CRM app."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:17
msgid "Generating tasks in any Odoo project."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:18
msgid "Creating tickets in the Helpdesk app."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:19
msgid "Searching and storing insights on your contacts."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:21
msgid ""
"Mail Plugins are available for :doc:`Outlook <mail_plugins/outlook>` and "
":doc:`Gmail <mail_plugins/gmail>`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:27
msgid "Pricing"
msgstr "Ціноутворення"
#: ../../content/applications/general/integrations/mail_plugins.rst:29
msgid "Mail Plugins are **free** to install and use."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:31
msgid ""
"However, they can provide **Lead Enrichment**, which is part of a paid "
"service known as **Lead Generation**."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:34
msgid ""
"Mail plugins allow you to test Lead Enrichment for free, whether you connect"
" the plugins to a database or not. After a while, the plugins ask you to buy"
" :doc:`../../essentials/in_app_purchase` credits if you would like to keep "
"using this service."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:41
msgid "Lead Generation IAP service"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:43
msgid ""
"Lead Enrichment uses the *Lead Generation IAP service*. Each request "
"consumes one *Lead Generation credit*."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:46
msgid ""
"To buy credits, go to :menuselection:`Settings --> CRM --> Lead Enrichment "
"--> Buy credits` and select a package."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:50
msgid ""
"If you are out of credits, the only information populated when clicking on "
"the suggested company is its website link and logo."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:52
msgid ""
"Check out the `Lead Generation IAP service Privacy Policy "
"<https://iap.odoo.com/privacy#header_3>`_."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:56
msgid ":doc:`../../essentials/in_app_purchase`"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins.rst:57
msgid "`Odoo Tutorials: Lead Enrichment <https://www.odoo.com/r/p73>`_"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:3
msgid "Gmail Plugin"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:5
msgid ""
"The *Gmail Plugin* integrates an Odoo database with a Gmail inbox, so users "
"can keep track of all their work between Gmail and Odoo, without losing any "
"information."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:9
msgid "Odoo Online users"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:11
msgid ""
"For databases hosted on Odoo Online (or Odoo.sh), follow the steps below to "
"configure the Gmail Plugin."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:15
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:94
msgid "Install the Gmail Plugin"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:17
msgid ""
"First, log in to the Gmail account that the user wishes to connect to Odoo."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:19
msgid ""
"From the Gmail inbox, click the plus sign icon on the right side panel to "
"get add-ons. If the side panel is not visible, click on the arrow icon at "
"the bottom right corner of the inbox to reveal it."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst-1
msgid "Plus sign icon on the Gmail inbox side panel."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:26
msgid ""
"Then, use the search bar to search for `Odoo` and locate the :guilabel:`Odoo"
" Inbox Addin`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst-1
msgid "Odoo Inbox Addin on Google Workspace Marketplace."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:32
msgid ""
"Or, go directly to the :guilabel:`Odoo Inbox Addin` page on the `Google "
"Workspace Marketplace "
"<https://workspace.google.com/marketplace/app/odoo_inbox_addin/873497133275>`_."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:35
msgid ""
"Once the plugin is located, click :guilabel:`Install`. Then, click "
":guilabel:`Continue` to start the installation."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:38
msgid ""
"Next, select which Gmail account the user wishes to connect to Odoo. Then "
"click :guilabel:`Allow` to let Odoo access the Google account. Google will "
"then show a pop-up window confirming that the installation was successful."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:43
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:134
msgid "Configure the Odoo database"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:45
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:136
msgid ""
"The :guilabel:`Mail Plugin` feature must be enabled in the Odoo database in "
"order to use the Gmail Plugin. To enable the feature, go to "
":menuselection:`Settings --> General Settings`. Under the "
":guilabel:`Integrations` section, activate :guilabel:`Mail Plugin`, and then"
" click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst-1
msgid "The Mail Plugin feature in the Settings."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:55
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:145
msgid "Configure the Gmail inbox"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:57
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:147
msgid ""
"In the Gmail inbox, a purple Odoo icon is now visible on the right side "
"panel. Click on the Odoo icon to open up the Odoo plugin window. Then, click"
" on any email in the inbox. Click :guilabel:`Authorize Access` in the plugin"
" window to grant Odoo access to the Gmail inbox."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst-1
msgid ""
"The Authorize Access button in the right sidebar of the Odoo plugin panel."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:65
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:155
msgid ""
"Next, click :guilabel:`Login`. Then, enter the URL of the Odoo database that"
" the user wishes to connect to the Gmail inbox, and log in to the database."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:69
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:159
msgid ""
"Use the general URL for the database, not the URL of a specific page in the "
"database. For example, use `https://mycompany.odoo.com`, not "
"`https://mycompany.odoo.com/web#cids=1&action=menu`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:73
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:163
msgid ""
"Finally, click :guilabel:`Allow` to let Gmail access the Odoo database. The "
"browser will then show a :guilabel:`Success!` message. After that, close the"
" window. The Gmail inbox and Odoo database are now connected."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:78
msgid "Odoo On-Premise users"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:80
msgid ""
"For databases hosted on servers other than Odoo Online (or Odoo.sh), follow "
"the steps below to configure the Gmail Plugin."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:84
msgid ""
"As part of their security guidelines, Google requires add-on creators to "
"provide a list of URLs that can be used in actions and redirections launched"
" by the add-on. This protects users by ensuring, for example, that no add-on"
" redirects users toward a malicious website. (Read more on `Google Apps "
"Script <https://developers.google.com/apps-script/manifest/allowlist-"
"url>`_.)"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:89
msgid ""
"Since Odoo can only list the `odoo.com` domain and not every on-premise "
"customer's unique server domain, on-premise customers cannot install the "
"Gmail Plugin from the Google Workspace Marketplace."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:96
msgid ""
"First, access the `GitHub repository <https://github.com/odoo/mail-client-"
"extensions>`_ for the Odoo Mail Plugins. Next, click on the green "
":guilabel:`Code` button. Then, click :guilabel:`Download ZIP` to download "
"the Mail Plugin files onto the user's computer."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst-1
msgid ""
"Download the ZIP file from the Odoo GitHub repository for Mail Plugins."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:104
msgid ""
"Open the ZIP file on the computer. Then, go to :menuselection:`mail-client-"
"extensions-master --> gmail --> src --> views`, and open the "
":file:`login.ts` file using any text editor software, such as Notepad "
"(Windows), TextEdit (Mac), or Visual Studio Code."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:108
msgid ""
"Delete the following three lines of text from the :file:`login.ts` file:"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:116
msgid ""
"This removes the `odoo.com` domain constraint from the Gmail Plugin program."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:118
msgid ""
"Next, in the ZIP file, go to :menuselection:`mail-client-extensions-master "
"--> gmail`, and open the file called :guilabel:`appsscript.json`. In the "
":guilabel:`urlFetchWhitelist` section, replace all the references to "
"`odoo.com` with the Odoo customer's unique server domain."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:122
msgid ""
"Then, in the same :guilabel:`gmail` folder, open the file called "
":guilabel:`README.md`. Follow the instructions in the :guilabel:`README.md` "
"file to push the Gmail Plugin files as a Google Project."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:126
msgid ""
"The computer must be able to run Linux commands in order to follow the "
"instructions on the :guilabel:`README.md` file."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:129
msgid ""
"After that, share the Google Project with the Gmail account that the user "
"wishes to connect to Odoo. Then, click :guilabel:`Publish` and "
":guilabel:`Deploy from manifest`. Lastly, click :guilabel:`Install the add-"
"on` to install the Gmail Plugin."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:3
msgid "Outlook Plugin"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:5
msgid ""
"Outlook allows for third-party applications to connect in order to execute "
"database actions from emails. Odoo has a plugin for Outlook that allows for "
"the creation of an opportunity from the email panel."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:10
#: ../../content/applications/general/iot/config.rst:5
#: ../../content/applications/general/users/azure.rst:22
#: ../../content/applications/general/users/google.rst:24
msgid "Configuration"
msgstr "Налаштування"
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:12
msgid ""
"The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both"
" on Odoo and Outlook."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:17
msgid "Enable Mail Plugin"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:19
msgid ""
"First, enable the *Mail Plugin* feature in the database. Go to "
":menuselection:`Settings --> General Settings --> Integrations`, enable "
":guilabel:`Mail Plugin`, and :guilabel:`Save` the configuration."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:25
msgid "Install the Outlook Plugin"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:27
msgid ""
"Download (:menuselection:`Save Page As --> Web Page XML only`) the following"
" XML file to upload later: "
"`https://download.odoocdn.com/plugins/outlook/manifest.xml "
"<https://download.odoocdn.com/plugins/outlook/manifest.xml>`_."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:31
msgid ""
"Next, open the Outlook mailbox, and select any email. After completing this,"
" click on the :guilabel:`More actions` button in the upper right-side and "
"select :guilabel:`Get Add-ins`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "More actions button in Outlook"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:38
msgid ""
"Following this step, select the :guilabel:`My add-ins` tab on the left-side."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "My add-ins in Outlook"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:44
msgid ""
"Under :guilabel:`Custom add-ins` towards the bottom, click on :guilabel:`+ "
"Add a custom add-in`, and then on :guilabel:`Add from file...`"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "Custom add-ins in Outlook"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:51
msgid ""
"For the next step, attach the `manifest.xml` file downloaded above, and "
"press :guilabel:`OK`. Next, read the warning and click on "
":guilabel:`Install`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "Custom add-in installation warning in Outlook"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:61
msgid "Connect the database"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:63
msgid ""
"Now, Outlook will be connected to the Odoo database. First, open any email "
"in the Outlook mailbox, click on the :guilabel:`More actions` button in the "
"upper right-side, and select :guilabel:`Odoo for Outlook`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "Odoo for Outlook add-in button"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:71
msgid ""
"The right-side panel can now display **Company Insights**. At the bottom, "
"click on :guilabel:`Login`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "Logging in the Odoo database"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:79
msgid ""
"Only a limited amount of **Company Insights** (*Lead Enrichment*) requests "
"are available as a trial database. This feature requires :ref:`prepaid "
"credits <mail_plugins/pricing>`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:83
msgid ""
"If, after a short while, the panel is still empty, it is possible that the "
"browser cookie settings prevented it from loading. Note that these settings "
"also change if the browser is in \"Incognito\" mode."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:87
msgid ""
"To fix this issue, configure the browser to always allow cookies on Odoo's "
"plugin page."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:89
msgid ""
"For Google Chrome, change the browser cookie settings by following the guide"
" at: `https://support.google.com/chrome/answer/95647 "
"<https://support.google.com/chrome/answer/95647>`_ and adding "
"`download.odoo.com` to the list of :guilabel:`Sites that can always use "
"cookies`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:94
msgid "Once this is complete, the Outlook panel needs to be opened again."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:96
msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "Entering the Odoo database URL"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:102
msgid "Next, click on :guilabel:`Allow` to open the pop-up window."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "New window pop-up warning"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:108
msgid ""
"If the user isn't logged into the database, enter the credentials. Click on "
":guilabel:`Allow` to let the Outlook Plugin connect to the database."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "Allowing the Outlook Plugin to connect to a database"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:118
msgid "Add a shortcut to the plugin"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:120
msgid ""
"By default, the Outlook Plugin can be opened from the *More actions* menu. "
"However, to save time, it's possible to add it next to the other default "
"actions."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:123
msgid ""
"In the Outlook mailbox, click on :guilabel:`Settings`, then on "
":guilabel:`View all Outlook settings`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "Viewing all Outlook settings"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:130
msgid ""
"Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on "
":guilabel:`Odoo for Outlook`, and then :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "Odoo for Outlook customized action"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:137
msgid "Following this step, open any email; the shortcut should be displayed."
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:144
msgid "Using the plugin"
msgstr ""
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:146
msgid ""
"Now that the plug-in is installed and operational, all that needs to be done"
" to create a lead is to click on the `O` [Odoo icon] or navigate to "
":guilabel:`More actions` and click on :guilabel:`Odoo for Outlook`. The side"
" panel will appear on the right-side, and under :guilabel:`Opportunities` "
"click on :guilabel:`New`. A new window with the created opportunity in the "
"Odoo database will populate."
msgstr ""
#: ../../content/applications/general/integrations/unsplash.rst:3
msgid "Unsplash (free images)"
msgstr ""
#: ../../content/applications/general/integrations/unsplash.rst:6
msgid "Generate an Unsplash access key"
msgstr ""
#: ../../content/applications/general/integrations/unsplash.rst:9
msgid ""
"**As an Odoo Online user**, you are ready to use Unsplash. You won't need to"
" follow this guide to set up Unsplash information since you will use our own"
" Odoo Unsplash key in a transparent way."
msgstr ""
#: ../../content/applications/general/integrations/unsplash.rst:13
msgid "Generate an Unsplash access key for non-Odoo Online users"
msgstr ""
#: ../../content/applications/general/integrations/unsplash.rst:15
msgid "Create an account on `Unsplash.com <https://unsplash.com/join>`_."
msgstr ""
"Створіть обліковий запис на `Unsplash.com <https://unsplash.com/join>`_."
#: ../../content/applications/general/integrations/unsplash.rst:17
msgid ""
"Go to your `applications dashboard "
"<https://unsplash.com/oauth/applications>`_ and click on **New "
"Application**."
msgstr ""
"Перейдіть до вашої `панелі приладів додатків "
"<https://unsplash.com/oauth/applications>`_ та натисніть на **Новий "
"додаток**."
#: ../../content/applications/general/integrations/unsplash.rst:23
msgid "Accept the conditions and click on **Accept terms**."
msgstr "Прийміть умови та натисніть **Прийняти умови**."
#: ../../content/applications/general/integrations/unsplash.rst:28
msgid ""
"You will be prompted to insert an **Application name** and a "
"**Description**. Please prefix your application name by \"**Odoo:** \" so "
"that Unsplash can recognize it as an Odoo instance. Once done, click on "
"**Create application**."
msgstr ""
"Вам буде запропоновано вставити **Назву заявки** та **Опис**.Будь ласка, "
"префіксуйте назву вашого модуля за \"** Odoo: **\", щоби Unsplash міг "
"розпізнати його як екземпляр Odoo. Після завершення натисніть на **Створити "
"додаток**."
#: ../../content/applications/general/integrations/unsplash.rst:35
msgid ""
"You should be redirected to your application details page. Scroll down a bit"
" to find your **access key**."
msgstr ""
"Ви повинні бути перенаправлені на сторінку деталей додатку. Прокрутіть вниз,"
" щоб знайти ваш **ключ доступу**."
#: ../../content/applications/general/integrations/unsplash.rst:42
msgid ""
"**As a non-Odoo Online user**, you won't be able to register for a "
"production Unsplash key and will be limited to your test key that has a "
"restriction of 50 Unsplash requests per hour."
msgstr ""
#: ../../content/applications/general/integrations/unsplash.rst:46
msgid "Generate an Unsplash application ID"
msgstr ""
#: ../../content/applications/general/integrations/unsplash.rst:49
msgid "You should first create and set up your Unsplash application."
msgstr ""
#: ../../content/applications/general/integrations/unsplash.rst:51
msgid ""
"Go to your `applications dashboard "
"<https://unsplash.com/oauth/applications>`_ and click on your newly created "
"Unsplash application under **Your applications**."
msgstr ""
"Перейдіть до `панелі приладів додатків "
"<https://unsplash.com/oauth/applications>`_ та натисніть на щойно створений "
"додаток Unsplash під **Вашими додатками**."
#: ../../content/applications/general/integrations/unsplash.rst:57
msgid ""
"You will be redirected to your application details page. The **application "
"ID** will be visible in your browser's URL. The URL should be something like"
" ``https://unsplash.com/oauth/applications/<application_id>``"
msgstr ""
"Вас буде перенаправлено на сторінку деталей вашого модуля. **ID модуля** "
"буде видимий у вашій URL-адресі браузера. URL-адреса повинна бути схожа на "
"``https://unsplash.com/oauth/applications/<application_id>``"
#: ../../content/applications/general/integrations/unsplash.rst:65
msgid ""
"**As a non-Odoo Online user**, you won't be able to register for a "
"production Unsplash key and will be limited to your test key that has a 50 "
"Unsplash requests per hour restriction."
msgstr ""
#: ../../content/applications/general/iot.rst:8
msgid "Internet of Things (IoT)"
msgstr "Інтернет речей (IoT)"
#: ../../content/applications/general/iot.rst:17
msgid ""
"The Open Platform Communications (OPC) Unified Architecture (UA) protocol is"
" now supported by the :abbr:`IoT (Internet of Things)` box. :abbr:`OPC (Open"
" Platform Communications)` :abbr:`UA (United Architecture)` is an open "
"standard that specifies information exchange for industrial communication on"
" devices, between machines and between systems. This includes communication "
"between information technology and operational technology. :abbr:`OPC (Open "
"Platform Communications)` :abbr:`UA (United Architecture)` can be used with "
"any software platform, on a wide variety of devices, and deployed securely. "
"The :abbr:`IoT (Internet of Things)` box has entered the world of the "
"Industry 4.0 standard and can be utilized in a wide variety of industries, "
"and for things like building automation, packaging, utilities, etc."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:3
msgid "Connect an IoT box to Odoo"
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:5
msgid ""
"An Internet of Things (IoT) box is a micro-computer device that allows for "
"the connection of input and output devices to an Odoo database. An "
":abbr:`IoT (Internet of Things)` box subscription is required in order to "
"use the :abbr:`IoT (Internet of Things)` box with a secured connection. A "
"computer is also required to set up the :abbr:`IoT (Internet of Things)` "
"box."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:11
msgid "`IoT Box FAQ <https://www.odoo.com/app/iot-faq>`_"
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:13
msgid ""
"Begin the :abbr:`IoT (Internet of Things)` configuration process by "
":ref:`installing the IoT app <general/install>` on the Odoo database through"
" the :menuselection:`Apps` application."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst-1
msgid "The Internet of Things (IoT) app on the Odoo database."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:20
msgid ""
"Next, after the *IoT app* is installed, navigate to :menuselection:`IoT app "
"--> IoT Boxes`, and then click on the :guilabel:`Connect` button located in "
"the upper-left corner of the :menuselection:`IoT Boxes` dashboard."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst-1
msgid "Connecting an IoT box to the Odoo database."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:28
msgid ""
"There are two recommended ways to connect the :abbr:`IoT (Internet of "
"Things)` box to the database once the *IoT app* is installed. Follow the "
"steps in either of the next two sections to connect the :abbr:`IoT (Internet"
" of Things)` box via :ref:`wired ethernet connection <iot_connect/ethernet>`"
" or via :ref:`WiFi <iot_connect/wifi>`."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst-1
msgid "Connection steps for a wired connection or WiFi connection."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:38
msgid ""
"The disk image that the :abbr:`IoT (Internet of Things)` box SD card is "
"formatted with is unique to the version of the Odoo database that the "
":abbr:`IoT (Internet of Things)` box is running on. Ensure that the "
":abbr:`IoT (Internet of Things)` box is :doc:`flashed <flash_sdcard>` with "
"the most up-to-date disk image."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:46
msgid "Ethernet connection"
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:48
msgid ""
"The following is the process to connect the :abbr:`IoT (Internet of Things)`"
" box via an ethernet cable to the Odoo database (by way of the ethernet "
"port; RJ-45)."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:51
msgid ""
"First, connect all wired devices to the :abbr:`IoT (Internet of Things)` box"
" (ethernet, :abbr:`USB (Universal Serial Bus)` devices, etc.). At minimum, "
"an HDMI screen should be connected. Then, plug the :abbr:`IoT (Internet of "
"Things)` box into a power source."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:55
msgid ""
"Immediately after the unit powers on and boots up, read the *pairing code* "
"from the screen or from the printout of a receipt printer connected to the "
":abbr:`IoT (Internet of Things)` box."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:59
msgid ""
"By default, the :abbr:`IoT (Internet of Things)` box will display the "
"*pairing code* for a maximum of 5 minutes after the unit boots up. After 5 "
"minutes, the *pairing code* will disappear for security purposes and the "
":abbr:`IoT (Internet of Things)` box will need to be rebooted manually by "
"unplugging the unit from the power source for ten seconds and re-plugging it"
" back in."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:65
msgid ""
"If no screen is attached to the :abbr:`IoT (Internet of Things)` box, then "
"the *pairing code* can be accessed from the :abbr:`IoT (Internet of Things)`"
" box homepage by clicking on the :guilabel:`POS Display` button. For "
"instructions on how to access the :abbr:`IoT (Internet of Things)` box "
"homepage visit :ref:`iot_connect/token`."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:70
msgid ""
"On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and "
"then click on the :guilabel:`Connect` button located in the upper-left "
"corner of the the :menuselection:`IoT Boxes` dashboard. Input the *pairing "
"code* in the :guilabel:`Pairing Code` field and click on the "
":guilabel:`Pair` button. The database will now link to the :abbr:`IoT "
"(Internet of Things)` box and it will appear on the :menuselection:`IoT "
"Boxes` page."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:79
msgid "WiFi connection"
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:81
msgid ""
"The following is the process to connect the :abbr:`IoT (Internet of Things)`"
" box via a WiFi connection to the Odoo database."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:84
msgid ""
"First, ensure there is no ethernet cable plugged into the :abbr:`IoT "
"(Internet of Things)` box. Then, connect all wired devices to the :abbr:`IoT"
" (Internet of Things)` box (:abbr:`USB (Universal Serial Bus)` devices, "
"etc.)."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:88
msgid ""
"After connecting the devices, plug the :abbr:`IoT (Internet of Things)` box "
"into to a power source. On the computer, navigate to :menuselection:`IoT app"
" --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in"
" the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Then"
" copy the :guilabel:`Token` from the :guilabel:`WiFi connection` section as "
"this will later be used to link the Odoo database to the :abbr:`IoT "
"(Internet of Things)` box."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:94
msgid ""
"Back on the computer, navigate to the available WiFi networks and connect to"
" the :abbr:`IoT (Internet of Things)` box WiFi network. The WiFi network "
"dispersed by the :abbr:`IoT (Internet of Things)` box will start with "
"`IoTBox-xxxxxxxxxx`."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst-1
msgid "WiFi networks available on the computer."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:102
msgid ""
"Upon connecting to the :abbr:`IoT (Internet of Things)` box WiFi, a browser "
"will automatically redirect to the :menuselection:`Configure Iot Box` "
"wizard. Name the :abbr:`IoT (Internet of Things)` box, then paste the "
"previously copied *token* into the :guilabel:`Server Token` field, and then "
"click on :guilabel:`Next`."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst-1
msgid "Enter the server token into the IoT box."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:112
msgid ""
"If the :abbr:`IoT (Internet of Things)` box WiFi connection wizard doesn't "
"start, then see the documentation on :ref:`connecting with a token "
"<iot_connect/token>`."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:115
msgid ""
"Now, choose the WiFi network that the :abbr:`IoT (Internet of Things)` box "
"will connect with (enter the password if there is one) and click on "
":guilabel:`Connect`. Wait a few seconds and the browser will redirect to the"
" :abbr:`IoT (Internet of Things)` box homepage. The computer may need to be "
"manually re-connected back to the original WiFi connection, if this does not"
" happen automatically."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst-1
msgid "Configuring the WiFi for the IoT box."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:124
msgid ""
"After completing each step, the :abbr:`IoT (Internet of Things)` box should "
"appear when navigating to :menuselection:`IoT app --> IoT Boxes` on the Odoo"
" database."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst-1
msgid "The IoT box has been successfully configured on the Odoo database."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:132
msgid ""
"The :abbr:`IoT (Internet of Things)` box may need to be manually rebooted "
"upon successfully connecting via WiFi for the box to appear in the *IoT app*"
" on the Odoo database. To do so, simply unplug the device and plug it back "
"into the power source after ten seconds."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:139
msgid "Manually connecting the IoT box using the token"
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:141
msgid ""
"A manual connection of the :abbr:`IoT (Internet of Things)` box to the "
":abbr:`IoT (Internet of Things)` app can be made using the *token*, from a "
"computer. The *token* can be found by navigating to :menuselection:`IoT app "
"--> IoT Boxes` and clicking on :guilabel:`Connect`."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:145
msgid ""
"Under the :guilabel:`WiFi Connection` section of the :guilabel:`Connect an "
"IoT Box` page that appears, click :guilabel:`Copy` to the right of the "
":guilabel:`Token`. This token will be entered into the :abbr:`IoT (Internet "
"of Things)` box homepage."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:149
msgid ""
"Access the :abbr:`IoT (Internet of Things)` box homepage by entering the "
":abbr:`IP (Internet Protocol)` address of the :abbr:`IoT (Internet of "
"Things)` box into a browser window from a computer on the same network as "
"the :abbr:`IoT (Internet of Things)` box (preferably by ethernet "
"connection)."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:154
msgid ""
"The :abbr:`IP (Internet Protocol)` address can be accessed by the router "
"admin console that the :abbr:`IoT (Internet of Things)` box is connected to,"
" or by connecting a receipt printer to the :abbr:`IoT (Internet of Things)` "
"box. A receipt will print out with the :abbr:`IoT (Internet of Things)` "
"box's :abbr:`IP (Internet Protocol)` address on it."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:159
msgid ""
"On the :abbr:`IoT (Internet of Things)` box homepage, enter the *token* "
"under the :guilabel:`Server` section by clicking on :guilabel:`Configure`. "
"Then, paste the *token* into the :guilabel:`Server Token` field and click "
":guilabel:`Connect`. The :abbr:`IoT (Internet of Things)` box will then link"
" to the Odoo database."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:167
msgid "IoT box schema"
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:170
msgid "Raspberry Pi 4"
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:174
msgid "The Odoo IoT box (Raspberry Pi 4) schema with labels."
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:177
msgid "Raspberry Pi 3"
msgstr ""
#: ../../content/applications/general/iot/config/connect.rst:181
msgid "The Odoo IoT box (Raspberry Pi 3) schema with labels."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:3
msgid "Flashing the SD card"
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:5
msgid ""
"In some circumstances, the :abbr:`IoT (Internet of Things)` box's micro SD "
"Card may need to be re-flashed to benefit from Odoo's latest :abbr:`IoT "
"(Internet of Things)` image update. This means that the Odoo :abbr:`IoT "
"(Internet of Things)` box software may need to be updated."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:10
msgid "Upgrade from the IoT box home page"
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:12
msgid ""
"Go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to "
":menuselection:`IoT app --> IoT Boxes` and clicking on the :guilabel:`IP "
"address` of the :abbr:`IoT (Internet of Things)` box. Then click on "
":guilabel:`Update` (next to the version number)."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:16
msgid ""
"If a new version of the :abbr:`IoT (Internet of Things)` Box image is "
"available, an :guilabel:`Upgrade to _xx.xx_` button will appear at the "
"bottom of the page. Click this button to upgrade the unit and the :abbr:`IoT"
" (Internet of Things)` box will then flash itself to the new version. All of"
" the previous configurations will be saved."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:22
msgid ""
"This process can take more than 30 minutes. Do not turn off or unplug the "
":abbr:`IoT (Internet of Things)` box as it would leave it in an inconsistent"
" state. This means that the :abbr:`IoT (Internet of Things)` box will need "
"to be re-flashed with a new image. See :ref:`flash_sdcard/etcher`."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst-1
msgid "IoT box software upgrade in the IoT Box Home Page."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:34
msgid "Upgrade with Etcher Software"
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:37
msgid ""
"A computer with a micro SD card reader/adapter is required in order to re-"
"flash the micro SD card."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:40
msgid ""
"Navigate to Balena's website and download `Etcher "
"<https://www.balena.io/>`_. It's a free and open-source utility used for "
"burning image files onto drives. Click to `download "
"<https://www.balena.io/etcher#download-etcher>`_. Install and launch the "
"program on the computer."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:44
msgid ""
"Then download the version-specific :abbr:`IoT (Internet of Things)` image "
"from `nightly <http://nightly.odoo.com/master/iotbox/>`_."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:47
msgid ""
"The following are image versions on the `nightly "
"<http://nightly.odoo.com/master/iotbox/>`_ website with their corresponding "
"Odoo database version:"
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:50
msgid "Odoo V16 --> iotbox-latest.zip"
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:51
msgid "Odoo V15 --> iotboxv21_10.zip"
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:52
msgid "Odoo V14 --> iotboxv21_04.zip"
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:53
msgid "Odoo V13 --> iotboxv20_10.zip"
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:55
msgid ""
"The images should be downloaded and extracted to a convenient file location."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:57
msgid ""
"After this step is complete, insert the :abbr:`IoT (Internet of Things)` "
"box's micro SD card into the computer or reader. Open *Etcher* and select "
":guilabel:`Flash from file`, then find and select the image just downloaded "
"and extracted. Next, select the drive the image should be burned to. Lastly,"
" click on :guilabel:`Flash` and wait for the process to finish."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst-1
msgid "Balena's Etcher software dashboard."
msgstr ""
#: ../../content/applications/general/iot/config/flash_sdcard.rst:67
msgid ""
"An alternative software for flashing the micro SD card is *Raspberry Pi "
"Imager*. Download the *Raspberry Pi* software `here "
"<https://www.raspberrypi.com/software/>`_."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:5
msgid "HTTPS certificate (IoT)"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:8
msgid "What is HTTPS?"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:10
msgid ""
"*Hypertext Transfer Protocol Secure* (HTTPS) is the secure version of "
"*Hypertext Transfer Protocol* (HTTP), which is the primary protocol used to "
"send data back and forth between a web browser and a website. :abbr:`HTTPS "
"(Hypertext Transfer Protocol Secure)` is encrypted in order to increase the "
"security of data transfer."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:15
msgid ""
":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` uses an encryption "
"protocol to encrypt communications. The protocol is called *Transport Layer "
"Security* (TLS), although formerly it was known as *Secure Sockets Layer* "
"(SSL)."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:19
msgid ""
":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` occurs based upon the "
"transmission of :abbr:`TLS (Transport Layer Security)`/:abbr:`SSL (Secure "
"Sockets Layer)` certificates, which verify that a particular provider is who"
" they say they are."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:24
msgid ""
"In this documentation and throughout Odoo the term \"HTTPS certificate\" "
"will be used to define the fact that the :abbr:`SSL (Secure Sockets Layer)` "
"certificate is valid and allows a :abbr:`HTTPS (Hypertext Transfer Protocol "
"Secure)` connection."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:29
msgid "Why is it needed?"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:31
msgid ""
"In order to communicate with certain network devices (in particular for "
"payment terminals), the usage of :abbr:`HTTPS (Hypertext Transfer Protocol "
"Secure)` is mandatory. If the :abbr:`HTTPS (Hypertext Transfer Protocol "
"Secure)` certificate isn't valid, some devices won't be able to interact "
"with the :abbr:`IoT (Internet of Things)` Box."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:37
msgid "How to obtain a Hypertext Transfer Protocol Secure (HTTPS) certificate"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:39
msgid ""
"The generation of the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` "
"certificate is automatic."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:41
msgid ""
"The :abbr:`IoT (Internet of Things)` Box will send a specific request to "
"`<https://www.odoo.com>`_ which will send back the :abbr:`HTTPS (Hypertext "
"Transfer Protocol Secure)` certificate if the :abbr:`IoT (Internet of "
"Things)` box and database are eligible."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:48
msgid "Internet of Things (IoT) eligibility"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:50
msgid ""
"The database should be a **production** instance. The database instance "
"should not be a copy, a duplicate, a staging, or a development environment."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:52
msgid "The Odoo subscription must:"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:54
msgid "Have an :guilabel:`IoT Box Subscription` line."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:55
msgid ":guilabel:`Status` must be :guilabel:`In Progress`."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:57
msgid ""
"If the subscription is linked to a `<https://www.odoo.com>`_ portal user "
"check the information on the portal subscription page."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:0
msgid "Odoo.com portal subscriptions filtered by \"in progress\"."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:64
msgid ""
"In this case, both subscriptions are considered \"in progress\" as the "
":guilabel:`Filter By\\: In Progress` was used."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:68
msgid ""
"If the subscription is in question, contact the database's Account Manager "
"or Partner regarding the matter."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:72
msgid ""
"Troubleshooting Hypertext Transfer Protocol Secure (HTTPS) certificate "
"errors"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:74
msgid ""
"If anything goes wrong during the process of the \"HTTPS certificate\" "
"generation or reception, a specific error will code be given on the "
":abbr:`IoT (Internet of Things)` box home page."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:78
msgid ""
"Accessing the :abbr:`IoT (Internet of Things)` box homepage will check for "
"the presence of the \"HTTPS certificate\" and will attempt its generation if"
" it is missing. As such, if there is an error on the :abbr:`IoT (Internet of"
" Things)` box home page, refresh the :abbr:`IoT (Internet of Things)` home "
"page to see if the error disappears."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:84
msgid "`ERR_IOT_HTTPS_CHECK_NO_SERVER`"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:88
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:101
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:110
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:132
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:149
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:166
msgid "Reason:"
msgstr "Причина:"
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:87
msgid ""
"The configuration regarding the server is missing. In other words, the Odoo "
"instance is not connected with the IoT box."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:91
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:104
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:114
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:137
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:159
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:170
msgid "Solution:"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:91
msgid "Ensure that the server is configured."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:94
msgid ":doc:`/applications/general/iot/config/connect`"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:97
msgid "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:100
msgid ""
"An unhandled error happened when trying to read the existing :abbr:`HTTPS "
"(Hypertext Transfer Protocol Secure)` certificate."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:104
msgid ""
"Ensure that the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` "
"certificate file is readable."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:107
msgid "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:110
msgid ""
"The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is "
"missing."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:113
msgid ""
"Ensure that both values are configured as intended. To modify them, go to "
"the :abbr:`IoT (Internet of Things)` box home page, and navigate to "
":guilabel:`Credential`."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:117
msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:120
msgid ""
"An unexpected error happened when the :abbr:`IoT (Internet of Things)` box "
"tried to reach `<https://www.odoo.com>`_. The causes are likely due to the "
"network infrastructure/configuration:"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:124
msgid ""
"The :abbr:`IoT (Internet of Things)` box does not have access to internet."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:125
msgid ""
"The network does not allow the :abbr:`IoT (Internet of Things)` box to "
"communicate with `<https://www.odoo.com>`_. This may be due to network "
"devices preventing the communication (firewalls, etc.) or the network "
"configuration (:abbr:`VPN (Virtual Private Network)`, etc.)."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:131
msgid ""
"More information regarding the error that occurred can be found in the full "
"request exception details, which are in the :abbr:`IoT (Internet of Things)`"
" box logs."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:136
msgid ""
"Consult with your system or network administrator should this issue arise. "
"This error code depends on the network infrastructure and goes beyond Odoo "
"support's service scope."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:140
msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:143
msgid ""
"The IoT-box was able to reach `<https://www.odoo.com>`_ but received an "
"unusual `HTTP response (status codes) <https://developer.mozilla.org/en-"
"US/docs/Web/HTTP/Status>`_."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:147
msgid ""
"This error code will also give the HTTP response status codes. For example, "
"if the error reads `ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` it means that the"
" page returned a 404 error, which is the \"Page Not Found\" code."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:152
msgid ""
"Check if `<https://www.odoo.com>`_ is down using a web browser, as it's "
"possible that it is down due to maintenance."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:155
msgid ""
"If `<https://www.odoo.com>`_ is down due to maintenance, unfortunately there"
" is nothing that can be done but instead wait for it to recover."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:157
msgid ""
"If `<https://www.odoo.com>`_ is not down due to maintenance, open a `support"
" ticket <https://www.odoo.com/help>`_ on the matter. Ensure that the 3 "
"digits status code next to the code error is included in the support ticket."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:162
msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:165
msgid ""
"The :abbr:`IoT (Internet of Things)` box was able to reach "
"`<https://www.odoo.com>`_ but it refused to deliver the :abbr:`HTTPS "
"(Hypertext Transfer Protocol Secure)` certificate."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:169
msgid ""
"Ensure that the :abbr:`IoT (Internet of Things)` box and database are "
"eligible for a certificate: :ref:`Internet of Things (IoT) eligibility "
"<iot/iot-eligibility>`."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:173
msgid "How to ensure that the HTTPS certificate is correct"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:175
msgid ""
"If the certificate has been applied successfully, a new :abbr:`HTTPS "
"(Hypertext Transfer Protocol Secure)` :abbr:`URL (Uniform Resource Locator)`"
" for the :abbr:`IoT (Internet of Things)` box ending with `.odoo-iot.com` "
"will appear on the Odoo database, inside of the :menuselection:`IoT` "
"application on that specific device's form."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst-1
msgid "Odoo IoT app IoT box with .odoo-iot.com domain."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:184
msgid ""
"When navigating to the :abbr:`URL (Uniform Resource Locator)` in a browser a"
" secured :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection will "
"be established."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:191
msgid "Example of valid SSL certificate details on the browser."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:191
msgid ""
"Padlock in Chrome on Windows 10 attesting the fact that the connection is "
"secured in :abbr:`HTTPS (Hypertext Transfer Protocol Secure)`."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:194
msgid ""
"The IoT-box homepage will now display an `OK` status next to `HTTPS "
"certificate`. The drop-down menu icon, when clicked, will reveal information"
" regarding the certificate."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst-1
msgid "IoT box homepage with HTTPS certificate OK status."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:202
msgid "Domain Name System (DNS) issue"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:204
msgid ""
"If the :abbr:`IoT (Internet of Things)` box can be accessed from its "
":abbr:`IP (Intrernet Protocol)` address but not the Odoo assigned domain: "
"`.odoo-iot.com`; then the :abbr:`IoT (Internet of Things)` box is likely "
"running into a :abbr:`DNS (Domain Name System)` issue. On some browsers, it "
"will give an error code mentioning :abbr:`DNS (Domain Name System)` (like "
"`DNS_PROBE_FINISHED_NXDOMAIN`)."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:209
msgid ""
"These :abbr:`DNS (Domain Name System)` issues may appear as the following in"
" different browsers:"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:213
msgid "Chrome"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:0
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:219
msgid "DNS issue on Chrome browser on Windows 10."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:222
msgid "Firefox"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:0
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:228
msgid "DNS issue on Firefox browser on Windows 10."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:230
msgid "Edge"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:0
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:236
msgid "DNS issue on Edge browser on Windows 10."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:240
msgid "Domain Name System (DNS) issue solution"
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:242
msgid ""
"Should the router allow the :abbr:`DNS (Domain Name System)` to be manually "
"changed, change the DNS to use `Google DNS "
"<https://developers.google.com/speed/public-dns>`_."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:244
msgid ""
"If your router doesn't allow for this, then a change will need to be made on"
" the :abbr:`DNS (Domain Name System)` settings of each of the devices using "
"`Google DNS <https://developers.google.com/speed/public-dns>`_. This will "
"need to occur on **every** device that plans to interact with the :abbr:`IoT"
" (Internet of Things)` box (e.g. computer, tablet or phone). The individual "
"device configuration processes can be found on the website of the device's "
"manufacturer."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:252
msgid ""
"Other :abbr:`IoT (Internet of Things)` devices such as payment terminals "
"likely won't need their :abbr:`DNS (Domain Name System)` settings changed as"
" they are already configured with custom :abbr:`DNS (Domain Name System)`."
msgstr ""
#: ../../content/applications/general/iot/config/https_certificate_iot.rst:257
msgid ""
"Consult with your system or network administrator should this issue arise. "
"This error code depends on the network infrastructure, and it goes beyond "
"Odoo support's service scope."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:3
msgid "Use an IoT box with a PoS"
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:6
msgid "Prerequisites"
msgstr "Передумови"
#: ../../content/applications/general/iot/config/pos.rst:8
msgid "Before starting, make sure the following equipment is available:"
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:10
msgid "An :abbr:`IoT (Internet of Things)` box, with its power adapter."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:11
msgid "A computer or tablet with an up-to-date web browser."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:12
msgid ""
"Odoo Online or an Odoo instance with the *Point of Sale* and *IoT* "
"applications installed."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:13
msgid ""
"A local network set up with :abbr:`DHCP (Dynamic Host Configuration "
"Protocol)` (this is the default setting)."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:15
msgid ""
"An RJ45 Ethernet Cable (optional, but preferred over WiFi, which is already "
"built in)."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:16
msgid ""
"Any of the supported hardware (receipt printer, barcode scanner, cash "
"drawer, payment terminal, scale, customer display, etc.). The list of "
"supported hardware can be found on the `POS Hardware page "
"<https://www.odoo.com/page/point-of-sale-hardware>`_."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:25
msgid "A suggested configuration for a point of sale system."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:27
msgid ""
"To connect hardware to the :abbr:`PoS (Point of Sale)`, the first step is to"
" connect an :abbr:`IoT (Internet of Things)` box to the database. To do "
"this, follow these instructions: :doc:`Connect an Internet of Things (IoT) "
"box to the Odoo database <connect>`."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:31
msgid ""
"Then, connect the peripheral devices to the :abbr:`IoT (Internet of Things)`"
" box."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:37
msgid "Device Name"
msgstr "Назва пристрою"
#: ../../content/applications/general/iot/config/pos.rst:38
msgid "Instructions"
msgstr "Інструкції"
#: ../../content/applications/general/iot/config/pos.rst:39
#: ../../content/applications/general/iot/config/troubleshooting.rst:66
msgid "Printer"
msgstr "Принтер"
#: ../../content/applications/general/iot/config/pos.rst:40
msgid ""
"Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus)` "
"port or to the network, and power it on. Refer to "
":doc:`/applications/sales/point_of_sale/restaurant/kitchen_printing`."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:43
#: ../../content/applications/general/iot/config/troubleshooting.rst:412
msgid "Cash drawer"
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:44
msgid "The cash drawer should be connected to the printer with an RJ25 cable."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:45
#: ../../content/applications/general/iot/config/troubleshooting.rst:360
msgid "Barcode scanner"
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:46
msgid ""
"In order for the barcode scanner to be compatible it must end barcodes with "
"an `ENTER` character (keycode 28). This is most likely the default "
"configuration of the barcode scanner."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:48
#: ../../content/applications/general/iot/config/troubleshooting.rst:423
msgid "Scale"
msgstr "Шкала"
#: ../../content/applications/general/iot/config/pos.rst:49
msgid "Connect the scale and power it on. Refer to :doc:`../devices/scale`."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:51
msgid "Customer display"
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:52
msgid ""
"Connect a screen to the :abbr:`IoT (Internet of Things)` box to display the "
":abbr:`PoS (Point of Sale)` order. Refer to :doc:`../devices/screen`."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:54
msgid "Payment terminal"
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:55
msgid ""
"The connection process depends on the terminal. Refer to the :doc:`payment "
"terminals documentation "
"</applications/sales/point_of_sale/payment_methods>`."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:58
msgid ""
"Once this is completed, connect the :abbr:`IoT (Internet of Things)` box to "
"the :menuselection:`PoS` application. To do this, go to "
":menuselection:`Point of Sale --> Configuration --> PoS`, tick the "
":guilabel:`IoT Box` option, and select the devices to be used in this "
":abbr:`PoS (Point of Sale)`. :guilabel:`Save` the the changes."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst-1
msgid "Configuring the connected devices in the POS application."
msgstr ""
#: ../../content/applications/general/iot/config/pos.rst:67
msgid ""
"Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be "
"launched."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:3
msgid "Troubleshooting"
msgstr "Вирішення проблем"
#: ../../content/applications/general/iot/config/troubleshooting.rst:6
msgid "IoT box connection"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:9
msgid "Unable to locate the pairing code to connect the IoT box"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:11
msgid ""
"The pairing code should be printed on receipt printers connected to the "
":abbr:`IoT (Internet of Things)` box and should also be displayed on "
"connected monitors."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:14
msgid "The pairing code does not show under the following circumstances:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:16
msgid ""
"The :abbr:`IoT (Internet of Things)` box is already connected to an Odoo "
"database."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:17
msgid ""
"The :abbr:`IoT (Internet of Things)` box is not connected to the Internet."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:18
msgid ""
"The code is only valid for 5 minutes after the :abbr:`IoT (Internet of "
"Things)` box has started. It is automatically removed from connected "
"displays when this time has expired."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:20
msgid ""
"The version of the :abbr:`IoT (Internet of Things)` box image is too old. If"
" the :abbr:`IoT (Internet of Things)` box image is from an earlier version, "
"then the SD card of the :abbr:`IoT (Internet of Things)` box will need to be"
" re-flashed to update the image (see :doc:`Flashing the SD Card "
"<flash_sdcard>`)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:25
msgid ""
"If none of the cases listed above correct the issue, then make sure that the"
" :abbr:`IoT (Internet of Things)` box has correctly started, by checking "
"that a fixed green LED is showing next to the power port."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:30
msgid "IoT box is connected but it is not showing in the database"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:32
msgid ""
"When an :abbr:`IoT (Internet of Things)` box connects to a database, it may "
"restart. If so, it can take up to five minutes before appearing in the "
"database. If the :abbr:`IoT (Internet of Things)` box is still not showing "
"after five minutes, make sure that the :abbr:`IoT (Internet of Things)` box "
"can reach the database and that the server does not use a multi-database "
"environment."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:37
msgid ""
"To access the database from the :abbr:`IoT (Internet of Things)` box, open a"
" browser and type in the database address."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:41
msgid "The IoT box is connected to the Odoo database, but cannot be reached"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:43
msgid ""
"Make sure that the :abbr:`IoT (Internet of Things)` box and the computer "
"running the browser are located on the same network, as the :abbr:`IoT "
"(Internet of Things)` box cannot be reached from outside the local network."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:48
msgid "The HTTPS certificate does not generate"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:50
msgid ""
"In order to generate a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` "
"certificate, an IoT box subscription is required for the :abbr:`IoT "
"(Internet of Things)` box. Connecting the :abbr:`IoT (Internet of Things)` "
"box prior to configuring an :abbr:`IoT (Internet of Things)` subscription "
"for the database and :abbr:`IoT (Internet of Things)` box with the Account "
"Manager will result in an unsecured connection."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:56
msgid ""
"In addition, a firewall can also prevent the :abbr:`HTTPS (Hypertext "
"Transfer Protocol Secure)` certificate from generating correctly. In this "
"case, deactivate the firewall until the certificate is successfully "
"generated. It should also be noted that certain devices, such as a router "
"that has a built-in firewall, can prevent the :abbr:`HTTPS (Hypertext "
"Transfer Protocol Secure)` certificate from generating."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:63
msgid ":doc:`HTTPS certificate (IoT) <https_certificate_iot>`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:69
msgid "The printer is not detected"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:71
msgid ""
"If a printer does not appear in the devices list, go to the :abbr:`IoT "
"(Internet of Things)` box homepage and make sure that it is listed under "
":guilabel:`Printers`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst-1
msgid "The IoT box Home Page landing page."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:78
msgid ""
"If the printer is not present on the :abbr:`IoT (Internet of Things)` box "
"homepage, click :guilabel:`Printers Server`, go to the "
":guilabel:`Administration` tab and click on :guilabel:`Add Printer`. If the "
"printer is not present in the list, it is likely not connected properly."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:83
msgid "The printer outputs random text"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:85
msgid ""
"For most printers, the correct driver should be automatically detected and "
"selected. However, in some cases, the automatic detection mechanism might "
"not be enough, and if no driver is found, the printer might print random "
"characters."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:89
msgid ""
"The solution is to manually select the corresponding driver. On the "
":abbr:`IoT (Internet of Things)` box homepage, click on :guilabel:`Printers "
"Server`, go to the :guilabel:`Printers` tab and select the printer in the "
"list. In the :guilabel:`Administration` drop-down menu, click on "
":guilabel:`Modify Printer`. Follow the steps and select the *make* and "
"*model* corresponding to the printer."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst-1
msgid "Edit the printer connected to the IoT box."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:100
msgid ""
"Epson and Star receipt printers and Zebra label printers do not need a "
"driver to work. Make sure that no driver is selected for those printers."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:104
msgid "Epson configuration special case"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:106
msgid ""
"Most Epson printers support printing receipts in Odoo :abbr:`POS (Point of "
"Sale)` using the `GS v 0` command. However, the following Epson printer "
"models do not support this command:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:109
msgid "TM-U220"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:110
msgid "TM-U230"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:111
msgid "TM-P60"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:112
msgid "TMP-P60II"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:114
msgid ""
"Bypass this issue by configuring the printer to use the `ESC *` command "
"instead."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:117
msgid "Process to force ESC * command"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:120
msgid "Epson printer compatibility"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:122
msgid ""
"The first step is to check whether the printer is incompatible with `GS v 0`"
" command."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:126
msgid ""
"`Epson GS v 0 documentation <https://reference.epson-"
"biz.com/modules/ref_escpos/index.php? content_id=94>`_ for `GS v 0` "
"compatible printers."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:128
msgid ""
"`Epson ESC * documentation <https://reference.epson-"
"biz.com/modules/ref_escpos/index.php ?content_id=88>`_ for `ESC *` "
"compatible printers."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:131
msgid ""
"If the printer is not compatible with the `ESC *` command then the following"
" process is not possible. Should the printer be compatible to use the `ESC "
"*` command to print, follow this process to configure the printer with the "
":abbr:`IoT (Internet of Things)` box."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:136
msgid "IoT box configuration for ESC *"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:138
msgid ""
"To configure the :abbr:`IoT (Internet of Things)` box to use the `ESC *` "
"command to print, go to the :abbr:`IoT (Internet of Things)` box homepage by"
" navigating to :menuselection:`IoT app --> IoT Boxes`. Then click on the "
":guilabel:`IP address` and this will direct to the :abbr:`IoT (Internet of "
"Things)` box homepage."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:143
msgid "**Choosing the printer**"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:145
msgid ""
"Now click on the :guilabel:`Printers server` button. This will redirect the "
"browser to the *CUPS* page. Next, go to :menuselection:`Administration --> "
"Printers --> Add Printer`, choose the printer that should be modified, and "
"then click :guilabel:`Continue`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:150
msgid ""
"If the name of the printer is still uncertain, take the following steps:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:152
msgid "Take note of the listed printers on the *CUPS* page."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:153
msgid "Turn the printer off and refresh the page."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:154
msgid ""
"Now compare the difference with the first list to see which printer "
"disappeared."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:155
msgid "Turn the printer back on and refresh the page again."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:156
msgid "Double-check the list again to see if the printer re-appears."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:157
msgid ""
"The printer that disappeared and reappears again on the listed printers is "
"the name of the printer in question."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:161
msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:163
msgid "**CUPS naming convention**"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:165
msgid ""
"`CUPS` will prompt the administrator for three pieces of information: the "
":guilabel:`Name`, :guilabel:`Description` and the :guilabel:`Location`. The "
"last two pieces of information do not need to be specific, however, the "
":guilabel:`Name` should follow a particular convention to work with the `ESC"
" *` command."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:170
msgid ""
"The :guilabel:`Name` should match this convention: "
"`<printer_name>__IMC_<param_1>_<param_2>_..._<param_n>__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:173
msgid "A breakdown of the naming convention:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:175
msgid ""
"`printer_name`: This is the printer name. It can be any character as long as"
" it does not contain `_`, `/`, `#`, or ` ` (space character)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:177
msgid ""
"`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC "
"*`)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:178
msgid "`param_1`: This stands for the specific parameter:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:180
msgid ""
"`SCALE<X>`: Scale of the picture (with the same aspect ratio). `X` should be"
" an integer describing the scale percentage that should be used."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:184
msgid ""
"`100` is the original size, `50` is half the size, `200` is twice the size."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:186
msgid ""
"`LDV`: *Low Density Vertical* (will be set to *High Density Vertical* if not"
" specified)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:187
msgid ""
"`LDH`: *Low Density Horizontal* (will be set to *High Density Horizontal* if"
" not specified)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:190
msgid ""
"*Density* parameters might need to be configured in a particular way "
"depending on the printer model."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:194
msgid ""
"Visit `Epson's ESC * documentation <https://reference.epson-"
"biz.com/modules/ref_escpos/index.php?content_id=88>`_ and click on the "
"printer model printer in the table above to see if the printer should set "
"these parameters."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:199
msgid "The following are examples of proper and improper name formatting:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:201
msgid "Proper name formatting:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:203
msgid "`EPSONTMm30II__IMC__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:204
msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:206
msgid ""
"Improper name formatting (this will not prevent printing, but the result "
"might not have the expected printed output):"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:209
msgid "`EPSON TMm 30II` -> The name cannot have spaces."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:210
msgid ""
"`EPSONTMm30II` -> The name itself is correct, but it will not use `ESC *`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:211
msgid "`EPSONTMm30II__IMC` -> This name is missing the end `__`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:212
msgid ""
"`EPSONTMm30II__IMC_XDV__` -> The parameter `XDV` does not match any existing"
" parameters."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:213
msgid ""
"`EPSONTMm30II__IMC_SCALE__` -> The parameter `SCALE` is missing the scale "
"value."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:215
msgid "**Finish adding a printer**"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:217
msgid ""
"After setting the name of the printer with the appropriate naming "
"convention, click :guilabel:`Continue`. Next, set the :guilabel:`Make` value"
" to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to "
":guilabel:`Raw Queue (en)`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:221
msgid ""
"After completing these steps, click :guilabel:`Add Printer`. If everything "
"was done correctly, the page should redirect to the *Banners* page."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:224
msgid ""
"At this point the printer should have been created, now the :abbr:`IoT "
"(Internet of Things)` box just needs to detect it and then sync to Odoo's "
"server (this could take a few minutes)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:227
msgid "**Adding the printer to Odoo PoS**"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:229
msgid ""
"Once the printer is visible on the Odoo database, do not forget to choose it"
" in the :abbr:`PoS (Point of Sale)`configuration as the :abbr:`IoT (Internet"
" of Things)` printer. Navigate to :menuselection:`Pos App --> Settings --> "
"Connected Devices --> IoT Box --> Receipt Printer --> Save`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:235
msgid ""
"If the printer was set up incorrectly (it is still printing random text or "
"the printed receipt is too big or small), then it cannot be modified via the"
" printer name with *CUPS*. Instead, the above process can be repeated to set"
" up another printer from scratch to create one with modified parameters."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:240
msgid "**Example setup of the Epson TM-U220B printer using ESC**"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:245
msgid ""
"The following is an example of the troubleshooting process for a TM-U220B "
"printer model using the `ESC *` command. The receipt pictured below is an "
"example of a receipt that is printing correctly due to proper formatting (in"
" theory):"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid "Properly formatted receipt picture from a demo database."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:253
msgid ""
"Trying to print this receipt right-away prior to the proper formatting will "
"not work as the TM-U220B printer model does not support `GS v 0`. Instead "
"random characters will print:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid "Printer paper with seemingly random characters."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:260
msgid ""
"To properly configure formatting for the Epson TM-U220B printer model take "
"the following steps."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:262
msgid ""
"After consulting Epson's website for compatibility for both of the commands:"
" `GS v 0 <https://reference.epson-"
"biz.com/modules/ref_escpos/index.php?content_id=94>`_ and `ESC * "
"<https://reference.epson-"
"biz.com/modules/ref_escpos/index.php?content_id=88>`_, it can be seen that "
"indeed the TM-U220B is not compatible with `GS v 0`, but is compatible with "
"`ESC *`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid "Epson compatibility evaluation from Epson website."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:271
msgid ""
"When adding the printer, *CUPS* will ask which printer should be added:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid "Administration menu, add printer selection."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:277
msgid ""
"In this case, the printer is connected via :abbr:`USB (Universal Serial "
"Bus)` so it won' be part of the :guilabel:`Discovered Network Printers`. "
"Instead it is likely part of the :guilabel:`Unknown` selection under "
":guilabel:`Local Printers`. By unplugging the printer's :abbr:`USB "
"(Universal Serial Bus)` cable from the :abbr:`IoT (Internet of Things)` box "
"and refreshing the page, the :guilabel:`Unknown` printer disappears. By "
"plugging it back in, the printer reappears, so it can be said that this is "
"the printer in question."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:284
msgid ""
"For the naming convention, since it needs to print using the `ESC *` "
"command, it is imperative to add `__IMC`. Reference the printer model on "
"`Epson's ESC * site <https://reference.epson-"
"biz.com/modules/ref_escpos/index.php?content_id=88>`_ to find out more about"
" the *density* parameters."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid "Epson TM-U220 specifications on manufacturer's website."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:293
msgid ""
"For this particular model, TM-U220, `m` should be equal to 0 or 1. While "
"referencing the :guilabel:`Description` below the pink box in the above "
"picture, the `m` values could be 0, 1, 32 or 33. So in this printers case, "
"the `m` value can NOT be 32 or 33 (otherwise there will be random characters"
" printed)."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:298
msgid ""
"The table includes the numeric values: 32 and 33, they both occur if the "
":guilabel:`Number of bits for vertical data` is set to 24. This means that "
"is a *High Vertical Density*. In the case of configuring the Epson TM-U220, "
"the *Low Vertical Density* will need to be forced, as this printer model "
"does not support *High Vertical Density* for this command `ESC *`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:303
msgid ""
"To add a *Low Vertical Density*, add the `LDV` parameter to the naming "
"convention."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid ""
"Add a *Low Vertical Density* (the `LDV` parameter) to the naming convention."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:309
msgid ""
"Click :guilabel:`Continue` to proceed. Next, set the :guilabel:`Make` value "
"to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to "
":guilabel:`Raw Queue (en)`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid "Epson TM-U220 specifications on manufacturers website."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:316
msgid ""
"However, when trying to print with the naming convention: "
"`EpsonTMU220B__IMC_LDV__`, it prints the receipt, but it is too big and "
"outside the margin. To resolve this, add a new printer (and naming "
"convention) with the `SCALE<X>` parameter to adapt to our receipt size."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:320
msgid "Here are some examples:"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:325
msgid "Printer Naming Convention"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:326
msgid "`EpsonTMU220B__IMC_LDV__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:327
msgid "`EpsonTMU220B__IMC_LDV_SCALE75__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:328
msgid "`EpsonTMU220B__IMC_LDV_LDH__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:329
msgid "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid "Receipt example format."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV__."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid ""
"Receipt format using naming convention: EpsonTMU220B__IMC_LDV_SCALE75__."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH__."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:0
msgid ""
"Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH_SCALE35__."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:347
msgid "The Zebra printer does not print anything"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:349
msgid ""
"Zebra printers are quite sensitive to the format of the Zebra Programming "
"Language (ZPL) code that is printed. If nothing comes out of the printer or "
"blank labels are printed, try changing the format of the report that is sent"
" to the printer by accessing :menuselection:`Settings --> Technical --> User"
" Interface --> Views` in :ref:`developer mode <developer-mode>` and look for"
" the corresponding template."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:356
msgid ""
"Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming "
"Language)` files `here <https://supportcommunity.zebra.com/s/article/Print-"
"a-zpl-file-using-the-Generic-Text-Printer>`_."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:363
msgid "The characters read by the barcode scanner do not match the barcode"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:365
msgid ""
"By default, most barcode scanners are configured in the US QWERTY format. If"
" the barcode scanner uses a different layout, go to the form view of the "
"device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select "
"the correct format."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:370
msgid "Nothing happens when a barcode is scanned"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:372
msgid ""
"Make sure that the correct device is selected in the :menuselection:`Point "
"of Sale` configuration and that the barcode is configured to send an `ENTER`"
" character (keycode 28) at the end of every barcode. To do so, navigate to "
":menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> "
"Edit`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:378
msgid "The barcode scanner is detected as a keyboard"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:381
msgid ""
"Some barcode scanners do not advertise themselves as barcode scanners but as"
" a USB keyboard instead, and will not be recognized by the :abbr:`IoT "
"(Internet of Things)` box."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:384
msgid ""
"The device type can be manually changed by going to its form view "
"(:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the"
" :guilabel:`Is scanner` option."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst-1
msgid "Modifying the form view of the barcode scanner."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:392
msgid "Barcode scanner processes barcode characters individually"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:394
msgid ""
"When accessing the mobile version of Odoo from a mobile device, or tablet, "
"paired with a barcode scanner, via the :abbr:`IoT (Internet of Things)` box,"
" the scanner may process each barcode character as an individual scan. In "
"this case, the *Keyboard Layout* option **must** be filled out with the "
"appropriate language of the barcode scanner on the *Barcode Scanner* form "
"page."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:400
msgid ""
"Access the barcode scanner form page by navigating to :menuselection:`IoT "
"App --> Devices --> Barcode Scanner`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst-1
msgid "Barcode scanner form page, with keyboard layout option highlighted."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:407
msgid ""
"The :guilabel:`Keyboard Layout` is language based, and the options available"
" vary, depending on the device and the language of the database. For "
"example: :guilabel:`English (UK)`, :guilabel:`English (US)`, etc."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:415
msgid "The cash drawer does not open"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:417
msgid ""
"The cash drawer should be connected to the printer and the :guilabel:`Cash "
"drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` "
"configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu "
"on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer "
"checkbox`."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:425
msgid ""
"Scales play a crucial role in the checkout process, especially for products "
"sold by weight, rather than fixed pricing."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:429
msgid "Set up Ariva S scales"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:431
msgid ""
"Odoo has determined that a specific setting in Ariva S series scales "
"(manufactured by Mettler-Toledo, LLC.) needs modification, and a dedicated "
"Mettler :abbr:`USB (Universal Serial Bus)`-to-proprietary RJ45 cable is "
"required for the scale to function with Odoo's :abbr:`IoT (Internet of "
"Things)` box."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:436
msgid ""
"To correctly configure the scale for recognition by the :abbr:`IoT (Internet"
" of Things)` box, follow this setup process for the Ariva S series scales."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:440
msgid ""
"It is crucial to use the official Mettler :abbr:`USB (Universal Serial "
"Bus)`-to-RJ45 cable during this process."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:444
msgid "Cable"
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:446
msgid ""
"The Mettler part number is 72256236 - :abbr:`USB (Universal Serial "
"Bus)`-to-:abbr:`POS (Point of Sale)` cable. Contact Mettler, or a partner, "
"to purchase an authentic cable. Note that **no other** cable outside of this"
" Mettler cable works for this configuration. Using a serial-only cable "
"attached to a serial-to-:abbr:`USB (Universal Serial Bus)` adapter is "
"**not** effective."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst-1
msgid "Authentic Mettler USB to POS cable, part number 72256236."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:458
msgid ""
"Refer to Mettler's Setup Guide for Ariva S series scales during the "
"following configuration: `Ariva Checkout Scale User's Guide "
"<https://www.mt.com/dam/RET_DOCS/Ariv.pdf>`_."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:461
msgid ""
"To begin, go to page 17 in the above manual for *Setup*. This guide lists "
"potential settings for the Ariva S series scales."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:464
msgid ""
"Follow the instructions, along with the following process, to set the scale "
"to setup mode. First, hold the **>T<** button for eight seconds, or until "
":guilabel:`CONF` appears."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:467
msgid ""
"Next, press **>T<** until :guilabel:`GRP 3` appears, then press **>0<** to "
"confirm."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:469
msgid ""
"Under :guilabel:`3.1`, ensure the setting is set to :guilabel:`1` (USB "
"Virtual COM ports). Press **>T<** to cycle through the options under group "
"3.1."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:472
msgid ""
"Once :guilabel:`3.1` is set to :guilabel:`1`, press **>0<** to confirm the "
"selection. Continue to press **>0<** until :guilabel:`GRP 4` appears."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:475
msgid "Now, press **>T<** until :guilabel:`EXIT` appears."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:478
msgid "Do **not** make any other changes unless otherwise needed."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:480
msgid ""
"Once :guilabel:`EXIT` appears, press **>0<**. Following this, press **>0<** "
"again to :guilabel:`SAVE`. Now the scale restarts."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:483
msgid ""
"Finally, restart the :abbr:`IoT (Internet of Things)` box to recognize the "
"changes made on the scale's configuration. After restarting, the scale "
"appears as `Toledo 8217`, as opposed to the previous display, where it "
"appeared as `Adam Equipment Serial`."
msgstr ""
#: ../../content/applications/general/iot/devices.rst:5
msgid "Devices"
msgstr "Пристрої"
#: ../../content/applications/general/iot/devices/camera.rst:3
msgid "Connect a camera"
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:5
msgid ""
"A camera can be connected to an :abbr:`IoT (Internet of Things)` box with an"
" Odoo database in just a few steps. Once a camera is connected to an "
":abbr:`IoT (Internet of Things)` box, it can be used in a manufacturing "
"process, or it can be linked to a quality control point/quality check. Doing"
" so allows for the taking of pictures when a chosen quality control "
"point/check has been reached, or when a specific key is pressed during "
"manufacturing."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:12
#: ../../content/applications/general/iot/devices/footswitch.rst:14
#: ../../content/applications/general/iot/devices/printer.rst:11
#: ../../content/applications/general/iot/devices/scale.rst:10
#: ../../content/applications/general/iot/devices/screen.rst:18
msgid "Connection"
msgstr "З'єднання"
#: ../../content/applications/general/iot/devices/camera.rst:14
msgid ""
"To connect a camera to an :abbr:`IoT (Internet of Things)` box, simply "
"connect the two via cable. This is usually done with a :abbr:`USB (Universal"
" Serial Bus)` cable of some sort."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:17
msgid ""
"If the camera is `supported <https://www.odoo.com/page/iot-hardware>`_, "
"there is no need to set up anything, as it'll be detected as soon as it's "
"connected."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst-1
msgid "Camera recognized on the IoT box."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:25
msgid "Link camera to quality control point in manufacturing process"
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:27
msgid ""
"In the :menuselection:`Quality app`, a device can be set up on a "
":guilabel:`Quality Control Point`. To do that, navigate to the "
":menuselection:`Quality app --> Quality Control --> Control Points` and open"
" the desired :guilabel:`Control Point` that'll be linked to the camera."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:31
msgid ""
"On the control point form, edit the control point by selecting the "
":guilabel:`Type` field, and clicking on :guilabel:`Take a Picture` from the "
"drop-down menu. Doing so reveals a field called :guilabel:`Device`, wherein "
"the attached *device* can be selected. :guilabel:`Save` the changes, if "
"required."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst-1
msgid "Setting up the device on the quality control point."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:40
msgid ""
"The camera is now useable with the selected quality control point. When the "
"quality control point is reached during the manufacturing process, the "
"database prompts the operator to take a picture."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst-1
msgid "Graphic user interface of the device on the quality control point."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:48
msgid ""
"Quality control points can also be accessed by navigating to "
":menuselection:`IoT App --> Devices`. From here, select the device. There is"
" a :guilabel:`Quality Control Points` tab, where they can be added with the "
"device."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:53
msgid ""
"On a quality check form, the :guilabel:`Type` of check can also be specified"
" to :guilabel:`Take a Picture`. Navigate to :menuselection:`Quality app --> "
"Quality Control --> Quality Checks --> New` to create a new quality check "
"from the :guilabel:`Quality Checks` page."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:58
#: ../../content/applications/general/iot/devices/measurement_tool.rst:66
#: ../../content/applications/general/iot/devices/printer.rst:70
msgid ""
":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_control_points`"
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:59
#: ../../content/applications/general/iot/devices/measurement_tool.rst:67
#: ../../content/applications/general/iot/devices/printer.rst:71
msgid ""
":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_alerts`"
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:62
msgid "Link camera to a work center in the Manufacturing app"
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:64
msgid ""
"To link a camera to an action, it first needs to be configured on a work "
"center. Navigate to :menuselection:`Manufacturing app --> Configuration --> "
"Work Centers`. Next, go to the desired :guilabel:`Work Center` in which a "
"camera will be used to reveal that specific work center's detail form. From "
"here, add the device in the :guilabel:`IoT Triggers` tab, in the "
":guilabel:`Device` column, by clicking :guilabel:`Add a Line`."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:70
msgid ""
"Now, the camera device can be linked to the :guilabel:`Action` column drop-"
"down option labeled :guilabel:`Take a Picture`. A key can also be added to "
"trigger the action."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:74
msgid ""
"The first trigger listed is chosen first. The order of triggers matters, and"
" they can be dragged into any desired order."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:78
msgid ""
"On the :guilabel:`Work Order` screen, a status graphic indicates whether the"
" database is correctly connected to the camera."
msgstr ""
#: ../../content/applications/general/iot/devices/camera.rst:82
#: ../../content/applications/general/iot/devices/footswitch.rst:52
#: ../../content/applications/general/iot/devices/measurement_tool.rst:90
#: ../../content/applications/general/iot/devices/printer.rst:95
msgid ":ref:`workcenter_iot`"
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst:3
msgid "Connect a footswitch"
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst:5
msgid ""
"When working in a manufacturing environment, it's always better for an "
"operator to have both hands available at all times. Odoo's :abbr:`IoT "
"(Internet of Things)` box makes this possible when using a footswitch."
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst:9
msgid ""
"In fact, with a footswitch, the operator is able to go from one screen to "
"another, and perform actions using their foot. This can be configured in "
"just a few steps on the work center in the *Manufacturing* app."
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst:16
msgid ""
"To connect a footswitch to the :abbr:`IoT (Internet of Things)` box, connect"
" the two devices via cable. More often than not, this is done with a "
":abbr:`USB (Universal Serial Bus)` cable."
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst:19
msgid ""
"If the footswitch is a `supported device <https://www.odoo.com/page/iot-"
"hardware>`_, there is no need to take further action, since it'll be "
"automatically detected when connected."
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst-1
msgid "Footswitch recognized on the IoT box."
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst:27
msgid "Link a footswitch to a work center in the Odoo Manufacturing app"
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst:29
msgid ""
"To link a footswitch to an action, it first needs to be configured on a work"
" center. Navigate to :menuselection:`Manufacturing app --> Configuration -->"
" Work Centers`. From here, go to the desired :guilabel:`Work Center` in "
"which the footswitch will be used, and add the device in the :guilabel:`IoT "
"Triggers` tab, under the :guilabel:`Device` column, by selecting "
":guilabel:`Add a Line`. Doing so means the footswitch can be linked to an "
"option in the :guilabel:`Action` column drop-down, and optionally, a key can"
" be added to trigger it. An example of an :guilabel:`Action` in the "
"*Manufacturing app* could be the :guilabel:`Validate` or :guilabel:`Mark as "
"Done` buttons on a manufacturing work order."
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst-1
msgid "Footswitch trigger setup on the Odoo database."
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst:43
msgid ""
"It should be noted that the first listed trigger is chosen first. So, the "
"order matters, and these triggers can be dragged into any order. In the "
"picture above, using the footswitch automatically skips the part of the "
"process that's currently being worked on."
msgstr ""
#: ../../content/applications/general/iot/devices/footswitch.rst:48
msgid ""
"On the :guilabel:`Work Order` screen, a status graphic indicates whether the"
" database is correctly connected to the footswitch."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:3
msgid "Connect a measurement tool"
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:5
msgid ""
"With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect "
"measurement tools to the Odoo database for use in the *Quality app* on a "
"quality control point/quality check, or for use in a work center during the "
"manufacturing process."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:9
msgid ""
"Find the list of supported devices here: `Supported devices "
"<https://www.odoo.com/page/iot-hardware>`_."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:13
msgid "Connect with universal serial bus (USB)"
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:15
msgid ""
"To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the "
":abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of "
"Things)` box, and the device appears in the Odoo database."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst-1
msgid "Measurement tool recognized on the IoT box."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:24
msgid "Connect with bluetooth"
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:26
msgid ""
"Activate the Bluetooth functionality on the device (see the device manual "
"for further explanation), and the :abbr:`IoT (Internet of Things)` box "
"automatically connects to the device."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst-1
msgid "Bluetooth indicator on measurement tool."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:35
msgid ""
"Link a measurement tool to a quality control point in the manufacturing "
"process"
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:37
msgid ""
"In the *Quality app*, a device can be set up on a quality control point. To "
"do that, navigate to :menuselection:`Quality app --> Quality Control --> "
"Control Points`, and open the desired control point to which the measurement"
" tool should be linked."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:41
msgid ""
"From here, edit the control point, by selecting the :guilabel:`Type` field, "
"and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a"
" field called :guilabel:`Device`, where the attached device can be selected."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:45
msgid ""
"Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. "
":guilabel:`Save` the changes, if required."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:48
msgid ""
"At this point, the measurement tool is linked to the chosen quality control "
"point. The value, which usually needs to be changed manually, is "
"automatically updated while the tool is being used."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst-1
msgid "Measurement tool input in the Odoo database."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:56
#: ../../content/applications/general/iot/devices/printer.rst:60
msgid ""
"Quality control points can also be accessed by navigating to "
":menuselection:`IoT App --> Devices`, then select the device. There is a "
":guilabel:`Quality Control Points` tab, where they can be added with the "
"device."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:61
msgid ""
"On a quality check detail form, the :guilabel:`Type` of check can also be "
"specified to :guilabel:`Measure`. Access a new quality check detail page, by"
" navigating to :menuselection:`Quality app --> Quality Control --> Quality "
"Checks --> New`."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:70
msgid "Link a measurement tool to a work center in the Manufacturing app"
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:72
msgid ""
"To link a measurement tool to an action, it first needs to be configured on "
"a work center. To do that, navigate to :menuselection:`Manufacturing app -->"
" Configuration --> Work Centers`. Then, select the desired work center in "
"which the measurement tool will be used."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:76
msgid ""
"On the work center page, add the device in the :guilabel:`IoT Triggers` tab,"
" under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. "
"Then, the measurement tool can be linked to the :guilabel:`Action` drop-down"
" menu option labeled :guilabel:`Take Measure`. A key can be added to trigger"
" the action."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:82
msgid ""
"It should be noted that the first listed trigger is chosen first. The order "
"matters, and these triggers can be dragged into any order."
msgstr ""
#: ../../content/applications/general/iot/devices/measurement_tool.rst:86
msgid ""
"On the :guilabel:`Work Order` screen, a status graphic indicates whether the"
" database is correctly connected to the measurement tool."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:3
msgid "Connect a printer"
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:5
msgid ""
"Printer installation can be done in a few easy steps. The printer can be "
"used to print receipts, labels, orders, or even reports from the different "
"Odoo apps. In addition, printer actions can be assigned as an *action on a "
"trigger* during the manufacturing process, or added onto a quality control "
"point or a quality check."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:13
msgid ""
"The :abbr:`IoT (Internet of Things)` box supports printers connected through"
" :abbr:`USB (Universal Serial Bus)`, network connection, or Bluetooth. "
"`Supported printers <https://www.odoo.com/page/iot-hardware>`__ are detected"
" automatically, and appear in the :guilabel:`Devices` list of the *IoT app*."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst-1
msgid "The printer as it would appear in the IoT app devices list."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:23
msgid ""
"The printer can take up to two minutes to appear in the *IoT app* devices "
"list."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:26
msgid "Link printer"
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:29
msgid "Link printer to work orders"
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:31
msgid ""
"*Work Orders* can be linked to printers, via a quality control point, to "
"print labels for manufactured products."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:34
msgid ""
"In the *Quality app*, a device can be set up on a quality control point. To "
"do that, go to the :menuselection:`Quality app --> Quality Control --> "
"Control Points`, and open the desired control point to which the printer "
"will be linked."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:39
msgid ""
"A *Manufacturing Operation* and *Work Order Operation* need to be attached "
"to a quality control point before the :guilabel:`Type` field allows for the "
":guilabel:`Print Label` option to be selected."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:43
msgid ""
"From here, edit the control point, by selecting the :guilabel:`Type` field, "
"and selecting :guilabel:`Print Label` from the drop-down menu of options. "
"Doing so reveals a field called :guilabel:`Device`, where the attached "
"*device* can be selected. :guilabel:`Save` the changes, if required."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst-1
msgid "This is the quality control point setup."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:52
msgid ""
"The printer can now be used with the selected quality control point. When "
"the quality control point is reached during the manufacturing process, the "
"database presents the option to print labels for a specific product."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:65
msgid ""
"On a quality check detail form, the :guilabel:`Type` of check can also be "
"specified to :guilabel:`Print Label`. To create new quality checks, navigate"
" to :menuselection:`Quality app --> Quality Control --> Quality Checks --> "
"New`."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:74
msgid "Link a printer to a work center in the Manufacturing app"
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:76
msgid ""
"To link a printer to an action, it first needs to be configured on a work "
"center. To do that, navigate to :menuselection:`Manufacturing app --> "
"Configuration --> Work Centers`. From here, select the desired work center "
"in which the printer will be used. Next, add the device in the "
":guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by "
"selecting :guilabel:`Add a Line`."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:82
msgid ""
"Then, the printer can be linked to either of the following options in the "
":guilabel:`Actions` drop-down menu: :guilabel:`Print Labels`, "
":guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can "
"also be added to trigger the action."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:87
msgid ""
"The first listed trigger on the form will be chosen first. So, the order "
"matters, and these triggers can be dragged into any order."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:91
msgid ""
"On the :guilabel:`Work Order` screen, a status graphic indicates whether the"
" database is correctly connected to the printer."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:98
msgid "Link printer to reports"
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:100
msgid ""
"It's also possible to link a type of report to a certain printer. In the "
"*IoT app*, go to the :guilabel:`Devices` menu, and select the desired "
"printer that needs to be configured."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:103
msgid ""
"From here, click :guilabel:`Edit`, go to the :guilabel:`Printer Reports` "
"tab, and select :guilabel:`Add a line`. In the window that appears, check "
"all the types of :guilabel:`Reports` that should be linked to this printer."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst-1
msgid "The printer devices listed in the IoT Devices menu."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:111
msgid ""
"Now, each time :guilabel:`Print` is selected in the control panel, instead "
"of downloading a PDF, a pop-up appears which displays all the printer(s) "
"linked to the report. Then Odoo sends the report to the selected printer(s),"
" and automatically prints it."
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:116
msgid ""
":doc:`POS Order Printing "
"<../../../sales/point_of_sale/restaurant/kitchen_printing>`"
msgstr ""
#: ../../content/applications/general/iot/devices/printer.rst:119
msgid ""
"Reports can also be configured in the :guilabel:`Technical Menu` while in "
":ref:`debug mode <developer-mode>`. To do that, navigate to "
":menuselection:`Settings App --> Technical Menu --> Actions --> Reports`. "
"From here, the individual report can be found in this list, where the "
":guilabel:`IoT Device` can be set on the report."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:3
msgid "Connect a scale"
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:5
msgid ""
"A scale can be connected to the :abbr:`IoT (Internet of Things)` box on an "
"Odoo database in a few easy steps. After setup, the *Point of Sale* app can "
"be used to weigh products, which is helpful if their prices are calculated "
"based on weight."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:12
msgid ""
"To link the scale to the :abbr:`IoT (Internet of Things)` box, connect it "
"with a :abbr:`USB (Universal Serial Bus)` cable."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:16
msgid ""
"In some cases, a serial port to :abbr:`USB (Universal Serial Bus)` adapter "
"may be needed."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:18
msgid ""
"If the scale is `compatible with Odoo IoT Box "
"<https://www.odoo.com/page/iot-hardware>`_, there is no need to set up "
"anything because it will be automatically detected as soon as it is "
"connected."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst-1
msgid "IOT box auto detection."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:25
msgid ""
"The :abbr:`IoT (Internet of Things)` box may need to be restarted and the "
"scale's drivers may need to be downloaded to the box in some cases. To "
"update the drivers, go to the :abbr:`IoT (Internet of Things)` box homepage "
"and click on :guilabel:`Drivers List`. Then, click on :guilabel:`Load "
"Drivers`."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst-1
msgid "View of the IoT box settings and driver list."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:34
msgid ""
"If loading the drivers still doesn't allow for the scale to function, it may"
" be that the scale is not compatible with the Odoo :abbr:`IoT (Internet of "
"Things)` box. In this case, a different scale will need to be used."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:39
msgid "Use a scale in a point of sale (POS) system"
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:41
msgid ""
"To use the scale in the *Point of Sale app*, go to :menuselection:`PoS app "
"--> 3-Dot Menu on the PoS --> Settings`, then enable the :abbr:`IoT "
"(Internet of Things)` box feature. After this is complete, the scale device "
"can be set."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:45
msgid ""
"Select the scale from the :guilabel:`Electronic Scale` drop-down menu. Then "
"click :guilabel:`Save` to save the changes, if required."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst-1
msgid "List of the external tools that can be used with PoS and the IoT box."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst:52
msgid ""
"The scale is now available in all the :abbr:`PoS (Point of Sale)` sessions. "
"Now, if a product has a price per weight set, clicking on it on the "
":guilabel:`PoS` screen opens the scale screen, where the cashier can weigh "
"the product and add the correct price to the cart."
msgstr ""
#: ../../content/applications/general/iot/devices/scale.rst-1
msgid "Electronic Scale dashboard view when no items are being weighed."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:3
msgid "Connect a screen"
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:5
msgid ""
"In Odoo, an :abbr:`IoT (Internet of Things)` box can be connected to a "
"screen display. After being configured, the screen can be used to display a "
"Point of Sale (PoS) order to a client."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:10
msgid "An example of a PoS (point of sale) order on a screen display."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:12
msgid ""
"Access the customer display by going to the :abbr:`IoT (Internet of Things)`"
" box homepage and clicking on the :guilabel:`PoS Display` button. To get to "
"the :abbr:`IoT (Internet of Things)` box homepage, navigate to "
":menuselection:`IoT app --> IoT Boxes` and click on the :abbr:`IoT (Internet"
" of Things)` box homepage link."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:20
msgid ""
"The way to connect the screen display to the :abbr:`IoT (Internet of "
"Things)` box differs depending on the model."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:25
msgid "IoT Box model 4"
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:27
msgid ""
"Connect up to two screens with micro-HDMI cables on the side of the "
":abbr:`IoT (Internet of Things)` box. If two screens are connected, they can"
" display distinct content (see :ref:`Screen Usage <iot/usage_screen>`)."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:31
msgid "IoT Box model 3"
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:33
msgid ""
"Connect the screen with an HDMI cable on the side of the :abbr:`IoT "
"(Internet of Things)` box."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:36
msgid ":ref:`See the Raspberry Pi Schema <iot/connect_schema>`."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:39
msgid ""
"Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` "
"box is switched on. If it is already on, connect the screen(s), and then "
"restart the :abbr:`IoT (Internet of Things)` box by unplugging it for ten "
"seconds and plugging it back into its power source."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:44
msgid ""
"The usage of HDMI/micro-HDMI adapters may cause issues which will result in "
"a blank, black screen on the screen display. Using the specific cable for "
"the display connection is recommended."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:47
msgid ""
"If the connection was successful, the screen should display the "
":guilabel:`POS Client display` screen."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst-1
msgid ""
"The default \"POS Client Display\" screen that appears when a screen display is successfully\n"
"connected to an IoT box."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:55
msgid ""
"The screen should also appear in the list of :guilabel:`Displays` on the "
":abbr:`IoT (Internet of Things)` box homepage. Alternatively, the display "
"can be seen by accessing :menuselection:`IoT app --> Devices`."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst-1
msgid "An example of a screen display name shown on the IoT Box Home Page."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:64
msgid ""
"If no screen is detected, a default display named :guilabel:`Distant "
"Display` will be displayed instead. This indicates that there is no hardware"
" screen connected."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:67
msgid "The \"Distant Display\" screen name will be used if no screen is detected."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:74
msgid "Usage"
msgstr "Застосування"
#: ../../content/applications/general/iot/devices/screen.rst:77
msgid "Show Point of Sale orders to customers"
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:79
msgid ""
"To use the screen in the *Point of Sale app*, go to :menuselection:`Point of"
" Sale --> Configuration --> Point of Sale`, select a :abbr:`PoS (Point of "
"Sale)`, click :guilabel:`Edit` if necessary, and enable the :guilabel:`IoT "
"Box` feature."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:83
msgid ""
"Next, select the screen from the :guilabel:`Customer Display` drop-down "
"menu. Then click :guilabel:`Save`, if required."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst-1
msgid "Connect the screen display to the Point of Sale app."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:90
msgid ""
"The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A "
"screen icon will appear in the menu at the top of the screen to indicate the"
" screen's connection status."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst-1
msgid ""
"The \"screen\" icon on the Point of Sale display shows the connection status with the\n"
"screen."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:98
msgid ""
"The screen will automatically show the :abbr:`PoS (Point of Sale)` orders "
"and update when changes are made to the order."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst-1
msgid "An example of a PoS order on a screen display."
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:106
msgid "Display a website on the screen"
msgstr ""
#: ../../content/applications/general/iot/devices/screen.rst:108
msgid ""
"Open the screen form view by accessing :menuselection:`IoT app --> Devices "
"--> Customer Display`. This allows the user to choose a particular website "
"URL to display on the screen using the :guilabel:`Display URL` field."
msgstr ""
#: ../../content/applications/general/users.rst:5
msgid "Users"
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.rst:12
msgid ":doc:`users/language`"
msgstr ""
#: ../../content/applications/general/users.rst:13
msgid ":doc:`users/access_rights`"
msgstr ""
#: ../../content/applications/general/users.rst:18
msgid "Add individual users"
msgstr "Додайте окремих користувачів"
#: ../../content/applications/general/users.rst:20
msgid ""
"Go to :menuselection:`Settings --> Manage Users` and click on *Create*."
msgstr ""
#: ../../content/applications/general/users.rst-1
msgid "View of the settings page emphasizing the manage users field in Odoo"
msgstr ""
#: ../../content/applications/general/users.rst:28
msgid ""
"Fill in the form with the needed information. Under the tab :doc:`Access "
"Rights <users/access_rights>` choose the group within each application the "
"user can have access to."
msgstr ""
#: ../../content/applications/general/users.rst:29
msgid ""
"The list of applications shown is based on the applications installed on the"
" database."
msgstr ""
#: ../../content/applications/general/users.rst-1
msgid "View of a users form emphasizing the access rights tab in Odoo"
msgstr ""
#: ../../content/applications/general/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.rst-1
msgid ""
"View of a users form with a notification that the invitation email has been"
" sent in Odoo"
msgstr ""
#: ../../content/applications/general/users.rst:41
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.rst:45
msgid ""
"With the :ref:`developer mode <developer-mode>` activated, *User Types* can "
"be selected."
msgstr ""
#: ../../content/applications/general/users.rst-1
msgid ""
"View of a users form in developer mode emphasizing the user type field in "
"Odoo"
msgstr ""
#: ../../content/applications/general/users.rst:51
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.rst:58
msgid "Deactivate users"
msgstr ""
#: ../../content/applications/general/users.rst:60
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.rst:64
msgid "**Never** deactivate the main user (*admin*)."
msgstr ""
#: ../../content/applications/general/users.rst:69
msgid "Passwords management"
msgstr ""
#: ../../content/applications/general/users.rst:74
msgid "Reset passwords"
msgstr ""
#: ../../content/applications/general/users.rst:79
msgid "Enable password resets from login page"
msgstr ""
#: ../../content/applications/general/users.rst:81
msgid "It is possible to enable password resets directly from the login page."
msgstr ""
#: ../../content/applications/general/users.rst:83
msgid ""
"To do so, go to :menuselection:`Settings --> Permissions`, activate "
"**Password Reset** and *Save*."
msgstr ""
#: ../../content/applications/general/users.rst-1
msgid "Enabling Password Reset in Odoo Settings"
msgstr ""
#: ../../content/applications/general/users.rst:91
msgid "Send reset instructions to users"
msgstr ""
#: ../../content/applications/general/users.rst:93
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.rst:98
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.rst:101
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.rst-1
msgid "Example of an email with a password reset link for an Odoo account"
msgstr ""
#: ../../content/applications/general/users.rst:110
msgid "Change users passwords"
msgstr ""
#: ../../content/applications/general/users.rst:112
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.rst-1
msgid "Change another user's password on Odoo"
msgstr ""
#: ../../content/applications/general/users.rst:118
msgid "Enter a new password and confirm by clicking on *Change Password*."
msgstr ""
#: ../../content/applications/general/users.rst:121
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.rst:125
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.rst:131
msgid "Multi Companies"
msgstr "Мультикомпанії"
#: ../../content/applications/general/users.rst:133
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.rst:137
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.rst-1
msgid "View of a users form emphasizing the multi companies field in Odoo"
msgstr ""
#: ../../content/applications/general/users.rst:146
msgid ":doc:`companies`"
msgstr ""
#: ../../content/applications/general/users/2fa.rst:3
msgid "Two-factor Authentication"
msgstr "Двофакторна аутентифікація"
#: ../../content/applications/general/users/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/users/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/users/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/users/2fa.rst:18
msgid "Requirements"
msgstr "Вимоги"
#: ../../content/applications/general/users/2fa.rst:20
msgid ""
"These lists are just examples, they are not endorsements of any specific "
"software."
msgstr ""
#: ../../content/applications/general/users/2fa.rst:23
msgid ""
"If you don't already have one, you will need to choose an authenticator."
msgstr ""
#: ../../content/applications/general/users/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/users/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/users/2fa.rst:43
msgid "Setting up two-factor authentication"
msgstr ""
#: ../../content/applications/general/users/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/users/2fa.rst:52
msgid ""
"Open the :guilabel:`Account Security` tab, then click the :guilabel:`Enable "
"two-factor authentication` button:"
msgstr ""
#: ../../content/applications/general/users/2fa.rst:58
msgid ""
"Because this is a security-sensitive action, you will need to input your "
"password:"
msgstr ""
#: ../../content/applications/general/users/2fa.rst:64
msgid "After which you will see this screen with a barcode:"
msgstr ""
#: ../../content/applications/general/users/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/users/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/users/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/users/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/users/2fa.rst:100
msgid ""
"Congratulation, your account is now protected by two-factor authentication!"
msgstr ""
#: ../../content/applications/general/users/2fa.rst:107
msgid "Logging in"
msgstr ""
#: ../../content/applications/general/users/2fa.rst:109
msgid "You should now :guilabel:`Log out` to follow along."
msgstr ""
#: ../../content/applications/general/users/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/users/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/users/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/users/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/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 groups 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 groups 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 groups 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 groups 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 groups 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/azure.rst:3
msgid "Microsoft Azure sign-in authentication"
msgstr ""
#: ../../content/applications/general/users/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/users/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/users/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/users/azure.rst:18
msgid ":doc:`../../productivity/calendar/outlook`"
msgstr ""
#: ../../content/applications/general/users/azure.rst:19
msgid ":doc:`../email_communication/azure_oauth`"
msgstr ""
#: ../../content/applications/general/users/azure.rst:24
msgid ""
"Integrating the Microsoft sign-in function requires configuration on "
"Microsoft and Odoo."
msgstr ""
#: ../../content/applications/general/users/azure.rst:27
msgid "Odoo System Parameter"
msgstr ""
#: ../../content/applications/general/users/azure.rst:29
msgid ""
"First activate the :ref:`developer mode <developer-mode>`, and then go to "
":menuselection:`Settings --> Technical --> System Parameters`."
msgstr ""
#: ../../content/applications/general/users/azure.rst:32
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/users/azure.rst:37
msgid "Microsoft Azure dashboard"
msgstr ""
#: ../../content/applications/general/users/azure.rst:42
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/users/azure.rst:49
msgid ""
"A user with administrative access to the *Azure Settings* must connect and "
"perform the following configuration steps below."
msgstr ""
#: ../../content/applications/general/users/azure.rst:52
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/users/azure.rst:55
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/users/azure.rst:62
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/users/azure.rst:67
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/users/azure.rst:71
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/users/azure.rst:78
msgid "Authentication"
msgstr "Аутентифікація"
#: ../../content/applications/general/users/azure.rst:80
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/users/azure.rst:83
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/users/azure.rst-1
msgid "Authentication settings and endpoint tokens."
msgstr ""
#: ../../content/applications/general/users/azure.rst:95
msgid "Click :guilabel:`Save` to ensure these settings are saved."
msgstr ""
#: ../../content/applications/general/users/azure.rst:98
msgid "Gather credentials"
msgstr ""
#: ../../content/applications/general/users/azure.rst:100
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/users/azure.rst:105
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/users/azure.rst-1
msgid "Application ID and OAuth 2.0 authorization endpoint (v2) credentials."
msgstr ""
#: ../../content/applications/general/users/azure.rst:114
msgid "Odoo setup"
msgstr ""
#: ../../content/applications/general/users/azure.rst:116
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/users/azure.rst:121
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/users/azure.rst:125
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/users/azure.rst:129
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/users/azure.rst:132
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/users/azure.rst:136
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/users/azure.rst-1
msgid "Odoo provider setup in the Settings application."
msgstr ""
#: ../../content/applications/general/users/azure.rst:144
msgid ""
":guilabel:`Save` the changes to complete the OAuth authentication setup in "
"Odoo."
msgstr ""
#: ../../content/applications/general/users/azure.rst:147
msgid "User experience flows"
msgstr ""
#: ../../content/applications/general/users/azure.rst:149
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/users/azure.rst:154
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/users/azure.rst:159
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/users/azure.rst-1
msgid "Microsoft Outlook login page."
msgstr ""
#: ../../content/applications/general/users/azure.rst:168
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/users/azure.rst-1
msgid "Enter Microsoft login credentials."
msgstr ""
#: ../../content/applications/general/users/azure.rst:176
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/users/azure.rst-1
msgid ""
"Accept Microsoft conditions for permission access to your account "
"information."
msgstr ""
#: ../../content/applications/general/users/google.rst:3
msgid "Google Sign-In Authentication"
msgstr ""
#: ../../content/applications/general/users/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/users/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/users/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/users/google.rst:19
msgid ":doc:`../email_communication/google_oauth`"
msgstr ""
#: ../../content/applications/general/users/google.rst:26
msgid ""
"The integration of the Google sign-in function requires configuration both "
"on Google *and* Odoo."
msgstr ""
#: ../../content/applications/general/users/google.rst:31
msgid "Google API Dashboard"
msgstr ""
#: ../../content/applications/general/users/google.rst:33
msgid ""
"Go to the `Google API Dashboard <https://console.developers.google.com/>`_."
msgstr ""
#: ../../content/applications/general/users/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/users/google.rst:0
msgid "Filling out the details of a new project."
msgstr ""
#: ../../content/applications/general/users/google.rst:43
msgid "Choose the name of the company from the drop-down menu."
msgstr ""
#: ../../content/applications/general/users/google.rst:50
msgid "On the left side menu, click on :menuselection:`OAuth consent screen`."
msgstr ""
#: ../../content/applications/general/users/google.rst:0
msgid "Google OAuth consent selection menu."
msgstr ""
#: ../../content/applications/general/users/google.rst:56
msgid ""
"Choose one of the options (:guilabel:`Internal` / :guilabel:`External`), and"
" click on :guilabel:`Create`."
msgstr ""
#: ../../content/applications/general/users/google.rst:0
msgid "Choice of a user type in OAuth consent."
msgstr ""
#: ../../content/applications/general/users/google.rst:71
msgid ""
"Fill out the required details and domain info, then click on :guilabel:`Save"
" and Continue`."
msgstr ""
#: ../../content/applications/general/users/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/users/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/users/google.rst:77
msgid ""
"Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`."
msgstr ""
#: ../../content/applications/general/users/google.rst:82
msgid "Credentials"
msgstr "Повноваження"
#: ../../content/applications/general/users/google.rst:84
msgid "On the left side menu, click on :menuselection:`Credentials`."
msgstr ""
#: ../../content/applications/general/users/google.rst:0
msgid "Credentials button menu."
msgstr ""
#: ../../content/applications/general/users/google.rst:90
msgid ""
"Click on :guilabel:`Create Credentials`, and select :guilabel:`OAuth client "
"ID`."
msgstr ""
#: ../../content/applications/general/users/google.rst:0
msgid "OAuth client id selection."
msgstr ""
#: ../../content/applications/general/users/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/users/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/users/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/users/google.rst:110
msgid "Google Authentication on Odoo"
msgstr ""
#: ../../content/applications/general/users/google.rst:115
msgid "Retrieve the Client ID"
msgstr ""
#: ../../content/applications/general/users/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/users/google.rst-1
msgid "Google OAuth Client ID generated."
msgstr ""
#: ../../content/applications/general/users/google.rst:127
msgid "Odoo activation"
msgstr ""
#: ../../content/applications/general/users/google.rst:129
msgid ""
"Go to :menuselection:`Odoo General Settings --> Integrations` and activate "
":guilabel:`OAuth Authentication`."
msgstr ""
#: ../../content/applications/general/users/google.rst:133
msgid "Odoo may prompt the user to log-in again after this step."
msgstr ""
#: ../../content/applications/general/users/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/users/google.rst:0
msgid "Filling out the client id in Odoo settings."
msgstr ""
#: ../../content/applications/general/users/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/users/google.rst:151
msgid "Log in to Odoo with Google"
msgstr ""
#: ../../content/applications/general/users/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/users/google.rst:156
msgid "Reset password screen with \"Log in with Google\" button."
msgstr ""
#: ../../content/applications/general/users/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/users/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/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 ""
"Odoo надає вам можливість керувати Odoo різними мовами, і кожен користувач "
"може використовувати Odoo своєю мовою."
#: ../../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 "Перше, що потрібно зробити, це завантажити бажану мову у версію Odoo."
#: ../../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 ""
"На загальній інформаційній панелі натисніть на додаток **Налаштування**; у "
"верхньому лівому куті сторінки виберіть :menuselection:`Переклад --> "
"Завантажити переклад`, виберіть мову для встановлення та натисніть на "
"**ЗАВАНТАЖИТИ**."
#: ../../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 ""
"Odoo також дає вам можливість для кожного користувача вибрати його бажану "
"мову."
#: ../../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 ""
"Щоби змінити мову іншого користувача, виберіть :menuselection:`Користувачі "
"--> Користувачі` в додатку Налаштування. Тут ви маєте список всіх "
"користувачів, і ви можете вибрати користувача, для якого ви хочете змінити "
"мову. Виберіть користувача та натисніть **Редагувати** у верхньому лівому "
"куті. У розділі Параметри ви можете змінити мову на будь-яку раніше "
"встановлену та натисніть **ЗБЕРЕГТИ**."
#: ../../content/applications/general/users/language.rst:61
msgid ":doc:`../../websites/website/configuration/translate`"
msgstr ""
#: ../../content/applications/general/users/ldap.rst:3
msgid "Sign in with LDAP"
msgstr ""
#: ../../content/applications/general/users/ldap.rst:5
msgid ""
"Install the Lightweight Directory Access Protocol (LDAP) module in General "
"Settings."
msgstr ""
#: ../../content/applications/general/users/ldap.rst:7
msgid ""
"Click on **Create** in Setup the :abbr:`LDAP (Lightweight Directory Access "
"Protocol)` Server."
msgstr ""
#: ../../content/applications/general/users/ldap.rst-1
msgid ""
"LDAP Authentication checkbox highlighted in the integrations settings on "
"Odoo."
msgstr ""
#: ../../content/applications/general/users/ldap.rst-1
msgid "Create highlighted in the LDAP server settings."
msgstr ""
#: ../../content/applications/general/users/ldap.rst:17
msgid "Choose the company using the LDAP."
msgstr ""
#: ../../content/applications/general/users/ldap.rst-1
msgid "Select the company drop-down menu highlighted in LDAP setup."
msgstr ""
#: ../../content/applications/general/users/ldap.rst:23
msgid ""
"In **Server Information**, enter the IP address of the server and the port "
"it listens to."
msgstr ""
#: ../../content/applications/general/users/ldap.rst:25
msgid "Tick **Use TLS** if the server is compatible."
msgstr ""
#: ../../content/applications/general/users/ldap.rst-1
msgid "LDAP server settings highlighted in LDAP server setup on Odoo."
msgstr ""
#: ../../content/applications/general/users/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/users/ldap.rst-1
msgid "Login information highlighted in LDAP server setup on Odoo."
msgstr ""
#: ../../content/applications/general/users/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/users/ldap.rst:41
msgid "In **LDAP filter**, enter ``uid=%s``"
msgstr "У **фільтрі LDAP**, введіть ``uid=%s``"
#: ../../content/applications/general/users/ldap.rst-1
msgid "Process parameter highlighted in LDAP server setup on Odoo."
msgstr ""
#: ../../content/applications/general/users/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/users/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/users/ldap.rst-1
msgid "User information highlighted on LDAP server setup on Odoo."
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:143
msgid "Add two-factor authentication"
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 ""