> 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/1.3/pbms/developer-zone/odoo-modules/openg2p-documents.md).

# G2P Documents Store

### Module name

g2p\_documents

### Module title

G2P Documents Store

### Technology base

[Odoo](https://www.odoo.com/)

### Functionality

1. The G2P Documents Store is a module developed by OpenG2P for managing and storing documents in the G2P system. This module provides functionalities for handling document storage, categorization, and tagging within the G2P application. It is designed to enhance document management capabilities and improve user experience.
2. **Document Storage**

   The G2P Documents Store allows users to store various types of documents within the G2P application. It provides a structured and organized approach to managing documents.

### Dependencies

The G2P Documents Store module depends on the following modules:

* `storage_backend_s3`
* `storage_file`

#### External Python dependencies

The module relies on the following external Python libraries:

* `boto3` (version <=1.15.18)
* `python_slugify`

### User interface

NA

### Configuration

Carefully structure the storage backend configuration (`data/storage_backend.xml`) to seamlessly integrate with the specified backends and to handle various document types.

### Error codes

NA

### Source code

<https://github.com/openg2p/openg2p-documents>

### Installation

Standard Odoo package installation


---

# 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/1.3/pbms/developer-zone/odoo-modules/openg2p-documents.md?ask=<question>&goal=<user_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.