documentation/locale/pl/LC_MESSAGES/general.po

# 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:
# Dariusz Żbikowski <darek@krokus.com.pl>, 2024
# Tadeusz Karpiński <tadeuszkarpinski@gmail.com>, 2024
# Musibau Hammed, 2025
# Emmanuel Clement, 2025
# Aatos Ewin, 2025
# Wil Odoo, 2025
# Marta Wacławek, 2025
# 
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-02-20 16:01+0000\n"
"PO-Revision-Date: 2024-10-08 06:34+0000\n"
"Last-Translator: Marta Wacławek, 2025\n"
"Language-Team: Polish (https://app.transifex.com/odoo/teams/41243/pl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pl\n"
"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && (n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && n%10<=9) || (n%100>=12 && 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 "Firmy"

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

#: ../../content/applications/general/companies.rst:13
msgid ""
"Utilizing a multi-company environment in an Odoo database warrants a "
"subscription change from *Standard* (or *One App Free*) to a *Custom* plan. "
"Should the administrator not migrate the subscription to a *Custom* plan "
"after adding another company, the database risks being deactivated. For more"
" information, consult the `Odoo Pricing page <https://www.odoo.com/pricing-"
"plan>`_."
msgstr ""

#: ../../content/applications/general/companies.rst:19
msgid ""
"If the customer is on the *Standard* plan, and adds multi-company "
"functionality to the database, it triggers an upsell for the *Custom* plan."
msgstr ""

#: ../../content/applications/general/companies.rst:22
msgid ""
"If they are on a *Yearly* or *Multi-year* contract, this creates an upsell "
"order, with a 30-day limit (risking deactivation). If multi-company "
"functionality is fully removed within that time period, the next time the "
"database pings, the upsell order and limit are removed automatically."
msgstr ""

#: ../../content/applications/general/companies.rst:26
msgid ""
"If the customer is on a *Monthly* contract, once the next bill is created, "
"and multi-company functionality is still detected while they are on a "
"*Standard* plan, they are automatically switched, and billed on the *Custom*"
" plan."
msgstr ""

#: ../../content/applications/general/companies.rst:30
msgid ""
"Should the customer want to go back to *Standard*, the Customer Success Team"
" **must** be contacted."
msgstr ""

#: ../../content/applications/general/companies.rst:33
msgid ""
"To create a new company, navigate to :menuselection:`Settings app --> "
"Companies section`, and click :guilabel:`Manage Companies`. Then, click "
":guilabel:`New` to create a new company."
msgstr ""

#: ../../content/applications/general/companies.rst:36
msgid "Proceed to fill out the new company form that appears."
msgstr ""

#: ../../content/applications/general/companies.rst:39
msgid ""
"To archive a company, navigate to :menuselection:`Settings app --> Companies"
" section --> Manage Companies`. Then, tick the checkbox to the left of the "
"company to be archived. If the :guilabel:`Companies` page is not in list "
"view, click the :guilabel:`≣ (four bars)` icon, located in the top-right "
"corner of the page."
msgstr ""

#: ../../content/applications/general/companies.rst:44
msgid ""
"After selecting the appropriate company, click the :guilabel:`⚙️ Actions` "
"icon, and select :guilabel:`Archive` from the resulting drop-down menu."
msgstr ""

#: ../../content/applications/general/companies.rst:47
msgid ""
"To ensure all records related to the archived company are archived, contact "
"Odoo's `Support Team <https://www.odoo.com/help>`_."
msgstr ""

#: ../../content/applications/general/companies.rst:50
msgid ""
"Should a record not be archived, there is a risk of reactivating the "
"archived company, and creating the upsell again."
msgstr ""

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

#: ../../content/applications/general/companies.rst:58
msgid ""
"Go to :menuselection:`Settings app --> Companies section --> Manage "
"Companies`. Then, either click :guilabel:`New`, and fill in the form with "
"the company's information, or select a pre-existing company to edit it."
msgstr ""

#: ../../content/applications/general/companies.rst-1
msgid "Overview of a new company's form in Odoo."
msgstr ""

#: ../../content/applications/general/companies.rst:67
msgid ""
"Activate the :ref:`developer mode <developer-mode>` to set social media "
"accounts and company-specific email parameters. See this documentation on "
":doc:`../marketing/social_marketing` and :doc:`email_communication`."
msgstr ""

#: ../../content/applications/general/companies.rst:71
msgid ""
"Companies also have a :guilabel:`Parent Company` set on the company form in "
":ref:`developer mode <developer-mode>`."
msgstr ""

#: ../../content/applications/general/companies.rst:75
msgid "Switch between companies"
msgstr ""

#: ../../content/applications/general/companies.rst:77
msgid ""
"Switch between (or select) multiple companies, by clicking on the company "
"name, located in the far-right corner of the header menu, anywhere "
"throughout the database. Tick the checkboxes next to the desired company "
"name(s) to activate them. The highlighted company represents the current "
"environment that is in use. To switch environments, click on the desired "
"company name."
msgstr ""

#: ../../content/applications/general/companies.rst:83
msgid ""
"In the example below, the user has access to eight companies, two are "
"activated, and the environment the database is in belongs to: *My Company "
"(San Francisco)*."
msgstr ""

#: ../../content/applications/general/companies.rst:0
msgid "View of the companies menu through the main dashboard in Odoo."
msgstr ""

#: ../../content/applications/general/companies.rst:91
msgid "Share records"
msgstr ""

#: ../../content/applications/general/companies.rst:93
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:96
msgid "*A blank field*: the record is shared within all companies."
msgstr ""

#: ../../content/applications/general/companies.rst:97
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:103
msgid ""
"When an environment is selected from the top menu, along with an additional "
"company, records are shared between the two companies."
msgstr ""

#: ../../content/applications/general/companies.rst:107
msgid "Branches"
msgstr "Oddziały"

#: ../../content/applications/general/companies.rst:109
msgid ""
"Branches are available to add to a company. Branches can be added by "
"navigating to :menuselection:`Settings app --> Companies section --> Manage "
"Companies`. Then, select the desired company from the list. From the company"
" detail form, open the :guilabel:`Branches` tab. To add a branch, click "
":guilabel:`Add a line`, and fill out the :guilabel:`Create Branches` pop-up "
"form that appears."
msgstr ""

#: ../../content/applications/general/companies.rst-1
msgid "Add a branch to a company with branches and add a line highlighted."
msgstr ""

#: ../../content/applications/general/companies.rst:120
msgid ""
"Activate the :ref:`developer mode <developer-mode>` to set social media "
"accounts and company-specific email system parameters. See this "
"documentation on :doc:`../marketing/social_marketing` and "
":doc:`email_communication`."
msgstr ""

#: ../../content/applications/general/companies.rst:124
msgid ""
"Branches also have a :guilabel:`Parent Company` set on the branch form in "
":ref:`developer mode <developer-mode>`. Accounting and fiscal localizations "
"for the branch are set on the :guilabel:`Parent Company`. To do so, select "
"the company from the *company selector* in the top menu, and go to "
":menuselection:`Settings app --> Accounting --> Fiscal Localization`."
msgstr ""

#: ../../content/applications/general/companies.rst:130
msgid ""
"If the database is on the standard *Paid* pricing plan, adding a branch to a"
" company triggers an upsell. Since adding one or more branches turns the "
"database into a multi-company setup, it will need to switch to the *Custom* "
"pricing plan. This does not affect databases on the *One-app free* plan."
msgstr ""

#: ../../content/applications/general/companies.rst:135
msgid ""
"For more information on pricing, see `Odoo's pricing "
"<https://www.odoo.com/pricing-plan>`_ page."
msgstr ""

#: ../../content/applications/general/companies.rst:140
msgid "Employee access"
msgstr ""

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

#: ../../content/applications/general/companies.rst:145
msgid ""
"To access the *Access Rights*, navigate to :menuselection:`Settings app --> "
"Users section --> Manage Users`."
msgstr ""

#: ../../content/applications/general/companies.rst:148
msgid ""
"From the :guilabel:`Users` page, select a user from the list to modify. "
"Then, either change the fields for :guilabel:`Allowed Companies` or "
":guilabel:`Default Company`."
msgstr ""

#: ../../content/applications/general/companies.rst:151
msgid ""
"Multiple companies can be set for :guilabel:`Allowed Companies`, and *only "
"one* can be set as the :guilabel:`Default Company`."
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:159
msgid ""
"If an administrator has multiple companies activated on the database, and is"
" editing a record, the editing occurs on the record's related company."
msgstr ""

#: ../../content/applications/general/companies.rst:163
msgid ""
"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:167
msgid "When creating a record, the company taken into account is:"
msgstr ""

#: ../../content/applications/general/companies.rst:169
msgid ""
"The current company selected in the company selector, in the upper-right "
"hand of the screen (the one that is highlighted/active)"
msgstr ""

#: ../../content/applications/general/companies.rst:172
#: ../../content/applications/general/companies.rst:176
msgid "**OR**"
msgstr ""

#: ../../content/applications/general/companies.rst:174
msgid ""
"No company is set (because none is set on the product and contact forms, for"
" example)"
msgstr ""

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

#: ../../content/applications/general/companies.rst:181
msgid "Document format"
msgstr ""

#: ../../content/applications/general/companies.rst:183
msgid ""
"To set document formats according to each company, *activate* and *select* "
"the respective company, and, under the :menuselection:`Settings app --> "
"Companies section`, click on :guilabel:`Configure Document Layout` and edit "
"the information as needed."
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:191
msgid ""
":guilabel:`Company Details` can be edited on the document layout. By "
"default, this field is populated from the company information listed, when "
"navigating here: :menuselection:`Settings app --> Companies section --> "
"Manage Companies`, and select a company from the list."
msgstr ""

#: ../../content/applications/general/companies.rst:198
#: ../../content/applications/general/multi_company.rst:79
msgid "Inter-company transactions"
msgstr ""

#: ../../content/applications/general/companies.rst:200
msgid ""
"First, activate the :ref:`developer mode <developer-mode>`. Then, make sure "
"each one of the companies is properly set in relation to:"
msgstr ""

#: ../../content/applications/general/companies.rst:203
msgid ""
":doc:`Chart of Accounts "
"<../finance/accounting/get_started/chart_of_accounts>`"
msgstr ""

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

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

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

#: ../../content/applications/general/companies.rst:207
msgid ":doc:`Fiscal Localizations <../finance/fiscal_localizations>`"
msgstr ""

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

#: ../../content/applications/general/companies.rst:210
msgid ""
"Next, navigate to :menuselection:`Settings app --> Companies section --> "
"Manage Companies`. Then, select the desired company from the list. On the "
"company form, select the :guilabel:`Inter-Company Transactions` tab, on the "
"individual company's detail form."
msgstr ""

#: ../../content/applications/general/companies.rst:214
msgid ""
"With the respective company activated and selected, choose one of the "
"following :guilabel:`Rule` options:"
msgstr ""

#: ../../content/applications/general/companies.rst:217
msgid ""
":guilabel:`Do not synchronize`: do not synchronize any inter-company "
"transactions."
msgstr ""

#: ../../content/applications/general/companies.rst:218
msgid ""
":guilabel:`Synchronized invoice/bills`: generates a bill/invoice when a "
"company confirms a bill/invoice for the selected company."
msgstr ""

#: ../../content/applications/general/companies.rst:220
msgid ""
":guilabel:`Synchronize Sales Order`: generates a drafted sales order using "
"the selected company warehouse, when a sales order is confirmed for the "
"selected company. If, instead of a drafted sales order, it should be "
"validated, enable :guilabel:`Automatic Validation`.\\*"
msgstr ""

#: ../../content/applications/general/companies.rst:223
msgid ""
":guilabel:`Synchronize Purchase Order`: generates a drafted purchase order "
"using the selected company warehouse, when a purchase order is confirmed for"
" the selected company. If, instead of a drafted purchase order, it should be"
" validated, enable :guilabel:`Automatic Validation`.\\*"
msgstr ""

#: ../../content/applications/general/companies.rst:226
msgid ""
":guilabel:`Synchronize Sales and 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, it should be validated, enable "
":guilabel:`Automatic Validation`.\\*"
msgstr ""

#: ../../content/applications/general/companies.rst:231
msgid ""
"\\* The given option needs to be selected, so :guilabel:`Automatic "
"Validation` appears in the configuration."
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:239
msgid ""
"Products **must** be configured as :guilabel:`Can be sold` and shared "
"between the companies. See "
":doc:`../inventory_and_mrp/inventory/product_management/configure/type`."
msgstr ""

#: ../../content/applications/general/companies.rst:243
msgid ""
":guilabel:`Synchronize invoice/bills`: an invoice posted on `JS Store "
"Belgium`, for `JS Store US`, automatically creates a vendor bill, and "
"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, it should be "
"validated, enable :guilabel:`Automatic Validation`."
msgstr ""

#: ../../content/applications/general/companies.rst:249
msgid ""
":guilabel:`Synchronize sales/purchase order`: 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 "
":guilabel:`Automatic Validation` feature was enabled)."
msgstr ""

#: ../../content/applications/general/companies.rst:254
msgid ""
"Remember to test all workflows as a user *other* than the administrator."
msgstr ""

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

#: ../../content/applications/general/companies.rst:258
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 via email to users in an "
"organization that include high-level information about how the business is "
"performing."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:8
msgid ""
"To start sending digest emails, begin by navigating to "
":menuselection:`Settings app --> Statistics section`, activate the "
":guilabel:`Digest Emails` feature, and click :guilabel:`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 "A variety of settings can be configured for digest emails, such as:"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:17
msgid ""
"Deciding which :abbr:`KPIs (key performance indicators)` are shared in the "
"digest emails"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:18
msgid "Determining how often digest emails are sent"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:19
msgid "Choosing who in the 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 :abbr:`KPIs (key performance indicators)` (*Studio* app "
"required)"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:24
msgid ""
"By default, the :guilabel:`Digest Email` feature is enabled. :guilabel:`Your"
" Odoo Periodic Digest` serves as the primary template, which includes all "
":abbr:`KPI (key performance indicator)` measurements across the Odoo "
"database, and is sent daily to administrators."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:29
msgid ""
"When creating duplicates of databases that have sending capabilities (not "
"testing-mode), the digest emails continue to send from the duplicate "
"database, unless deactivated."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:32
msgid ""
"To deactivate the digest email, navigate to :menuselection:`Settings --> "
"Statistics section`. Then, deactivate the :guilabel:`Digest Emails` feature,"
" by un-ticking the checkbox, and clicking :guilabel:`Save`. See the section "
"on :ref:`digest-emails/deactivate`."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:39
msgid "Customize default digest email"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:41
msgid ""
"To customize the default digest email (*Your Odoo Periodic Digest*), go to "
":menuselection:`Settings app --> Statistics section --> Digest Email field`."
" Then, select :guilabel:`Your Odoo Periodic Digest`, and click on the "
":guilabel:`↗️ (External link)` icon, next to the drop-down menu selection."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:45
msgid ""
"A pop-up window appears, and presents a variety of editable settings, which "
"include:"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:47
#: ../../content/applications/general/companies/digest_emails.rst:179
msgid ":guilabel:`Digest Name`: the name of the digest email."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:48
#: ../../content/applications/general/companies/digest_emails.rst:180
msgid ""
":guilabel:`Periodicity`: control how often digest emails are sent "
"(:guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Monthly`, or "
":guilabel:`Quarterly`)."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:50
#: ../../content/applications/general/companies/digest_emails.rst:182
msgid ""
":guilabel:`Next Send Date`: the date on which the digest email will be sent "
"again."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:51
#: ../../content/applications/general/companies/digest_emails.rst:183
msgid ""
":guilabel:`KPIs` tab: check/uncheck each calculated :abbr:`KPI (key "
"performance indicator)` that appears in digest emails. A ticked box "
"indicates an active :abbr:`KPI (key performance indicator)` in the digest "
"email. See the section on :ref:`digest-emails/kpis`."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:54
#: ../../content/applications/general/companies/digest_emails.rst:186
msgid ""
":guilabel:`Recipients` tab: add/remove users who receive the digest emails. "
"See the section on :ref:`digest-emails/recipients`."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:58
msgid ""
"The :abbr:`KPIs (key performance indicators)` can be customized using Odoo "
"*Studio*. Additional costs to the database subscription are incurred should "
"*Studio* need to be installed. See this section on :ref:`digest-"
"emails/custom-kpi`."
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:69
msgid "Deactivate digest email"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:71
msgid ""
"To manually deactivate an individual digest email, first navigate to "
":menuselection:`Settings app --> Statistics section`, and click "
":guilabel:`Configure Digest Emails`. Then, select the desired digest email "
"from the list that should be deactivated."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:75
msgid ""
"Next, click :guilabel:`DEACTIVATE FOR EVERYONE` to deactivate the digest "
"email for everyone, or :guilabel:`UNSUBSCRIBE ME` to remove the logged in "
"user from the mailing list. These buttons are located in the top menu, just "
"above the :guilabel:`Digest Name`."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:80
msgid "Manually send digest email"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:82
msgid ""
"To manually send a digest email, first navigate to :menuselection:`Settings "
"app --> Statistics section`, and click :guilabel:`Configure Digest Emails`. "
"Then, select the desired digest email, and click :guilabel:`SEND NOW`. This "
"button is located in the top menu, just above the :guilabel:`Digest Name`."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:90
msgid "KPIs"
msgstr "KPIs"

#: ../../content/applications/general/companies/digest_emails.rst:92
msgid ""
"Pre-configured :abbr:`KPIs (key performance indicators)` can be added to the"
" digest email from the :guilabel:`KPIs` tab of the digest email template "
"form."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:95
msgid ""
"First, navigate to :menuselection:`Settings app --> Statistics section`, and"
" click :guilabel:`Configure Digest Emails`."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:98
msgid ""
"Then, select the desired digest email, and open the :guilabel:`KPIs` tab."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:100
msgid ""
"To add a :abbr:`KPI (key performance indicator)` to the digest email, tick "
"the checkbox next to the desired :abbr:`KPI (key performance indicator)`. "
"After all :abbr:`KPIs (key performance indicators)` are added (or "
"deselected), click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:104
msgid ""
"The following :abbr:`KPIs (key performance indicators)` are available in the"
" :guilabel:`KPIs` tab on a digest email template form out-of-box in Odoo:"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst-1
msgid "KPIs listed in the out-of-box digest email."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:113
msgid ":guilabel:`General`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:112
msgid ":guilabel:`Connected Users`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:113
msgid ":guilabel:`Messages`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:116
msgid ":guilabel:`Project`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:116
msgid ":guilabel:`Open Tasks`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:119
msgid ":guilabel:`Recruitment`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:119
msgid ":guilabel:`Employees`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:123
msgid ":guilabel:`CRM`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:122
msgid ":guilabel:`New Leads/Opportunities`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:123
msgid ":guilabel:`Opportunities Won`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:127
msgid ":guilabel:`Sales`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:126
msgid ":guilabel:`All Sales`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:127
msgid ":guilabel:`eCommerce Sales`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:130
msgid ":guilabel:`Point of Sale`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:130
msgid ":guilabel:`POS Sales`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:135
msgid ":guilabel:`Live Chat`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:133
msgid ":guilabel:`% of Happiness`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:134
msgid ":guilabel:`Conversations handled`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:135
msgid ":guilabel:`Time to answer (sec)`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:138
msgid ":guilabel:`Helpdesk`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:138
msgid ":guilabel:`Tickets Closed`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:142
msgid ":guilabel:`Invoicing`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:141
msgid ":guilabel:`Revenue`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:142
msgid ":guilabel:`Banks and Cash Moves`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:147
msgid "Recipients"
msgstr "Odbiorcy"

#: ../../content/applications/general/companies/digest_emails.rst:149
msgid ""
"Digest email recipients are added from the :guilabel:`Recipients` tab of the"
" digest email template form."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:152
msgid ""
"To add a recipient, navigate to :menuselection:`Settings app --> Statistics "
"section`, and click :guilabel:`Configure Digest Emails`. Then, select the "
"desired digest email, and open the :guilabel:`Recipients` tab."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:156
msgid ""
"To add a recipient, click :guilabel:`Add a line`, and an :guilabel:`Add "
"Recipients` pop-up window appears, with all available users to add as "
"recipients."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:159
msgid ""
"From the pop-up window, tick the checkbox next to the :guilabel:`Name` of "
"the user(s), and click the :guilabel:`Select` button."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:162
msgid ""
"To remove a user as a recipient, click the :guilabel:`❌ (remove)` icon to "
"the far-right of the user listed in the :guilabel:`Recipients` tab."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:165
msgid "Click :guilabel:`Save` to implement the changes."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:170
msgid "Create digest emails"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:172
msgid ""
"To create a new digest email, navigate to :menuselection:`Settings app --> "
"Statistics section`, and click :guilabel:`Configure Digest Emails`. Then, "
"click :guilabel:`Create` to create a new digest email."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:176
msgid ""
"A separate page, with a blank digest email template appears, and presents a "
"variety of editable settings, including:"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:189
msgid ""
"From there, give the digest email a :guilabel:`Digest Name`, specify "
":guilabel:`Periodicity`, choose the desired :abbr:`KPIs (key performance "
"indicators)`, and add :guilabel:`Recipients`, as needed."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:193
msgid ""
"After clicking :guilabel:`Save`, the new custom digest email is available as"
" a selection in the :guilabel:`Digest Email` field, located in the "
":menuselection:`Settings app --> Statistics section`."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:199
msgid "Custom KPIs with Odoo Studio"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:201
msgid ""
"The :abbr:`KPIs (key performance indicators)` on a digest email template "
"form, in the :guilabel:`KPIs` tab, can be customized using Odoo *Studio*."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:205
msgid ""
"Additional costs to the database subscription are incurred, should Odoo "
"*Studio* need to be installed."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:208
msgid ""
"To begin, click the :guilabel:`🛠️ (tools)` icon in the top-right of the "
"screen. This is the link to the Odoo *Studio* application."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:211
msgid ""
"In order to create additional fields, create two fields on the digest "
"object:"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:213
msgid ""
"Create a boolean field called `kpi_myfield`, and display it in the "
":guilabel:`KPIs` tab."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:214
msgid ""
"Create a computed field called `kpi_myfield_value` that computes the "
"customized :abbr:`KPI (key performance indicator)`."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:216
msgid ""
"Select the :abbr:`KPIs (key performance indicators)` in the :guilabel:`KPIs`"
" tab."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:219
msgid ""
"Here is the `source code "
"<https://github.com/odoo/odoo/blob/15.0/addons/digest/models/digest.py>`_ "
"for the `digest.py` file, which guides the programmer in the coding of the "
"computed field."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:224
msgid ""
"Users can also click the :guilabel:`Recipients` tab, and then the vertical "
"three-dot :guilabel:`(kebab)` menu to edit this view. Either click "
":guilabel:`EDIT LIST VIEW` or :guilabel:`EDIT FORM VIEW` to modify this tab."
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:229
msgid "Computed values reference table"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:232
msgid "LABEL"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:232
msgid "VALUE"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:234
msgid "Connected Users"
msgstr "Połączonych użytkowników"

#: ../../content/applications/general/companies/digest_emails.rst:234
msgid "`kpi_res_users_connected_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:236
msgid "Messages Sent"
msgstr "Wysłane wiadomości"

#: ../../content/applications/general/companies/digest_emails.rst:236
msgid "`kpi_mail_message_total_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:238
msgid "New Leads"
msgstr "Nowe leady"

#: ../../content/applications/general/companies/digest_emails.rst:238
msgid "`kpi_crm_lead_created_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:240
msgid "Opportunities Won"
msgstr "Szanse wygrane"

#: ../../content/applications/general/companies/digest_emails.rst:240
msgid "`kpi_crm_opportunities_won_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:242
msgid "Open Tasks"
msgstr "Otwarte zadania"

#: ../../content/applications/general/companies/digest_emails.rst:242
msgid "`kpi_project_task_opened_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:244
msgid "Tickets Closed"
msgstr "Zgłoszenia zamknięte"

#: ../../content/applications/general/companies/digest_emails.rst:244
msgid "`kpi_helpdesk_tickets_closed_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:246
msgid "% of Happiness"
msgstr "% szczęśliwych"

#: ../../content/applications/general/companies/digest_emails.rst:246
msgid "`kpi_livechat_rating_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:248
msgid "Conversations handled"
msgstr "Rozmowy przeprowadzone"

#: ../../content/applications/general/companies/digest_emails.rst:248
msgid "`kpi_livechat_conversations_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:250
msgid "Time to answer (sec)"
msgstr "Czas na odpowiedź (sek.)"

#: ../../content/applications/general/companies/digest_emails.rst:250
msgid "`kpi_livechat_response_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:252
msgid "All Sales"
msgstr "Cała sprzedaż"

#: ../../content/applications/general/companies/digest_emails.rst:252
msgid "`kpi_all_sale_total_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:254
msgid "eCommerce Sales"
msgstr "Sprzedaż eCommerce"

#: ../../content/applications/general/companies/digest_emails.rst:254
msgid "`kpi_website_sale_total_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:256
msgid "Revenue"
msgstr "Przychód"

#: ../../content/applications/general/companies/digest_emails.rst:256
msgid "`kpi_account_total_revenue_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:258
msgid "Bank & Cash Moves"
msgstr "Operacje bankowe i gotówkowe"

#: ../../content/applications/general/companies/digest_emails.rst:258
msgid "`kpi_account_bank_cash_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:260
msgid "POS Sales"
msgstr "Sprzedaż POS"

#: ../../content/applications/general/companies/digest_emails.rst:260
msgid "`kpi_pos_total_value`"
msgstr ""

#: ../../content/applications/general/companies/digest_emails.rst:262
msgid "New Employees"
msgstr "Nowi pracownicy"

#: ../../content/applications/general/companies/digest_emails.rst:262
msgid "`kpi_hr_recruitment_new_colleagues_value`"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:3
msgid "Email templates"
msgstr "Szablony wiadomości e-mail"

#: ../../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. Dynamic placeholders (referencing "
"fields within Odoo) are also available for use in the email template."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:34
msgid "Powerbox"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:36
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:40
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:43
msgid ":guilabel:`Structure`"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:45
msgid ":guilabel:`Bulleted list`: Create a simple bulleted list."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:46
msgid ":guilabel:`Numbered list`: Create a list with numbering."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:47
msgid ":guilabel:`Checklist`: Track tasks with a checklist."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:48
msgid ":guilabel:`Table`: Insert a table."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:49
msgid ":guilabel:`Separator`: Insert a horizontal rule separator."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:50
msgid ":guilabel:`Quote`: Add a blockquote section."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:51
msgid ":guilabel:`Code`: Add a code section."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:52
msgid ":guilabel:`2 columns`: Convert into two columns."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:53
msgid ":guilabel:`3 columns`: Convert into three columns."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:54
msgid ":guilabel:`4 columns`: Convert into four columns."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:56
msgid ":guilabel:`Format`"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:58
msgid ":guilabel:`Heading 1`: Big section heading."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:59
msgid ":guilabel:`Heading 2`: Medium section heading."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:60
msgid ":guilabel:`Heading 3`: Small section heading."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:61
msgid ":guilabel:`Switch direction`: Switch the text's direction."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:62
msgid ":guilabel:`Text`: Paragraph block."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:64
msgid ":guilabel:`Media`"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:66
msgid ":guilabel:`Image`: Insert an image."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:67
msgid ":guilabel:`Article`: Link an article."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:69
msgid ":guilabel:`Navigation`"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:71
msgid ":guilabel:`Link`: Add a link."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:72
msgid ":guilabel:`Button`: Add a button."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:73
msgid ":guilabel:`Appointment`: Add a specific appointment."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:74
msgid ":guilabel:`Calendar`: Schedule an appointment."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:76
msgid ":guilabel:`Widgets`"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:78
msgid ":guilabel:`3 Stars`: Insert a rating over three stars."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:79
msgid ":guilabel:`5 Stars`: Insert a rating over five stars."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:81
msgid ":guilabel:`Basic Blocks`"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:83
msgid ":guilabel:`Signature`: Insert your signature."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:85
msgid ":guilabel:`Marketing Tools`"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:87
msgid ":guilabel:`Dynamic Placeholders`: Insert personalized content."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:90
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:100
msgid ""
":ref:`Using dynamic placeholders <email_template/dynamic-placeholders>`"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:103
msgid "XML/HTML code editor"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:105
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:115
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:122
msgid "Dynamic placeholders"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:124
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:128
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:134
msgid ""
"Dynamic placeholders are encoded to display fields from within the database."
" Dynamic placeholders can be used in the :guilabel:`Body` "
"(:guilabel:`Content` Tab) of the email template. They can also 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:139
msgid ""
"To use the dynamic placeholders in the :guilabel:`Body` of an email open the"
" **powerbox** feature by typing in `/` into the body of the email template "
"under the :guilabel:`Content` tab. Scroll to the bottom of the options list,"
" to :guilabel:`Marketing Tools`. Next, select :guilabel:`Dynamic "
"Placeholder`. Then select the dynamic placeholder from a list of available "
"options and follow the prompts to configure it with the desired "
"corresponding Odoo field. Each dynamic placeholder will vary in "
"configuration."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst-1
msgid "Using dynamic placeholders in an email template."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:151
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:155
msgid ""
"To search the available fields, simply type in the front-end name (on user-"
"interface) of the field in the search. This will find a result from all of "
"the available fields for the model that the email template is created for."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:160
msgid "Customizing email templates are out of the scope of Odoo Support."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:163
msgid "Rich text editor"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:165
msgid ""
"A rich text editor toolbar can be accessed by highlighting text in the email"
" template. This can be used to change the heading, font size/style, color, "
"add a list type, or a link."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst-1
msgid "Rich text editor in the email template."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:173
msgid "Resetting email templates"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:175
msgid ""
"Should the email template not work because the code has been altered it can "
"be reset to restore it back to the out-of-box default template. Simply click"
" on the :guilabel:`Reset Template` button in the upper left-hand of the "
"screen and the template will be reset."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst-1
msgid "Resetting the email template."
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:184
msgid "Default reply on email templates"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:186
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:191
msgid ""
"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:198
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:201
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:206
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:216
msgid "Transactional emails and corresponding URLs"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:218
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:221
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:225
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:229
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:235
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:241
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:247
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:252
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:257
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:261
msgid "Updating translations within email templates"
msgstr ""

#: ../../content/applications/general/companies/email_template.rst:263
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:268
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:272
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:281
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:284
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:293
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, also known as debug mode, unlocks access to advanced "
":ref:`tools and settings <developer-mode/tools>` in Odoo."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:11
msgid ""
"Proceed with caution, as some developer tools and technical settings are "
"considered advanced and may have associated risks. Only use them if you "
"understand the implications and are confident in your actions."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:16
msgid ""
"The developer mode is also available with :ref:`assets "
"<frontend/framework/assets_debug_mode>`, which are used to debug JavaScript "
"code, and with :ref:`tests assets <frontend/framework/tests_debug_mode>`, "
"which are used to run test tours."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:23
msgid "Activation"
msgstr "Aktywacja"

#: ../../content/applications/general/developer_mode.rst:25
msgid ""
"To activate it, open the :guilabel:`Settings` app, scroll down to the "
":guilabel:`Developer Tools` section, and click :guilabel:`Activate the "
"developer mode`."
msgstr ""

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

#: ../../content/applications/general/developer_mode.rst-1
msgid "Activating the developer mode in the Settings app"
msgstr ""

#: ../../content/applications/general/developer_mode.rst:33
msgid ""
"To activate the developer mode **from anywhere in the database**, add "
"`?debug=1` at the end of the URL (e.g., "
"`https://example.odoo.com/odoo?debug=1`). To deactivate it, use `?debug=0` "
"instead."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:36
msgid ""
"Use `?debug=assets` to activate the developer mode with assets and "
"`?debug=tests` to activate it with tests assets."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:40
msgid ""
"Open the **command palette** by pressing `Ctrl + K` or `Cmd ⌘ + K`, then "
"type `debug` to activate the developer mode with assets or deactivate it."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:43
msgid "Browser extension"
msgstr ""

#: ../../content/applications/general/developer_mode.rst:45
msgid ""
"The `Odoo Debug <https://github.com/Droggol/OdooDebug>`_ browser extension "
"adds an icon to toggle developer mode on or off from the browser's toolbar. "
"It is available on the `Chrome Web Store "
"<https://chromewebstore.google.com/detail/odoo-"
"debug/hmdmhilocobgohohpdpolmibjklfgkbi>`_ and `Firefox Add-ons "
"<https://addons.mozilla.org/firefox/addon/odoo-debug/>`_."
msgstr ""

#: ../../content/applications/general/developer_mode.rst:53
msgid "Developer tools and technical menu"
msgstr ""

#: ../../content/applications/general/developer_mode.rst:55
msgid ""
"Once the developer mode is activated, the developer tools can be accessed by"
" clicking the :icon:`fa-bug` :guilabel:`(bug)` icon. The menu contains tools"
" useful for understanding or editing technical data, such as a view's field,"
" filters, or actions. The options available depend on where the menu is "
"accessed from."
msgstr ""

#: ../../content/applications/general/developer_mode.rst-1
msgid "Accessing the developer tools"
msgstr ""

#: ../../content/applications/general/developer_mode.rst:63
msgid ""
"Database administrators can access the technical menu from the "
":guilabel:`Settings` app. It contains advanced database settings, such as "
"ones related to the database structure, security, actions, etc."
msgstr ""

#: ../../content/applications/general/developer_mode.rst-1
msgid "Accessing the technical menu"
msgstr ""

#: ../../content/applications/general/email_communication.rst:5
msgid "Communication in Odoo by email"
msgstr ""

#: ../../content/applications/general/email_communication.rst:7
msgid ""
"Communication in Odoo related to records such as CRM opportunities, sales "
"orders, invoices, ... have a discussion thread called **chatter**, often "
"displayed on the right side of the record."
msgstr ""

#: ../../content/applications/general/email_communication.rst:10
msgid ""
"On the chatter, you can send direct emails or Odoo notifications to the "
"followers of a document (depending on their notification preferences), log "
"internal notes, send WhatsApp messages or SMSes, and schedule activities."
msgstr ""

#: ../../content/applications/general/email_communication.rst:14
msgid ""
"If a follower replies to a message, the reply updates the chatter, and Odoo "
"relays it to the followers as a notification. All emails - outgoing and "
"incoming - appear in the same chatter."
msgstr ""

#: ../../content/applications/general/email_communication.rst:20
msgid "Odoo Online and Odoo.sh users"
msgstr ""

#: ../../content/applications/general/email_communication.rst:22
msgid ""
"On Odoo Online and Odoo.sh, outgoing and incoming emails work out of the "
"box, **nothing needs to be done**. Everything is already configured on your "
"subdomain."
msgstr ""

#: ../../content/applications/general/email_communication.rst:25
msgid ""
"By default, outgoing emails use the following :ref:`notification email "
"address <email-outbound-notifications>` `notifications@company-"
"name.odoo.com`."
msgstr ""

#: ../../content/applications/general/email_communication.rst:31
msgid "Using another domain"
msgstr ""

#: ../../content/applications/general/email_communication.rst:33
msgid ""
"If you prefer not to have outgoing emails sent from Odoo's subdomain "
"`@company-name.odoo.com` but instead :ref:`from your own domain <email-"
"outbound-custom-domain>`, **additional configuration will be necessary** on "
"the domain and within Odoo. This introduces an extra layer of complexity and"
" necessitates technical knowledge (mainly regarding DNS and mail protocols)."
msgstr ""

#: ../../content/applications/general/email_communication.rst:38
msgid ""
"By adding a domain and configuring the administration access rights, you can"
" also access the :ref:`new domain alias <email-outbound-alias-domain>` page "
"to configure the alias of your companies. If only one domain is configured, "
"this domain will be shared by all companies on the database."
msgstr ""

#: ../../content/applications/general/email_communication.rst:42
msgid ""
"If you want to keep using Odoo's mail server, you will have to "
":ref:`configure the SPF and DKIM <email-domain-spf>`."
msgstr ""

#: ../../content/applications/general/email_communication.rst:45
msgid ""
"If :ref:`you want to use your own mail server <email-outbound-custom-domain-"
"smtp-server>`, you will have to follow the mail server provider's specific "
"documentation."
msgstr ""

#: ../../content/applications/general/email_communication.rst:48
msgid ""
"For incoming emails, after adding your own domain, :ref:`replies from "
"customers will come back to your domain <email-inbound-custom-domain>`, and "
"you will need to use one of the three possible ways to get the emails back "
"into Odoo (using either :ref:`incoming mail server <email-inbound-custom-"
"domain-incoming-server>`, :ref:`redirection/forwarding <email-inbound-"
"custom-domain-redirections>` or :ref:`DNS MX record <email-inbound-custom-"
"domain-mx>`). Everything is covered in the :doc:`Manage inbound messages "
"documentation <email_communication/email_servers_inbound>`."
msgstr ""

#: ../../content/applications/general/email_communication.rst:59
msgid "On-premise users"
msgstr ""

#: ../../content/applications/general/email_communication.rst:61
msgid ""
"If you are on-premise, you will have to completely configure your outgoing "
"and incoming emails:"
msgstr ""

#: ../../content/applications/general/email_communication.rst:63
msgid ""
"For outgoing emails, you will need :ref:`to use an SMTP server and a custom "
"domain <email-outbound-custom-domain-odoo-server>`."
msgstr ""

#: ../../content/applications/general/email_communication.rst:65
msgid ""
"For incoming emails, set the frequency at which you fetch new emails low "
"enough for responsiveness but high enough in order not to stress your system"
" or provider. Due to this reason and the simplicity of this configuration, "
"we usually advise on using incoming mail servers. To use an SMTP server, "
"check out the :ref:`\"Use a custom domain for inbound messages\" "
"documentation <email-inbound-custom-domain>`."
msgstr ""

#: ../../content/applications/general/email_communication.rst:74
msgid "Using a third-party provider's mail server"
msgstr ""

#: ../../content/applications/general/email_communication.rst:76
msgid ""
"Odoo's documentation also covers several popular mail servers. As they "
"require specific authorizations and configuration, they add a layer of "
"complexity. For this reason, using Odoo's outgoing mail server is "
"recommended."
msgstr ""

#: ../../content/applications/general/email_communication.rst:80
msgid ":doc:`Outlook documentation <email_communication/azure_oauth>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:81
msgid ":doc:`Gmail documentation <email_communication/google_oauth>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:82
msgid ":doc:`Mailjet documentation <email_communication/mailjet_api>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:85
msgid ""
"Every provider has its own limitations. Research the desired provider "
"*before* configuring it. For example, Outlook and Gmail might not be "
"suitable for large marketing campaigns."
msgstr ""

#: ../../content/applications/general/email_communication.rst:89
msgid ":doc:`Activities <../essentials/activities>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:90
msgid ":doc:`Discuss app <../productivity/discuss>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:91
msgid ":doc:`Digest emails <companies/digest_emails>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:92
msgid ":doc:`Email Marketing app <../marketing/email_marketing>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:93
msgid ":doc:`Email templates <companies/email_template>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:94
msgid ":ref:`Expense creation using an email alias <expenses/email_expense>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:95
msgid ""
":ref:`Helpdesk ticket creation using an email alias "
"<helpdesk/receiving_tickets/email-alias>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:96
msgid ":ref:`Lead creation using an email alias <crm/configure_email_alias>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:97
msgid ""
":ref:`Project task creation using an email alias "
"<task_creation/email_alias>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:98
msgid ""
":doc:`Technical mail getaway for on-premise users "
"<../../administration/on_premise/email_gateway>`"
msgstr ""

#: ../../content/applications/general/email_communication.rst:100
msgid ""
":ref:`Technical start of Odoo database with an outgoing mail server "
"configured from the command-line interface "
"<reference/cmdline/server/emails>`"
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://<web base url>/microsoft_outlook/confirm` "
"in the :guilabel:`URL` field. The `web.base.url` is subject to change "
"depending on the URL used to log in to the database."
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:41
msgid ""
"The documentation about the :ref:`web.base.url <domain-name/web-base-url>` "
"explains how to freeze a unique URL. It is also possible to add different "
"redirect URLs on the Microsoft app."
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
#: ../../content/applications/general/integrations/google_translate.rst:59
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 ""

#: ../../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-outbound-unique-address>`."
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:248
msgid ""
"Visit the :ref:`From Filtering documentation <email-outbound-different-"
"servers-personalized-from-filtering>` for more information."
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:210
#: ../../content/applications/general/email_communication/azure_oauth.rst:256
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:213
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:222
msgid "Single outgoing mail server configuration:"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:224
msgid ""
"Outgoing mail server **username** (login) = `notifications@example.com`"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:225
msgid ""
"Outgoing mail server :guilabel:`FROM Filtering` = "
"`notifications@example.com`"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:226
#: ../../content/applications/general/email_communication/azure_oauth.rst:281
msgid "`mail.catchall.domain` in system parameters = `example.com`"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:227
#: ../../content/applications/general/email_communication/azure_oauth.rst:282
msgid "`mail.default.from` in system parameters = `notifications`"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:230
msgid "User-specific (multiple user) configuration"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:232
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:236
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:241
msgid "Setup"
msgstr "Ustawienia"

#: ../../content/applications/general/email_communication/azure_oauth.rst:243
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:251
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:260
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:265
msgid ""
"For more information on setting the mass-mailing email server visit "
":ref:`email-outbound-custom-domain-smtp-server`."
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:269
msgid "Multiple user outgoing mail server configuration:"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:272
msgid "User #1 mailbox"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:272
msgid "Outgoing mail server #1 **username** (login) = `john@example.com`"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:273
msgid ""
"Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:275
msgid "User #2 mailbox"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:275
msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:276
msgid ""
"Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:278
msgid "Notifications mailbox"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:278
msgid ""
"Outgoing mail server #3 **username** (login) = `notifications@example.com`"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:279
msgid ""
"Outgoing mail server #3 :guilabel:`FROM Filtering` = "
"`notifications@example.com`"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:281
msgid "System Parameters"
msgstr "Parametry systemu"

#: ../../content/applications/general/email_communication/azure_oauth.rst:285
msgid "Configure incoming email server"
msgstr ""

#: ../../content/applications/general/email_communication/azure_oauth.rst:287
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/email_domain.rst:3
msgid "Configure DNS records to send emails in Odoo"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:5
msgid ""
"This documentation presents three complementary authentication protocols "
"(SPF, DKIM, and DMARC) used to prove the legitimacy of an email sender. Not "
"complying with these protocols will greatly reduce chances of your emails to"
" reach their destination."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:9
msgid ""
"**Odoo Online** and **Odoo.sh** databases using the **default Odoo subdomain"
" address** (e.g., `\\@company-name.odoo.com`) are pre-configured to **send "
"authenticated emails** compliant with the SPF, DKIM, and DMARC protocols."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:13
msgid ""
"If choosing to use a **custom domain** instead, **configuring SPF and DKIM "
"records correctly is essential** to prevent emails from being quarantined as"
" spam or not being delivered to recipients."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:16
msgid ""
"If using :ref:`the default Odoo email server to send emails from a custom "
"domain <email-outbound-custom-domain-odoo-server>`, the SPF and DKIM records"
" must be configured as presented below. If using an outgoing email server, "
"it is required to use the SPF and DKIM records specific to that email "
"service and a custom domain."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:22
msgid ""
"Email service providers apply different rules to incoming emails. An email "
"may be classified as spam even if it passes the SPF and DKIM checks."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:28
msgid "SPF (Sender Policy Framework)"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:30
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:35
msgid ""
"In Odoo, the **SPF test is performed on the bounce address** defined under "
"the :guilabel:`Alias Domain` field found under the database's "
":guilabel:`General Settings`. If using a custom domain as :guilabel:`Alias "
"Domain`, it is necessary to configure it to be SPF-compliant."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:39
msgid ""
"The SPF policy of a domain is set using a TXT record. The way to create or "
"modify this record depends on the provider hosting the :abbr:`DNS (Domain "
"Name System)` zone of the domain name."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:42
msgid ""
"If the domain name does not yet have an SPF record, create one using the "
"following input:"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:48
msgid ""
"If the domain name **already has an SPF record, the record must be "
"updated**. Do not create a new one, as a domain must have only one SPF "
"record."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:52
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:55
msgid ""
"Check the SPF record using a tool like `MXToolbox SPF Record Check "
"<https://mxtoolbox.com/spf.aspx>`_. The process to create or modify an SPF "
"record depends on the provider hosting the DNS zone of the domain name. The "
":ref:`most common providers <email-domain-providers-documentation>` and "
"their documentation are listed below."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:63
msgid "DKIM (DomainKeys Identified Mail)"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:65
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:67
msgid ""
"When sending an email, the Odoo email server includes a unique :abbr:`DKIM "
"(DomainKeys Identified Mail)` signature in the headers. The recipient's "
"server decrypts this signature using the DKIM record in the database's "
"domain name. If the signature and the key contained in the record match, it "
"proves the message is authentic and has not been altered during transport."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:72
msgid ""
"Enabling DKIM is **required** when sending emails **from a custom domain** "
"using the Odoo email server."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:75
msgid ""
"To enable DKIM, 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:83
msgid ""
"If the domain name is `company-name.com`, make sure to create a subdomain "
"`odoo._domainkey.company-name.com` whose canonical name is "
"`odoo._domainkey.odoo.com.`."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:86
msgid ""
"The way to create or modify a CNAME record depends on the provider hosting "
"the DNS zone of the domain name. The :ref:`most common providers <email-"
"domain-providers-documentation>` and their documentation are listed below."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:90
msgid ""
"Check if the DKIM record is valid using a tool like `MXToolbox DKIM Record "
"Lookup <https://mxtoolbox.com/dkim.aspx>`_. Enter `example.com:odoo` in the "
"DKIM lookup tool, specifying that the selector being tested is `odoo` for "
"the custom domain `example.com`."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:97
msgid "DMARC (Domain-based Message Authentication, Reporting and Conformance)"
msgstr ""

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

#: ../../content/applications/general/email_communication/email_domain.rst:105
msgid ""
"The aim of this documentation is to help **understand the impact DMARC has "
"on the deliverability of emails**, rather than give precise instructions for"
" creating a DMARC record. Refer to a resource like `DMARC.org "
"<https://dmarc.org/>`_ to set the DMARC record."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:109
msgid "There are three DMARC policies:"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:111
msgid "`p=none`"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:112
msgid "`p=quarantine`"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:113
msgid "`p=reject`"
msgstr ""

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

#: ../../content/applications/general/email_communication/email_domain.rst:119
msgid ""
"**For the DMARC to pass, the DKIM or SPF check needs to pass** and the "
"domains must be in alignment. If the hosting type is Odoo Online, DKIM "
"configuration on the sending domain is required to pass the DMARC."
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:123
msgid ""
"Passing DMARC generally means that the email will be successfully delivered."
" However, it's important to note that **other factors like spam filters can "
"still reject or quarantine a message**."
msgstr ""

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

#: ../../content/applications/general/email_communication/email_domain.rst:130
msgid ""
":literal:`_dmarc IN TXT “v=DMARC1; p=none; "
"rua=mailto:postmaster@example.com”` means that aggregate DMARC reports will "
"be sent to `postmaster\\@example.com`."
msgstr ""

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

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

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

#: ../../content/applications/general/email_communication/email_domain.rst:142
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:143
msgid ""
"`CloudFlare DNS <https://support.cloudflare.com/hc/en-"
"us/articles/360019093151>`_"
msgstr ""

#: ../../content/applications/general/email_communication/email_domain.rst:144
msgid ""
"`Squarespace DNS records <https://support.squarespace.com/hc/en-"
"us/articles/360002101888-Adding-custom-DNS-records-to-your-Squarespace-"
"managed-domain>`_"
msgstr ""

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

#: ../../content/applications/general/email_communication/email_domain.rst:147
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:152
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_inbound.rst:3
msgid "Manage inbound messages"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:5
msgid ""
"An inbound message is an email delivered to an Odoo database. Anyone can "
"send an email to an email alias created in the database or reply to an email"
" that was previously sent from the database based on the *reply-to* header."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:12
msgid "Email aliases"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:17
msgid "Model specific aliases"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:19
msgid ""
"Some applications have their specific aliases (sales teams, helpdesk teams, "
"projects, etc.). These aliases are used to:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:22
msgid "Create a record when an email is sent directly to the alias,"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:23
msgid "Receive replies to an email initially sent from a record."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst-1
msgid "The local-part \"info\" is used for the alias of the sales team."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:30
msgid ""
"In the example displayed above, sending an email to `info@company-"
"name.odoo.com` will create a new opportunity or a new lead automatically "
"assigned to the corresponding sales team. If an email is sent from the "
"chatter of an existing opportunity, the *reply-to* will be `info@company-"
"name.odoo.com`. The reply will be posted in the right chatter, according to "
"the *message-id* header."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:39
msgid "Catchall"
msgstr "Catchall"

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:41
msgid ""
"If an application does not have an alias, a generic fallback alias is used: "
"the catchall. An email sent from a chatter has a reply address set to this "
"catchall alias. A reply sent to the catchall is posted to the right chatter "
"thanks to the *message-id* header."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:45
msgid ""
"By default, the local-part *catchall* will be used. Enable :ref:`developer-"
"mode` and go to :menuselection:`Settings --> Technical --> Emails: Alias "
"Domains` to access the configuration."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:48
msgid ""
"An email to the catchall always needs to be a reply to a previous email sent"
" from the database. If an email is sent directly to the catchall, the sender"
" will receive the following message:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst-1
msgid ""
"Bounce email from \"MAILER-DEAMON\" explaining how to contact the database."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:55
msgid ""
"The email address `info@company-name.com` displayed in the screenshot above "
"is the email address set on the company. Upon entering the developer mode on"
" a company profile, additional configuration options (such as catchall and "
"bounce) become readable. It can be modified by clicking on the internal link"
" of the Email Domain. It is generally not recommended to modify these "
"options unless specific needs dictate, as it will affect all replies to "
"previously sent emails."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:63
msgid ""
"An alias can be configured on a sales team in the CRM app. When a customer "
"replies to an email coming from the CRM app, the *reply-to* is "
"`info@company-name.odoo.com`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:66
msgid ""
"When an email is sent from the Contact app, the reply address is "
"`catchall@company-name.odoo.com` because there is no alias on the contact "
"model."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:70
msgid ""
"It is advised to keep the local-part of the catchall and the bounce "
"unchanged. If this value is modified, previous emails sent from the database"
" will still have the previous local-part values. This could lead to replies "
"not being correctly received in the database."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:77
msgid "Bounce"
msgstr "Odbijanie"

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:79
msgid ""
"In the same way the catchall alias is used to build the reply address, the "
"bounce alias is used to build the *return-path* of the email. The *return-"
"path* is used when emails cannot be delivered to the recipient and an error "
"is returned to the sender."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:83
msgid ""
"By default the name *bounce* will be used. Enable :ref:`developer-mode` and "
"go to :menuselection:`Settings --> Technical --> Emails: Alias Domains` to "
"access the configuration."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:87
msgid ""
"On Odoo Online, when using the default outgoing email server, the return-"
"path address is forced to the value `bounce@company-name.odoo.com` "
"independently of the value set as bounce alias."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:90
msgid ""
"When an error occurs, a notification is received and displayed in a red "
"envelope in the chatter. In some cases, the red envelope can just contain a "
"`no error` message, meaning there is an error that could not be handled by "
"Odoo."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:94
msgid ""
"A notification will also be displayed in the Discuss icon on the navigation "
"bar."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst-1
msgid ""
"An email sent to a contact had an issue and the error is reported on the "
"navbar."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:100
msgid ""
"If the email address of the recipient is incorrect, by clicking on the red "
"envelope in the chatter an error message containing the reason for the "
"failure will be given."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:0
msgid ""
"An email sent to a wrong domain generates a bounce displayed as a red "
"envelope."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:109
msgid "Receive emails with Odoo's default configuration"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:111
msgid ""
"On **Odoo Online** and **Odoo.sh**, the email alias, reply, and bounce "
"addresses are pre-configured. These addresses use the alias domain "
"automatically added to a standard database."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:115
msgid ""
"Assuming the database URL is `https://mydatabase.odoo.com`, the alias domain"
" `mydatabase.odoo.com` is automatically created. Catchall and bounce can be "
"used and their address is respectively `catchall@mydatabase.odoo.com`, and "
"`bounce@mydatabase.odoo.com`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:119
msgid ""
"If the CRM app is installed, and a sales team with the alias `info` is "
"created, the `info@mydatabase.odoo.com` address can be used immediately. The"
" same goes for any other alias created in other applications."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:123
msgid ""
"The database domain is ready to be used to receive emails without any "
"additional configuration."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:128
msgid "Use multiple Odoo subdomains"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:130
msgid ""
"On **Odoo Online**, the only Odoo subdomain is the one defined at the "
"database creation."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:132
msgid ""
"On **Odoo.sh**, it is possible to use several Odoo subdomains. In the "
"settings of the branch, additional Odoo subdomains can be added as long as "
"they are not used yet in another branch. These domains must then be added to"
" the alias domains to be used by a company."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst-1
msgid "Setting up an Odoo subdomain on a branch."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:142
msgid "Use a custom domain for inbound messages"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:144
msgid ""
"The :ref:`alias domain <email-outbound-alias-domain>` must be selected in "
"the general settings. If you have multiple companies, each one must be "
"configured."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst-1
msgid "The alias domain in the general settings."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:150
msgid ""
"All the aliases will use this custom domain. Replies on models for which an "
"alias is configured are done to `[alias]@my-custom-domain.com`. Replies to "
"other models are sent to the catchall through `catchall@my-custom-"
"domain.com`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst-1
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:0
msgid "Technical schema of mailing route when using a custom domain in Odoo."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:158
msgid ""
"If emails are sent using Odoo's email servers while using a custom domain, "
"follow the :ref:`\"Using a custom domain with Odoo’s email server\" "
"instructions <email-outbound-custom-domain-odoo-server>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:162
msgid ""
"Since this custom domain is used, all emails using an alias (replies, "
"bounces and direct sends) are sent to an address of the domain. They are "
"thus delivered to the email server linked to the domain (MX record). To "
"display them in the chatter or to create new records, it is necessary to "
"retrieve these incoming emails in the Odoo database."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:171
msgid "Method"
msgstr "Metoda"

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:172
msgid "Benefits"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:173
msgid "Drawbacks"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:174
msgid ":ref:`Redirections <email-inbound-custom-domain-redirections>`"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:175
msgid "Easy to set up, emails are directly sent to the database."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:176
msgid "Each alias of a database needs to be configured."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:177
msgid ""
":ref:`Incoming mail servers <email-inbound-custom-domain-incoming-server>`"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:178
msgid ""
"Allows to keep a copy of the email in your mailbox (with IMAP). Allows to "
"create records in the chosen model."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:180
msgid ""
"Depends on a CRON, meaning emails are not retrieved immediately in the "
"database. Each alias of a database needs to be configured."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:182
msgid ":ref:`MX record <email-inbound-custom-domain-mx>`"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:183
msgid "Only one record needs to be created to make all aliases work properly."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:184
msgid "Using a subdomain is required. Requires advanced technical knowledge."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:188
msgid ""
"For **on-premise databases**, the redirection and the MX record methods also"
" require configuring the :doc:`mail gateway script "
"<../../../../administration/on_premise/email_gateway>`. Going through this "
"script requires **advanced technical and infrastructure knowledge**."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:193
msgid ""
"Refer to your provider’s documentation for more detailed information on how "
"to handle the methods detailed below."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:199
msgid "Redirections"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:201
msgid ""
"If the database is hosted on **Odoo Online** or **Odoo.sh**, using "
"redirections is recommended. They allow messages to be received without "
"delay in the database."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:204
msgid ""
"It is mandatory to redirect the catchall and bounce address to the Odoo "
"subdomain of the database. Every other alias used must be redirected as "
"well."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:208
msgid "With one sales team, the following redirections are required:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:210
msgid "`catchall@company-name.com` → `catchall@company-name.odoo.com`"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:211
msgid "`bounce@company-name.com` → `bounce@company-name.odoo.com`"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:212
msgid "`info@company-name.com` → `info@company-name.odoo.com`"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:215
msgid ""
"Some providers ask to validate the redirection by sending a link to the "
"target email address. This procedure is an issue for catchall and bounce "
"since they are not used to create records."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:218
msgid ""
"Modify the catchall value on the mail alias domain. :ref:`developer-mode` "
"must be enabled to access this menu. For example, it can be changed from "
"`catchall` to `temp-catchall`. This will allow to use `catchall` as the "
"local-part of another alias."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:221
msgid ""
"Open an app that uses an alias. For example, CRM contains aliases for each "
"sales team. Set `catchall` as the local-part of the alias of a sales team."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:223
msgid ""
"The validation email will create a record in the CRM app. The email sent "
"will be visible in the chatter, allowing you to validate the redirection."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:225
msgid ""
"Do not forget to change back the alias of the sales team and the catchall "
"value on the mail alias domain, just as they were before this procedure."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:229
msgid ""
"An alternative to redirections is **forwarding**. With forwarding, **the "
"address forwarding the email will be identified as the sender**, while with "
"redirections, the original sender will always remain."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:236
msgid "Incoming mail servers"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:238
msgid ""
"As mentioned earlier, using redirections is the recommended method to "
"receive emails in Odoo. However, it is also possible to set up incoming mail"
" servers. Using this method means creating an incoming email server for each"
" mailbox on your server, catchall, bounce, and every alias of the database, "
"in order to fetch all incoming emails. Incoming mail servers are created by "
"going to :menuselection:`Settings --> Technical --> Emails: Incoming Mail "
"Servers`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:245
msgid ""
"We recommend using the IMAP protocol over the POP protocol, as IMAP fetches "
"all unread emails, while POP fetches all the emails' history and then tags "
"them as deleted in your mailbox."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:249
msgid ""
"It is also possible to connect a mailbox through :doc:`Gmail with Google "
"OAuth <google_oauth>` or :doc:`Outlook with Microsoft Azure OAuth "
"<azure_oauth>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:252
msgid ""
"Regardless of the protocol chosen, emails are fetched using the *Mail: "
"Fetchmail Service* scheduled action."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:255
msgid ""
"Additionally, using an incoming mail server in Odoo gives the opportunity to"
" create new records in a specified model. Each incoming mail server can "
"create records in a different model."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:259
msgid ""
"Emails received on `task@company-name.com` are fetched by the Odoo database."
" All fetched emails will create a new project task in the database."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:268
msgid "MX record"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:270
msgid ""
"A third option is to create a MX record in your DNS zone which specifies the"
" mail server managing emails sent to your domain. **Advanced technical "
"knowledge is required.**"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:274
msgid ""
"This configuration only works with a subdomain on the Odoo Online or Odoo.sh"
" infrastructure (e.g., `@mail.mydomain.com`)"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:277
msgid "Below are presented some specifications depending on the hosting type:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:281
#: ../../content/applications/general/email_communication/faq.rst:296
msgid "Odoo Online"
msgstr "Odoo Online"

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:283
msgid ""
"The custom subdomain must be added to your :doc:`Odoo Portal "
"<../../websites/website/configuration/domain_names>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:286
#: ../../content/applications/general/email_communication/faq.rst:301
msgid "Odoo.sh"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:288
msgid ""
"The custom subdomain must be added to the :doc:`settings of the project "
"<../../../administration/odoo_sh/getting_started/settings>`:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:0
msgid "Adding a custom subdomain for mail to Odoo.sh project settings."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:297
msgid "Infinite email loops"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:299
msgid ""
"In some cases, infinite mailing loops can be created. Odoo provides some "
"protection against such loops, ensuring the same sender cannot send too many"
" emails **that would create records** to an alias in a specific time span."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:303
msgid ""
"By default, an email address can send up to 20 emails in 120 minutes. If "
"more emails are sent, they are blocked and the sender receives the following"
" message:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst-1
msgid ""
"Bounce email received after attempting contact too many times an alias."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:309
msgid ""
"To change the default behavior, enable :ref:`developer-mode`, then go to "
":menuselection:`Settings --> Technical --> Parameters: System Parameters` to"
" add two parameters."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:312
msgid ""
"For the first parameter, enter `mail.gateway.loop.minutes` as the "
":guilabel:`Key` and choose a number of minutes as the :guilabel:`Value` "
"(`120` is the default behavior)."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:314
msgid ""
"For the second parameter, enter `mail.gateway.loop.threshold` as the "
":guilabel:`Key` and choose a number of emails as the :guilabel:`Value` (`20`"
" is the default behavior)."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:318
msgid ""
"These parameters are only used to prevent the creation of new records. They "
"**do not prevent replies** from being added to the chatter."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:322
msgid "Allow alias domain system parameter"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:324
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 --> Aliases`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:328
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 domains 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_inbound.rst:333
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_inbound.rst:338
msgid ""
"When Odoo receives emails with the `commercial` prefix alias in the sender, "
"recipient, or :abbr:`CC (Carbon Copy)` email addresses (e.g. "
"commercial\\@example.com), 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_inbound.rst:343
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 --> System Parameters`. Click "
":guilabel:`New`. Then, type in `mail.catchall.domain.allowed` for the "
":guilabel:`Key` field."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:347
msgid ""
"Next, for the :guilabel:`Value` field, add the domains separated by commas. "
"Manually :icon:`fa-cloud-upload` :guilabel:`(Save)`, and the system "
"parameter takes immediate effect."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst-1
msgid "mail.catchall.domain.allowed system parameter set."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:354
msgid "Local-part based incoming detection"
msgstr "Wykrywanie przychodzących połączeń w oparciu o części lokalne"

#: ../../content/applications/general/email_communication/email_servers_inbound.rst:356
msgid ""
"When creating a new alias, there is an option to enable :guilabel:`Local-"
"part based incoming detection`. If enabled, Odoo only requires the local-"
"part to match for routing an incoming email. If this feature is turned off, "
"Odoo requires the whole email address to match for routing an incoming "
"email."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:3
msgid "Manage outbound messages"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:8
msgid "Sending emails with Odoo's default configuration"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:10
msgid ""
"On **Odoo Online** and **Odoo.sh**, sending and receiving emails works out "
"of the box. No configuration is required."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:13
msgid ""
"When a database is created, the subdomain `company-name.odoo.com` is used to"
" send and receive emails. The deliverability is optimized for this subdomain"
" as it uses Odoo’s DNS configuration."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:17
msgid ""
"If the database subdomain is `company-name.odoo.com` and all mailing "
"configurations are the default ones, all emails will be sent from "
"`notifications@company-name.odoo.com`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:21
msgid ""
"Only **one** subdomain can be used as a mailing server in Odoo. Subdomains "
"for additional companies require an external email server with a custom "
"domain."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst-1
msgid "Odoo’s default outbound messages configuration."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:27
msgid ""
"Emails are sent with `catchall@company-name.odoo.com` as the *reply-to* "
"address. In addition, delivery errors are sent to `bounce@company-"
"name.odoo.com`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:31
msgid ""
"The catchall, bounce, and notification addresses do not work like other "
"aliases. They do not have the vocation to create records in a database. "
"Emails sent to an alias are automatically routed and will reply to an "
"existing and linked record or will create a new one in the database."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:38
msgid "Using a custom domain to send emails"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:40
msgid ""
"The database can be configured to use a custom domain, in which case all "
"default email addresses are built using the custom domain. If the custom "
"domain is `company-name.com`, the sender address will be "
"`notifications@company-name.com`, the *reply-to* address `catchall@company-"
"name.com`, and the *bounce* address `bounce@company-name.com`. The custom "
"domain can be utilized when sending emails either with Odoo’s email servers "
"or an external one."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:46
msgid ""
"This section assumes ownership of a custom domain. If not, a custom domain "
"must be purchased from a domain registrar such as GoDaddy, Namecheap, or any"
" alternative provider."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:52
msgid "Using a custom domain with Odoo’s email server"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:54
msgid ""
"On **Odoo Online** or **Odoo.sh**, some configurations are mandatory in the "
"custom domain's DNS to ensure good deliverability."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:58
msgid ""
"Most of the configuration will be done on the domain provider’s side, and it"
" might require some configuration on the mail server itself. **Some "
"technical knowledge is required.**"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:61
msgid ""
"The first step is to configure the :ref:`SPF <email-domain-spf>` and "
":ref:`DKIM <email-domain-dkim>` to be compliant with Odoo’s mail server."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:64
msgid ""
"Next, the custom domain must be set as the alias domain of a company. Select"
" the company, open the :guilabel:`Settings`, and add the custom domain under"
" the :guilabel:`Alias Domain` field."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:67
msgid ""
"After adding the alias domain, click the :icon:`oi-arrow-right` "
"(:guilabel:`internal link`) icon to assign more companies to the custom "
"domain if needed. Enable the :ref:`developer-mode` mode to modify the "
"default aliases if desired:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:71
msgid ""
":guilabel:`Bounce Alias`: the mailbox used to catch delivery errors and "
"populate the :ref:`red envelope <email-issues-outgoing-delivery-failure>` on"
" the corresponding message."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:73
msgid ""
":guilabel:`Catchall Alias`: the default mailbox used to centralize all "
"replies."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:74
msgid ":guilabel:`Default From Alias`: the default sender address."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:77
msgid ""
"At the creation of the first alias domain, all companies will use it. If you"
" create a new company, the alias domain automatically set is the one with "
"the lowest priority (ad displayed on the alias domain list in "
":ref:`developer-mode`)."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:81
msgid ""
"All email aliases (e.g., related to CRM or Helpdesk teams) must have their "
"corresponding mailbox in the custom domain mail server."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst-1
msgid "Technical schema of external mail server configuration with Odoo."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:87
msgid ""
"To receive emails in the Odoo database within the corresponding chatter "
"(CRM, invoices, sales orders, etc.), one of these three methods must be "
"used:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:90
msgid ""
":ref:`Redirections/forwarding <email-inbound-custom-domain-redirections>`,"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:91
msgid ""
":ref:`Incoming mail servers <email-inbound-custom-domain-incoming-server>`,"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:92
msgid ""
":ref:`MX record <email-inbound-custom-domain-mx>` (requires advanced "
"technical knowledge)"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:94
msgid ""
"Using a custom domain implies that specific :ref:`local-parts <email-"
"outbound-custom-domain-smtp-server-local-part>` might be used by Odoo to "
"send emails."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:100
msgid "Sending emails with an external SMTP server"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:103
msgid ""
"If utilizing your own outgoing mail server, it must be paired with your own "
"domain, as updating the DNS of an Odoo subdomain is not feasible."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:106
msgid ""
"To add an external SMTP server in Odoo, open :guilabel:`Settings`, and "
"enable the :guilabel:`Use Custom Email Servers` option found under the "
":guilabel:`Emails` section. Then, click :guilabel:`Save` at the top of the "
"page to save the changes."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:110
msgid ""
"Returning to the :guilabel:`Emails` section, click :guilabel:`Outgoing Email"
" Servers`, then `New` to create an outgoing mail server record. Most fields "
"are the common parameters used to set up a connection to an SMTP server; use"
" the values provided by your email provider."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:114
msgid ""
"Once completed, click :guilabel:`Test Connection`. Note that a successful "
"test connection does not confirm that the email will go out as some "
"restriction might remain on the provider side, thus, it is recommended to "
"consult your provider’s documentation."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:121
msgid "Local-part values"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:123
msgid ""
"Below are presented the different local-part values that can be used by Odoo"
" to send emails. It might be required to whitelist them in your mail server:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:126
msgid "The Alias Domain Bounce Alias (default value = `bounce`),"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:127
msgid "The Alias Domain Default From (default value = `notifications`),"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:128
msgid ""
"The default admin address `admin@company-name.odoo.com` or, if changed, the "
"new value),"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:129
msgid ""
"The default Odoobot address `odoobot@company-name.odoo.com` or, if changed, "
"the new value),"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:130
msgid "The specific FROM defined on an email marketing campaign,"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:131
msgid "The specific FROM that can be defined in an email template."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:134
msgid ":doc:`google_oauth`"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:135
msgid ":doc:`azure_oauth`"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:140
msgid "Setting up different servers for transactional and mass emails"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:145
msgid "Personalized mail servers"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:147
msgid ""
"Transactional emails and mass mailings can be sent using separate email "
"servers in Odoo. Doing so means day-to-day emails, quotations, or invoices "
"sent to clients will be handled as *transactional emails*. *Mass mailing "
"emails*, including the sending of batches of invoices or quotations, will be"
" managed by the Marketing Automation or Email Marketing application."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:153
msgid ""
"You can use services like Gmail, Amazon SES, or Brevo for transactional "
"emails, and services like Mailgun, Sendgrid, or Mailjet for mass mailings."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:156
msgid ""
"First, activate the :ref:`developer-mode` and go to :menuselection:`Settings"
" --> Technical --> Email: Outgoing Mail Servers`. There, add two outgoing "
"email server records, one for the transactional emails server and one for "
"the mass mailings server. Enter a lower :guilabel:`Priority` value for the "
"transactional server (e.g., `1`) over the mass mailings server (e.g., `2`) "
"so transactional emails are given priority."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst-1
msgid "Example of split between transaction and mass mailing mail servers."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:165
msgid ""
"Now, go to :menuselection:`Email Marketing --> Configuration --> Settings`, "
"enable :guilabel:`Dedicated Server`, and select the appropriate email "
"server. Odoo uses the server with the lowest priority value for "
"transactional emails, and the server selected here for mass mailings."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst-1
msgid "Dedicated mail server on Email Marketing app settings."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:175
msgid "FROM filtering"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:178
msgid ""
"It’s **highly recommended** to configure the FROM Filtering on the outgoing "
"mail servers as per the instructions of your provider."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:181
msgid ""
"The :guilabel:`FROM Filtering` field allows for the use of a specific "
"outgoing email server depending on the *From* email address or domain that "
"Odoo is sending on behalf of. The **value must be a domain or a complete "
"address** that matches the sender’s email address and is trusted on the "
"outgoing mail server provider's side."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:186
msgid ""
"If FROM filtering is not used, emails will go out using the notification "
"address."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:189
msgid ""
"Some outgoing mail servers require a specific configuration of the FROM "
"filter."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:191
msgid ""
"When an email is sent from Odoo, the following sequence is used to choose "
"the outgoing email server:"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:193
msgid ""
"First, Odoo searches for a server that has the same FROM filtering value as "
"the From value (i.e., email address) defined in the outgoing email. This "
"configuration is ideal if all users of a company share the same domain but "
"have different local-parts."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:198
msgid ""
"If the sender's email address is `test@example.com`, only an email server "
"having a FROM filtering value equal to `test@example.com` or `example.com` "
"can be used."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:201
msgid ""
"If no server is found based on the first criteria, Odoo looks for the first "
"server without a FROM filtering value set. The email will be overridden with"
" the notification address."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:204
msgid ""
"If no server is found based on the second criteria, Odoo uses the first "
"server, and the email will be overridden with the notification address."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:208
msgid ""
"To determine which server is first, Odoo uses the priority value (the lower "
"the value is, the higher the priority is). Failing to do so, the first "
"server is determined by the servers' names, using alphabetical order."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:212
msgid ""
"It is also possible to use Odoo's mail server for transactional emails in "
"addition to mass mailings."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:217
msgid "Using an external email server and Odoo’s default server"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:219
msgid ""
"On Odoo Online and Odoo.sh, databases are started with Odoo's SMTP server. "
"If no outgoing mail server is set, the default Odoo's SMTP server will be "
"used."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst-1
msgid ""
"Adding a mail server using the Odoo's mail server with the CLI "
"authentication."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:226
msgid ""
"If an outgoing mail server is used simultaneously with Odoo’s default server"
" (CLI), the FROM filter of the outgoing mail server must contain a custom "
"domain, and the FROM filter of the CLI must contain Odoo’s subdomain. If "
"there is no FROM filtering, the email will go out using the notification "
"address."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst-1
msgid ""
"Splitting of Odoo mail server for transactional emails and Mail server for "
"Mass mailing."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:235
msgid ""
"On Odoo Online, the command line interface is equivalent to the default Odoo"
" mail server, using the same limit as if there was no outgoing mail server "
"in place."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:239
msgid ""
"On Odoo Online, the page also shows your daily email usage and your daily "
"limit. On Odoo.sh, you need to check on the monitor page the number of "
"outgoing emails that were sent."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:243
msgid ""
"On Odoo.sh, to use the command-line interface, an outgoing mail server can "
"be configured on the configuration file."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:247
msgid ""
"Odoo’s mail server is meant for transactional emails and small-scale "
"marketing campaigns. The :ref:`daily limit <email-issues-outgoing-delivery-"
"failure-messages-limit>` depends on the database type and the applications "
"used."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:254
msgid "Using a custom domain with an external email server"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:256
msgid ""
"Similar to the :ref:`previous chapter <email-outbound-different-servers-"
"external-odoo>`, proper configuration might be needed to ensure that the "
"external email server is allowed to send emails using your custom domain. "
"Refer to your provider’s documentation to properly set up the relevant "
"records (SPF, DKIM, and DMARC). A list of the :ref:`most common providers is"
" available <email-domain-providers-documentation>`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:263
msgid ""
"DNS configuration is required when you use your own domain. If an external "
"outgoing mail server is used, configuring the records as described in the "
":doc:`Odoo DNS configuration for our mail servers documentation "
"<email_domain>` **will not have the desired effect**, as it is independent "
"of Odoo when using a custom email server. Odoo does not allow the "
"configuration of Odoo's subdomain."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:272
msgid "Port restriction"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:274
msgid ""
"Port 25 is blocked for security reasons on Odoo Online and Odoo.sh. Try "
"using port 465, 587, or 2525 instead."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:280
msgid "Alias domain"
msgstr "Domena aliasu"

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:282
msgid ""
"The catchall domain is company-specific. By default, all companies share "
"Odoo’s subdomain (e.g., `company-name.odoo.com`), but each company may have "
"its own custom email domain."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:285
msgid ""
"When the :ref:`developer-mode` is activated, the alias domain options are "
"available by going to :menuselection:`Settings --> Technical --> Email: "
"Alias Domains`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:289
msgid ""
"Any modification of the alias domain must be done very carefully. If one of "
"the aliases (bounce, catchall, default from) is changed, all previous emails"
" that are not properly redirected to the new aliases will be lost."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:293
msgid ""
"The :guilabel:`Default From Alias` field can be filled with a local-part of "
"the email address (by default `notifications`) or a full email address. "
"Configure it to determine the `FROM` header of your emails. If a full email "
"address is used, all outgoing emails will be overwritten with this address."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:301
msgid "Notification system"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:303
msgid ""
"When an email is sent from the chatter, customers can reply directly to it. "
"If a customer replies directly to an email, the answer is logged in the same"
" chatter, thus functioning as a message thread related to the record."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:307
msgid ""
"Upon receiving the reply, Odoo then uses the subscribed followers (based on "
"the subscribed subtypes) to send them a notification by email, or in the "
"Odoo inbox, depending on the user’s preferences."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:311
msgid ""
"If a customer with the email address `“Mary” <mary@customer.example.com>` "
"makes a direct reply to an email coming from the Odoo database, Odoo's "
"default behavior is to redistribute the email's content to all other "
"followers within the thread."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:315
msgid ""
"As Mary’s domain does not belong to the alias domain, Odoo overrides the "
"email address and uses the notification email address to notify the "
"followers. This override depends on the configuration done in the database. "
"By default, on Odoo Online and Odoo.sh, the email `FROM` address will be "
"overridden with the value `notifications@company-name.odoo.com` instead of "
"`mary@customer.example.com`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:321
msgid ""
"The address is constructed using the name of the sender and `{alias domain, "
"default from alias}`@`{alias domain, domain name}`, by default, "
"`notifications@company-name.odoo.com`."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:328
msgid "Using a unique email address for all outgoing emails"
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:330
msgid ""
"To force the email address from which emails are sent, activate the "
":ref:`developer-mode`, and go to :menuselection:`Settings --> Technical --> "
"Email: Alias Domains`. On the :guilabel:`Default From Alias`, use the the "
"local-part or a complete email address as the value."
msgstr ""

#: ../../content/applications/general/email_communication/email_servers_outbound.rst:335
msgid ""
"If a **complete address** is used as the :guilabel:`Default From Alias` "
"value, **all** outgoing emails will be overwritten by this address."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:3
msgid "Common emailing issues and solutions"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:5
msgid "This page lists the most common emailing issues and their solutions."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:10
msgid "Odoo is not an email provider"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:12
msgid ""
"Odoo does not function like a classic email inbox, such as Gmail, Outlook, "
"Yahoo, etc."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:14
msgid ""
"While Odoo uses emails as a way to notify and communicate with "
"users/customers, it is, by design, not a replacement for a dedicated email "
"server. Therefore, it might not behave in the expected way when compared to "
"a traditional email inbox."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:18
msgid "The main differences are the following:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:20
msgid ""
"By default, once a notification or transactional email (quote, invoice, "
"direct message to a contact) is sent out successfully, the email object is "
"deleted. The email message's content lives in the chatter of the related "
"record. It prevents cluttering the database with multiple copies of the "
"content of the same email (when sent to multiple recipients) if the content "
"is already present in the chatter."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:25
msgid ""
"There is no concept of (blind) carbon copy ([B]CC). Odoo uses the concept of"
" *followers* added to a chatter to automatically decide when and how :ref:`a"
" contact is notified <email-outbound-notifications>` or receives a copy of "
"an email."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:28
msgid ""
"Incoming emails are handled by checking if the *TO* email address is a valid"
" email address in the Odoo database or, in case of a reply email, if there "
"is a reference in the email header that matches a message sent from the Odoo"
" database. All other emails will be bounced and **not** temporarily parked "
"in a spam or quarantine folder. In other words, any email unrelated to an "
"Odoo database is lost."
msgstr ""

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

#: ../../content/applications/general/email_communication/faq.rst:42
msgid "Changing the email address of the admin user account"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:44
msgid ""
"When an Odoo database is created, the main admin account is assigned a "
"placeholder email address. It is recommended to **replace the admin email "
"address** with a valid email address to prevent outgoing email issues."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:48
msgid ""
"To do so, on the admin account, click the user icon, click :guilabel:`My "
"Profile` (or :guilabel:`Preferences`), and update the :guilabel:`Email` "
"field found under the :guilabel:`Preferences` tab. Either use any other "
"email address or use your Odoo subdomain (e.g., `company-name.odoo.com`) and"
" `admin` for the local-part (e.g., `admin@company-name.odoo.com`)."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:56
msgid "Delivery failure"
msgstr "Błąd dostarczenia"

#: ../../content/applications/general/email_communication/faq.rst:58
msgid ""
"When a message is sent, an :icon:`fa-envelope-o` :guilabel:`(envelope)` icon"
" is displayed in the chatter. The icon turns red when delivery has failed "
"for at least one recipient."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst-1
msgid "Red envelope icon displayed in the chatter."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:64
msgid ""
"Left-click the envelope to display information about the delivery, and, if "
"possible, the relevant :ref:`error messages <email-issues-outgoing-delivery-"
"failure-messages>`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst-1
msgid "Example of a sending failure."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:70
msgid ""
"Click :guilabel:`See Error Details` to get extra information for the fail "
"reason, **if** Odoo was able to process the original error or bounce email."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:73
msgid ""
"Click :guilabel:`Send & close` to retry sending the email to all **toggled-"
"on** (:icon:`fa-toggle-on`) recipients under the :guilabel:`Try Again` "
"column. All **toggled-off** (:icon:`fa-toggle-off`) recipients will be "
"ignored."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:77
msgid ""
"Click :guilabel:`Ignore all` to ignore all currently failing emails and turn"
" the envelope icon from red to white."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:80
msgid ""
"Unsent emails also appear in the Odoo email queue. To access it, activate "
"the :ref:`developer mode <developer-mode>` and go to "
":menuselection:`Settings --> Technical --> Email: Emails`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst-1
msgid "Example of the technical email queue view."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:86
msgid ""
"Failed emails display the :guilabel:`Delivery Failed` status. Click "
":guilabel:`Retry` to put a failed email in the email queue again. It will "
"then appear with the :guilabel:`Outgoing` status. The email will be sent "
"again the next time the scheduled action for the email queue runs."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:90
msgid ""
"Optionally, queued emails can be sent immediately by clicking "
":guilabel:`Send Now`. Click :guilabel:`Cancel Email` to remove it from the "
"email queue."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:94
msgid ""
"Sent emails are periodically cleaned from the queue. This is controlled by "
"the *Auto-Vacuum* scheduled action that cleans redundant data on your Odoo "
"database."
msgstr ""

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

#: ../../content/applications/general/email_communication/faq.rst:105
msgid "Daily limit reached"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst-1
msgid "Email limit reached warning."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:110
msgid ""
"Odoo limits the number of emails that can be sent from an Odoo Online "
"database. Most email service providers (e.g., Google, Yahoo, etc.) will "
"blacklist Odoo's server IP if Odoo's email server is sending too many emails"
" to addresses that do not exist or are no longer valid. It also applies to "
"unsolicited spam emails sent through an Odoo database."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:115
msgid ""
"The default daily email limit varies between **5 and 200 emails**. The exact"
" limit is depends on several factors (subject to change):"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:118
msgid ""
"Type of database subscription (one app free, trial, paying subscription)"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:119
msgid "Apps installed (i.e., Email Marketing, Marketing Automation)"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:120
msgid "If a database migration is ongoing"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:122
msgid "If the daily limit is reached, you can:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:124
msgid ""
"Contact :ref:`Odoo Support <email-issues-support>` to increase your email "
"quota. The following factors will be taken into account:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:127
msgid "Numbers of users on the database"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:128
msgid "Apps installed"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:129
msgid ""
"Bounce rate (the percentage of email addresses that did not receive emails "
"because they were returned by an email server on their way to the final "
"recipient)."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:131
msgid ""
"Whether your :ref:`email aliases are correctly set up and use the "
"appropriate custom domains <email-outbound-alias-domain>`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:135
msgid ""
"When using a custom domain, verify that :ref:`SPF <email-domain-spf>`, "
":ref:`DKIM <email-domain-dkim>`, and :ref:`DMARC <email-domain-dmarc>` are "
"correctly configured so that :ref:`Odoo's email servers are allowed to send "
"emails on your custom domain's behalf <email-outbound-custom-domain-odoo-"
"server>`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:140
msgid ""
":doc:`Use an external outgoing email server <../email_communication>` to be "
"independent of Odoo's email limit."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:142
msgid ""
"Wait until the next day, and retry sending the email. To do so, activate the"
" :ref:`developer mode <developer-mode>`, go to :menuselection:`Settings --> "
"Technical --> Email: Emails`, and click :guilabel:`Retry` next to the unsent"
" email."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:147
msgid ""
"The daily email limit counts every email leaving your Odoo database, "
"triggered either manually or automatically. By default, any internal "
"message, notification, logged note, etc., counts as an email if it notifies "
"someone via email. This can be mitigated by receiving :ref:`notifications in"
" Odoo <discuss_app/notification_preferences>` instead of by email."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:155
msgid "SMTP error"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:157
msgid ""
"`Simple Mail Transport Protocol (SMTP) "
"<https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol>`_ is a "
"standard used to transmit emails between email servers and/or email clients."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:161
msgid ""
"If you use :ref:`an external STMP server to send emails <email-outbound-"
"custom-domain-smtp-server>`, a standard set of `SMTP error codes exists "
"<https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes#Common_status_codes>`_."
" While the code numbers are not specific to Odoo, the exact content of the "
"error message might vary from email server to email server."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:168
msgid "A 550 SMTP permanent delivery error from sendgrid.com:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:179
msgid ""
"The error message indicates that you tried sending an email from an "
"unverified email address. Investigating the outgoing email server "
"configuration or the default *FROM* address of your database is a good "
"starting point to troubleshoot the issue, and verify that you whitelisted "
"the email address on the side of sendgrid.com."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:184
msgid ""
"Usually, inputting the error message content in a Google search can yield "
"information on what the root cause might be and how to correct the issue."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:187
msgid ""
"If the issue cannot be resolved and keeps occurring, contact :ref:`Odoo "
"Support <email-issues-support>`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:193
msgid "No error populated"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:195
msgid ""
"Odoo is not always capable of providing information on the reason a delivery"
" failed. The different email providers implement their own policy on bounced"
" emails, and it is not always possible for Odoo to interpret it correctly."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:199
msgid ""
"If there is a recurring problem with the same customer or the same domain, "
"contact :ref:`Odoo Support <email-issues-support>`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:203
msgid ""
"One of the most common reasons for an email failing to be sent with no error"
" message is related to the :ref:`SPF <email-domain-spf>` or :ref:`DKIM "
"<email-domain-dkim>` configuration. Also, verify that the implemented email "
"notification setup is adapted to your business needs. See the "
":doc:`Communication in Odoo by email documentation <../email_communication>`"
" for more information."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:212
msgid "Execution time"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:214
msgid ""
"The exact time of an email is sent is handled by a system utility *cron* "
"(scheduled action) that can be used to schedule tasks to run automatically "
"at predetermined intervals. Odoo uses this approach to send emails that are "
"considered \"not urgent\" (i.e., newsletters formats such as mass mailing, "
"marketing automation, and events). This avoids cluttering the mail servers "
"and, instead, prioritizes individual communication."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:222
msgid ""
"A cron is an action that Odoo runs in the background to execute particular "
"code to complete a task. Odoo also creates cron triggers in certain "
"workflows that can trigger a scheduled action earlier than its scheduled "
"date. Running a scheduled action manually or changing its frequency is "
"generally not recommended, as it might create errors or break specific "
"workflows."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:227
msgid ""
"By default, for the normal email queue, the :guilabel:`Mail: Email Queue "
"Manager` cron runs every 60 minutes. The lowest running interval for a cron "
"is 5 minutes. Odoo recommends an interval of 15 minutes to ensure proper "
"operation. If the interval is too short, not all emails may be processed, "
"which may cause the cron to timeout."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:232
msgid ""
"Emails that are considered urgent (from one person to another, such as sales"
" orders, invoices, purchase orders, etc.) are sent immediately. They do not "
"show up under :menuselection:`Settings --> Technical --> Email: Emails`, "
"unless their delivery fails."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst-1
msgid ""
"Example of sending information header when a mailing campaign is queued."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:239
msgid ""
"Email campaigns are sent as soon as possible (after clicking the "
":guilabel:`Send` button) or at a scheduled time (after clicking the "
":guilabel:`Schedule` button)."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:242
msgid ""
"For the email marketing queue, the :guilabel:`Mail Marketing: Process queue`"
" cron runs once a day, but will be **automatically triggered early** if a "
"campaign is scheduled outside of this default frequency. If a mailing list "
"contains a large number of recipients, triggering the cron manually multiple"
" times is **not recommended**, as it will not accelerate the processing time"
" and might create errors."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:249
msgid ""
"To edit crons, enable the :ref:`developer mode <developer-mode>` and go to "
":menuselection:`Settings --> Technical --> Automation: Scheduled Actions`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:253
msgid ""
"For more information about crons when using Odoo.sh, check out :doc:`Odoo.sh"
" frequent technical questions "
"<../../../administration/odoo_sh/advanced/frequent_technical_questions>`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:259
msgid "Email Marketing campaigns stuck in the queue"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:261
msgid ""
"If multiple Email Marketing campaigns are put in the queue, they are "
"processed in chronological order based on their creation date."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:265
msgid ""
"If there are three campaigns: Campaign_1 (created 1st of January), "
"Campaign_2 (created 2nd of January), and Campaign_3 (created 3rd of "
"January), they are put in the queue by clicking :guilabel:`Send` on all "
"three of them."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst-1
msgid "Example of three email marketing campaigns."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:272
msgid ""
"The cron will try to process Campaign_1, then Campaign_2, and finally "
"Campaign_3. It will not start processing Campaign_2 until it finishes "
"processing Campaign_1."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:275
msgid ""
"If an email campaign never leaves the queue, there might be an issue with "
"the campaign at the top of the queue. To troubleshoot, we could remove "
"Campaign_1 from the queue by clicking the :guilabel:`Cancel` button, and see"
" if the two other campaigns are sent. Then we could try to fix Campaign_1 or"
" contact :ref:`Odoo Support <email-issues-support>`."
msgstr ""

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

#: ../../content/applications/general/email_communication/faq.rst:285
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 message (most of the time a "
":guilabel:`550: mailbox unavailable` error message)."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:292
msgid "Email is not received"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:298
msgid ""
"Contact :ref:`Odoo Support <email-issues-support>` if there is a recurring "
"issue with the same client or domain."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:303
msgid ""
"You can use database logs to understand and fix issues. 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. Sending "
"failures can also be seen by logs when they indicate that the message tried "
"to send repeatedly. Logs show every action to the email servers from the "
"database."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:310
msgid ""
"Live logs are located in the :file:`~/logs/` folder (accessed by the command"
" line or on the Odoo.sh dashboard). Log files are created everyday at 5:00 "
"AM (UTC)."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:314
msgid ""
"The two most recent files, for the current day and the previous one, are "
"named :file:`odoo.log` and :file:`odoo.log.1`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:317
msgid ""
"Log files for older dates are named using their dates and are compressed. "
"Use the commands :command:`grep` and :command:`zgrep` (for the compressed "
"ones) to search through the files."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:321
msgid ""
"For more information on logs and how to access them via the Odoo.sh "
"dashboard, refer to the :ref:`Odoo.sh logs documentation <odoosh/logs>`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:324
msgid ""
"For more information on accessing logs via the command line, refer to the "
":ref:`developer logging documentation <reference/cmdline/server/logging>`."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:330
msgid "Information for Odoo Support"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:332
msgid ""
"Here is a list of helpful information to include when reaching out to `Odoo "
"Support <https://www.odoo.com/help>`_:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:335
msgid ""
"An export of the full email from the inbox. These are usually in `.eml` or "
"`.msg` file formats containing technical information required for an "
"investigation. The exact process to download the file depends on your third-"
"party email provider."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:340
msgid ""
"`Gmail Help Center: Trace an email with its full header "
"<https://support.google.com/mail/answer/29436>`_"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:342
msgid ""
"`Microsoft Support: View internet message headers in Outlook "
"<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:344
msgid ""
"When using a local email software (e.g., Thunderbird, Apple Mail, Outlook, "
"etc.) to synchronize emails, it is usually possible to export the local "
"copies of emails as EML/MSG files. Refer to the documentation of the "
"software used for more information."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:349
msgid ""
"If possible, the EML/MSG file should be based on the original email that was"
" sent and is failing or is causing issues."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:352
msgid ""
"For **incoming emails**: if possible contact the original email sender and "
"request an EML/MSG copy of the original email. Sending a copy of the "
"original email (forwarded) only contains partial information related to the "
"troubleshooting."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:356
msgid ""
"For **outgoing emails**: either provide the EML/MSG of the email or specify "
"what record in the database is affected (e.g., sales order number, contact "
"name, invoice number) and the date/time when the email was sent (e.g., email"
" sent on the 10th January 2024 11:45 AM Central European Time)."
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:361
msgid ""
"An explanation of the exact flow that is being followed to normally receive "
"those emails in Odoo. Try to answer the following questions:"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:364
msgid "Is this a notification message from a reply being received in Odoo?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:365
msgid "Is this a message being sent from the Odoo database?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:366
msgid ""
"Is there an incoming email server being used, or is the email being "
"redirected/forwarded through a custom email server or provider?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:368
msgid "Is there an example of an email that has been correctly forwarded?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:369
msgid ""
"Have you changed any email-related settings recently? Did it stop working "
"after those changes?"
msgstr ""

#: ../../content/applications/general/email_communication/faq.rst:371
msgid "An answer to the following questions:"
msgstr ""

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

#: ../../content/applications/general/email_communication/faq.rst:374
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 "
"<email-issues-outgoing-delivery-failure>`."
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 ""

#: ../../content/applications/general/email_communication/google_oauth.rst:22
#: ../../content/applications/general/integrations/google_translate.rst:17
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
#: ../../content/applications/general/integrations/google_translate.rst-1
msgid "Project Name and Location for Google OAuth."
msgstr ""

#: ../../content/applications/general/email_communication/google_oauth.rst:42
#: ../../content/applications/general/integrations/google_translate.rst:39
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
#: ../../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:23
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:31
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:35
msgid ""
"Odoo :ref:`blocks port 25 <email-outbound-port-restriction>` on Odoo Online "
"and Odoo.sh databases."
msgstr ""

#: ../../content/applications/general/email_communication/mailjet_api.rst-1
msgid "SMTP configuration from Mailjet."
msgstr ""

#: ../../content/applications/general/email_communication/mailjet_api.rst:41
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:44
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:50
msgid "Add verified sender address(es)"
msgstr ""

#: ../../content/applications/general/email_communication/mailjet_api.rst:52
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:60
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:66
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:69
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:73
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:75
msgid "notifications\\@yourdomain.com"
msgstr ""

#: ../../content/applications/general/email_communication/mailjet_api.rst:76
msgid "bounce\\@yourdomain.com"
msgstr ""

#: ../../content/applications/general/email_communication/mailjet_api.rst:77
msgid "catchall\\@yourdomain.com"
msgstr ""

#: ../../content/applications/general/email_communication/mailjet_api.rst:80
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:83
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:87
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:92
#: ../../content/applications/general/email_communication/mailjet_api.rst:157
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:96
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:104
msgid "Add a domain"
msgstr ""

#: ../../content/applications/general/email_communication/mailjet_api.rst:106
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:113
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:116
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:119
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:128
msgid "Setup in the domain's DNS"
msgstr ""

#: ../../content/applications/general/email_communication/mailjet_api.rst:130
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:137
msgid "Return to Mailjet account information"
msgstr ""

#: ../../content/applications/general/email_communication/mailjet_api.rst:139
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:143
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:146
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:152
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:166
msgid "Set up in Odoo"
msgstr ""

#: ../../content/applications/general/email_communication/mailjet_api.rst:168
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:173
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:178
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:183
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/integrations.rst:3
msgid "Integrations"
msgstr "Integracje"

#: ../../content/applications/general/integrations/barcodelookup.rst:5
msgid "Barcode Lookup"
msgstr ""

#: ../../content/applications/general/integrations/barcodelookup.rst:7
msgid ""
"`Barcode Lookup <https://www.barcodelookup.com/>`_ allows you to scan (or "
"enter) products' barcodes (:abbr:`UPC (Universal Product Code)`, :abbr:`EAN "
"(European Article Number)`, or :abbr:`ISBN (International Standard Book "
"Number)`) to automatically create them in your Odoo database, complete with "
"product names, descriptions, images, categories, etc."
msgstr ""

#: ../../content/applications/general/integrations/barcodelookup.rst:15
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:10
#: ../../content/applications/general/users/azure.rst:22
#: ../../content/applications/general/users/google.rst:24
msgid "Configuration"
msgstr "Konfiguracja"

#: ../../content/applications/general/integrations/barcodelookup.rst:17
msgid ""
"If your database is hosted on **Odoo Online**, you can use Barcode Lookup "
"without configuration."
msgstr ""

#: ../../content/applications/general/integrations/barcodelookup.rst:19
msgid ""
"If your database is hosted on **Odoo.sh** or **on-premise**, proceed as "
"follows:"
msgstr ""

#: ../../content/applications/general/integrations/barcodelookup.rst:21
msgid ""
"Visit the `Barcode Lookup website <https://www.barcodelookup.com/api>`_ and "
"click :guilabel:`Sign Up for the API`."
msgstr ""

#: ../../content/applications/general/integrations/barcodelookup.rst:23
msgid ""
"Choose the appropriate plan based on the number of barcodes you need to "
"scan."
msgstr ""

#: ../../content/applications/general/integrations/barcodelookup.rst:24
msgid "Fill in the required details and complete the registration process."
msgstr ""

#: ../../content/applications/general/integrations/barcodelookup.rst:25
msgid "Copy the API key."
msgstr ""

#: ../../content/applications/general/integrations/barcodelookup.rst:26
msgid ""
"In Odoo, open the Settings app, scroll down to the :guilabel:`Integrations` "
"section, and, under :guilabel:`Barcode Database`, paste the Barcode Lookup "
":guilabel:`API Key`."
msgstr ""

#: ../../content/applications/general/integrations/barcodelookup.rst:30
msgid "Use"
msgstr "Użyj"

#: ../../content/applications/general/integrations/barcodelookup.rst:32
msgid ""
"To fill in product information using Barcode Lookup, create a new product "
"and fill in the :guilabel:`Barcode` field. The product's details are then "
"automatically imported from Barcode Lookup, updating the following fields: "
":guilabel:`Name`, :guilabel:`Price`, :guilabel:`Description`, "
":guilabel:`Tax`, :guilabel:`Image`, :guilabel:`Weight`, "
":guilabel:`Attributes`, :guilabel:`Product category`, and "
":guilabel:`Volume`. You can then modify any field(s) as needed."
msgstr ""

#: ../../content/applications/general/integrations/barcodelookup.rst:39
msgid ""
":ref:`Create new products during internal transfers using the Barcode Lookup"
" database <barcode/setup/barcodelookup>`."
msgstr ""

#: ../../content/applications/general/integrations/geolocation.rst:3
msgid "Geolocation"
msgstr "Geolokacja"

#: ../../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 :ref:`API Key "
"<address_autocomplete/generate_api_key>`."
msgstr ""

#: ../../content/applications/general/integrations/geolocation.rst-1
msgid "Google Places API key"
msgstr ""

#: ../../content/applications/general/integrations/geolocation.rst:39
msgid ""
":doc:`/applications/websites/website/configuration/address_autocomplete`"
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:3
msgid "Google Translate"
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:5
msgid ""
"*Google Translate* can be used to translate user generated text in the Odoo "
"chatter."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:8
msgid "Google API console"
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:10
msgid ""
"A majority of the setup for integrating *Google Translate* into Odoo is done"
" with the *Google API console*. Once the following processes are complete, "
"an *API key* is created to input in Odoo."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:14
msgid ""
"`Google Translate setup on Google "
"<https://cloud.google.com/translate/docs/setup>`_"
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:19
msgid ""
"To get started, go to the `Google API Console "
"<https://console.developers.google.com>`_. Then, log in with a *Google "
"Workspace* account, if there is one. If not, log in with a personal Gmail "
"account (this should match the email address that has billing attached to "
"it)."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:23
msgid ""
"Next, click :guilabel:`Create Project` on the far-right of the "
":guilabel:`OAuth consent screen`."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:26
msgid ""
"If the *Google API Console* has existing projects, click the drop-down menu "
"next to the :guilabel:`Google Cloud` icon, and a pop-over window appears. "
"Next, click :guilabel:`New Project` top-right of the pop-over window."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:30
msgid ""
"On the :guilabel:`New Project` screen, rename the :guilabel:`Project name` "
"to `Odoo Translate`, and browse for the :guilabel:`Location`. Set the "
":guilabel:`Location` as the *Google Workspace organization*. If a personal "
"Gmail account is being used, leave the :guilabel:`Location` as :guilabel:`No"
" Organization`."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:42
msgid "API library"
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:44
msgid ""
"Next, the *Cloud Translation API* needs to be installed on this newly-"
"created project. To do that, click :menuselection:`Library` in the left "
"menu. Then, search the term `Cloud Translation API`, and click into the "
"result. This should be a *Google Enterprise API* labeled :guilabel:`Cloud "
"Translation API`."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:49
msgid "Click :guilabel:`Enable` to install the library on this project."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:52
msgid ""
"Using the *Google Translate* API **requires** a current billing account with"
" `Google <https://myaccount.google.com/>`_."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:55
msgid ""
"Once a billing account is setup with *Google* and the library is enabled, "
"click :guilabel:`Manage` to finish configuration on the API."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:61
msgid ""
"Now that the project is set up, and the *Cloud Translation API* is enabled, "
"credentials **must** be created. This includes the *API key*."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:64
msgid ""
"To begin this process, click :menuselection:`Credentials` in the left "
"sidebar menu."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:66
msgid ""
"Then, click :guilabel:`Create Credentials` in the top menu, and select "
":guilabel:`API key` from the drop-down menu."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst-1
msgid "Create an API key in the Google API console."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:73
msgid "Copy the :guilabel:`API key` for use in the next section."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:76
msgid "For security purposes, the usage of the *API key* can be restricted."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:78
msgid ""
"To do that, go to the *API restrictions* by clicking on :guilabel:`Edit API "
"key` in the pop-over window, or by clicking on the listed API key on the "
":guilabel:`Credentials` page. From here, key restrictions can be set. This "
"includes setting an application to restrict the use of the API key, and "
"whether this API key can call any API."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:83
msgid ""
"It is recommended that the Odoo *Translate API* be restricted to **only** "
"allow requests from the configured Odoo database and to the *Cloud "
"Translation API*."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:86
msgid ""
"To add the website restriction, click :guilabel:`Websites`, under the "
":guilabel:`Set an application restriction`. Then, enter the address of the "
"database *Google Translate* is being used in, by clicking on "
":guilabel:`Add`. Lastly, add the :abbr:`URL (Uniform Resource Locator)`, and"
" click :guilabel:`Done`."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:91
msgid ""
"To restrict use of the key to a selected API, first, select "
":guilabel:`Restrict key`, under the :guilabel:`API restrictions` section. "
"Then use the drop-down menu to choose the API being configured (*Cloud "
"Translation API*)."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:96
msgid "Save the API key: copy the API key and store it somewhere secure."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:97
msgid ""
"Do **not** share the API key publicly or expose it in client-side code."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:100
msgid "Odoo configuration"
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:102
msgid ""
"To access the integration in Odoo, navigate to the :menuselection:`Settings "
"app --> Discuss section`. Enter the API key into the field labeled "
":guilabel:`Message Translation`. Then, :guilabel:`Save` the settings, and "
"*Google Translate* can be used in any chatter throughout the database."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst-1
msgid "Odoo configuration of the API key from the *Google API Console*."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:112
msgid "Translate chatter"
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:114
msgid ""
"To translate a user's text from another language, click the :guilabel:`... "
"(three dot)` icon menu to the right of the chatter. Then, select "
":guilabel:`Translate`. The content translates to the *language* set on the "
"user's preferences."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst-1
msgid "Google Translate present in an Odoo database's chatter."
msgstr ""

#: ../../content/applications/general/integrations/google_translate.rst:123
msgid ":ref:`language/install`"
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 "Ceny"

#: ../../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
#: ../../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
#: ../../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: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:39
msgid ""
"For locally installed versions of Microsoft Outlook, access the "
":guilabel:`Get Add-ins` menu item while in preview mode (**not** with a "
"message open). First, click on the :guilabel:`... (ellipsis)` icon in the "
"upper right of the previewed message, then scroll down, and click on "
":guilabel:`Get Add-ins`."
msgstr ""

#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:44
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:50
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:57
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:67
msgid "Connect the database"
msgstr ""

#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:69
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:77
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:85
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:89
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:93
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:95
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:100
msgid "Once this is complete, the Outlook panel needs to be opened again."
msgstr ""

#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:102
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:108
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:114
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:124
msgid "Add a shortcut to the plugin"
msgstr ""

#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:126
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:129
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:136
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
#: ../../content/applications/general/integrations/mail_plugins/outlook.rst-1
msgid "Odoo for Outlook customized action"
msgstr ""

#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:143
msgid "Following this step, open any email; the shortcut should be displayed."
msgstr ""

#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:150
msgid "Using the plugin"
msgstr ""

#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:152
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"
msgstr ""

#: ../../content/applications/general/integrations/unsplash.rst:5
msgid ""
"**Unsplash** is a recognized stock photography library integrated with Odoo."
msgstr ""

#: ../../content/applications/general/integrations/unsplash.rst:7
msgid ""
"If your database is hosted on **Odoo Online**, you can access Unsplash "
"pictures without configuration."
msgstr ""

#: ../../content/applications/general/integrations/unsplash.rst:10
msgid ""
"If your database is hosted on **Odoo.sh or on-premise**, proceed as follows:"
msgstr ""

#: ../../content/applications/general/integrations/unsplash.rst:12
msgid ""
"To **generate an Unsplash access key**, create or sign in to an `Unsplash "
"account <https://unsplash.com>`_."
msgstr ""

#: ../../content/applications/general/integrations/unsplash.rst:15
msgid ""
"Access your `applications dashboard "
"<https://unsplash.com/oauth/applications>`_, click :guilabel:`New "
"Application`, select all checkboxes, and click :guilabel:`Accept terms`."
msgstr ""

#: ../../content/applications/general/integrations/unsplash.rst:18
msgid ""
"In the pop-up window, enter your :guilabel:`Application Name`, starting with"
" the prefix `Odoo:` (e.g., `Odoo: connection`), so Unsplash recognizes it as"
" an Odoo instance. Then, add a :guilabel:`Description` and click "
":guilabel:`Create application`."
msgstr ""

#: ../../content/applications/general/integrations/unsplash.rst:22
msgid ""
"On the application details page, scroll down to the :guilabel:`Keys` section"
" and copy the :guilabel:`Access Key` and :guilabel:`Application ID`."
msgstr ""

#: ../../content/applications/general/integrations/unsplash.rst:25
msgid ""
"In Odoo, go to :menuselection:`General Settings` and enable the "
":guilabel:`Unsplash Image Library` feature. Then, enter the Unsplash "
":guilabel:`Access Key` and :guilabel:`Application ID`."
msgstr ""

#: ../../content/applications/general/integrations/unsplash.rst:29
msgid ""
"As a non-Odoo Online user, you are limited to a test key with a maximum of "
"50 Unsplash requests per hour."
msgstr ""

#: ../../content/applications/general/iot.rst:7
msgid "Internet of Things (IoT)"
msgstr "Internet Rzeczy (IoT)"

#: ../../content/applications/general/iot.rst:9
msgid ""
"Odoo Internet of Things (IoT) allows to connect physical devices such as "
"barcode scanners, receipt printers, payment terminals, measurement tools, "
"etc. to an Odoo database using an IoT system."
msgstr ""

#: ../../content/applications/general/iot.rst:12
msgid "The following IoT systems are supported:"
msgstr ""

#: ../../content/applications/general/iot.rst:14
msgid ""
":doc:`IoT box <iot/iot_box>`: micro-computer, plug-and-play device (i.e., "
"the Odoo IoT program is pre-installed);"
msgstr ""

#: ../../content/applications/general/iot.rst:16
msgid ""
":doc:`Windows virtual IoT <iot/windows_iot>`: Odoo IoT program for Windows "
"that can be installed on a Windows computer."
msgstr ""

#: ../../content/applications/general/iot.rst:20
#: ../../content/applications/general/iot/windows_iot.rst:25
msgid ""
":abbr:`MRP (Material Requirement Planning)` devices, including cameras and "
"measurement tools, are not compatible with Windows virtual IoT."
msgstr ""

#: ../../content/applications/general/iot.rst:22
msgid "Multiple IoT systems can be used at the same time."
msgstr ""

#: ../../content/applications/general/iot.rst:23
#: ../../content/applications/general/iot/windows_iot.rst:27
msgid ""
"It is also possible to create a Windows Virtual Machine on a MacOS/Linux "
"computer. However, this option is not supported by Odoo, and no "
"troubleshooting assistance will be provided."
msgstr ""

#: ../../content/applications/general/iot.rst:29
msgid "IoT box subscription"
msgstr ""

#: ../../content/applications/general/iot.rst:31
msgid ""
"An IoT box subscription is required for production use of IoT systems. If "
"you have issues related to your subscription, contact the database's account"
" manager or Odoo partner for assistance."
msgstr ""

#: ../../content/applications/general/iot.rst:35
msgid ""
"If the subscription is linked to an `Odoo.com <https://www.odoo.com>`_ "
"portal user, check the information on the portal's subscription page."
msgstr ""

#: ../../content/applications/general/iot.rst:39
msgid ""
"`Odoo's compatible IoT devices <https://www.odoo.com/app/iot-hardware>`_"
msgstr ""

#: ../../content/applications/general/iot.rst:40
msgid ""
"`Odoo Tutorials: Internet of Things (IoT) Tutorials "
"<https://www.odoo.com/slides/internet-of-things-iot-175>`_"
msgstr ""

#: ../../content/applications/general/iot.rst:42
msgid "`IoT system FAQ <https://www.odoo.com/app/iot-faq>`_"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:3
msgid "IoT system connection to Odoo"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:6
#: ../../content/applications/general/iot/windows_iot.rst:16
msgid "Prerequisites"
msgstr "Wymagania wstępne"

#: ../../content/applications/general/iot/connect.rst:8
msgid ""
"To connect the IoT system to an Odoo database, the following prerequisites "
"must be met:"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:10
msgid ""
"The Internet of Things (IoT) app must be :ref:`installed <general/install>`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:11
msgid "The IoT system must be connected to the network."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:12
msgid ""
"The computer connecting to Odoo must be on the same network as the IoT "
"system."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:15
msgid ""
"It is recommended to connect the IoT system to a **production** instance, as"
" other types of environments may cause issues (e.g., with :ref:`HTTPS "
"certificate generation <iot/https_certificate_iot/iot-eligibility>`)."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:20
msgid ":doc:`iot_box`"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:21
msgid ":doc:`windows_iot`"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:24
#: ../../content/applications/general/iot/devices/camera.rst:12
#: ../../content/applications/general/iot/devices/footswitch.rst:14
#: ../../content/applications/general/iot/devices/printer.rst:16
#: ../../content/applications/general/iot/devices/screen.rst:18
msgid "Connection"
msgstr "Połączenie"

#: ../../content/applications/general/iot/connect.rst:26
msgid ""
"The IoT system can be connected to the Odoo database using a :ref:`pairing "
"code <iot/connect/pairing-code>` or a :ref:`connection token "
"<iot/connect/token>`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:32
msgid "Connection using a pairing code"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:35
msgid ""
"The pairing code is displayed for up to 5 minutes after the IoT system "
"starts. If the code is no longer visible, reboot the IoT box or "
":ref:`restart the Windows virtual IoT service <iot/windows_iot/restart>` to "
"display the pairing code again. Alternatively, connect the IoT system to the"
" database using a :ref:`connection token <iot/connect/token>`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:39
msgid ""
"The pairing code is not displayed if the IoT system is already connected to "
"a database (e.g., a test database)."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:42
msgid "Retrieve the IoT's system pairing code:"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:46
#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:17
#: ../../content/applications/general/iot/iot_box.rst:3
msgid "IoT box"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:48
msgid ""
"Connect the IoT box to an external monitor or printer. If the IoT box was "
"already plugged prior to this, reboot it by unplugging it for a few seconds "
"and replugging it."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:51
msgid ""
"External monitor: The pairing code should be displayed on the screen a few "
"minutes after rebooting the IoT box."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:53
msgid "Printer: The pairing code should be printed automatically."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:56
msgid ""
"If no external monitor or printer is connected to the IoT box, access the "
":ref:`IoT box's homepage <iot/iot-box/homepage>`; the code is displayed in "
"the :guilabel:`Pairing Code` section."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:60
#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:60
#: ../../content/applications/general/iot/windows_iot.rst:3
msgid "Windows virtual IoT"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:62
msgid ""
"On the computer with the Windows virtual IoT installed, open the IoT "
"system's homepage in a web browser by navigating to the URL "
"`http://localhost:8069`. Then, scroll to the :guilabel:`Pairing Code` "
"section."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:66
#: ../../content/applications/general/iot/connect.rst:75
msgid "In Odoo, open the IoT app and click :guilabel:`Connect`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:67
msgid ""
"In the :guilabel:`Connect an IoT Box` popup that opens, enter the "
":guilabel:`Pairing code`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:68
msgid "Click :guilabel:`Pair`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:73
msgid "Connection using a connection token"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:76
msgid ""
"In the :guilabel:`Connect an IoT Box` popup that opens, copy the "
":guilabel:`Token`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:77
#: ../../content/applications/general/iot/devices/printer.rst:177
msgid ""
"Access the :ref:`IoT box's <iot/iot-box/homepage>` or :ref:`Windows virtual "
"IoT's <iot/windows-iot/homepage>` homepage."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:79
msgid ""
"In the :guilabel:`Odoo database connected` section, click "
":guilabel:`Configure`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:80
msgid ""
"Paste the token into the :guilabel:`Server Token` field and click "
":guilabel:`Connect`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:85
msgid "IoT system form"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:87
msgid ""
"Once the IoT system is connected to the Odoo database, it is displayed as a "
"card in the IoT app. Click the IP address on the card to access the "
":ref:`IoT box's <iot/windows-iot/homepage>` or :ref:`Windows virtual IoT's "
"<iot/iot-box/homepage>` homepage. Click the card to access the list of "
":doc:`devices <devices>` connected to the IoT system."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:93
msgid ""
":ref:`Enable the developer mode <developer-mode>` to access the IoT system's"
" :guilabel:`Technical Information`, such as its :guilabel:`Identifier`, "
":guilabel:`Domain address`, and :guilabel:`Image version`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:98
msgid ""
"By default, drivers are automatically :ref:`udpated "
"<iot_updating_iot/handlers>` every time the IoT system is restarted. To "
"disable automatic updates, uncheck the :guilabel:`Automatic drivers update` "
"option."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:105
msgid "Troubleshooting"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:108
msgid "The pairing code does not appear or does not work"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:110
msgid ""
"The :ref:`pairing code <iot/connect/pairing-code>` might not be displayed or"
" printed under the following circumstances:"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:113
msgid "The IoT system is not connected to the Internet."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:114
msgid "The IoT system is already connected to an Odoo database."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:115
msgid ""
"The :ref:`pairing code <iot/connect/pairing-code>` display time has expired."
" Reboot the IoT box or :ref:`restart the Windows virtual IoT service "
"<iot/windows_iot/restart>` to display the pairing code again."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:118
msgid ""
"The IoT system's image version is too old and needs to be :ref:`updated "
"<iot/updating_iot/image-code>`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:122
msgid "The IoT system is connected but does not appear in the database"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:124
msgid ""
"The IoT system might take a few minutes to restart when it connects to a "
"database. If it still does not appear after a few minutes:"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:127
msgid ""
"Verify that the IoT system can reach the database and the server does not "
"use a multi-database environment."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:129
msgid ""
"Reboot the IoT box or :ref:`restart the Windows virtual IoT service "
"<iot/windows_iot/restart>`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:132
msgid "The IoT box is connected to the Odoo database but cannot be reached"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:134
msgid ""
"Verify that the IoT system and the computer running the Odoo database are "
"connected to the same network."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:138
msgid ""
"The Windows virtual IoT's homepage cannot be accessed from another device"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:140
msgid "Check the :ref:`iot/windows-iot/firewall`."
msgstr ""

#: ../../content/applications/general/iot/connect.rst:143
msgid "The IoT system is disconnected from the database after an Odoo upgrade"
msgstr ""

#: ../../content/applications/general/iot/connect.rst:145
msgid ""
":ref:`Update the IoT system's image <iot/updating_iot/image-code>` by "
"flashing the IoT box's card or :ref:`uninstalling the Windows virtual IoT "
"program <iot/windows_iot/uninstall>` and :ref:`reinstalling <iot/windows-"
"iot/installation>` the latest package for Windows **matching your database's"
" version**."
msgstr ""

#: ../../content/applications/general/iot/devices.rst:7
msgid "Devices"
msgstr "Urządzenia"

#: ../../content/applications/general/iot/devices.rst:10
msgid ""
":doc:`Connect a Worldline payment terminal "
"<../../sales/point_of_sale/payment_methods/terminals/worldline>`"
msgstr ""

#: ../../content/applications/general/iot/devices.rst:12
msgid ""
":doc:`Connect an Ingenico payment terminal "
"<../../sales/point_of_sale/payment_methods/terminals/ingenico>`"
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: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/printer.rst:65
msgid ""
":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_control_points`"
msgstr ""

#: ../../content/applications/general/iot/devices/camera.rst:59
#: ../../content/applications/general/iot/devices/printer.rst:66
msgid ""
":doc:`/applications/inventory_and_mrp/quality/quality_management/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:92
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:7
msgid ""
"With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect "
"measurement tools to the Odoo database for use in the *Quality app* on a "
"quality control point/quality check, or for use in a work center during the "
"manufacturing process."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:11
msgid ""
"Find the list of supported devices here: `Supported devices "
"<https://www.odoo.com/page/iot-hardware>`_."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:15
msgid "Connect with universal serial bus (USB)"
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:17
msgid ""
"To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the "
":abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of "
"Things)` box, and the device appears in the Odoo database."
msgstr ""

#: ../../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:26
msgid "Connect with bluetooth"
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:28
msgid ""
"Activate the Bluetooth functionality on the device (see the device manual "
"for further explanation), and the :abbr:`IoT (Internet of Things)` box "
"automatically connects to the device."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst-1
msgid "Bluetooth indicator on measurement tool."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:37
msgid ""
"Link a measurement tool to a quality control point in the manufacturing "
"process"
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:39
msgid ""
"In the *Quality app*, a device can be set up on a quality control point. To "
"do that, navigate to :menuselection:`Quality app --> Quality Control --> "
"Control Points`, and open the desired control point to which the measurement"
" tool should be linked."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:43
msgid ""
"From here, edit the control point, by selecting the :guilabel:`Type` field, "
"and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a"
" field called :guilabel:`Device`, where the attached device can be selected."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:47
msgid ""
"Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. "
":guilabel:`Save` the changes, if required."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:50
msgid ""
"At this point, the measurement tool is linked to the chosen quality control "
"point. The value, which usually needs to be changed manually, is "
"automatically updated while the tool is being used."
msgstr ""

#: ../../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:58
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:63
msgid ""
"On a quality check detail form, the :guilabel:`Type` of check can also be "
"specified to :guilabel:`Measure`. Access a new quality check detail page, by"
" navigating to :menuselection:`Quality app --> Quality Control --> Quality "
"Checks --> New`."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:68
msgid ""
":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`"
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:69
msgid ""
":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`"
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:72
msgid "Link a measurement tool to a work center in the Manufacturing app"
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:74
msgid ""
"To link a measurement tool to an action, it first needs to be configured on "
"a work center. To do that, navigate to :menuselection:`Manufacturing app -->"
" Configuration --> Work Centers`. Then, select the desired work center in "
"which the measurement tool will be used."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:78
msgid ""
"On the work center page, add the device in the :guilabel:`IoT Triggers` tab,"
" under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. "
"Then, the measurement tool can be linked to the :guilabel:`Action` drop-down"
" menu option labeled :guilabel:`Take Measure`. A key can be added to trigger"
" the action."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:84
msgid ""
"It should be noted that the first listed trigger is chosen first. The order "
"matters, and these triggers can be dragged into any order."
msgstr ""

#: ../../content/applications/general/iot/devices/measurement_tool.rst:88
msgid ""
"On the :guilabel:`Work Order` screen, a status graphic indicates whether the"
" database is correctly connected to the measurement tool."
msgstr ""

#: ../../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:11
msgid ""
"The **only** way to connect a printer directly to an Odoo database is "
"through the use of an IoT system. Without an IoT system, printing can still "
"occur, but it is managed through the printer itself, which is not the "
"recommended process."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:18
msgid ""
"IoT systems support printers connected through USB, 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:26
msgid ""
"Printers can take up to two minutes to appear in the IoT app "
":guilabel:`Devices` list."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:29
msgid "Link a printer"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:32
msgid "Link work orders to a printer"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:34
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:37
msgid ""
"In the :doc:`Quality app </applications/inventory_and_mrp/quality>`, a "
"device can be set up on a quality control point. To do so, go to the "
":menuselection:`Quality --> Quality Control --> Control Points`, and open "
"the desired control point."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:42
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:46
msgid ""
"From here, edit the control point by selecting the :guilabel:`Type` field, "
"and selecting :guilabel:`Print Label` from the dropdown menu of options. "
"Doing so reveals the :guilabel:`Device` field, where the attached device can"
" be selected."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:50
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:55
msgid ""
"Quality control points can also be accessed by navigating to "
":menuselection:`IoT --> Devices`, then selecting the device. Go to the "
":guilabel:`Quality Control Points` tab to add them to the device."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:60
msgid ""
"On a :doc:`quality check form "
"</applications/inventory_and_mrp/quality/quality_management/quality_checks>`,"
" the :guilabel:`Type` of check can also be set to :guilabel:`Print Label`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:71
msgid "Link reports to a printer"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:73
msgid "It is possible to link report types to a specific printer. To do so:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:75
msgid "Go to :menuselection:`IoT --> Devices` and select the desired printer."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:76
msgid ""
"Go to the :guilabel:`Printer Reports` tab and click :guilabel:`Add a line`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:77
msgid ""
"In the pop-up that opens, select the types of reports to be linked to the "
"printer and click :guilabel:`Select`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst-1
msgid "The list of reports assigned to a printer in the IoT app."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:84
msgid ""
"Reports can also be configured by :ref:`enabling the developer mode "
"<developer-mode>` and going to :menuselection:`Settings --> Technical --> "
"Reports`. Select the desired report from the list and set an :guilabel:`IoT "
"Device`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:88
msgid ""
"The first time a linked report is selected to print, a :guilabel:`Select "
"Printers` pop-up window appears. Tick the checkbox next to the correct "
"printer for the report, and click :guilabel:`Print`. At that point, the "
"report is linked to the printer."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:93
msgid "Clear device printer cache"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:95
msgid ""
"After a printer is linked to print a report, the setting is saved in a "
"browser's cache. This means a user can have different devices saved in their"
" cache for different reports, based on the device they use to access Odoo. "
"It also means different users can have a report automatically printed from "
"different printers, based on their preferences."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:100
msgid ""
"To unlink a report from a printer, navigate to :menuselection:`IoT --> "
"Configuration --> Reset Linked Printers`. This generates a list of reports "
"that are linked to a printer on the current device. Click the "
":guilabel:`Unlink` button next to each report to remove the link."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:105
msgid ""
"This step **only** prevents the report from automatically printing to the "
"listed printer from the current browser. The report is still :ref:`linked "
"<iot/link-printer>` on the device, under the :guilabel:`Printer Reports` "
"tab."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst-1
msgid "A list of reports currently linked to a printer in the IoT app."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:113
msgid ""
":doc:`POS Order Printing "
"<../../../sales/point_of_sale/restaurant/kitchen_printing>`"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:116
msgid "Potential issues"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:119
msgid "The printer is not detected"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:121
msgid ""
"If a printer does not appear in the devices list, go to the :ref:`IoT box's "
"<iot/iot-box/homepage>` or :ref:`Windows virtual IoT's <iot/windows-"
"iot/homepage>` homepage, click :guilabel:`Show` in the :guilabel:`Devices` "
"section, and make sure the printer is listed."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:125
msgid ""
"If the printer does not appear on the IoT system's homepage, click "
":guilabel:`Printer Server`, then :guilabel:`Administration`, and "
":guilabel:`Add Printer`. If the printer is not in the list, it is likely not"
" connected properly."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:130
msgid "The printer outputs random text"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:132
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/devices/printer.rst:136
msgid ""
"The solution is to manually select the corresponding driver. On the IoT "
"system's homepage, click :guilabel:`Printer Server`, then "
":guilabel:`Printers`, and select the printer in the list. In the "
":guilabel:`Administration` dropdown menu, click :guilabel:`Modify Printer`. "
"Follow the steps and select the printer's *make* and *model*."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst-1
msgid "Edit the printer connected to the IoT system."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:146
msgid ""
"Epson 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/devices/printer.rst:150
msgid "The printer is detected but is not recognized correctly"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:152
msgid ""
"If Odoo and the IoT system do not recognize the printer correctly, go to "
":menuselection:`IoT --> Devices`, click the device's card to access its "
"form, and set the :guilabel:`Subtype` field to the appropriate option: "
":guilabel:`Receipt Printer`, :guilabel:`Label Printer`, or :guilabel:`Office"
" Printer`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:158
msgid "Epson configuration special case"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:160
msgid ""
"Most Epson printers support printing receipts in Odoo 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/devices/printer.rst:163
msgid "TM-U220"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:164
msgid "TM-U230"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:165
msgid "TM-P60"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:166
msgid "TMP-P60II"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:168
msgid ""
"To bypass this issue, you can configure the printer to use the `ESC *` "
"command."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:170
msgid ""
"First, review Epson's website for compatibility for both the `GS v 0 "
"<https://download4.epson.biz/sec_pubs/pos/reference_en/escpos/gs_lv_0.html>`_"
" and `ESC * "
"<https://download4.epson.biz/sec_pubs/pos/reference_en/escpos/esc_asterisk.html>`_"
" commands."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:174
msgid ""
"If the printer is incompatible with `GS v 0` but supports `ESC *`, configure"
" the IoT system to use the `ESC *` command as follows:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:179
msgid ""
"Click the :guilabel:`Printer server` button, then click "
":guilabel:`Administration` on the CUPS page."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:181
msgid ""
"Click :guilabel:`Add Printer` in the :guilabel:`Printers` section, select "
"the printer, and click :guilabel:`Continue`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:185
msgid "If the printer's name is still uncertain, take the following steps:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:187
msgid "Take note of the listed printers on the CUPS page."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:188
msgid "Turn the printer off and refresh the page."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:189
msgid ""
"Compare the difference with the first list to see which printer disappeared."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:190
msgid "Turn the printer back on and refresh the page again."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:191
msgid "Double-check the list again to see if the printer re-appears."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:192
msgid ""
"The printer that disappeared and reappears again on the listed printers is "
"the name of the printer in question. It can be :guilabel:`Unknown` under "
":guilabel:`Local printers`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:195
msgid ""
"On the :guilabel:`Add Printer` page, specify the printer's :guilabel:`Name` "
"using the following convention: "
"`<printer_name>__IMC_<param_1>_<param_2>_..._<param_n>__`, where:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:198
msgid ""
"`printer_name` is the printer's name. It can contain any character except "
"`_`, `/`, `#`, or ` ` (space character)."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:200
msgid ""
"`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC "
"*`)."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:201
msgid "`param_1`: This stands for the specific parameter:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:203
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. For "
"example, `100` is the original size, `50` is half the size, and `200` is "
"twice the size."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:206
msgid ""
"`LDV`: *Low Density Vertical* (will be set to *High Density Vertical* if not"
" specified)."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:207
msgid ""
"`LDH`: *Low Density Horizontal* (will be set to *High Density Horizontal* if"
" not specified)."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:210
msgid ""
"*Density* parameters might need to be configured in a particular way, "
"depending on the printer model."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:212
msgid ""
"Refer to `Epson's ESC * documentation "
"<https://download4.epson.biz/sec_pubs/pos/reference_en/escpos/esc_asterisk.html>`_"
" to determine if the printer requires these parameters to be set."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:216
msgid "The following are examples of proper and improper name formatting:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:218
msgid "Proper name formatting:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:220
msgid "`EPSONTMm30II__IMC__`"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:221
msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:223
msgid ""
"Improper name formatting (this will not prevent printing, but the result "
"might not have the expected printed output):"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:226
msgid "`EPSON TMm 30II`: The name cannot contain spaces."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:227
msgid ""
"`EPSONTMm30II`: The name itself is correct, but it will not use `ESC *`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:228
msgid "`EPSONTMm30II__IMC`: This name is missing the end `__`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:229
msgid ""
"`EPSONTMm30II__IMC_XDV__`: The parameter `XDV` does not match any existing "
"parameters."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:230
msgid ""
"`EPSONTMm30II__IMC_SCALE__`: The parameter `SCALE` is missing the scale "
"value."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:232
msgid ""
"Once the printer's name has been defined using the appropriate naming "
"convention, click :guilabel:`Continue`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:234
msgid ""
"Set the :guilabel:`Make` value to :guilabel:`Raw` and the :guilabel:`Model` "
"value to :guilabel:`Raw Queue (en)`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:236
msgid ""
"Click :guilabel:`Add Printer`. If everything was done correctly, the page "
"should redirect to the :guilabel:`Banners` page."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:238
msgid ""
"Wait a few minutes for the IoT system to detect the printer and sync to "
"Odoo's server."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:239
msgid ""
":ref:`Access the POS settings <configuration/settings>` and select your POS,"
" or click the vertical ellipsis button (:guilabel:`⋮`) on a POS card and "
"click :guilabel:`Edit`. Scroll down to the :guilabel:`Connected Devices` "
"section, enable :guilabel:`IoT Box`, and select the printer in the "
":guilabel:`Receipt Printer` field. Click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:245
msgid ""
"If the printer was set up incorrectly (e.g., it continues to print random "
"text, or the printed receipt is too large or too small), it cannot be "
"modified via the printer's name in CUPS. Instead, configure a new printer "
"from scratch with modified parameters, following the steps above."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:253
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/devices/printer.rst:0
msgid "Properly formatted receipt picture from a demo database."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:261
msgid ""
"Printing this receipt immediately without proper formatting will not work, "
"as the TM-U220B printer model does not support the `GS v 0` command. "
"Instead, random characters will be printed:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid "Printer paper with seemingly random characters."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:268
msgid ""
"To properly configure formatting for the Epson TM-U220B printer model, "
"follow these steps:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:270
msgid ""
"After checking Epson's website for compatibility with both the `GS v 0 "
"<https://download4.epson.biz/sec_pubs/pos/reference_en/escpos/gs_lv_0.html>`_"
" and `ESC * "
"<https://download4.epson.biz/sec_pubs/pos/reference_en/escpos/esc_asterisk.html>`_"
" commands, the TM-U220B printer is indeed incompatible with `GS v 0` but "
"supports `ESC *`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid "Epson compatibility evaluation from Epson website."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:278
msgid "When adding the printer, CUPS displays the list of available printers:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid "Administration menu, add printer selection."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:284
msgid ""
"In this case, the printer is connected via USB, so it is not 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 USB cable from the IoT system and refreshing the "
"page, the :guilabel:`Unknown` printer disappears. By plugging it back in, "
"the printer reappears."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:290
msgid ""
"For the naming convention, since the printer must print using the `ESC *` "
"command, it is imperative to add `__IMC`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid "Epson TM-U220 specifications on manufacturer's website."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:296
msgid ""
"For this particular model (TM-U220) `m` should be equal to 0 or 1. While "
"referencing the :guilabel:`Description` table on `Epson's ESC * website "
"<https://download4.epson.biz/sec_pubs/pos/reference_en/escpos/esc_asterisk.html>`_,"
" the `m` values could be 0, 1, 32, or 33. So, in this case, the `m` value "
"**cannot** be 32 or 33 (otherwise, random characters will be printed)."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:302
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, i.e. it has 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/devices/printer.rst:307
msgid ""
"To add a *Low Vertical Density*, add the `LDV` parameter to the naming "
"convention."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid ""
"Add a *Low Vertical Density* (the `LDV` parameter) to the naming convention."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:312
msgid ""
"Click :guilabel:`Continue` to proceed. Next, set the :guilabel:`Make` value "
"to :guilabel:`Raw` and the :guilabel:`Model` value to :guilabel:`Raw Queue "
"(en)`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid "Epson TM-U220 specifications on manufacturers website."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:318
msgid ""
"However, when trying to print with the naming convention "
"`EpsonTMU220B__IMC_LDV__`, the receipt is printed, but it is too large and "
"outside the margin. To resolve this, add a new printer (and naming "
"convention) with the `SCALE<X>` parameter to adapt to the receipt's size."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:322
msgid "Here are some examples:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:327
msgid "Printer Naming Convention"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:328
msgid "`EpsonTMU220B__IMC_LDV__`"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:329
msgid "`EpsonTMU220B__IMC_LDV_SCALE75__`"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:330
msgid "`EpsonTMU220B__IMC_LDV_LDH__`"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:331
msgid "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid "Receipt example format."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV__."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid ""
"Receipt format using naming convention: EpsonTMU220B__IMC_LDV_SCALE75__."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH__."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid ""
"Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH_SCALE35__."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:344
msgid "DYMO LabelWriter print issue"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:346
msgid ""
"The DYMO LabelWriter has a known issue in printing with IoT systems. The "
"OpenPrinting CUPS server installs the printer using :guilabel:`Local RAW "
"Printer` drivers. In order to print anything, the correct :guilabel:`Make "
"and Model` needs to be set to reference the correct driver when using the "
"device."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:351
msgid ""
"Additionally, a new printer needs to be added to reduce the print delay that"
" occurs after updating the driver."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:355
msgid ""
"The DYMO LabelWriter 450 DUO printer is the recommended DYMO printer for use"
" with Odoo and IoT systems. This device combines two printers: a label "
"printer and a tape printer. When configuring the following processes, it is "
"essential to select the correct model (either DYMO LabelWriter 450 DUO Label"
" (en) or DYMO LabelWriter 450 DUO Tape (en)). For consistency, the following"
" processes outline configuration steps for the DYMO LabelWriter 450 DUO "
"Label (en) model. Adjust the model selections as needed."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:365
msgid "DYMO LabelWriter not printing"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:367
msgid "If the DYMO LabelWriter fails to print, install a new driver:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:369
#: ../../content/applications/general/iot/devices/printer.rst:405
msgid ""
"Access the IoT system's homepage and click :menuselection:`Printer server` "
"to open the OpenPrinting CUPS console."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:371
msgid ""
"Click :menuselection:`Printers` in the top menu, then click the printer in "
"the list."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:372
msgid "Select :guilabel:`Maintenance` in the first dropdown menu."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:373
msgid "Select :guilabel:`Modify Printer` in the second dropdown menu."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid ""
"Modify the make and model of the DYMO LabelWriter. Maintenance and Modify dropdown\n"
"menus highlighted."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:379
msgid ""
"Select the specific network connection/printer on which the modification "
"should be made and click :guilabel:`Continue`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:381
msgid ""
"On the next page, click :guilabel:`Continue`, then select :guilabel:`DYMO` "
"from the :guilabel:`Make` dropdown list."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:383
msgid ""
"Click on :guilabel:`Continue` and set the :guilabel:`Model` to "
":guilabel:`DYMO LabelWriter 450 DUO Label (en)` (or whichever DYMO printer "
"model is being used)."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:385
msgid ""
"Click :guilabel:`Modify Printer` to set the new driver; a confirmation page "
"appears."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:386
msgid ""
"Click :menuselection:`Printers` in the top menu; all printers installed on "
"the OpenPrinting CUPS server appear, including the newly updated "
":guilabel:`DYMO LabelWriter 450 DUO Label` (or whichever DYMO printer model "
"is being used)."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:389
msgid ""
"Click the newly updated printer, then click the :guilabel:`Maintenance` "
"dropdown menu and select :guilabel:`Print Test Page` to print a test label. "
"The test label is printed after a few seconds if the driver update was "
"successful."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:393
msgid "To reduce this delay, add a new printer using the steps below."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:396
msgid "DYMO LabelWriter print delay"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:399
msgid ""
"If the DYMO LabelWriter 450 DUO printer is not printing at all, or is not "
"recognized (i.e., it has a :guilabel:`RAW` driver type), then :ref:`update "
"the drivers on the device <printer/dymo/update_drivers>`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:403
msgid ""
"To resolve the delay issue after modifying the driver, reinstall the "
"printer:"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:407
msgid ""
"Click :menuselection:`Administration` in the top menu, then click "
":guilabel:`Add a Printer`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:408
msgid ""
"On the next page, in the :guilabel:`Local Printers` section, select "
":guilabel:`DYMO LabelWriter 450 DUO Label (DYMO LabelWriter 450 DUO Label)` "
"(or whichever DYMO printer model is being used) pre-installed printer. Click"
" :guilabel:`Continue`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid ""
"Add a printer screen on OpenPrinting CUPS with DYMO LabelWriter 450 DUO Label\n"
"highlighted."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:416
msgid ""
"On the following screen, update the :guilabel:`Name` to something easily "
"identifiable, as the original printer will remain in the list. Then, click "
":guilabel:`Continue`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid ""
"Rename printer page in the 'Add a Printer' flow, with the name field "
"highlighted."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:422
msgid ""
"Set the :guilabel:`Model` field to :guilabel:`DYMO LabelWriter 450 DUO Label"
" (en)` (or whichever DYMO printer model is being used), then click "
":guilabel:`Add Printer` to complete the installation."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid ""
"Choose model screen on the OpenPrinting CUPS console with model and add a printer\n"
"highlighted."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:430
msgid ""
"Click :menuselection:`Printers` in the top menu and click the newly "
"installed printer :guilabel:`DYMO LabelWriter 450 DUO Label` (or whichever "
"DYMO printer model is being used) from in the list."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:0
msgid "Printer page with newly installed printer highlighted."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:437
msgid ""
"Click the :guilabel:`Maintenance` dropdown list and select :guilabel:`Print "
"Test Page` to print a test label. The test label should print out "
"immediately, or after one or two seconds."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:441
msgid "The Zebra printer does not print anything"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:443
msgid ""
"Zebra printers are quite sensitive to the format of the printed Zebra "
"Programming Language (ZPL) code. If nothing comes out of the printer or "
"blank labels are printed, try changing the format of the report sent to the "
"printer. To do so, activate the :ref:`developer mode <developer-mode>`, go "
"to :menuselection:`Settings --> Technical --> User Interface --> Views`, and"
" search for the corresponding template."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:450
msgid ""
"`Zebra's instructions on printing ZPL files "
"<https://supportcommunity.zebra.com/s/article/Print-a-zpl-file-using-the-"
"Generic-Text-Printer>`_"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:454
msgid "Barcode scanner issues"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:457
msgid "The characters read by the barcode scanner do not match the barcode"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:459
msgid ""
"By default, most barcode scanners are configured in the US QWERTY format. If"
" the barcode scanner uses a different layout, go to :menuselection:`IoT --> "
"Devices` and click the barcode device's card. Then, select the correct "
"language in the :guilabel:`Keyboard Layout` field."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:464
#: ../../content/applications/general/iot/devices/printer.rst:494
msgid ""
"The :guilabel:`Keyboard Layout` is language-specific, with available options"
" varying based on the device and the language of the database (e.g., "
":guilabel:`English (UK)`, :guilabel:`English (US)`, etc.)."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:469
msgid "Nothing happens when a barcode is scanned"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:471
msgid ""
"Make sure the correct device is selected in the :doc:`Point of Sale settings"
" </applications/sales/point_of_sale/configuration/pos_iot>` (when "
"applicable) and the barcode is configured to send an `ENTER` character "
"(keycode 28) at the end of every barcode."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:476
msgid "The barcode scanner is detected as a keyboard"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:479
msgid ""
"Some barcode scanners are identified as USB keyboards rather than barcode "
"scanners and are not recognized by IoT systems."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:482
msgid ""
"To change the device type manually, go to :menuselection:`IoT --> Devices` "
"and click the barcode device's card. Then, enable :guilabel:`Is scanner`."
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:486
msgid "The barcode scanner processes barcode characters individually"
msgstr ""

#: ../../content/applications/general/iot/devices/printer.rst:488
msgid ""
"When accessing the mobile version of Odoo from a mobile device or tablet "
"paired with a barcode scanner via the IoT system, the scanner might "
"interpret each character in a barcode as a separate scan. To resolve this, "
"go to :menuselection:`IoT --> Devices` and click the barcode device's card. "
"Then, select the correct language in the :guilabel:`Keyboard Layout` field."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:3
msgid "Connect a scale"
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:6
msgid ""
"In EU member states, `certification is legally required <https://eur-"
"lex.europa.eu/legal-"
"content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.096.01.0107.01.ENG>`_ to use a "
"scale as an integrated device."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:9
msgid ""
"Odoo is not certified in several countries, including France, Germany, and "
"Switzerland. If you reside in one of these countries, you can still use a "
"scale but without integration into your Odoo database. Alternatively, you "
"can acquire a *non-integrated* certified scale that prints certified labels,"
" which can then be scanned into your Odoo database."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:14
msgid ""
"To connect a scale to the IoT system, use a USB cable. In some cases, you "
"may need a serial-to-US adapter to complete the connection. If the scale is "
"`compatible with an IoT system <https://www.odoo.com/page/iot-hardware>`_, "
"no additional setup is required; the scale is automatically detected as soon"
" as it is connected. If the scale is not detected, reboot the IoT box or "
":ref:`restart the Windows virtual IoT service <iot/windows_iot/restart>` and"
" :ref:`update the scale's drivers <iot_updating_iot/handlers>`."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:22
msgid ""
"If the scale still does not function after updating the drivers, it might "
"not be `compatible with the Odoo IoT system <https://www.odoo.com/page/iot-"
"hardware>`_. In such cases, a different scale must be used."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:26
msgid ""
"Once the scale is connected to the IoT system, follow these steps to "
"configure it in the POS settings:"
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:29
msgid ""
":ref:`Access the POS settings <configuration/settings>` and select your POS,"
" or click the vertical ellipsis button (:guilabel:`⋮`) on a POS card and "
"click :guilabel:`Edit`."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:31
msgid ""
"Scroll down to the :guilabel:`Connected Devices` section and enable "
":guilabel:`IoT Box`."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:32
msgid "Select the scale in the :guilabel:`Electronic Scale` field."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:33
msgid "Click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:36
msgid ""
":doc:`Connect an IoT system to a POS "
"</applications/sales/point_of_sale/configuration/pos_iot>`"
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:38
msgid ""
"The scale is then available in all the :doc:`POS's sessions "
"</applications/sales/point_of_sale>`. If a product is configured with a "
"price per weight, selecting it on the :guilabel:`PoS screen` opens the scale"
" popup. The cashier can then weigh the product to automatically 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/scale.rst:48
msgid "Ariva S scales"
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:50
msgid ""
"For Ariva S series scales (manufactured by Mettler-Toledo, LLC.) to function"
" with IoT systems, a specific setting must be modified, and a dedicated "
"Mettler USB-to-proprietary RJ45 cable is required."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:54
msgid ""
"The official Mettler USB-to-RJ45 cable (Mettler part number 72256236) must "
"be used. Contact Mettler or a partner to purchase an authentic cable. **No "
"other** cable works for this configuration."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:58
msgid ""
"To configure the Ariva S scale for IoT system recognition, refer to page 17 "
"of `Mettler's Setup Guide for Ariva S series scales "
"<https://www.mt.com/dam/RET_DOCS/Ariv.pdf>`_ and follow these steps:"
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:61
msgid ""
"Hold the **>T<** button for eight seconds, or until :guilabel:`CONF` "
"appears."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:62
msgid ""
"Press **>T<** until :guilabel:`GRP 3` appears, then press **>0<** to "
"confirm."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:63
msgid ""
"Under :guilabel:`3.1`, ensure the setting is set to :guilabel:`1` (USB "
"Virtual COM ports) and press **>T<** to cycle through the options under "
"group 3.1."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:65
msgid ""
"Once :guilabel:`3.1` is set to :guilabel:`1`, press **>0<** to confirm the "
"selection."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:66
msgid "Continue to press **>0<** until :guilabel:`GRP 4` appears."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:67
msgid "Press **>T<** until :guilabel:`EXIT` appears."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:70
msgid "Do **not** make any other changes unless otherwise needed."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:72
msgid "Press **>0<**."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:73
msgid "Press **>0<** again to :guilabel:`SAVE`; the scale restarts."
msgstr ""

#: ../../content/applications/general/iot/devices/scale.rst:74
msgid ""
"Reboot the IoT box or :ref:`restart the Windows virtual IoT service "
"<iot/windows_iot/restart>`. The scale should then appear as `Toledo 8217`, "
"as opposed to the previous display, where it appeared as `Adam Equipment "
"Serial`."
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 <pos/pos_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:0
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 "Użycie"

#: ../../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/iot/iot_advanced.rst:5
msgid "Advanced"
msgstr "Zaawansowane"

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:5
msgid "HTTPS certificate (IoT)"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:7
msgid ""
"*Hypertext Transfer Protocol Secure* (HTTPS) is the secure and encrypted "
"version of *Hypertext Transfer Protocol* (HTTP), which is the primary "
"protocol used for data communication between a web browser and a website. It"
" secures communications by using an encryption protocol known as *Transport "
"Layer Security* (TLS), previously called *Secure Sockets Layer* (SSL). The "
"security of :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` relies on "
":abbr:`TLS (Transport Layer Security)` /:abbr:`SSL (Secure Sockets Layer)` "
"certificates, which authenticate the provider and verify their identity."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:15
msgid ""
"The use of HTTPS is required to communicate with certain network devices, "
"particularly payment terminals. If the HTTPS certificate is not valid, some "
"devices cannot interact with the IoT system."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:20
msgid ""
"In this documentation and throughout Odoo, the term *HTTPS certificate*  "
"refers to a valid SSL certificate that allows an HTTPS connection."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:26
msgid "HTTPS certificate generation"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:28
msgid ""
"The HTTPS certificate is generated automatically. When the IoT system is "
"(re-)started (e.g., after it is connected to the Odoo database), a request "
"is sent to `<https://www.odoo.com>`_, which returns the HTTPS certificate if"
" the IoT system and database meet the eligibility criteria:"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:34
msgid ""
"The database must 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/iot_advanced/https_certificate_iot.rst:36
msgid ""
"The Odoo subscription must be ongoing (:guilabel:`In Progress` status) and "
"have an :ref:`IoT box subscription <iot/iot/iot-subscription>` line."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:39
msgid "When the certificate has been received:"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:41
msgid ""
"The IoT system's homepage address is updated to a new HTTPS URL ending with "
"`.odoo-iot.com`. Click the URL to establish a secure HTTPS connection."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:0
msgid "Odoo IoT app IoT box with .odoo-iot.com domain."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:47
msgid ""
"The :guilabel:`HTTPS certificate` banner displays the certificate's validity"
" period. To view this information, click the :icon:`fa-cogs` "
"(:guilabel:`cogs`) button on the IoT system's homepage."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:0
msgid "IoT box homepage with HTTPS certificate validity date."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:54
msgid "HTTPS certificate generation issues and errors"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:57
msgid "The HTTPS certificate does not generate"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:59
msgid "Potential causes include the following:"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:61
msgid ""
"No :ref:`IoT box subscription <iot/iot/iot-subscription>` is linked to your "
"account."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:62
msgid ""
"The :ref:`IoT box subscription <iot/iot/iot-subscription>` was added *after*"
" connecting the IoT system to the database. In this case, refresh the IoT "
"system's homepage or reboot/:ref:`restart <iot/windows_iot/restart>` the IoT"
" system to regenerate the HTTPS certificate."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:65
msgid ""
"The firewall is preventing the HTTPS certificate from generating correctly. "
"In this case, deactivate the firewall until the certificate is successfully "
"generated."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:69
msgid ""
"Some devices, such as routers with a built-in firewall, can prevent the "
"HTTPS certificate from generating."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:73
msgid ""
"The IoT system's homepage can be accessed using its IP address but not the "
"`xxx.odoo-iot.com` URL"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:75
msgid ""
"Contact your system or network administrator to address the issue. Network-"
"related problems are beyond the scope of Odoo support services."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:78
msgid ""
"If the router allows manual :abbr:`DNS (Domain Name System)` configuration, "
"update the settings to use `Google DNS "
"<https://developers.google.com/speed/public-dns>`_."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:80
msgid ""
"If the router does not support this, you need to update the DNS settings "
"directly on each device that interacts with the IoT system to use `Google "
"DNS <https://developers.google.com/speed/public-dns>`_. Instructions for "
"configuring DNS on individual devices can be found on the respective "
"manufacturer's website."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:86
msgid ""
"Some IoT devices, such as payment terminals, likely do not require DNS "
"changes, as they are typically pre-configured with custom DNS settings."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:88
msgid ""
"On some browsers, an error code mentioning the DNS (such as "
"`DNS_PROBE_FINISHED_NXDOMAIN`) is displayed."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:92
msgid "Errors"
msgstr "Błędy"

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:94
msgid ""
"A specific error code is displayed on the IoT system's homepage if any "
"issues occur during the generation or reception of the HTTPS certificate."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:98
msgid ""
"When you access the IoT system's homepage, it automatically checks for an "
"HTTPS certificate and attempts to generate one if it is missing. If an error"
" appears, refresh the page to see if the issue is resolved."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:103
msgid "`ERR_IOT_HTTPS_CHECK_NO_SERVER`"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:105
msgid ""
"The server configuration is missing, i.e., the Odoo instance is not "
":doc:`connected <../connect>` to the IoT system."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:109
msgid "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:111
msgid ""
"An error occurred while attempting to read the existing HTTPS certificate. "
"Verify that the HTTPS certificate file is readable."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:115
msgid "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:117
msgid ""
"The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is "
"missing form the IoT."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:119
msgid ""
"Verify that both values are correctly configured. To update them, "
":ref:`access the IoT box's <iot/iot-box/homepage>` or :ref:`Windows virtual "
"IoT's homepage <iot/windows-iot/homepage>`, click the :icon:`fa-cogs` "
"(:guilabel:`cogs`) button, then click :guilabel:`Credential`."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:124
msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:126
msgid ""
"An unexpected error occurred while the IoT system tried to reach "
"`<https://www.odoo.com>`_. This is likely due to network-related issues, "
"such as:"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:129
msgid "The IoT system does not have Internet access."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:130
msgid ""
"Network restrictions (e.g., firewalls or VPNs) are preventing communication "
"with https://www.odoo.com."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:134
msgid ""
"To access the full request exception details with information regarding the "
"error, :ref:`enable the developer mode <developer-mode>`, click the IoT "
"system's card in the IoT app, and click :guilabel:`Download logs` on the "
":ref:`IoT system's form <iot/connect/IoT-form>`. To define the log levels "
"recorded in the IoT system's log file, :ref:`access the IoT box's "
"<iot/windows-iot/homepage>` or :ref:`Windows virtual IoT's <iot/iot-"
"box/homepage>` homepage, click the :icon:`fa-cogs` (:guilabel:`cogs`) "
"button, then :guilabel:`Log level` at the bottom of the page."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:141
msgid ""
"To address network-related issues, contact your system or network "
"administrator; these issues are beyond the scope of Odoo support services."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:145
msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:147
msgid ""
"The IoT system successfully reached `<https://www.odoo.com>`_ but received "
"an unexpected `HTTP response (status codes) "
"<https://developer.mozilla.org/en-US/docs/Web/HTTP/Status>`_."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:150
msgid ""
"This error code includes the HTTP status. For example, "
"`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` means the server returned a \"Page "
"Not Found\" response."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:153
msgid "To solve this issue:"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:155
msgid ""
"Open `<https://www.odoo.com>`_ in a web browser to check if the website is "
"temporarily down for maintenance."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:0
msgid ""
"If `<https://www.odoo.com>`_ is down for maintenance, wait for it to resume."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:0
msgid ""
"If the website is operational, open a `support ticket "
"<https://www.odoo.com/help>`_ and make sure to include the 3-digit HTTPS "
"status code in the ticket."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:162
msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:164
msgid ""
"The IoT system successfully connected to `<https://www.odoo.com>`_, but the "
"server refused to provide the HTTPS certificate."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/https_certificate_iot.rst:167
msgid ""
"Check that the IoT system and database meet the :ref:`eligibility "
"requirements <iot/https_certificate_iot/iot-eligibility>` for an HTTPS "
"certificate."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:3
msgid "IoT box SSH connection"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:6
msgid ""
"SSH connections are only available for :doc:`IoT boxes <../iot_box>`, not "
"the :doc:`Windows virtual IoT <../windows_iot>`."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:10
msgid ""
"This feature should **only** be used with trusted parties, as it provides "
"administrative access to the IoT box, which can create security issues."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:12
msgid ""
"Managing an SSH connection is **not** covered under the standard Odoo "
"support scope. Visit the `Odoo Support <https://www.odoo.com/help>`_ page "
"for additional information about what is covered."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:16
msgid ""
"To provide an :abbr:`SSH (secure shell protocol)` connection to an IoT box, "
"you must generate a password:"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:19
msgid ""
"Access the IoT box's homepage by opening the IoT app and clicking the IP "
"address displayed on the IoT box's card."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:21
msgid ""
"Click the :icon:`fa-cogs` (:guilabel:`cogs`) button at the top-right, then "
":guilabel:`Remote Debug`."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:23
msgid ""
"In the :guilabel:`Remote Debugging` popup that opens, click "
":guilabel:`Generate` and save the password securely. Once you close the "
"popup, the password will no longer be available."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:0
msgid "The Remote Debugging password generation window."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:29
msgid ""
"Enter the :guilabel:`Authentication Token` provided by the user attempting "
"to connect to the IoT box."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:31
msgid "Click :guilabel:`Enable Remote Debugging`."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:34
msgid ":doc:`../iot_box`"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/ssh_connect.rst:35
msgid ":doc:`../connect`"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:3
msgid "IoT system updates"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:5
msgid ""
"Due to the complexity of IoT systems, the term *updating* can refer to "
"several processes, including:"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:7
msgid ""
":ref:`Updating the IoT system's image and/or core code "
"<iot/updating_iot/image-code>`;"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:8
msgid ""
":ref:`Updating the handlers <iot_updating_iot/handlers>`, which include the "
"interfaces and drivers."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:13
msgid "Image and core code update"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:19
msgid ""
"To check if the IoT box is up-to-date (and update it if needed), "
":ref:`access the IoT box's homepage <iot/iot-box/homepage>`, click the "
":icon:`fa-cogs` (:guilabel:`cogs`) button at the top-right, then "
":guilabel:`Update` in the :guilabel:`Version` section."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:24
msgid ""
":ref:`Enable the developer mode <developer-mode>` to view the current "
"versions of the IoT box's image and core code."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:27
msgid "**Image update**"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:29
msgid ""
"To update the IoT box's image, flash its SD card. Flashing can be performed "
"using `balenaEtcher <https://etcher.balena.io>`_, a free and open-source "
"tool for writing disk images to SD cards."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:34
msgid ""
"Updating the IoT system's image is often required after upgrading the Odoo "
"database to a newer version."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:36
msgid ""
"A computer with a micro SD card reader/adapter is required to flash the "
"micro SD card."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:37
msgid ""
"An alternative software for flashing the micro SD card is `Raspberry Pi "
"Imager <https://www.raspberrypi.com/software/>`_."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:40
msgid "`Download balenaEtcher. <https://etcher.balena.io/#download-etcher>`_"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:41
msgid "Insert the IoT box's micro SD card into the computer or adapter."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:42
msgid ""
"Open balenaEtcher, click :guilabel:`Flash from URL`, and enter the following"
" URL: `http://nightly.odoo.com/master/iotbox/iotbox-latest.zip`."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:44
msgid "Click :guilabel:`Select target` and select the SD card."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:45
msgid "Click :guilabel:`Flash` and wait for the process to finish."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:0
msgid "Flashing the SD card with balenaEtcher"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:50
msgid "**Core code update**"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:52
msgid ""
"To update the IoT box's core code, click :guilabel:`Update` under "
":guilabel:`IoT Box Update` in the :guilabel:`Update` popup."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:56
msgid ""
"This process may take over 30 minutes. **Do not turn off or unplug the IoT "
"box** during this time, as doing so could leave the device in an "
"inconsistent state, requiring the IoT box to be reflashed with a new image."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:62
msgid ""
"To update the Windows virtual IoT's image and code, :ref:`uninstall the "
"program <iot/windows_iot/uninstall>` and :ref:`reinstall <iot/windows-"
"iot/installation>` the latest package."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:69
msgid "Handler (driver) update"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:71
msgid ""
"To update the IoT system's handlers (i.e., drivers and interfaces) and "
"synchronize them with the configured server handler's code, for example, to "
"resolve issues where :doc:`devices <../devices>` are not functioning "
"properly with the IoT system, proceed as follows:"
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:75
msgid ""
"Access the :ref:`IoT box's <iot/iot-box/homepage>` or :ref:`Windows virtual "
"IoT's <iot/windows-iot/homepage>` homepage and click the :icon:`fa-cogs` "
"(:guilabel:`cogs`) button at the top-right."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:78
msgid "Click :guilabel:`Update` in the :guilabel:`Version` section."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:79
msgid ""
"In the :guilabel:`Update` popup that opens, click :guilabel:`Force Drivers "
"Update`."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:82
msgid ""
"If you have an :doc:`on-premise </administration/on_premise>` or "
":doc:`Odoo.sh </administration/odoo_sh/overview/introduction>` database, the"
" configured server must be up-to-date to ensure the handlers' code includes "
"the latest fixes and patches."
msgstr ""

#: ../../content/applications/general/iot/iot_advanced/updating_iot.rst:87
msgid ""
"A handler update is also performed automatically every time the IoT system "
"is restarted unless the :guilabel:`Automatic drivers update` option is "
"disabled in the :guilabel:`Technical information` tab in the :ref:`IoT "
"system's form <iot/connect/IoT-form>` in Odoo."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:5
msgid "To start using an IoT box:"
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:7
msgid ""
"Make sure you have a :ref:`valid IoT box subscription <iot/iot/iot-"
"subscription>` in addition to your Odoo subscription."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:9
msgid "Connect your :doc:`devices <devices>` to the IoT box."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:10
msgid ":ref:`Connect the IoT box to the network <iot/iot_box/network>`."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:11
msgid ":doc:`Connect the IoT box to your Odoo database <connect>`."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:14
msgid ""
"Devices can also be connected after the IoT box is added to the network "
"and/or connected to the database; however, a reboot of the IoT box might be "
"required."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:20
msgid "Network connection"
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:22
msgid ""
"The IoT box can be connected to the network via :ref:`Ethernet "
"<iot/iot_box/network-ethernet>` or :ref:`Wi-Fi <iot/iot_box/network-wifi>`."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:26
msgid ""
"**All** devices must be connected to the **same network**: the IoT box, the "
"device(s) connected to the IoT box, and the computer connected to Odoo."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:32
msgid "Ethernet"
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:34
msgid ""
"Plug the Ethernet cable into the IoT box's Ethernet port and an available "
"port on your router, then connect the IoT box to a power source."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:40
msgid "Wi-Fi"
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:42
msgid ""
"Make sure no Ethernet cable is connected to the IoT box and follow these "
"steps:"
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:44
msgid ""
"Connect the IoT box to a power source and wait a few minutes for it to power"
" on."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:45
msgid ""
"Access your computer's Wi-Fi settings and select the IoT box's network. The "
"network name is in the format `IoTBox-xxxxxxxxxxxx` (where `xxxxxxxxxxxx` is"
" a unique identifier)."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:47
msgid ""
"Connect to the IoT box's Wi-Fi network and sign into it; your browser should"
" automatically open and redirect to the :ref:`IoT box's homepage <iot/iot-"
"box/homepage>`."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:51
msgid ""
"Depending on your operating system, the browser might not open and redirect "
"to the IoT box's homepage. In this case, open your browser manually and "
"navigate to `http://10.11.12.1`."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:54
msgid ""
"On the IoT box's homepage, click :guilabel:`Configure` next to the "
":guilabel:`Internet Status` section."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:56
msgid ""
"Wait a few minutes for the available networks to be scanned, select the "
"network, enter the Wi-Fi's password, and click :guilabel:`Connect`."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:60
msgid ""
"Once connected to the Wi-Fi network, the IoT box stops emitting its Wi-Fi "
"signal, and the computer should automatically reconnect to its original "
"network. If it does not, reconnect to it manually."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:67
msgid "IoT box homepage"
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:69
msgid ""
"To access the IoT box's homepage, open a web browser **on the same network "
"as the IoT box** and navigate to the IoT box's IP address."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst-1
msgid "IoT box's homepage"
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:76
msgid "The IoT box's IP address can be retrieved by:"
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:78
msgid ""
"connecting the IoT box to an external monitor: the IP address is displayed "
"on the screen."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:0
msgid "POS display with IoT box's IP address"
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:84
msgid ""
"connecting the IoT box to a printer: the IP address is automatically "
"printed."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:85
msgid ""
"accessing the administrator interface of the router to which the IoT box is "
"connected or using third-party software to scan the network."
msgstr ""

#: ../../content/applications/general/iot/iot_box.rst:88
msgid ""
"Once the IoT box is :doc:`connected to the Odoo database <connect>`, its "
"homepage can be accessed from Odoo by opening the IoT app and clicking the "
"URL displayed on the IoT box's card."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:5
msgid "To start using the Windows virtual IoT:"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:7
msgid ""
"Make sure all :ref:`prerequisites <iot/windows-iot/prerequisites>` are met."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:8
msgid ""
":ref:`Install the Windows virtual IoT <iot/windows-iot/installation>` on a "
"Windows computer."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:9
msgid ":ref:`Configure the Windows Firewall <iot/windows-iot/firewall>`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:10
msgid "Connect your :doc:`devices <devices>` to the Windows virtual IoT."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:11
msgid ""
":doc:`Connect the Windows virtual IoT to your Odoo database <connect>`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:18
msgid ""
"The following prerequisites must be met before setting up and using the "
"Windows virtual IoT:"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:20
msgid "A valid :ref:`IoT box subscription <iot/iot/iot-subscription>`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:21
msgid ""
"An updated and recent version of Windows (i.e., Windows 10 or Windows 11) "
"installed on a Windows computer (laptop, desktop, or server)."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:33
msgid "Installation"
msgstr "Instalacja"

#: ../../content/applications/general/iot/windows_iot.rst:35
msgid "To install the Windows virtual IoT on a Windows computer:"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:37
msgid ""
"Access `Odoo's download page <https://odoo.com/download>`_ and download the "
"Odoo installation package for Windows **matching your database's version**."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:39
msgid ""
"Open the downloaded :file:`.exe` file, allow the app to make changes to your"
" device, select a language, and click :guilabel:`OK`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:41
msgid ""
"Click :guilabel:`Next`, then :guilabel:`I Agree` to accept the terms and "
"conditions and continue."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:42
msgid ""
"Select :guilabel:`Odoo IoT` from the :guilabel:`Select the type of install` "
"dropdown list. The following components should be selected: Odoo Server, "
"Odoo IoT, Nginx WebServer, and Ghostscript interpreter."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:45
msgid ""
"Verify you have the required space on your computer and click "
":guilabel:`Next`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:46
msgid ""
"In the :guilabel:`Destination folder`, enter C:\\\\odoo and click "
":guilabel:`Install`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:49
msgid ""
"Do not install Odoo's Windows virtual IoT in any Windows user directory, as "
"this can cause issues with :ref:`iot/https_certificate_iot/generation`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:52
msgid "Once the installation is complete, click :guilabel:`Next`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:53
msgid ""
"Set up GPL Ghostscript: Click :guilabel:`Next`, agree to the terms and "
"conditions, click :guilabel:`Install`, then :guilabel:`Finish`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:55
msgid ""
"Click :guilabel:`Next`, :guilabel:`Next`, and :guilabel:`Finish` to complete"
" the setup. The :ref:`IoT system's homepage <iot/windows-iot/homepage>` "
"automatically opens in a web browser with the URL `http://localhost:8069`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:60
msgid ""
"If the web browser does not show anything, :ref:`restart "
"<iot/windows_iot/restart>` the Windows virtual IoT service."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:63
msgid ""
"Check that you can access the :ref:`IoT system's homepage <iot/windows-"
"iot/homepage>` in a web browser:"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:66
msgid "on the Windows virtual IoT computer, and"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:67
msgid ""
"on another device **on the same network as the IoT system** by navigating to"
" the URL `http://xxx:8069` (where `xxx` is the IoT system's IP address)."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:69
msgid ""
"on another device **on the same network as the IoT system** by navigating to"
" the URL `https://xxx` (where `xxx` is the IoT system's IP address) to test "
"for :doc:`HTTPS <iot_advanced/https_certificate_iot>` connection."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:74
msgid ""
"If you cannot access the :ref:`IoT system's homepage <iot/windows-"
"iot/homepage>` from another device, create a :ref:`Windows Firewall "
"<iot/windows-iot/firewall>` rule to allow communication through port `8069`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:81
msgid "Windows Firewall configuration"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:83
msgid ""
"Firewalls help keep devices secure but can sometimes block legitimate "
"connections. If the Windows virtual IoT isn't accessible on the :abbr:`LAN "
"(Local Area Network)`, for example from another device, it could be due to a"
" firewall blocking the connection. To prevent this issue, configure "
"exceptions for network discovery in the :abbr:`OS (Operating System)` or "
"firewall settings."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:89
msgid ""
"If third-party firewall software is installed on the Windows computer, refer"
" to the software's documentation to configure firewall exceptions."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:92
msgid ""
"To create a rule on Windows Defender and allow communication through port "
"`8069`, follow these steps:"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:95
msgid ""
"Search the Windows start menu for `firewall` and select the "
":guilabel:`Windows Defender Firewall with Advanced Security` app."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:97
msgid "In the left part of the window, select :guilabel:`Inbound Rules`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:98
msgid ""
"In the right part of the window, under :guilabel:`Actions`, click "
":guilabel:`New Rule`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:99
msgid ""
"In the :guilabel:`New Inbound Rule Wizard` that opens, select the "
":guilabel:`Port` type of rule and click :guilabel:`Next`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:101
msgid ""
"On the :guilabel:`Protocols and Ports` page, make sure :guilabel:`TCP` and "
":guilabel:`Specified local ports` are selected, enter the following in the "
"field: `8069, 80, 443`, and click :guilabel:`Next`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:106
msgid ""
"Other ports may be necessary depending on your IoT devices. For example, for"
" the "
":doc:`/applications/sales/point_of_sale/payment_methods/terminals/worldline`"
" payment terminal, add the `9050` port."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:110
msgid ""
"On the :guilabel:`Action` page, select :guilabel:`Allow the connection` and "
"click :guilabel:`Next`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:112
msgid ""
"On the :guilabel:`Profile` page, disable any connection type(s) that don't "
"apply to your Windows computer and click :guilabel:`Next`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:114
msgid ""
"On the :guilabel:`Name` page, provide a :guilabel:`Name` (e.g., `Odoo`) and,"
" optionally, a brief :guilabel:`Description`, then click :guilabel:`Finish`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:118
msgid ""
"`Windows Firewall rules documentation <https://learn.microsoft.com/en-"
"us/windows/security/operating-system-security/network-security/windows-"
"firewall/rules>`_"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:124
msgid "Windows virtual IoT homepage"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:126
msgid ""
"To access the Windows virtual IoT's homepage, navigate to the URL "
"`http://localhost:8069` on the Windows virtual IoT computer or open a web "
"browser from another computer **on the same network as the IoT system** and "
"navigate to the URL `http://xxx:8069` (where `xxx` is the IoT system's IP "
"address)."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:131
msgid ""
"Once the Windows virtual IoT is :doc:`connected to the Odoo database "
"<connect>`, its homepage can be accessed from Odoo by opening the IoT app "
"and clicking the URL displayed on the IoT system's card."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst-1
msgid "Windows virtual IoT's homepage"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:140
msgid ""
"Make sure the :ref:`Windows Firewall is configured <iot/windows-"
"iot/firewall>` to allow access."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:143
msgid "Device connection"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:145
msgid ""
"Most :doc:`devices <devices>` automatically connect to the Windows computer "
"used for the Windows Virtual IoT through `Windows Plug and Play (PnP) "
"<https://learn.microsoft.com/en-us/windows-"
"hardware/drivers/kernel/introduction-to-plug-and-play>`_. However, if "
"Windows does not recognize the device automatically upon connection, the "
"administrator may need to manually install the appropriate drivers."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:152
msgid ""
"After connecting the devices to the computer, refresh the :ref:`IoT system's"
" homepage <iot/windows-iot/homepage>` to verify that the device is listed. "
"If the device does not appear, :ref:`reload the handlers "
"<iot_updating_iot/handlers>` from the :ref:`IoT system's homepage "
"<iot/windows-iot/homepage>`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:160
msgid "Windows virtual IoT restart"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:162
msgid ""
"To manually restart the Windows IoT server, search the Windows start menu "
"for `services` and select the :guilabel:`Services` app. Scroll down to the "
":guilabel:`odoo-server-xxx` service (where `xxx` is the odoo version), "
"right-click it, and select :guilabel:`Start` or :guilabel:`Restart`."
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:169
msgid "Windows virtual IoT uninstall"
msgstr ""

#: ../../content/applications/general/iot/windows_iot.rst:171
msgid ""
"To uninstall the Windows virtual IoT, `uninstall "
"<https://support.microsoft.com/en-us/windows/uninstall-or-remove-apps-and-"
"programs-in-"
"windows-4b55f974-2cc6-2d2b-d092-5905080eaf98#ID0EBD=Windows_11>`_ the Odoo "
"program on your Windows computer. Confirm the uninstallation and complete "
"the steps in the :guilabel:`Odoo Uninstall` dialog."
msgstr ""

#: ../../content/applications/general/multi_company.rst:3
msgid "Multi-company"
msgstr ""
"Wielofirmowość\n"
" \n"
" "

#: ../../content/applications/general/multi_company.rst:7
msgid ""
"In Odoo, multiple companies can exist within a single database. This allows "
"for some data to be shared among companies, while still maintaining some "
"level of separation between entities."
msgstr ""

#: ../../content/applications/general/multi_company.rst:10
msgid ""
"Before deciding to use the multi-company feature, there are several factors "
"to consider."
msgstr ""

#: ../../content/applications/general/multi_company.rst:13
msgid ""
"Multi-company is **only** available in *One App Free* databases, or with "
"`Custom <https://www.odoo.com/pricing-plan>`_ plans."
msgstr ""

#: ../../content/applications/general/multi_company.rst:17
msgid "Accessing multiple companies"
msgstr ""

#: ../../content/applications/general/multi_company.rst:19
msgid ""
"The list of :ref:`companies an employee has access to <general/employee-"
"access>` in a |mcd| can be found at the top-right of the main Odoo menu bar,"
" where the active company is listed. Click on the company name to reveal a "
"list of all allowed companies. To switch to a different company, click on "
"the company name in the drop-down menu. To enable multiple companies at "
"once, tick the checkbox next to each desired company name."
msgstr ""

#: ../../content/applications/general/multi_company.rst:29
msgid ""
"An example of the list of companies a user has access to when logged into a "
"database."
msgstr ""

#: ../../content/applications/general/multi_company.rst:29
msgid ""
"An example of a user with access to multiple companies. The current company "
"is My Company (San Francisco), while My Company (Chicago) is also active."
msgstr ""

#: ../../content/applications/general/multi_company.rst:33
msgid "The database may refresh after each checkbox is ticked."
msgstr ""

#: ../../content/applications/general/multi_company.rst:38
msgid "Multiple active companies"
msgstr ""

#: ../../content/applications/general/multi_company.rst:40
msgid ""
"If more than one company is active at a time, one company is highlighted in "
"purple, and is listed on the menu bar. This is the considered the *current* "
"company."
msgstr ""

#: ../../content/applications/general/multi_company.rst:43
msgid ""
"When creating a new record, the current company is added to the record in "
"the *Company* field, except under the following circumstances:"
msgstr ""

#: ../../content/applications/general/multi_company.rst:46
msgid ""
"The *Company* field for a new product, or a new contact, is left blank."
msgstr ""

#: ../../content/applications/general/multi_company.rst:47
msgid ""
"If there is a related document already in the system, the *Company* field on"
" the new record defaults to the same company."
msgstr ""

#: ../../content/applications/general/multi_company.rst:51
msgid ""
"Mitchell Admin has multiple companies enabled, but the current company is "
"`My Company (Chicago)`. When he creates a new product record, the "
":guilabel:`Company` field is left blank by default."
msgstr ""

#: ../../content/applications/general/multi_company.rst:54
msgid ""
"When a new sales team is created, the :guilabel:`Company` field "
"automatically defaults to `My Company (Chicago)`."
msgstr ""

#: ../../content/applications/general/multi_company.rst:60
msgid "Share data"
msgstr ""

#: ../../content/applications/general/multi_company.rst:62
msgid ""
"In a |mcd|, certain records are able to be utilized by all of the companies "
"(or several, based on permissions)."
msgstr ""

#: ../../content/applications/general/multi_company.rst:66
msgid "Products"
msgstr "Produkty"

#: ../../content/applications/general/multi_company.rst:68
msgid ""
"In an |mcd|, new products are created with the :ref:`Company field "
"<general/active-companies>` blank, by default. If the *Company* field "
"remains blank, the product is shared across all companies."
msgstr ""

#: ../../content/applications/general/multi_company.rst:72
msgid "Contacts"
msgstr "Kontakty"

#: ../../content/applications/general/multi_company.rst:74
msgid ""
"Similar to products, contact records are shared across companies, by "
"default. To limit access to a single company, click the :ref:`Company field "
"<general/active-companies>` on a contact form, and select a company to "
"assign the contact to."
msgstr ""

#: ../../content/applications/general/multi_company.rst:81
msgid ""
"The :ref:`Inter-Company Transactions <general/inter-company>` feature allows"
" for one company in the database to sell or purchase goods and services from"
" another company within the same database. Counterpart documents for orders "
"and invoices can be automatically generated and synchronized, depending on "
"the configuration settings."
msgstr ""

#: ../../content/applications/general/multi_company.rst:87
msgid ""
"To ensure inter-company transactions are handled appropriately, certain "
"configurations, such as fiscal positions and localizations, need to be "
"accurately assigned. See :ref:`Inter-Company Transactions <general/inter-"
"company>` for additional information."
msgstr ""

#: ../../content/applications/general/multi_company.rst:92
msgid "Use cases"
msgstr "Przykłady użycia"

#: ../../content/applications/general/multi_company.rst:95
msgid "Multinational companies"
msgstr ""

#: ../../content/applications/general/multi_company.rst:97
msgid ""
"A multinational retail chain, which operates in the United States and "
"Canada, needs to manage transactions in both USD and CAD currencies."
msgstr ""

#: ../../content/applications/general/multi_company.rst:100
msgid ""
"Additionally, because both countries have different tax laws and "
"regulations, it is in the best interest of the customer to utilize the "
"multi-company feature."
msgstr ""

#: ../../content/applications/general/multi_company.rst:103
msgid ""
"This allows for inter-company transactions they need to manage inventory "
"moves across international borders, while making it simple to sell to "
"customers in both countries in their own currency."
msgstr ""

#: ../../content/applications/general/multi_company.rst:107
msgid "Separate processes"
msgstr ""

#: ../../content/applications/general/multi_company.rst:109
msgid ""
"A small furniture company is developing a new line of products that require "
"a separate procurement, inventory, and manufacturing process. The new "
"products are drastically different from the existing catalog. The company is"
" considering utilizing the multi-company feature to treat this new line as a"
" different entity."
msgstr ""

#: ../../content/applications/general/multi_company.rst:114
msgid ""
"To keep their database from becoming overly complex, the furniture company "
"does not need to add an entirely new company. Instead, they can take "
"advantage of existing features, such as :doc:`analytic accounting "
"<../finance/accounting/reporting/analytic_accounting>`, and multiple "
"warehouses, to manage the new product line, without having to overly "
"complicate transactions."
msgstr ""

#: ../../content/applications/general/multi_company.rst:120
msgid "Limitations"
msgstr ""

#: ../../content/applications/general/multi_company.rst:122
msgid ""
"In some instances, a |mcd| may *not* be the best option, due to potential "
"limitations."
msgstr ""

#: ../../content/applications/general/multi_company.rst:125
#: ../../content/applications/general/users/access_rights.rst:3
msgid "Access rights"
msgstr "Prawa dostępu"

#: ../../content/applications/general/multi_company.rst:127
msgid ""
"A user's access rights are configured on a database level. If a user has "
"access to more than one company in a |mcd|, their access rights are the same"
" across every company."
msgstr ""

#: ../../content/applications/general/multi_company.rst:131
msgid "Shared records"
msgstr ""

#: ../../content/applications/general/multi_company.rst:133
msgid ""
"Individual records are either :ref:`shared <general/sharing-data>` between "
"all companies, or belong to a single company."
msgstr ""

#: ../../content/applications/general/multi_company.rst:137
msgid "PDF Reports"
msgstr ""

#: ../../content/applications/general/multi_company.rst:139
msgid ""
"Some customizations, specifically for PDF reports, apply to all companies. "
"It is not always possible to separate reports for individual companies."
msgstr ""

#: ../../content/applications/general/users.rst:5
#: ../../content/applications/general/users/access_rights.rst:32
msgid "Users"
msgstr "Użytkownicy"

#: ../../content/applications/general/users.rst:7
msgid ""
"Odoo defines a *user* as someone who has access to a database. An "
"administrator can add as many users as the company needs and, in order to "
"restrict the type of information each user can access, rules can be applied "
"to each user. 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:14
msgid ":ref:`access-rights/superuser`"
msgstr ""

#: ../../content/applications/general/users.rst:15
msgid ":ref:`access-rights/groups`"
msgstr ""

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

#: ../../content/applications/general/users.rst:22
msgid ""
"To add new users, navigate to :menuselection:`Settings app --> Users section"
" --> Manage Users`, and click on :guilabel:`New`."
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:29
msgid ""
"Fill in the form with all the required information. Under the :doc:`Access "
"Rights <users/access_rights>` tab, choose the group within each application "
"the user can have access to."
msgstr ""

#: ../../content/applications/general/users.rst:32
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 user's form emphasizing the access rights tab in Odoo."
msgstr ""

#: ../../content/applications/general/users.rst:38
msgid ""
"After filling out all the necessary fields on the page, manually "
":guilabel:`Save`. An invitation email is automatically sent to the user, "
"using the email in the :guilabel:`Email Address` field. The user must click "
"on the link included in the email to accept the invitation, and to create a "
"database login."
msgstr ""

#: ../../content/applications/general/users.rst-1
msgid ""
"View of a user's form with a notification that the invitation email has been"
" sent in Odoo."
msgstr ""

#: ../../content/applications/general/users.rst:48
msgid ""
"If the company is on a monthly subscription plan, the database automatically"
" updates to reflect the added users. If the company is on a yearly or multi-"
"year plan, an expiration banner appears in the database. An upsell quotation"
" can be created by clicking the banner to update the subscription. "
"Alternatively, `send a support ticket <https://www.odoo.com/help>`_ to "
"resolve the issue."
msgstr ""

#: ../../content/applications/general/users.rst:55
msgid "User type"
msgstr ""

#: ../../content/applications/general/users.rst:57
msgid ""
":guilabel:`User Type` can be selected from the :guilabel:`Access Rights` tab"
" of the user form, accessible via :menuselection:`Settings app --> Users "
"section --> Manage Users`."
msgstr ""

#: ../../content/applications/general/users.rst:60
msgid ""
"There are three types of users: :guilabel:`Internal User`, "
":guilabel:`Portal`, and :guilabel:`Public`."
msgstr ""

#: ../../content/applications/general/users.rst-1
msgid ""
"View of a user's form in developer mode emphasizing the user type field in "
"Odoo."
msgstr ""

#: ../../content/applications/general/users.rst:68
msgid ""
"Users are considered internal database users. Portal users are external "
"users, who only have access to the database portal to view records. See the "
"documentation on :doc:`users/portal`."
msgstr ""

#: ../../content/applications/general/users.rst:71
msgid "Public users are those visiting websites, via the website's frontend."
msgstr ""

#: ../../content/applications/general/users.rst:73
msgid ""
"The :guilabel:`Portal` and :guilabel:`Public` user options do **not** allow "
"the administrator to choose access rights. These users have specific access "
"rights pre-set (such as, record rules and restricted menus), and usually do "
"not belong to the usual Odoo groups."
msgstr ""

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

#: ../../content/applications/general/users.rst:82
msgid ""
"To deactivate (i.e. archive) a user, navigate to :menuselection:`Settings "
"app --> Users section --> Manage Users`. Then, tick the checkbox to the left"
" of the user(s) to be deactivated."
msgstr ""

#: ../../content/applications/general/users.rst:85
msgid ""
"After selecting the appropriate user to be archived, click the :guilabel:`⚙️"
" Actions` icon, and select :guilabel:`Archive` from the resulting drop-down "
"menu. Then, click :guilabel:`OK` from the :guilabel:`Confirmation` pop-up "
"window that appears."
msgstr ""

#: ../../content/applications/general/users.rst:90
msgid ""
"**Never** deactivate the main/administrator user (admin). Making changes to "
"admin users can have a detrimental impact on the database. This includes "
"*impotent admin*, which means that no user in the database can make changes "
"to the access rights. For this reason, Odoo recommends contacting an Odoo "
"Business Analyst, or our Support Team, before making changes."
msgstr ""

#: ../../content/applications/general/users.rst:96
msgid "Error: too many users"
msgstr ""

#: ../../content/applications/general/users.rst:98
msgid ""
"If there are more users in an Odoo database than provisioned in the Odoo "
"Enterprise subscription, the following message is displayed."
msgstr ""

#: ../../content/applications/general/users.rst-1
msgid "Too many users on a database error message."
msgstr ""

#: ../../content/applications/general/users.rst:105
msgid ""
"When the message appears, the database administrator has 30 days to act "
"before the database expires. The countdown is updated every day."
msgstr ""

#: ../../content/applications/general/users.rst:108
msgid "To resolve the issue, either:"
msgstr ""

#: ../../content/applications/general/users.rst:110
msgid ""
"Add more users to the subscription by clicking the :guilabel:`Upgrade your "
"subscription` link displayed in the message to validate the upsell "
"quotation, and pay for the extra users."
msgstr ""

#: ../../content/applications/general/users.rst:112
msgid ""
":ref:`Deactivate users <users/deactivate>`, and reject the upsell quotation."
msgstr ""

#: ../../content/applications/general/users.rst:115
msgid ""
"If the company is on a monthly subscription plan, the database automatically"
" updates to reflect the added users. If the company is on a yearly or multi-"
"year plan, an expiration banner appears in the database. An upsell quotation"
" can be created by clicking the banner to update the subscription. "
"Alternatively, users can `send a support ticket "
"<https://www.odoo.com/help>`_ to resolve the issue."
msgstr ""

#: ../../content/applications/general/users.rst:121
msgid ""
"Once the database has the correct number of users, the expiration message "
"disappears automatically after a few days, when the next verification "
"occurs."
msgstr ""

#: ../../content/applications/general/users.rst:127
msgid "Password management"
msgstr ""

#: ../../content/applications/general/users.rst:129
msgid ""
"Password management is an important part of granting users autonomous access"
" to the database at all times. Odoo offers a few different methods to reset "
"a user's password."
msgstr ""

#: ../../content/applications/general/users.rst:133
msgid ""
"Odoo has a setting to specify the length needed for a password. This setting"
" can be accessed by navigating to :menuselection:`Settings app --> "
"Permissions` section, and entering the desired password length in the "
":guilabel:`Minimum Password Length` field. By default the value is `8`."
msgstr ""

#: ../../content/applications/general/users.rst-1
msgid ""
"Minimum Password Length highlighted in the Permissions section of General "
"Settings."
msgstr ""

#: ../../content/applications/general/users.rst:144
msgid "Reset password"
msgstr ""

#: ../../content/applications/general/users.rst:146
msgid ""
"Sometimes, users might wish to reset their personal password for added "
"security, so they are the only ones with access to the password. Odoo offers"
" two different reset options: one initiated by the user to reset the "
"password, and another where the administrator triggers a reset."
msgstr ""

#: ../../content/applications/general/users.rst:153
msgid "Enable password reset from login page"
msgstr ""

#: ../../content/applications/general/users.rst:155
msgid ""
"It is possible to enable/disable password resets directly from the login "
"page. This action is completed by the individual user, and this setting is "
"enabled by default."
msgstr ""

#: ../../content/applications/general/users.rst:158
msgid ""
"To change this setting, go to :menuselection:`Settings app --> Permissions` "
"section, activate :guilabel:`Password Reset`, and then click "
":guilabel:`Save`."
msgstr ""

#: ../../content/applications/general/users.rst-1
msgid "Enabling Password Reset in Odoo Settings"
msgstr ""

#: ../../content/applications/general/users.rst:165
msgid ""
"On the login page, click :guilabel:`Reset Password` to initiate the password"
" reset process, and have a reset-token sent to the email on file."
msgstr ""

#: ../../content/applications/general/users.rst-1
msgid "Login screen on Odoo.com with the password reset option highlighted."
msgstr ""

#: ../../content/applications/general/users.rst:175
msgid "Send reset instructions"
msgstr ""

#: ../../content/applications/general/users.rst:177
msgid ""
"Go to :menuselection:`Settings app --> Users & Companies --> Users`, select "
"the user from the list, and click on :guilabel:`Send Password Reset "
"Instructions` on the user form. An email is automatically sent to them with "
"password reset instructions."
msgstr ""

#: ../../content/applications/general/users.rst:182
msgid ""
"The :guilabel:`Send Password Reset Instructions` button **only** appears if "
"the Odoo invitation email has already been confirmed by the user. Otherwise,"
" a :guilabel:`Re-send Invitation Email` button appears."
msgstr ""

#: ../../content/applications/general/users.rst:186
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:196
msgid "Change user password"
msgstr ""

#: ../../content/applications/general/users.rst:198
msgid ""
"Go to :menuselection:`Settings app --> Users & Companies --> Users`, and "
"select a user to access its form. Click on the :guilabel:`⚙️ Actions` icon, "
"and select :guilabel:`Change Password` from, the resulting drop-down menu. "
"Enter a new password in the :guilabel:`New Password` column of the "
":guilabel:`Change Password` pop-up window that appears, and confirm the "
"change by clicking :guilabel:`Change Password`."
msgstr ""

#: ../../content/applications/general/users.rst-1
msgid "Change a user's password on Odoo."
msgstr ""

#: ../../content/applications/general/users.rst:209
msgid ""
"This operation only modifies the password of the users locally, and does "
"**not** affect their odoo.com account."
msgstr ""

#: ../../content/applications/general/users.rst:212
msgid ""
"If the odoo.com password needs to be changed, use the :ref:`send the "
"password reset instructions <users/reset-password-email>`. Odoo.com "
"passwords grant access to the *My Databases* page, and other portal "
"features."
msgstr ""

#: ../../content/applications/general/users.rst:216
msgid ""
"After clicking :guilabel:`Change Password`, the page is redirected to an "
"Odoo login page where the database can be re-accessed using the new "
"password."
msgstr ""

#: ../../content/applications/general/users.rst:222
msgid "Multi Companies"
msgstr "Wielofirmowość"

#: ../../content/applications/general/users.rst:224
msgid ""
"The :guilabel:`Multi Companies` field on a user form allows an administrator"
" to provide access to multiple companies for users. To configure a multi-"
"company environment for a user, navigate to the desired user by going to: "
":menuselection:`Settings app --> Users section --> Manage users`. Then, "
"select the user to open their user form, and configure with multi-company "
"access."
msgstr ""

#: ../../content/applications/general/users.rst:229
msgid ""
"Under :guilabel:`Multi Companies` in the :guilabel:`Access Rights` tab, set "
"the fields labeled :guilabel:`Allowed Companies` and :guilabel:`Default "
"Company`."
msgstr ""

#: ../../content/applications/general/users.rst:232
msgid ""
"The :guilabel:`Allowed Companies` field can contain multiple companies. "
"These are the companies the user can access and edit, according to the set "
"access rights. The :guilabel:`Default Company` is the company the user "
"defaults to, upon logging in each time. This field can contain only **one** "
"company."
msgstr ""

#: ../../content/applications/general/users.rst:238
msgid ""
"If multi-company access is not configured correctly, it could lead to "
"inconsistent multi-company behaviors. Because of this, only experienced Odoo"
" users should make access rights changes to users for databases with a "
"multi-company configuration. For technical explanations, refer to the "
"developer documentation on :doc:`../../../developer/howtos/company`."
msgstr ""

#: ../../content/applications/general/users.rst-1
msgid "View of a user's form emphasizing the multi companies field in Odoo."
msgstr ""

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

#: ../../content/applications/general/users/2fa.rst:3
msgid "Two-factor authentication"
msgstr "Uwierzytelnianie dwuskładnikowe"

#: ../../content/applications/general/users/2fa.rst:8
msgid ""
"*Two-factor authentication (2FA)* is a way to improve security, and prevent "
"unauthorized persons from accessing user accounts."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:11
msgid ""
"Practically, |2fa| means storing a secret inside an *authenticator*, usually"
" on a mobile phone, and exchanging a code from the authenticator when trying"
" to log in."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:14
msgid ""
"This means an unauthorized user would need to guess the account password "
"*and* have access to the authenticator, which is a more difficult "
"proposition."
msgstr ""

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

#: ../../content/applications/general/users/2fa.rst:21
msgid ""
"These lists are just examples. They are **not** endorsements of any specific"
" software."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:23
msgid ""
"Phone-based authenticators are the easiest and most commonly used. Examples "
"include:"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:25
msgid "`Authy <https://authy.com/>`_"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:26
msgid "`FreeOTP <https://freeotp.github.io/>`_"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:27
msgid ""
"`Google Authenticator "
"<https://support.google.com/accounts/answer/1066447?hl=en>`_"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:28
msgid "`LastPass Authenticator <https://lastpass.com/auth/>`_"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:29
msgid ""
"`Microsoft Authenticator <https://www.microsoft.com/en-"
"gb/account/authenticator?cmp=h66ftb_42hbak>`_"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:32
msgid "Password managers are another option. Common examples include:"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:34
msgid "`1Password <https://support.1password.com/one-time-passwords/>`_"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:35
msgid "`Bitwarden <https://bitwarden.com/help/article/authenticator-keys/>`_,"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:38
msgid ""
"The remainder of this document uses Google Authenticator as an example, as "
"it is one of the most commonly used. This is **not** an endorsement of the "
"product."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:42
msgid "Two-factor authentication setup"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:44
msgid ""
"After selecting an authenticator, log in to Odoo, then click the profile "
"avatar in the upper-right corner, and select :guilabel:`My Profile` from the"
" resulting drop-down menu."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:47
msgid ""
"Click the :guilabel:`Account Security` tab, then slide the :guilabel:`Two-"
"Factor Authentication` toggle to *active*."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:53
msgid ""
"This generates a :guilabel:`Security Control` pop-up window that requires "
"password confirmation to continue. Enter the appropriate password, then "
"click :guilabel:`Confirm Password`. Next, a :guilabel:`Two-Factor "
"Authentication Activation` pop-up window appears, with a |QR|."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:61
msgid ""
"Using the desired authenticator application, scan the |QR| when prompted."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:64
msgid ""
"If scanning the screen is not possible (e.g. the setup is being completed on"
" the *same* device as the authenticator application), clicking the provided "
":guilabel:`Cannot scan it?` link, or copying the secret to manually set up "
"the authenticator, is an alternative."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:74
msgid "Afterwards, the authenticator should display a *verification code*."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:79
msgid ""
"Enter the code into the :guilabel:`Verification Code` field, then click "
":guilabel:`Activate`."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:85
msgid "Logging in"
msgstr ""

#: ../../content/applications/general/users/2fa.rst:87
msgid "To confirm |2fa| setup is complete, log out of Odoo."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:89
msgid ""
"On the login page, input the username and password, then click "
":guilabel:`Log in`. On the :guilabel:`Two-factor Authentication` page, input"
" the code provided by the chosen authenticator in the "
":guilabel:`Authentication Code` field, then click :guilabel:`Log in`."
msgstr ""

#: ../../content/applications/general/users/2fa.rst-1
msgid "The login page with 2fa enabled."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:98
msgid ""
"If a user loses access to their authenticator, an administrator **must** "
"deactivate |2fa| on the account before the user can log in."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:102
msgid "Enforce two-factor authentication"
msgstr "Wymuszanie uwierzytelniania dwuskładnikowego"

#: ../../content/applications/general/users/2fa.rst:104
msgid ""
"To enforce the use of |2fa| for all users, first navigate to "
":menuselection:`Main Odoo Dashboard --> Apps`. Remove the :guilabel:`Apps` "
"filter from the :guilabel:`Search...` bar, then search for `2FA by mail`."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:108
msgid ""
"Click :guilabel:`Install` on the Kanban card for the :guilabel:`2FA by mail`"
" module."
msgstr ""

#: ../../content/applications/general/users/2fa.rst-1
msgid "The 2FA by mail module in the Apps directory."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:114
msgid ""
"After installation is complete, go to :guilabel:`Settings app: Permissions`."
" Tick the checkbox labeled, :guilabel:`Enforce two-factor authentication`. "
"Then, use the radio buttons to choose whether to apply this setting to "
":guilabel:`Employees only`, or :guilabel:`All users`."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:119
msgid ""
"Selecting :guilabel:`All users` applies the setting to portal users, in "
"addition to employees."
msgstr ""

#: ../../content/applications/general/users/2fa.rst-1
msgid "The enforce two factor setting in the Settings application."
msgstr ""

#: ../../content/applications/general/users/2fa.rst:125
msgid "Click :guilabel:`Save` to commit any unsaved changes."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:5
msgid ""
"*Access rights* are permissions that determine the content and applications "
"users can access and edit. In Odoo, these permissions can be set for "
"individual users or for groups of users. Limiting permissions to only those "
"who need them ensures that users do not modify or delete anything they "
"should not have access to."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:10
msgid "**Only** an *administrator* can change access rights."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:13
msgid ""
"Making changes to access rights can have a detrimental impact on the "
"database. This includes *impotent admin*, which means that no user in the "
"database can make changes to the access rights. For this reason, Odoo "
"recommends contacting an Odoo Business Analyst, or our Support Team, before "
"making changes."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:19
msgid ""
"A user **must** have the specific *Administration* access rights set on "
"their user profile, in order to make changes on another user's settings for "
"access rights."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:22
msgid ""
"To access this setting, navigate to :menuselection:`Settings app --> Manage "
"users --> select a user --> Access Rights tab --> Administration section -->"
" Administration field`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:25
msgid ""
"Once at the setting, an already existing administrator **must** change the "
"setting in the :guilabel:`Administration` field to :guilabel:`Access "
"Rights`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:28
msgid ""
"Once complete, click :guilabel:`Save` to save the changes, and implement the"
" user as an administrator."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:34
msgid ""
"The access rights for :ref:`individual users <users/add-individual>` are set"
" when the user is added to the database, but they can be adjusted at any "
"point in the user's profile."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:37
msgid ""
"To make changes to a user's rights, click on the desired user to edit their "
"profile."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst-1
msgid ""
"Users menu in the Users & Companies section of the Settings app of Odoo."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:43
msgid ""
"On the user's profile page, in the :guilabel:`Access Rights` tab, scroll "
"down to view the current permissions."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:46
msgid ""
"For each app, use the drop-down menu to select what level of permission this"
" user should have. The options vary for each section, yet the most common "
"are: :guilabel:`Blank/None`, :guilabel:`User: Own Documents`, "
":guilabel:`User: All Documents`, or :guilabel:`Administrator`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:50
msgid ""
"The :guilabel:`Administration` field in the :guilabel:`Access Rights` tab "
"has the following options: :guilabel:`Settings` or :guilabel:`Access "
"Rights`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst-1
msgid "The Sales apps drop-down menu to set the user's level of permissions."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:60
msgid "Create and modify groups"
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:62
msgid ""
"*Groups* are app-specific sets of permissions that are used to manage common"
" access rights for a large amount of users. Administrators can modify the "
"existing groups in Odoo, or create new ones to define rules for models "
"within an application."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:66
msgid ""
"To access groups, first activate Odoo's :ref:`developer mode <developer-"
"mode>`, then go to :menuselection:`Settings app --> Users & Companies --> "
"Groups`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst-1
msgid ""
"Groups menu in the Users & Companies section of the Settings app of Odoo."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:73
msgid ""
"To create a new group from the :guilabel:`Groups` page, click "
":guilabel:`Create`. Then, from the blank group form, select an "
":guilabel:`Application`, and complete the group form (detailed below)."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:76
msgid ""
"To modify existing groups, click on an existing group from the list "
"displayed on the :guilabel:`Groups` page, and edit the contents of the form."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:79
msgid ""
"Enter a :guilabel:`Name` for the group and tick the checkbox next to "
":guilabel:`Share Group`, if this group was created to set access rights for "
"sharing data with some users."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:83
msgid ""
"Always test the settings being changed to ensure they are being applied to "
"the correct users."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:85
msgid ""
"The group form contains multiple tabs for managing all elements of the "
"group. In each tab, click :guilabel:`Add a line` to add a new row for users "
"or rules, and click the :guilabel:`❌ (remove)` icon to remove a row."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst-1
msgid "Tabs in the Groups form to modify the settings of the group."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:93
msgid ""
":guilabel:`Users` tab: lists the current users in the group. Users listed in"
" black have administrative rights. Users without administrative access "
"appear in blue. Click :guilabel:`Add a line` to add users to this group."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:96
msgid ""
":guilabel:`Inherited` tab: inherited means that users added to this group "
"are automatically added to the groups listed on this tab. Click "
":guilabel:`Add a line` to add inherited groups."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:100
msgid ""
"For example, if the group *Sales/Administrator* lists the group "
"*Website/Restricted Editor* in its :guilabel:`Inherited` tab, then any users"
" added to the *Sales/Administrator* group automatically receive access to "
"the *Website/Restricted Editor* group, as well."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:104
msgid ""
":guilabel:`Menus` tab: defines which menus/models the group can have access "
"to. Click :guilabel:`Add a line` to add a specific menu."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:106
msgid ""
":guilabel:`Views` tab: lists which views in Odoo the group has access to. "
"Click :guilabel:`Add a line` to add a view to the group."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:108
msgid ""
":guilabel:`Access Rights` tab: lists the first level of rights (models) that"
" this group has access rights to. Click :guilabel:`Add a line` to link "
"access rights to this group. In this tab, the :guilabel:`Model` column "
"represents the common name of the menu/model, and the :guilabel:`Name` "
"column represents the technical name given to the model. For each model, "
"enable the following options as appropriate:"
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:114
msgid ":guilabel:`Read`: users can see the object's existing values."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:115
msgid ":guilabel:`Write`: users can edit the object's existing values."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:116
msgid ":guilabel:`Create`: users can create new values for the object."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:117
msgid ":guilabel:`Delete`: users can delete values for the object."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:120
msgid ""
"First try searching for the common name of the model in the drop-down menu "
"of the :guilabel:`Model` column. The :guilabel:`Model` technical name can be"
" found by expanding the model common name, which can be done by clicking the"
" :guilabel:`(external link)` icon."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:124
msgid ""
"The model technical name can also be accessed in :ref:`developer mode "
"<developer-mode>`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:126
msgid ""
"On a form, navigate to any field, and hover over the field name. A box of "
"backend information reveals itself with the specific Odoo :guilabel:`Model` "
"name in the backend. This is the technical name of the model that should be "
"added."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:0
msgid ""
"Technical information shown on a field of a model, with object highlighted."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:134
msgid ""
":guilabel:`Record Rules`: lists the second layer of editing and visibility "
"rights. :guilabel:`Record Rules` overwrite, or refine, the group's access "
"rights. Click :guilabel:`Add a line` to add a record rule to this group. For"
" each rule, choose values for the following options:"
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:138
msgid ":guilabel:`Apply for Read`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:139
msgid ":guilabel:`Apply for Write`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:140
msgid ":guilabel:`Apply for Create`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:141
msgid ":guilabel:`Apply for Delete`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:144
msgid ""
"Record rules are written using a *domain*, or conditions that filter data. A"
" domain expression is a list of such conditions. For example:"
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:147
msgid ""
"`[('mrp_production_ids', 'in', "
"user.partner_id.commercial_partner_id.production_ids.ids)]`"
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:149
msgid ""
"This record rule is to enable MRP consumption warnings for subcontractors."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:151
msgid ""
"Odoo has a library of preconfigured record rules for ease of use. Users "
"without knowledge of domains (and domain expressions) should consult an Odoo"
" Business Analyst, or the Odoo Support Team, before making changes."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:158
msgid "Superuser mode"
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:160
msgid ""
"*Superuser mode* allows the user to bypass record rules and access rights. "
"To activate *Superuser mode*, first, activate :ref:`developer mode "
"<developer-mode>`. Then, navigate to the *debug* menu, represented by a "
":guilabel:`🪲 (bug)` icon, located in the top banner."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:164
msgid ""
"Finally, towards the bottom of the menu, click :guilabel:`Become Superuser`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:167
msgid ""
"Only users with *Settings* access for the *Administration* section of the "
"*Access Rights* (in their user profile) are allowed to log in to *Superuser "
"mode*."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:171
msgid ""
"*Superuser mode* allows for circumvention of record rules and access rights,"
" and therefore, should be exercised with extreme caution."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:174
msgid ""
"Upon exiting *Superuser mode*, users may be locked out of the database, due "
"to changes that were made. This can cause *impotent admin*, or an "
"administrator without the ability to change access rights/settings."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:178
msgid ""
"In this case contact Odoo Support here: `new help ticket "
"<https://www.odoo.com/help>`_. The support team is able to restore access "
"using a support login."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:181
msgid ""
"To leave *Superuser mode*, log out of the account, by navigating to the "
"upper-right corner, and clicking on the :guilabel:`OdooBot` username. Then, "
"select the :guilabel:`Log out` option."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:185
msgid ""
"An alternative way to activate *Superuser mode* is to login as a superuser. "
"To do that, navigate to the login screen, and enter the appropriate "
":guilabel:`Email` and :guilabel:`Password`."
msgstr ""

#: ../../content/applications/general/users/access_rights.rst:188
msgid ""
"Instead of clicking :guilabel:`Login`, click :guilabel:`Log in as "
"superuser`."
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 "Uwierzytelnienie"

#: ../../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
#: ../../content/applications/general/users/facebook.rst:111
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/facebook.rst:3
msgid "Facebook sign-in authentication"
msgstr ""

#: ../../content/applications/general/users/facebook.rst:5
msgid ""
"The *Facebook* OAuth sign-in function allows Odoo users to sign in to their "
"database with their Facebook account."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:9
msgid ""
"Databases housed 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 setup for that user, the database can no "
"longer be duplicated, renamed, or otherwise managed from the Odoo.com "
"portal."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:15
msgid "Meta for Developers setup"
msgstr ""

#: ../../content/applications/general/users/facebook.rst:17
msgid ""
"Go to `Meta for Developers <https://developers.facebook.com/>`_ and log in. "
"Click :guilabel:`My Apps`. On the :guilabel:`Apps` page, click "
":guilabel:`Create App`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:20
msgid ""
"On the :guilabel:`Use cases` page, select :guilabel:`Authenticate and "
"request data from users with Facebook Login`, then click :guilabel:`Next`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:23
msgid ""
"In the :guilabel:`Add an app name` field, enter `Odoo Login OAuth`, or a "
"similar title."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:26
msgid ""
"The :guilabel:`App contact email` automatically defaults to the email "
"address associated with the Meta account. If this email address is not "
"regularly monitored, it may be wise to use another email address."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:30
msgid ""
"Click :guilabel:`Next`. Review the :guilabel:`Publishing requirements`, the "
":guilabel:`Meta Platform Terms`, and :guilabel:`Developer Policies`. Then, "
"click :guilabel:`Create app`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:34
msgid "Clicking :guilabel:`Create app` may require password re-entry."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:37
msgid "Customize app"
msgstr ""

#: ../../content/applications/general/users/facebook.rst:39
msgid ""
"After the new app is created, the :guilabel:`Dashboard` page appears, with a"
" list of steps to be completed before the app can be published. From here, "
"click :guilabel:`Customize adding a Facebook Login button`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst-1
msgid "The App Dashboard in the Meta for developers platform."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:47
msgid "On the :guilabel:`Customize` page, click :guilabel:`Settings`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:49
msgid ""
"In the :guilabel:`Valid OAuth Redirect URIs` field, enter `https://<odoo "
"base url>/auth_oauth/signin`, replacing `<odoo base url>` with the URL of "
"the applicable database."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:53
msgid ""
"If a database has the URL `https://example.odoo.com`, the URL "
"`https://example.odoo.com/auth_oauth/signin` would be entered in the "
":guilabel:`Valid OAuth Redirect URIs` field."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:57
msgid "Click :guilabel:`Save changes` when finished."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:60
msgid "Configure settings"
msgstr ""

#: ../../content/applications/general/users/facebook.rst:62
msgid ""
"At the far left of the page, click :menuselection:`App settings --> Basic`. "
"This page contains additional settings that are required before the app can "
"be submitted for approval."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:65
msgid ""
"In the :guilabel:`Privacy Policy URL` field, enter "
"`https://www.odoo.com/privacy`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:68
msgid ""
"`<https://www.odoo.com/privacy>`_ is the default privacy policy for "
"databases hosted on Odoo.com."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:70
msgid ""
"Click the :guilabel:`App Icon` field to open a file upload window. From "
"here, select and upload an app icon."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:73
msgid ""
"In the :guilabel:`User data deletion` field, enter "
"`https://www.odoo.com/documentation/17.0/administration/odoo_accounts.html`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:77
msgid ""
"This document provides instructions on how a user can delete their Odoo "
"account."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:79
msgid ""
"Lastly, click the :guilabel:`Category` field, and select :guilabel:`Business"
" and pages` from the drop-down menu."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:82
msgid "Click :guilabel:`Save changes`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst-1
msgid ""
"An exampled of the Basic Settings page in the Meta for developers platform."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:91
msgid "Capture app ID"
msgstr ""

#: ../../content/applications/general/users/facebook.rst:93
msgid ""
"After the app is created, and approved, select and copy the :guilabel:`App "
"ID`. Paste this information on a clipboard or notepad file, as it is needed "
"in a later step to complete the setup."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:97
msgid "Publish"
msgstr "Publikuj"

#: ../../content/applications/general/users/facebook.rst:99
msgid ""
"On the left side of the page, click :guilabel:`Publish`. Depending on the "
"status of the connected Facebook account, additional verification and "
"testing steps may be required, and are listed on this page."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:103
msgid "After reviewing the information, click :guilabel:`Publish`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:106
msgid ""
"Additional information regarding Meta App Development, including further "
"details on building, testing, and use cases, can be found in the `Meta for "
"developers documentation "
"<https://developers.facebook.com/docs/development>`_."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:113
msgid "First, activate :ref:`Developer mode <developer-mode/activation>`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:115
msgid ""
"Navigate to the :menuselection:`Settings app`, and scroll down to the "
":guilabel:`Integrations` section. There, tick the checkbox labeled, "
":guilabel:`OAuth Authentication`. Click :guilabel:`Save`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst-1
msgid "The enable OAuth setting in the Settings app."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:122
msgid "Then, sign in to the database once the login screen loads."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:124
msgid ""
"After successfully logging in, navigate to :menuselection:`Settings app --> "
"Users & Companies --> OAuth Providers`. Click :guilabel:`Facebook Graph`."
msgstr ""

#: ../../content/applications/general/users/facebook.rst:127
msgid ""
"In the :guilabel:`Client ID` field, enter the :ref:`App ID <users/app-id>` "
"from the previous section, then tick the :guilabel:`Allowed` checkbox."
msgstr ""

#: ../../content/applications/general/users/facebook.rst-1
msgid "The Facebook Graph record in Odoo."
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 "Uwierzytelnienia"

#: ../../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:0
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
#: ../../content/applications/general/users/language.rst:30
msgid "Change languages"
msgstr ""

#: ../../content/applications/general/users/language.rst:5
msgid ""
"You select the language of your database upon its creation. However, you can"
" :ref:`add <language/add>` and :ref:`install <language/install>` additional "
"languages to allow users to manage the database in another language or to "
":doc:`translate <../../websites/website/configuration/translate>` your "
"website."
msgstr ""

#: ../../content/applications/general/users/language.rst:13
msgid "Add languages"
msgstr "Dodaj języki"

#: ../../content/applications/general/users/language.rst:15
msgid "To download additional languages:"
msgstr ""

#: ../../content/applications/general/users/language.rst:17
msgid ""
"either click the profile icon in the upper-right corner, select "
":menuselection:`My profile`, and click the :icon:`fa-globe` "
"(:guilabel:`globe`) icon next to the :guilabel:`Language` field;"
msgstr ""

#: ../../content/applications/general/users/language.rst:19
msgid ""
"or go to the **Settings** app, and click :guilabel:`Add Languages` in the "
":guilabel:`Languages` section."
msgstr ""

#: ../../content/applications/general/users/language.rst:22
msgid ""
"You can then select the languages you want from the dropdown menu and click "
":guilabel:`Add`."
msgstr ""

#: ../../content/applications/general/users/language.rst:25
msgid ":doc:`Translations <../../websites/website/configuration/translate>`"
msgstr ""

#: ../../content/applications/general/users/language.rst:32
msgid ""
"To select their preferred language, users can click the profile icon in the "
"upper-right corner, go to :menuselection:`My profile`, and select a "
":guilabel:`Language` in the dropdown list."
msgstr ""

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

#: ../../content/applications/general/users/language.rst:38
msgid "To change the database language for a user:"
msgstr ""

#: ../../content/applications/general/users/language.rst:40
msgid ""
"Go to the :guilabel:`Settings` app and click :guilabel:`Manage Users` in the"
" :guilabel:`Users` section."
msgstr ""

#: ../../content/applications/general/users/language.rst:43
msgid "Click on the user whose language you want to change."
msgstr ""

#: ../../content/applications/general/users/language.rst:45
msgid ""
"Go to the :guilabel:`Preferences` tab and select a previously "
":ref:`installed language <language/add>` from the :guilabel:`Language` "
"dropdown menu."
msgstr ""

#: ../../content/applications/general/users/language.rst:49
msgid ""
"Emails and documents will be sent to the user in the selected language."
msgstr ""

#: ../../content/applications/general/users/ldap.rst:3
msgid "LDAP authentication"
msgstr ""

#: ../../content/applications/general/users/ldap.rst:5
msgid ""
"To configure :abbr:`LDAP (Lightweight Directory Access Protocol)` "
"authentication in Odoo:"
msgstr ""

#: ../../content/applications/general/users/ldap.rst:7
msgid ""
"Open the Settings app, scroll down to the :guilabel:`Integrations` section, "
"and enable :guilabel:`LDAP Authentication`."
msgstr ""

#: ../../content/applications/general/users/ldap.rst:9
msgid ""
"Click :guilabel:`Save`, then go back to the :guilabel:`Integrations` section"
" and click :guilabel:`LDAP Server`."
msgstr ""

#: ../../content/applications/general/users/ldap.rst:11
msgid ""
"In the :guilabel:`Set up your LDAP Server` list, click :guilabel:`New`, then"
" select the required company in the dropdown list."
msgstr ""

#: ../../content/applications/general/users/ldap.rst:13
msgid ""
"In the :guilabel:`Server information` section, enter the server's IP address"
" and port in the :guilabel:`LDAP server address` and :guilabel:`LDAP Server "
"port` fields, respectively."
msgstr ""

#: ../../content/applications/general/users/ldap.rst:15
msgid ""
"Enable :guilabel:`Use TLS` to request secure TLS/SSL encryption when "
"connecting to the LDAP server, providing the server has StartTLS enabled."
msgstr ""

#: ../../content/applications/general/users/ldap.rst:17
msgid ""
"In the :guilabel:`Login information` section, enter the ID and password of "
"the account used to query the server in the :guilabel:`LDAP binddn` and "
":guilabel:`LDAP password` fields, respectively. If the fields are left "
"empty, the server will perform the query anonymously."
msgstr ""

#: ../../content/applications/general/users/ldap.rst:20
msgid "In the :guilabel:`Process parameter` section, enter:"
msgstr ""

#: ../../content/applications/general/users/ldap.rst:22
msgid ""
"the LDAP server's name in the :guilabel:`LDAP base` field using LDAP format "
"(e.g., ``dc=example,dc=com``);"
msgstr ""

#: ../../content/applications/general/users/ldap.rst:24
msgid "``uid=%s`` in the :guilabel:`LDAP filter` field."
msgstr ""

#: ../../content/applications/general/users/ldap.rst:26
msgid "In the :guilabel:`User information` section:"
msgstr ""

#: ../../content/applications/general/users/ldap.rst:28
msgid ""
"Enable :guilabel:`Create user` to create a user profile in Odoo the first "
"time someone logs in using LDAP;"
msgstr ""

#: ../../content/applications/general/users/ldap.rst:30
msgid ""
"Select the :guilabel:`User template` to be used to create the new user "
"profiles. If no template is selected, the administrator's profile is used."
msgstr ""

#: ../../content/applications/general/users/ldap.rst:34
msgid ""
"When using Microsoft Active Directory (AD) for LDAP authentication, if users"
" experience login issues despite using valid credentials, create a new "
"system parameter to disable referral chasing in the LDAP client:"
msgstr ""

#: ../../content/applications/general/users/ldap.rst:38
msgid ":ref:`Activate the developer mode. <developer-mode>`"
msgstr ""

#: ../../content/applications/general/users/ldap.rst:39
msgid ""
"Go to :menuselection:`Settings --> Technical --> System Parameters` and "
"click :guilabel:`New`."
msgstr ""

#: ../../content/applications/general/users/ldap.rst:41
msgid "Fill in the fields:"
msgstr ""

#: ../../content/applications/general/users/ldap.rst:43
msgid ":guilabel:`Key`: ``auth_ldap.disable_chase_ref``"
msgstr ""

#: ../../content/applications/general/users/ldap.rst:44
msgid ":guilabel:`Value`: ``True``"
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 "zgłoszenia"

#: ../../content/applications/general/users/portal.rst:21
msgid "signatures"
msgstr ""

#: ../../content/applications/general/users/portal.rst:22
msgid "subscriptions"
msgstr "subskrypcje"

#: ../../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:31
msgid "Provide portal access to customers"
msgstr ""

#: ../../content/applications/general/users/portal.rst:33
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:42
msgid ""
"Then select :guilabel:`Grant portal access`. A pop-up window appears, "
"listing three fields:"
msgstr ""

#: ../../content/applications/general/users/portal.rst:44
msgid ""
":guilabel:`Contact`: the recorded name of the contact in the Odoo database"
msgstr ""

#: ../../content/applications/general/users/portal.rst:45
msgid ""
":guilabel:`Email`: the contact's email address that they will use to log "
"into the portal"
msgstr ""

#: ../../content/applications/general/users/portal.rst:46
msgid ":guilabel:`In Portal`: whether or not the user has portal access"
msgstr ""

#: ../../content/applications/general/users/portal.rst:48
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:57
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:61
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:67
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:74
msgid "Change portal username"
msgstr ""

#: ../../content/applications/general/users/portal.rst:76
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:81
msgid ""
":doc:`See the documentation on setting access rights "
"</applications/general/users/access_rights>`."
msgstr ""

#: ../../content/applications/general/users/portal.rst:84
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:89
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:94
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:97
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:102
msgid "Customer portal changes"
msgstr ""

#: ../../content/applications/general/users/portal.rst:104
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:112
msgid "Change customer info"
msgstr ""

#: ../../content/applications/general/users/portal.rst:114
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:119
msgid ":ref:`Portal access documentation <portal/main>`."
msgstr ""

#: ../../content/applications/general/users/portal.rst:121
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:126
msgid "Change password"
msgstr "Zmień hasło"

#: ../../content/applications/general/users/portal.rst:128
#: ../../content/applications/general/users/portal.rst:147
#: ../../content/applications/general/users/portal.rst:166
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:131
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:137
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:141
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:145
msgid "Add two-factor authentication"
msgstr "Dodaj uwierzytelnianie dwuskładnikowe"

#: ../../content/applications/general/users/portal.rst:150
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:153
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:159
msgid ""
"Finally, click :guilabel:`Enable two-factor authentication` to complete the "
"setup."
msgstr ""

#: ../../content/applications/general/users/portal.rst:164
msgid "Change payment info"
msgstr ""

#: ../../content/applications/general/users/portal.rst:169
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 ""