> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/pbms/_archive/previous-generation/deployment/installation-of-odoo-modules.md).
# Installation of Odoo Modules
Once the PBMS module is deployed, individual Odoo modules can be installed directly from the Odoo dashboard as required.
## Procedure
1. Open the landing page for your environment (e.g., ), and log in to the PBMS module using valid credentials available in the Secrets section of the Rancher UI.
2. Once you logged in enable `Activate the developer mode` under **settings -> General Settings -> Developer Tools.**
3. Click the main menu icon  and select **Apps**.
4. Search G2P modules inside the **Search field** available on the dashboard.
5. You can search for a module by name to **Install** it according to your project requirements. And to upgrade an existing module, click the **Upgrade** button to apply the latest version.
6. Click the **Learn More** button to learn about OpenG2P.
7. Click the  icon to get Module Information.
| Feature | Description |
| ----------- | ------------------------------------------ |
| Module Info | It contains the information of the module. |
| Learn More | It navigates to the OpenG2P website page. |
Similarly, you can activate the other modules for PBMS based on your project requirements.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.openg2p.org/products/pbms/_archive/previous-generation/deployment/installation-of-odoo-modules.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
