> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/essentials/documents.md). # Documents

IN THIS ARTICLE Attach documents to your FieldDoc records to different folders in your portfolio. *** ## Documents The **Documents** feature in FieldDoc allows users to upload and store important files within a **Project**, **Pact**, or **Activity**. This centralizes documentation so that relevant materials—such as reports, designs, permits, or data sheets—are easily accessible to all collaborators working on a project. Documents uploaded to a record are only visible to users with access to that specific record, helping ensure that sensitive or project-specific information remains secure. This feature is especially helpful for teams that need to share reference materials or maintain a clear record of supporting documentation over the lifecycle of a project. To add a document, navigate to the **Documents** tab of your chosen record and click the upload button. Supported file types include common formats such as PDF, DOCX, XLSX, and more. --- # 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://help.fielddoc.org/essentials/documents.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.