odoo-forge-bundle 0.1.0

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

@@ -0,0 +1,89 @@
+---
+title: ""
+source_url: "https://docs.odoo.sbggai.top/applications/general/iot.html"
+---
+
+:show-content:
+:hide-page-toc:
+:nosearch:
+# 
+# Internet of Things (IoT)
+
+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.
+
+The following IoT systems are supported:
+
+- :doc:`IoT box <iot/iot_box>`: micro-computer, plug-and-play device (i.e., the Odoo IoT program is
+  pre-installed);
+- :doc:`Windows virtual IoT <iot/windows_iot>`: Odoo IoT program for Windows that can be installed
+  on a Windows computer.
+
+> **note**:
+>    - :abbr:`MRP (Material Requirement Planning)` devices, including cameras and measurement tools,
+     are not compatible with Windows virtual IoT.
+   - Multiple IoT systems can be used at the same time.
+   - 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.
+
+.. _iot/iot/iot-subscription:
+
+# IoT box subscription
+
+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.
+
+> **tip**:
+>    If the subscription is linked to an [Odoo.com ](https://www.odoo.com) portal user, check the
+   information on the portal's subscription page.
+
+.. seealso::
+   - [Odoo's compatible IoT devices ](https://www.odoo.com/app/iot-hardware)
+   - [Odoo Tutorials: Internet of Things (IoT) Tutorials
+     ](https://www.odoo.com/slides/internet-of-things-iot-175)
+   - [IoT system FAQ ](https://www.odoo.com/app/iot-faq)
+
+.. cards::
+
+   .. card:: IoT box
+      :target: iot/iot_box
+      :large:
+
+      Set up an IoT box.
+
+   .. card:: Windows virtual IoT
+      :target: iot/windows_iot
+      :large:
+
+      Set up Windows virtual IoT.
+
+   .. card:: IoT system connection to Odoo
+      :target: iot/connect
+
+      Connect the IoT system to your Odoo database and troubleshoot potential connection issues.
+
+   .. card:: Devices
+      :target: iot/devices
+
+      Connect devices such as printers, screens, measurement tools, etc., to the IoT system.
+
+   .. card:: HTTPS certificate
+      :target: iot/iot_advanced/https_certificate_iot
+
+      Verify your IoT system and database meet the eligibility requirements for HTTPS certificate
+      generation and address any related issues.
+
+   .. card:: IoT system updates
+      :target: iot/iot_advanced/updating_iot
+
+      Update your IoT system's image, core code, and handlers to benefit from the latest IoT fixes
+      and features or reset the IoT system if needed.
+
+.. toctree::
+   :titlesonly:
+
+   iot/iot_box
+   iot/windows_iot
+   iot/connect
+   iot/iot_advanced
+   iot/devices

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

@@ -0,0 +1,131 @@
+---
+title: "Multi-company"
+source_url: "https://docs.odoo.sbggai.top/applications/general/multi_company.html"
+---
+
+=============
+# Multi-company
+
+.. |mcd| replace:: multi-company database
+
+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.
+
+Before deciding to use the multi-company feature, there are several factors to consider.
+
+> **important**:
+>    Multi-company is **only** available in *One App Free* databases, or with [Custom
+   ](https://www.odoo.com/pricing-plan) plans.
+
+# Accessing multiple companies
+
+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.
+
+.. figure:: multi_company/company-access.png
+   :align: center
+   :alt: An example of the list of companies a user has access to when logged into a database.
+
+   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.
+
+> **note**:
+>    The database may refresh after each checkbox is ticked.
+
+.. _general/active-companies:
+
+## Multiple active companies
+
+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.
+
+When creating a new record, the current company is added to the record in the *Company* field,
+except under the following circumstances:
+
+- The *Company* field for a new product, or a new contact, is left blank.
+- If there is a related document already in the system, the *Company* field on the new record
+  defaults to the same company.
+
+.. example::
+   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.
+
+   When a new sales team is created, the :guilabel:`Company` field automatically defaults to `My
+   Company (Chicago)`.
+
+.. _general/sharing-data:
+
+# Share data
+
+In a |mcd|, certain records are able to be utilized by all of the companies (or several, based on
+permissions).
+
+## Products
+
+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.
+
+## Contacts
+
+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.
+
+# Inter-company transactions
+
+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.
+
+> **warning**:
+>    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.
+
+# Use cases
+
+## Multinational companies
+
+A multinational retail chain, which operates in the United States and Canada, needs to manage
+transactions in both USD and CAD currencies.
+
+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.
+
+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.
+
+## Separate processes
+
+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.
+
+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.
+
+# Limitations
+
+In some instances, a |mcd| may *not* be the best option, due to potential limitations.
+
+## Access rights
+
+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.
+
+## Shared records
+
+Individual records are either :ref:`shared <general/sharing-data>` between all companies, or belong
+to a single company.
+
+## PDF Reports
+
+Some customizations, specifically for PDF reports, apply to all companies. It is not always possible
+to separate reports for individual companies.

package/payload/skills/odoo18-docs/references/docs/applications/general/users/2fa.md

@@ -0,0 +1,125 @@
+---
+title: "Two-factor authentication"
+source_url: "https://docs.odoo.sbggai.top/applications/general/users/2fa.html"
+---
+
+=========================
+# Two-factor authentication
+
+.. |2fa| replace:: :abbr:`2FA (two-factor authentication)`
+.. |QR| replace:: :abbr:`QR (Quick Response)` code
+
+*Two-factor authentication (2FA)* is a way to improve security, and prevent unauthorized persons
+from accessing user accounts.
+
+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.
+
+This means an unauthorized user would need to guess the account password *and* have access to the
+authenticator, which is a more difficult proposition.
+
+# Requirements
+
+> **important**:
+>    These lists are just examples. They are **not** endorsements of any specific software.
+
+Phone-based authenticators are the easiest and most commonly used. Examples include:
+
+- [Authy ](https://authy.com/)
+- [FreeOTP ](https://freeotp.github.io/)
+- [Google Authenticator ](https://support.google.com/accounts/answer/1066447?hl=en)
+- [LastPass Authenticator ](https://lastpass.com/auth/)
+- [Microsoft Authenticator
+  ](https://www.microsoft.com/en-gb/account/authenticator?cmp=h66ftb_42hbak)
+
+Password managers are another option. Common examples include:
+
+- [1Password ](https://support.1password.com/one-time-passwords/)
+- [Bitwarden ](https://bitwarden.com/help/article/authenticator-keys/),
+
+> **note**:
+>    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.
+
+# Two-factor authentication setup
+
+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.
+
+Click the :guilabel:`Account Security` tab, then slide the :guilabel:`Two-Factor Authentication`
+toggle to *active*.
+
+.. figure:: 2fa/account-security.png
+   :align: center
+
+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|.
+
+
+.. figure:: 2fa/qr-code.png
+   :align: center
+
+Using the desired authenticator application, scan the |QR| when prompted.
+
+> **tip**:
+>    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.
+
+   .. figure:: 2fa/secret-visible.png
+      :align: center
+
+   .. figure:: 2fa/input-secret.png
+      :align: center
+
+Afterwards, the authenticator should display a *verification code*.
+
+.. figure:: 2fa/authenticator.png
+   :align: center
+
+Enter the code into the :guilabel:`Verification Code` field, then click :guilabel:`Activate`.
+
+.. figure:: 2fa/2fa-enabled.png
+   :align: center
+
+# Logging in
+
+To confirm |2fa| setup is complete, log out of Odoo.
+
+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`.
+
+.. image:: 2fa/2fa-login.png
+   :align: center
+   :alt: The login page with 2fa enabled.
+
+.. danger::
+   If a user loses access to their authenticator, an administrator **must** deactivate |2fa| on the
+   account before the user can log in.
+
+# Enforce two-factor authentication
+
+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`.
+
+Click :guilabel:`Install` on the Kanban card for the :guilabel:`2FA by mail` module.
+
+.. image:: 2fa/2FA-by-mail.png
+   :align: center
+   :alt: The 2FA by mail module in the Apps directory.
+
+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`.
+
+> **note**:
+>    Selecting :guilabel:`All users` applies the setting to portal users, in addition to employees.
+
+.. image:: 2fa/enforce-settings.png
+   :align: center
+   :alt: The enforce two factor setting in the Settings application.
+
+Click :guilabel:`Save` to commit any unsaved changes.

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

@@ -0,0 +1,187 @@
+---
+title: "Access rights"
+source_url: "https://docs.odoo.sbggai.top/applications/general/users/access_rights.html"
+---
+
+=============
+# Access rights
+
+*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.
+
+**Only** an *administrator* can change access rights.
+
+.. danger::
+   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.
+
+> **tip**:
+>    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.
+
+   To access this setting, navigate to :menuselection:`Settings app --> Manage users --> select a
+   user --> Access Rights tab --> Administration section --> Administration field`.
+
+   Once at the setting, an already existing administrator **must** change the setting in the
+   :guilabel:`Administration` field to :guilabel:`Access Rights`.
+
+   Once complete, click :guilabel:`Save` to save the changes, and implement the user as an
+   administrator.
+
+# Users
+
+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.
+
+To make changes to a user's rights, click on the desired user to edit their profile.
+
+.. image:: access_rights/navigate-to-users-menu.png
+   :alt: Users menu in the Users & Companies section of the Settings app of Odoo.
+
+On the user's profile page, in the :guilabel:`Access Rights` tab, scroll down to view the current
+permissions.
+
+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`.
+
+The :guilabel:`Administration` field in the :guilabel:`Access Rights` tab has the following options:
+:guilabel:`Settings` or :guilabel:`Access Rights`.
+
+.. image:: access_rights/user-permissions-dropdown-menu.png
+   :alt: The Sales apps drop-down menu to set the user's level of permissions.
+
+.. _access-rights/groups:
+
+# Create and modify groups
+
+*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.
+
+To access groups, first activate Odoo's :ref:`developer mode <developer-mode>`, then go to
+:menuselection:`Settings app --> Users & Companies --> Groups`.
+
+.. image:: access_rights/click-users-and-companies.png
+   :alt: Groups menu in the Users & Companies section of the Settings app of Odoo.
+
+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).
+
+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.
+
+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.
+
+> **important**:
+>    Always test the settings being changed to ensure they are being applied to the correct users.
+
+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 :icon:`fa-times`
+:guilabel:`(cancel)` icon to remove a row.
+
+.. image:: access_rights/groups-form.png
+   :alt: Tabs in the Groups form to modify the settings of the group.
+
+- :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.
+- :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.
+
+  .. example::
+     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.
+
+- :guilabel:`Menus` tab: defines which models the group can have access to. Click
+  :guilabel:`Add a line` to add a specific menu.
+- :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.
+- :guilabel:`Access Rights` tab: lists the first level of rights (models) that this group has. The
+  :guilabel:`Name` column represents the name for the current group's access to the model
+  selected in the :guilabel:`Model` column.
+
+  To link a new access right to a group, click :guilabel:`Add a line`. Select the appropriate model
+  from the :guilabel:`Model` drop-down, then enter a name for the access right in the
+  :guilabel:`Name` column. For each model, enable the following options as appropriate:
+
+  - :guilabel:`Read`: Users can see the object's existing values.
+  - :guilabel:`Write`: Users can edit the object's existing values.
+  - :guilabel:`Create`: Users can create new values for the object.
+  - :guilabel:`Delete`: Users can delete values for the object.
+
+  > **tip**:
+>      While there are no conventions for naming access rights, it is advisable to choose a name that
+     identifies its purpose.
+
+     For example, the access that purchase managers have to the :guilabel:`Contact` model could be
+     named `res.partner.purchase.manager`. This consists of the technical name of the model,
+     followed by a name identifying the group of users in question.
+
+     .. image:: access_rights/name-field.png
+        :alt: Name of access rights to a model.
+
+     To find the model's technical name from the current view, first enter a placeholder text
+     in the :guilabel:`Name` field, then click the :guilabel:`Model` name, then the
+     :icon:`fa-arrow-right` :guilabel:`(Internal link)` icon.
+
+- :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:
+
+  - :guilabel:`Apply for Read`.
+  - :guilabel:`Apply for Write`.
+  - :guilabel:`Apply for Create`.
+  - :guilabel:`Apply for Delete`.
+
+  > **important**:
+>      Record rules are written using a *domain*, or conditions that filter data. A domain expression
+     is a list of such conditions. For example:
+
+     `[('mrp_production_ids', 'in', user.partner_id.commercial_partner_id.production_ids.ids)]`
+
+     This record rule is to enable MRP consumption warnings for subcontractors.
+
+     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.
+
+.. _access-rights/superuser:
+
+# Superuser mode
+
+*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 :icon:`fa-bug` :guilabel:`(debug)` icon, located in the top banner.
+
+Finally, towards the bottom of the menu, click :guilabel:`Become Superuser`.
+
+> **important**:
+>    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*.
+
+.. danger::
+   *Superuser mode* allows for circumvention of record rules and access rights, and therefore,
+   should be exercised with extreme caution.
+
+   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.
+
+   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.
+
+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.
+
+> **tip**:
+>    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`.
+
+   Instead of clicking :guilabel:`Login`, click :guilabel:`Log in as superuser`.