> For the complete documentation index, see [llms.txt](https://userguide.mburger.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.mburger.cloud/section-1/element-type/document.md).

# Document

The ***document*** element is used to add a document file to your block.

{% hint style="info" %}
It could be a downloadable PDF, text document, spreadsheet file, powerpoint, etc.
{% endhint %}

&#x20;The document element is intended for individual documents

{% hint style="warning" %}
if you need to use a packaged file (such as .zip, .ipa, .apk) use the File element&#x20;
{% endhint %}

Document element **properties**:

* **Required**: if selected, this element becomes required and cannot be left empty
* **Size**: exact dimension of file in bites (if needed)
* **Min**: minimum dimension of file in bites
* **Max**: maximum dimension of file in bites
* **In**: define the file format, e.g. .doc, .docx, .csv, .pdf, etc..


---

# 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:

```
GET https://userguide.mburger.cloud/section-1/element-type/document.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
