diff --git a/content/administration/odoo_sh/advanced/submodules.rst b/content/administration/odoo_sh/advanced/submodules.rst index 23ee06ec56..954cf3343c 100644 --- a/content/administration/odoo_sh/advanced/submodules.rst +++ b/content/administration/odoo_sh/advanced/submodules.rst @@ -28,7 +28,7 @@ and add them to your addons path automatically so you can install them in your d If you add private repositories as submodules in your branches, you need to configure a deploy key in your Odoo.sh project settings and in your repository settings. Otherwise Odoo.sh won't be allowed to download them. -The procedure is detailed in the chapter :ref:`Settings > Submodules `. +The procedure is detailed in the chapter :ref:`Settings > Submodules `. Adding a submodule ================== @@ -38,7 +38,7 @@ With Odoo.sh (simple) .. warning:: For now it is not possible to add **private** repositories with this method. You can nevertheless - do so :ref:`with Git `. + do so :ref:`with Git `. On Odoo.sh, in the branches view of your project, choose the branch in which you want to add a submodule. diff --git a/content/administration/odoo_sh/getting_started/branches.rst b/content/administration/odoo_sh/getting_started/branches.rst index efb6e6477e..2558586652 100644 --- a/content/administration/odoo_sh/getting_started/branches.rst +++ b/content/administration/odoo_sh/getting_started/branches.rst @@ -2,7 +2,7 @@ Branches ======== -The branches view provides an overview of the different branches in your repository. +The :guilabel:`Branches` view provides an overview of the different branches in your repository. .. _odoo-sh/branches/stages: @@ -109,9 +109,14 @@ documentation ` to view examples. Staging databases are not automatically backed up. Nevertheless, you can restore a backup of the production database in a staging branch for testing purposes or to manually recover data that has -been accidently deleted from the production database. It is possible to create manual backups of +been accidentally deleted from the production database. It is possible to create manual backups of staging databases. +.. warning:: + Databases created for staging branches are intended to last up to three months. After that, they + can be automatically blocked without prior notice. Only rebuilding the branch will allow you to + use that specific branch again. + .. _odoo-sh/branches/stages/development: Development @@ -704,7 +709,9 @@ Clone The clone command is used to create a local copy of your Git repository. .. example:: - :command:`git clone --recurse-submodules --branch development git@github.com:my-organization/my-repository.git` + .. code-block:: shell + + git clone --recurse-submodules --branch development git@github.com:my-organization/my-repository.git - `--recurse-submodules` to download the submodules of your repository - `--branch main` to check out to a specific branch of the repository (e.g., `development`) @@ -720,11 +727,13 @@ Fork The fork command is used to create a new branch based on the current one. .. example:: - :command:`git checkout -b main-1 development && git push -u origin development-1` + .. code-block:: shell + + git checkout -b main-1 development && git push -u origin development-1 - - :command:`git checkout -b main-1 main` a command to create a new branch (e.g., `development-1`) + - `git checkout -b main-1 main` a command to create a new branch (e.g., `development-1`) based on the current branch (e.g., `development`) - - :command:`git push -u origin development-1` a command to upload the new branch (e.g., + - `git push -u origin development-1` a command to upload the new branch (e.g., `development-1`) to the remote repository .. _odoo-sh/branches/shell-commands/merge: @@ -735,11 +744,13 @@ Merge The merge command is used to combine changes on one branch into another branch. .. example:: - :command:`git merge staging-1 && git push -u origin staging` + .. code-block:: shell - - :command:`git merge staging-1` a command to merge the changes of the current branch into + git merge staging-1 && git push -u origin staging + + - `git merge staging-1` a command to merge the changes of the current branch into another branch (e.g., `staging-1`) - - :command:`git push -u origin staging` a command to upload the merged changes to the remote + - `git push -u origin staging` a command to upload the merged changes to the remote repository branch (e.g., `staging`) .. _odoo-sh/branches/shell-commands/ssh: @@ -764,13 +775,15 @@ To use the SSH command, it is necessary to set up an SSH key first. To do so: :alt: Adding an SSH key manually .. example:: - :command:`ssh 25004381@my-user-my-repository-staging-25004381.dev.odoo.com` + .. code-block:: shell + + ssh 25004381@my-user-my-repository-staging-25004381.dev.odoo.com - `25004381` the build ID - `my-user-my-repository-staging-25004381.dev.odoo.com` the domain used to connect to the build -Provided you have the necessary :ref:`access rights ` -on the project, you will be granted SSH access to the build. +Provided you have the necessary :ref:`access rights ` on the +project, you will be granted SSH access to the build. .. note:: Long-running SSH connections are not guaranteed. Idle connections can be disconnected to free up @@ -788,13 +801,15 @@ submodule. :doc:`Submodules documentation <../advanced/submodules>` .. example:: - :command:`git submodule add -b master && git commit -a && git push -u origin staging` + .. code-block:: shell - - :command:`git submodule add -b master ` a command to add a specific branch (e.g., + git submodule add -b master && git commit -a && git push -u origin staging + + - `git submodule add -b master ` a command to add a specific branch (e.g., `master`) of a repository (``) as a submodule under the specified path (``) in your current branch. - - :command:`git commit -a` a command to commit all current changes - - :command:`git push -u origin staging` a command to upload the changes of the current branch + - `git commit -a` a command to commit all current changes + - `git push -u origin staging` a command to upload the changes of the current branch (e.g., `staging`) to the remote repository. .. _odoo-sh/branches/shell-commands/delete: @@ -809,11 +824,13 @@ The delete command is used to delete a branch from your repository. are not automatically backed up, but can be manually. Development branches cannot be backed up. .. example:: - :command:`git push origin :staging && git branch -D staging` + .. code-block:: shell + + git push origin :staging && git branch -D staging - - :command:`git push origin :staging` a command to delete a specific branch (e.g., `staging`) on + - `git push origin :staging` a command to delete a specific branch (e.g., `staging`) on the remote repository - - :command:`git branch -D staging` a command to delete the specific branch on your local copy of + - `git branch -D staging` a command to delete the specific branch on your local copy of the repository .. warning:: diff --git a/content/administration/odoo_sh/getting_started/builds.rst b/content/administration/odoo_sh/getting_started/builds.rst index 62dc64dbe8..2217d9f343 100644 --- a/content/administration/odoo_sh/getting_started/builds.rst +++ b/content/administration/odoo_sh/getting_started/builds.rst @@ -16,7 +16,7 @@ Overview .. image:: builds/builds-overview.png :alt: Overiew of the builds -In the :guilabel:`Builds` overview, a row represents a branch, and a cell within that row represents +In the :guilabel:`Builds` view, a row represents a branch, and a cell within that row represents a build of that branch. Most builds are created after pushes to your GitHub repository branches. They can also be created diff --git a/content/administration/odoo_sh/getting_started/settings.rst b/content/administration/odoo_sh/getting_started/settings.rst index 0fbe149bba..a2fdb51b3f 100644 --- a/content/administration/odoo_sh/getting_started/settings.rst +++ b/content/administration/odoo_sh/getting_started/settings.rst @@ -2,338 +2,375 @@ Settings ======== -Overview -======== - -The settings allow you to manage the configuration of your project. +The :guilabel:`Settings` view allow you to manage the configuration of your project. -.. image:: settings/interface-settings.png - :align: center +.. _odoo-sh/settings/name: Project name ============ -The name of your project. - -.. image:: settings/interface-settings-projectname.png - :align: center - -This defines the address that will be used to access your production database. +The name of your project defines the address used to access your production database. The addresses +of your staging and development builds are automatically derived from this name. If you change the +project name, only future builds will use the new name. -Addresses of your staging and development builds are derived from this name and assigned -automatically. However, when you change your project name, only future builds will use the new name. +.. image:: settings/project-name.png + :alt: The project name setting -.. _odoosh-gettingstarted-settings-collaborators: +.. _odoo-sh/settings/collaborators: Collaborators ============= -Manage the Github users who can access your project. +To grant access to a GitHub user, enter their username and click :guilabel:`Add`. By default, the +user is is granted the :guilabel:`Developer` role. Click the dropdown menu to select another one: -.. image:: settings/interface-settings-collaborators.png - :align: center +- :guilabel:`Admin`: full access to all Odoo.sh features and tools. This role is dedicated to + project management and has exclusive access to the project's settings. +- :guilabel:`Tester`: access to staging and development databases and their tools. This role is + intended for users performing user acceptance testing (UAT). Testers can work with copies of + production data, but they cannot access the production database through Odoo.sh's tools. +- :guilabel:`Developer`: no access to the production and staging databases. This role is intended + for users who modify the code but should not access production data. Developers cannot connect to + the production or staging databases and do not have access to the web shell or server logs. -There are three levels of users: +.. image:: settings/collaborators.png + :alt: The collaborators setting -- :guilabel:`Admin`: has access to all features of an Odoo.sh project. +.. _odoo-sh/settings/collaborators/table: -- :guilabel:`Tester`: has access to the *Staging* and *Development* databases and their tooling. - This role is for users conducting User Acceptance Tests. Testers can work with copies of - production data but cannot access the production database through the Odoo.sh tooling. - -- :guilabel:`Developer`: has access only to the *Development* databases and their tooling. This - role is for developers who propose code modifications but are not allowed to access production - and staging databases through the Odoo.sh tooling. +Feature access by stage and role +-------------------------------- .. list-table:: :header-rows: 1 + :stub-columns: 1 :widths: auto - * - - - + * - Stage + - Feature - Developer - Tester - Admin * - Development - - History + - Connect + / Connect as + - |green| + - |green| + - |green| + * - + - :ref:`History ` + - |green| + - |green| + - |green| + * - + - :ref:`Mails ` - |green| - |green| - |green| * - - - 1-click connect + - :ref:`Editor ` - |green| - |green| - |green| * - - - Logs + - :ref:`Monitor ` - |green| - |green| - |green| * - - - Shell/SSH + - :ref:`Logs ` - |green| - |green| - |green| * - - - Mails + - :ref:`Upgrade ` - |green| - |green| - |green| * - - - Settings + - :ref:`Settings ` + - |green| + - |green| + - |green| + * - + - Status - |green| - |green| - |green| * - Staging - - History + - Connect + / Connect as - |green| - |green| - |green| * - - - 1-click connect - - + - :ref:`History ` + - |green| - |green| - |green| * - - - Logs - - + - :ref:`Mails ` + - |red| - |green| - |green| * - - - Shell/SSH - - + - :ref:`Shell ` + - |red| - |green| - |green| * - - - Mails - - + - :ref:`Editor ` + - |red| - |green| - |green| * - - - Monitoring - - + - :ref:`Monitor ` + - |red| - |green| - |green| * - - - Backups - - - - + - :ref:`Logs ` + - |red| + - |green| - |green| * - - - Upgrade - - + - :ref:`Upgrade ` + - |red| - |green| - |green| * - - - Settings - - + - :ref:`Settings ` + - |red| + - |green| + - |green| + * - + - Status + - |green| - |green| - |green| * - Production - - History + - Connect + / Connect as - |green| - |green| - |green| * - - - 1-click connect - - - - + - :ref:`History ` + - |green| - |green| - * - - - Logs - - - - - |green| * - - - Shell/SSH - - - - + - :ref:`Shell ` + - |red| + - |red| - |green| * - - - Mails - - - - + - :ref:`Editor ` + - |red| + - |red| - |green| * - - - Monitoring - - - - + - :ref:`Monitor ` + - |red| + - |red| - |green| * - - - Backups - - - - + - :ref:`Logs ` + - |red| + - |red| - |green| * - - - Upgrade - - - - + - :ref:`Backups ` + - |red| + - |red| - |green| * - - - Settings - - - - + - :ref:`Upgrade ` + - |red| + - |red| - |green| - * - Status - - + * - + - :ref:`Settings ` + - |red| + - |red| - |green| + * - + - Status - |green| - |green| - * - Settings - - - - - - - |green| -.. warning:: - Those roles only apply to the usage of Odoo.sh. It is important to reflect the user roles - attribution within the repository on GitHub. Please refer to the GitHub documentation section on - `Managing a branch protection rule `_ - for detailed guidance. +.. admonition:: Legend -.. |green| raw:: html + |green| : Available - ● + |red| : Not available -.. |orange| raw:: html +.. |green| raw:: html - ● + ● .. |red| raw:: html - ● + ● -Public Access -============= +.. note:: + - Only admins can access the audit logs and the project settings. + - All roles can access the :doc:`builds page `, but the features available are specific + to each role. -Allow public access to your development builds. +.. _odoo-sh/settings/public: -.. image:: settings/interface-settings-public.png - :align: center +Public access +============= -If activated, this option exposes the Builds page publicly, allowing visitors to view logs of development builds. +When enabling :guilabel:`Allow public access`, the :doc:`builds page ` becomes publicly +accessible, allowing visitors to connect to development builds. Visitors can also access :ref:`logs +`, the :ref:`shell `, and :ref:`mails +` for development builds. Production and staging builds remain private; +visitors can only view their status. -Production and staging builds are excluded, visitors can only see their status. +.. image:: settings/public-access.png + :alt: The public access setting -.. _odoosh-gettingstarted-settings-modules-installation: +.. _odoo-sh/settings/commit: GitHub commit statuses ====================== -This option enables Odoo.sh to push commit statuses to your GitHub repository when a build is -created or updated. It requires a GitHub token with permissions to push commit statuses to the -repository. Refer to `GitHub's documentation on personal access tokens `_ -for instructions to create yours. +You can add a GitHub token to allow Odoo.sh to push commit statuses back to GitHub. The token must +have the *commit statuses (write)* repository permission. -.. note:: - GitHub's **fine-grained personal tokens** have an expiration date and will be disabled if they - fail to update the commit status. You can replace the token at any time on Odoo.sh. +.. image:: settings/commit-statuses.png + :alt: The GitHub commit statuses setting + +.. seealso:: + For more information, refer to `GitHub’s documentation on managing access tokens `_. -The commit statuses pushed to GitHub can have the following contexts: +.. _odoo-sh/settings/key-webhook: -- :guilabel:`ci/odoo.sh (dev)`: status of a development build -- :guilabel:`ci/odoo.sh (staging)`: status of a staging build -- :guilabel:`ci/odoo.sh (production)`: status of a production build -- :guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page will push a test - status on the last commit of your repository +GitHub key and webhook +====================== + +A deploy key and a webhook are automatically created on your GitHub repository to allow Odoo.sh to +fetch code and receive commit notifications. As they can be unintentionally modified or deleted, +you can use the :guilabel:`Verify Deploy Key` and :guilabel:`Verify Webhook` buttons below to verify +their configuration. -Custom domains -============== +.. image:: settings/key-webhook.png + :alt: The GitHub key and webhook setting -To configure additional domains please refer to the corresponding branch's :ref:`settings tab -`. +.. note:: + Administrative rights on the GitHub repository are necessary. -.. _odoosh-gettingstarted-settings-submodules: +.. _odoo-sh/settings/submodules: Submodules ========== -Configure the deploy keys for the private repositories you use -as submodules in your branches to allow Odoo.sh to download them. +The `git submodule` command allows you to `integrate other Git projects +`_ into your codebase without copying the code +directly. -.. warning:: - These settings are required for **private repositories** only. If you are looking on how to set - up your submodules, instructions are available in the chapter :ref:`Submodules - ` of this documentation. +.. image:: settings/submodules.png + :alt: The submodules setting + :scale: 50% -.. image:: settings/interface-settings-submodules.png - :align: center +.. note:: + A Git repository containing Odoo modules, for example from the `Odoo Apps Store + `_ or `community modules `_, is necessary. -When a repository is private, it is not possible to publicly download its branches and revisions. -For that reason, you need to configure a deploy key for Odoo.sh, -so the remote Git server allows our platform to download the revisions -of this private repository. +.. admonition:: Private repositories -To configure the deploy key for a private repository, proceed as follows: + Before adding `private GitHub repository + `_ as a submodule, it is + necessary to add a deploy key: -* in the input, paste the SSH URL of your private sub-repository and click on *Add*, + #. Paste the SSH URL of the sub-repository (e.g., `git@github.com:USERNAME/REPOSITORY.git`) and + click :guilabel:`Add`. + #. Copy the generated :guilabel:`Public Key`. + #. On the sub-repository's GitHub, go to :menuselection:`Settings --> Deploy keys`. + #. Click :menuselection:`Add deploy key`, enter a :guilabel:`Title`, paste the public key into + the :guilabel:`Key` field, and click :guilabel:`Add key`. - * e.g. *git@github.com:USERNAME/REPOSITORY.git* - * it can be another Git server than Github, such as Bitbucket, Gitlab or even your own self-hosted - server +To add a public repository or private repository with a deploy key as a submodule: -* copy the public key, +#. Add the submodule to your project. - * it should look like *ssh-rsa some...random...characters...here...==* + .. code-block:: shell -* in the settings of the private sub-repository, add the public key amongst the deploy keys. + git submodule add -b BRANCH git@github.com:USERNAME/REPOSITORY.git PATH - * Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key` - * Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key` - * Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys` - * Self-hosted: append the key to the git user’s authorized_keys file in its .ssh directory +#. Commit and push the change. -Storage Size -============ + .. code-block:: shell -This section shows the storage size used by your project. + git commit -a && git push -u origin master -.. image:: settings/interface-settings-storage.png - :align: center +#. Wait for Odoo.sh to rebuild the project. -Storage size is computed as follows: +.. _odoo-sh/settings/storage: -* the size of the PostgreSQL database +Production database size +======================== -* the size of the disk files available in your container: database filestore, sessions storage directory... +This section displays the total storage used by the project. It includes the PostgreSQL database +size and disk files in your container (database filestore, session storage, etc.). If the production +database exceeds the storage included in your subscription, the plan will be automatically adjusted. -.. warning:: - In case you want to analyze disk usage, you can run the tool `ncdu - `_ in your Web Shell. +.. image:: settings/database-size.png + :alt: The production database size setting -Should your production database size grow to exceed what's provisioned in your subscription, it -will automatically be synchronized with it. +.. tip:: + To analyze disk usage, run the `Ncdu tool `_ in the :ref:`web + shell `. -Database Workers +.. _odoo-sh/settings/workers: + +Database workers ================ -Additional database workers can be configured here. More workers help increase the load your -production database is able to handle. If you add more, it will automatically be synchronized -with your subscription. +Additional database workers can be configured to allow your production database to handle higher +concurrent loads. + +.. image:: settings/database-workers.png + :alt: The database workers setting -.. image:: settings/interface-settings-workers.png - :align: center +To add more workers, contact your account manager. After payment, the new worker(s) will be added to +your project. -.. Warning:: - Adding more workers will not magically solve all performance issues. It only allows the server - to handle more connections at the same time. If some operations are unusually slow, it's most - likely a problem with the code, if it's not due to your own customizations you can open a ticket - `here `_. +.. note:: + Adding more workers does not automatically fix performance issues. It only increases the number + of concurrent connections the server can handle. If some operations remain slow, the issue is + likely code-related. If it is not due to your customizations, contact `Odoo Support + `_. -Staging Branches +.. _odoo-sh/settings/staging: + +Staging branches ================ -Additional staging branches allow you to develop and test more features at the same time. If you -add more, it will automatically be synchronized with your subscription. +Additional staging branches allow you to develop and test multiple features simultaneously. To add +more staging branches, request a product increase directly from your Odoo.sh project. A widget will +guide you to the subscription portal to complete the purchase. After payment, synchronization with +Odoo.sh will occur automatically, and the number of available staging branches will be updated. + +.. image:: settings/staging-branches.png + :alt: The staging branches setting -.. image:: settings/interface-settings-staging-branches.png - :align: center +.. _odoo-sh/settings/activation: Activation ========== -Shows the status of the project's activation. You can change the project's activation code if -needed. +This section shows the activation status of the project. You can change the activation code if +necessary, provided the new code is not already assigned to another project. + +.. image:: settings/activation.png + :alt: The staging branches setting + +.. warning:: + You cannot change the activation code to: + + - A code already used in another project + - A trial code (downgrading from paid to trial is not allowed) + - An invalid code (not linked to an Odoo.sh custom plan) -.. image:: settings/interface-settings-activation.png - :align: center + For any other issue, contact `Odoo Support `_. diff --git a/content/administration/odoo_sh/getting_started/settings/activation.png b/content/administration/odoo_sh/getting_started/settings/activation.png new file mode 100644 index 0000000000..0429b19123 Binary files /dev/null and b/content/administration/odoo_sh/getting_started/settings/activation.png differ diff --git a/content/administration/odoo_sh/getting_started/settings/collaborators.png b/content/administration/odoo_sh/getting_started/settings/collaborators.png new file mode 100644 index 0000000000..3b9180a637 Binary files /dev/null and b/content/administration/odoo_sh/getting_started/settings/collaborators.png differ diff --git a/content/administration/odoo_sh/getting_started/settings/commit-statuses.png b/content/administration/odoo_sh/getting_started/settings/commit-statuses.png new file mode 100644 index 0000000000..e75a7a1c60 Binary files /dev/null and b/content/administration/odoo_sh/getting_started/settings/commit-statuses.png differ diff --git a/content/administration/odoo_sh/getting_started/settings/database-size.png b/content/administration/odoo_sh/getting_started/settings/database-size.png new file mode 100644 index 0000000000..1bb0561728 Binary files /dev/null and b/content/administration/odoo_sh/getting_started/settings/database-size.png differ diff --git a/content/administration/odoo_sh/getting_started/settings/database-workers.png b/content/administration/odoo_sh/getting_started/settings/database-workers.png new file mode 100644 index 0000000000..efb5b590ad Binary files /dev/null and b/content/administration/odoo_sh/getting_started/settings/database-workers.png differ diff --git a/content/administration/odoo_sh/getting_started/settings/interface-settings-activation.png b/content/administration/odoo_sh/getting_started/settings/interface-settings-activation.png deleted file mode 100644 index 362edfc8ca..0000000000 Binary files a/content/administration/odoo_sh/getting_started/settings/interface-settings-activation.png and /dev/null differ diff --git a/content/administration/odoo_sh/getting_started/settings/interface-settings-collaborators.png b/content/administration/odoo_sh/getting_started/settings/interface-settings-collaborators.png deleted file mode 100644 index 3c0f07eabe..0000000000 Binary files a/content/administration/odoo_sh/getting_started/settings/interface-settings-collaborators.png and /dev/null differ diff --git a/content/administration/odoo_sh/getting_started/settings/interface-settings-projectname.png b/content/administration/odoo_sh/getting_started/settings/interface-settings-projectname.png deleted file mode 100644 index 2ef44eaf17..0000000000 Binary files a/content/administration/odoo_sh/getting_started/settings/interface-settings-projectname.png and /dev/null differ diff --git a/content/administration/odoo_sh/getting_started/settings/interface-settings-public.png b/content/administration/odoo_sh/getting_started/settings/interface-settings-public.png deleted file mode 100644 index 7bf144b7c1..0000000000 Binary files a/content/administration/odoo_sh/getting_started/settings/interface-settings-public.png and /dev/null differ diff --git a/content/administration/odoo_sh/getting_started/settings/interface-settings-staging-branches.png b/content/administration/odoo_sh/getting_started/settings/interface-settings-staging-branches.png deleted file mode 100644 index 378c8eefd8..0000000000 Binary files a/content/administration/odoo_sh/getting_started/settings/interface-settings-staging-branches.png and /dev/null differ diff --git a/content/administration/odoo_sh/getting_started/settings/interface-settings-storage.png b/content/administration/odoo_sh/getting_started/settings/interface-settings-storage.png deleted file mode 100644 index 91d62d6cda..0000000000 Binary files a/content/administration/odoo_sh/getting_started/settings/interface-settings-storage.png and /dev/null differ diff --git a/content/administration/odoo_sh/getting_started/settings/interface-settings-submodules.png b/content/administration/odoo_sh/getting_started/settings/interface-settings-submodules.png deleted file mode 100644 index 5d1453e07f..0000000000 Binary files a/content/administration/odoo_sh/getting_started/settings/interface-settings-submodules.png and /dev/null differ diff --git a/content/administration/odoo_sh/getting_started/settings/interface-settings-workers.png b/content/administration/odoo_sh/getting_started/settings/interface-settings-workers.png deleted file mode 100644 index c5cb00a701..0000000000 Binary files a/content/administration/odoo_sh/getting_started/settings/interface-settings-workers.png and /dev/null differ diff --git a/content/administration/odoo_sh/getting_started/settings/interface-settings.png b/content/administration/odoo_sh/getting_started/settings/interface-settings.png deleted file mode 100644 index f6d830c602..0000000000 Binary files a/content/administration/odoo_sh/getting_started/settings/interface-settings.png and /dev/null differ diff --git a/content/administration/odoo_sh/getting_started/settings/key-webhook.png b/content/administration/odoo_sh/getting_started/settings/key-webhook.png new file mode 100644 index 0000000000..aae286209b Binary files /dev/null and b/content/administration/odoo_sh/getting_started/settings/key-webhook.png differ diff --git a/content/administration/odoo_sh/getting_started/settings/project-name.png b/content/administration/odoo_sh/getting_started/settings/project-name.png new file mode 100644 index 0000000000..e2e9dc78a2 Binary files /dev/null and b/content/administration/odoo_sh/getting_started/settings/project-name.png differ diff --git a/content/administration/odoo_sh/getting_started/settings/public-access.png b/content/administration/odoo_sh/getting_started/settings/public-access.png new file mode 100644 index 0000000000..7244a71abb Binary files /dev/null and b/content/administration/odoo_sh/getting_started/settings/public-access.png differ diff --git a/content/administration/odoo_sh/getting_started/settings/staging-branches.png b/content/administration/odoo_sh/getting_started/settings/staging-branches.png new file mode 100644 index 0000000000..4df81f1695 Binary files /dev/null and b/content/administration/odoo_sh/getting_started/settings/staging-branches.png differ diff --git a/content/administration/odoo_sh/getting_started/settings/submodules.png b/content/administration/odoo_sh/getting_started/settings/submodules.png new file mode 100644 index 0000000000..a5e017ea59 Binary files /dev/null and b/content/administration/odoo_sh/getting_started/settings/submodules.png differ