> For the complete documentation index, see [llms.txt](https://manual.harpe.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.harpe.io/start/manual/docs/adding-a-document.md).
# Adding a Document
New documents can be added by clicking the Add Document button and filling in the required fields.
Add Document form
**Reference Document**
The document file to upload.
**Title**
The title of the document.
**Type**
The document type.
* Policy
* Procedure
* Certificate
* Record
**Classification**
The security classification of the document.
* Public - Available for public and general viewing. The lowest classification.
* Private - Internal viewing only.
* Confidential - Selected viewers only. The highest classification.
**Status**
The status of the document.
* Retired - The document is no longer in active use.
* Draft - The document is undergoing editing or requires approval.
* Approved - The document is approved.
**Uploaded by**
The user who uploaded the document.
**Uploaded date**
The upload date of the document.
**Last review date**
The last date on which the document was reviewed.
**Next review date**
The date of the next review of the document.
**Owner**
The owner of the document who has responsibility for reviewing and keeping it updated.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://manual.harpe.io/start/manual/docs/adding-a-document.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.