> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigiflow/entering-and-structuring-data-in-reports/attaching-additional-documents-to-a-report.md). # Attaching additional documents to a report In the “**`Report information`**” section, you can upload documents under the “**`Documents`**” tab. {% embed url="" %} 1. Name the document with an appropriate description. 2. Click the :paperclip: icon. 3. Select the file. Supported file types include: .pdf, .jpeg, .jpg, .txt, .rtf, .tiff, .tif, .html, .doc, .docx, .xls, .xlsx, .dicom, .png, .htm, .dcm. The total attachment size for **each report** is 15 MB. These documents are part of the report but are not searchable. You need to check the “Additional documents” section to see if there are any documents in a report. Some organisations add information about additional documents in the case narrative. --- # 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://support.who-umc.org/vigiflow/entering-and-structuring-data-in-reports/attaching-additional-documents-to-a-report.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.