odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/general/companies.md

@@ -0,0 +1,251 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/general/companies.html"
+---
+
+:show-content:
+# 
+# Companies
+
+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.
+
+> **warning**:
+>    Enabling multi-company functionality in an Odoo database on a *Standard* plan automatically
+   triggers an upsell to the *Custom* plan. This does not apply to databases on the *One-App Free*
+   plan.
+
+   - **For yearly or multi-year contracts**: An upsell order is created with a 30-day limit.
+   - **For monthly contracts**: The subscription automatically switches to the *Custom* plan and
+     the new rate is applied when the next bill is generated.
+
+   For more information, refer to [Odoo's pricing page ](https://www.odoo.com/pricing-plan) or
+   contact your account manager.
+
+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.
+
+Proceed to fill out the new company form that appears.
+
+> **tip**:
+>    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.
+
+   After selecting the appropriate company, click the :guilabel:`⚙️ Actions` icon, and select
+   :guilabel:`Archive` from the resulting drop-down menu.
+
+   To ensure all records related to the archived company are archived, contact Odoo's [Support Team
+   ](https://www.odoo.com/help).
+
+   Should a record not be archived, there is a risk of reactivating the archived company, and
+   creating the upsell again.
+
+.. _companies/manage:
+
+# Manage companies and records
+
+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.
+
+.. image:: companies/company-info.png
+   :align: center
+   :alt: Overview of a new company's form in Odoo.
+
+> **tip**:
+>    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`.
+
+   Companies also have a :guilabel:`Parent Company` set on the company form in :ref:`developer mode
+   <developer-mode>`.
+
+## Switch between companies
+
+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.
+
+.. example::
+   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)*.
+
+   .. image:: companies/multi-companies-menu-dashboard.png
+      :align: center
+      :alt: View of the companies menu through the main dashboard in Odoo.
+
+## Share records
+
+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:
+
+- *A blank field*: the record is shared within all companies.
+- *Adding a company*: the record is visible to users logged in to that specific company.
+
+.. image:: companies/product-form-company.png
+   :align: center
+   :alt: View of a product's form emphasizing the company field in Odoo Sales.
+
+When an environment is selected from the top menu, along with an additional company, records are
+shared between the two companies.
+
+# Branches
+
+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.
+
+.. image:: companies/add-branch.png
+   :align: center
+   :alt: Add a branch to a company with branches and add a line highlighted.
+
+> **tip**:
+>    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`.
+
+   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`.
+
+.. danger::
+   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.
+
+   For more information on pricing, see [Odoo's pricing ](https://www.odoo.com/pricing-plan) page.
+
+.. _general/employee-access:
+
+# Employee access
+
+Once companies are created, manage the employees' :doc:`Access Rights <users/access_rights>` for
+*Multi Companies*.
+
+To access the *Access Rights*, navigate to :menuselection:`Settings app --> Users section --> Manage
+Users`.
+
+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`.
+
+Multiple companies can be set for :guilabel:`Allowed Companies`, and *only one* can be set as the
+:guilabel:`Default Company`.
+
+.. image:: companies/access-rights-multi-companies.png
+   :align: center
+   :alt: View of an user form emphasizing the multi companies field under the access rights tabs
+         in Odoo.
+
+If an administrator has multiple companies activated on the database, and is editing a record, the
+editing occurs on the record's related company.
+
+.. example::
+   If editing a sale order issued under `JS Store US`, while working on the `JS Store Belgium`
+   environment, the changes are applied under `JS Store US` (the company from which the sale order
+   was issued).
+
+When creating a record, the company taken into account is:
+
+- The current company selected in the company selector, in the upper-right hand of the screen (the
+  one that is highlighted/active)
+
+**OR**
+
+- No company is set (because none is set on the product and contact forms, for example)
+
+**OR**
+
+- The company set is the company linked to the document (the same as if a record is being edited)
+
+# Document format
+
+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.
+
+.. image:: companies/document-layout.png
+   :align: center
+   :alt: View of the settings page emphasizing the document layout field in Odoo.
+
+: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.
+
+.. _general/inter-company:
+
+# Inter-company transactions
+
+First, activate the :ref:`developer mode <developer-mode>`. Then, make sure each one of the
+companies is properly set in relation to:
+
+- :doc:`Chart of Accounts <../finance/accounting/get_started/chart_of_accounts>`
+- :doc:`Taxes <../finance/accounting/taxes>`
+- :doc:`Fiscal Positions <../finance/accounting/taxes/fiscal_positions>`
+- :doc:`Journals <../finance/accounting/bank>`
+- :doc:`Fiscal Localizations <../finance/fiscal_localizations>`
+- :doc:`Pricelists <../sales/sales/products_prices/prices/pricing>`
+
+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.
+
+With the respective company activated and selected, choose one of the following :guilabel:`Rule`
+options:
+
+- :guilabel:`Do not synchronize`: do not synchronize any inter-company transactions.
+- :guilabel:`Synchronized invoice/bills`: generates a bill/invoice when a company confirms a
+  bill/invoice for the selected company.
+- :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`.\*
+- :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`.\*
+- :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`.\*
+
+  \* The given option needs to be selected, so :guilabel:`Automatic Validation` appears in the
+  configuration.
+
+.. image:: companies/inter-company-transactions.png
+   :align: center
+   :alt: View of the settings page emphasizing the inter company transaction field in Odoo.
+
+> **note**:
+>    Products **must** be configured as :guilabel:`Can be sold` and shared between the companies. See
+   :doc:`../inventory_and_mrp/inventory/product_management/configure/type`.
+
+.. example::
+   :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`.
+
+   :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).
+
+> **tip**:
+>    Remember to test all workflows as a user *other* than the administrator.
+
+.. seealso::
+   - :doc:`Multi-company Guidelines <../../developer/howtos/company>`
+   - :doc:`../finance/accounting/get_started/multi_currency`
+
+.. toctree::
+   :titlesonly:
+
+   companies/digest_emails
+   companies/email_template

package/payload/skills/odoo18-docs/references/docs/applications/general/developer_mode.md

@@ -0,0 +1,68 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/general/developer_mode.html"
+---
+
+.. _developer-mode:
+# 
+# Developer mode (debug mode)
+
+The developer mode, also known as debug mode, unlocks access to advanced :ref:`tools and settings
+<developer-mode/tools>` in Odoo.
+
+> **warning**:
+>    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.
+
+> **note**:
+>    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.
+
+.. _developer-mode/activation:
+
+# Activation
+
+To activate it, open the :guilabel:`Settings` app, scroll down to the :guilabel:`Developer Tools`
+section, and click :guilabel:`Activate the developer mode`.
+
+Once activated, the :guilabel:`Deactivate the developer mode` option becomes available.
+
+.. image:: developer_mode/settings.png
+   :alt: Activating the developer mode in the Settings app
+
+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.
+
+Use `?debug=assets` to activate the developer mode with assets and `?debug=tests` to activate it
+with tests assets.
+
+> **tip**:
+>    Open the **command palette** by pressing `Ctrl + K` or `Cmd ⌘ + K`, then type `debug` to
+   activate the developer mode with assets or deactivate it.
+
+.. admonition:: Browser extension
+
+   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/).
+
+.. _developer-mode/tools:
+
+# Developer tools and technical menu
+
+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.
+
+.. image:: developer_mode/tools.png
+   :alt: Accessing the developer tools
+
+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.
+
+.. image:: developer_mode/technical.png
+   :alt: Accessing the technical menu

package/payload/skills/odoo18-docs/references/docs/applications/general/email_communication/azure_oauth.md

@@ -0,0 +1,285 @@
+---
+title: "Connect Microsoft Outlook 365 to Odoo using Azure OAuth"
+source_url: "https://docs.odoo.sbggai.top/applications/general/email_communication/azure_oauth.html"
+---
+
+=======================================================
+# Connect Microsoft Outlook 365 to Odoo using Azure OAuth
+
+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.
+
+.. seealso::
+   [Microsoft Learn: Register an application with the Microsoft identity platform
+   ](https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app)
+
+.. seealso::
+   - :doc:`/applications/general/users/azure`
+   - :doc:`/applications/productivity/calendar/outlook`
+
+# Setup in Microsoft Azure Portal
+
+## Create a new application
+
+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*).
+
+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)`.
+
+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.
+
+> **note**:
+>    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.
+
+After the URL has been added to the field, :guilabel:`Register` the application, so it is created.
+
+## API permissions
+
+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.
+
+In the search bar, search for the following :guilabel:`Delegated permissions` and click
+:guilabel:`Add permissions` for each one:
+
+- :guilabel:`SMTP.Send`
+- :guilabel:`IMAP.AccessAsUser.All`
+
+> **note**:
+>    The :guilabel:`User.Read` permission will be added by default.
+
+.. image:: azure_oauth/permissions.png
+   :align: center
+   :alt: API permissions needed for Odoo integration are listed under the Microsoft Graph.
+
+# Assign users and groups
+
+After adding the API permissions, navigate back to the :guilabel:`Overview` of the
+:guilabel:`Application` in the top of the left sidebar menu.
+
+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.
+
+.. image:: azure_oauth/managed-application.png
+   :align: center
+   :alt: Add users/groups by clicking the Managed application in local directory link for the
+         created application.
+
+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.
+
+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.
+
+## Create credentials
+
+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.
+
+.. image:: azure_oauth/application-id.png
+   :align: center
+   :alt: Application/Client ID located in the Overview of the app.
+
+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.
+
+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`.
+
+> **important**:
+>    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.
+
+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.
+
+.. image:: azure_oauth/secretvalue.png
+   :align: center
+   :alt: Client Secret Value or Value in the app's credentials.
+
+After these steps, the following items should be ready to be set up in Odoo:
+
+- A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)
+- A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)
+
+This completes the setup on the :guilabel:`Microsoft Azure Portal` side.
+
+# Setup in Odoo
+
+## Enter Microsoft Outlook credentials
+
+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`.
+
+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`.
+
+:guilabel:`Save` the progress.
+
+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.
+
+.. image:: azure_oauth/outlookcreds.png
+   :align: center
+   :alt: Outlook Credentials in Odoo General Settings.
+
+## Configure outgoing email server
+
+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.
+
+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`.
+
+If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address
+<email-outbound-unique-address>`.
+
+Then, click on :guilabel:`Connect your Outlook account`.
+
+A new window from Microsoft opens to complete the :guilabel:`authorization process`. Select the
+appropriate email address that is being configured in Odoo.
+
+.. image:: azure_oauth/verify-outlook.png
+   :align: center
+   :alt: Permission page to grant access between newly created app and Odoo.
+
+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.
+
+.. image:: azure_oauth/outlook-token.png
+   :align: center
+   :alt: Valid Outlook Token indicator.
+
+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.
+
+.. _azure_oauth/notifications:
+
+### Configuration with a single outgoing mail server
+
+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.
+
+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.
+
+.. seealso::
+   Visit the :ref:`From Filtering documentation <email-outbound-different-servers-personalized-from-filtering>` for more
+   information.
+
+> **note**:
+>    The :guilabel:`System Parameters` can be accessed by activating :ref:`developer-mode` in the
+   :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu.
+
+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:
+
+.. image:: azure_oauth/from-name-remain.png
+   :align: center
+   :alt: Name from real sender with static email.
+
+.. example::
+   Single outgoing mail server configuration:
+
+   - Outgoing mail server **username** (login) = `notifications@example.com`
+   - Outgoing mail server :guilabel:`FROM Filtering` = `notifications@example.com`
+   - `mail.catchall.domain` in system parameters = `example.com`
+   - `mail.default.from` in system parameters = `notifications`
+
+### User-specific (multiple user) configuration
+
+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.
+
+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.
+
+Setup
+*****
+
+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.
+
+.. seealso::
+   Visit the :ref:`From Filtering documentation <email-outbound-different-servers-personalized-from-filtering>` for more
+   information.
+
+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}`.
+
+> **note**:
+>    The :guilabel:`System Parameters` can be accessed by activating :ref:`developer-mode` in the
+   :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu.
+
+> **important**:
+>    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.
+
+   .. seealso::
+      For more information on setting the mass-mailing email server visit
+      :ref:`email-outbound-custom-domain-smtp-server`.
+
+.. example::
+   Multiple user outgoing mail server configuration:
+
+   - User #1 mailbox
+      - Outgoing mail server #1 **username** (login) = `john@example.com`
+      - Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`
+   - User #2 mailbox
+      - Outgoing mail server #2 **username** (login) = `jane@example.com`
+      - Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`
+   - Notifications mailbox
+      - Outgoing mail server #3 **username** (login) = `notifications@example.com`
+      - Outgoing mail server #3 :guilabel:`FROM Filtering` = `notifications@example.com`
+   - System Parameters
+      - `mail.catchall.domain` in system parameters = `example.com`
+      - `mail.default.from` in system parameters = `notifications`
+
+## Configure incoming email server
+
+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.