> 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.1/system-administration/document-storage.md).
# Document Store
## Introduction
OpenG2P platform allows multiple options for storing registrant documents, evidence documents, entitlement vouchers, accounts payable files, etc. Program administrators can later view these documents from the program view for assessment and verification. These are the currently supported document store options:
1. AWS S3 object store
2. MinIO object store
3. Private filesystem
Users can configure multiple document stores from a single view. The diagram below shows three document stores using the Amazon S3 object-store.
All the users of the OpenG2P platform such as System Administrators, Program Administrators, Finance Officers, and Social workers can upload/edit/delete these documents based on their [role-based access](/1.1/system-administration/role-based-access-control.md#pre-defined-groups).
### Document files
Each document file is assigned a Universally Unique ID (UUID) known as S*lug* by the system. Information about document store, file UUID, size, and type are available from a single view.
### Document tags
The platform users can define unique tags and associate them with their upload files.
---
# 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.1/system-administration/document-storage.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.
