> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/tracking-context/files.md). # Files Contracts, decks, order forms — the documents behind a relationship usually end up in someone's inbox. The **Files** tab on every company, contact and deal is where they should end up instead, with a count in its header. ## Uploading **Upload files** attaches one or more files from your computer to the record you are on, visible to everyone in the workspace. You can also have them arrive by themselves: an [agent](/features/agents.md) with the **Save email attachments** action copies attachments off a synced email onto the company, contact or deal, which is how signed contracts get from your inbox onto the account without anyone thinking about it. ## Previewing and managing a file Click a file to preview it — PDFs page by page, images inline, with **Load full document** for a large PDF. The sidebar shows the file type, dimensions where they apply, size, and a free-form **Description**. The **⋯** menu offers **Rename**, **Download** and **Delete file**. ## Files and AI An attached file is part of the record, which means it can be asked about. * **Chat** lists a record's files and reads PDFs and images to answer questions about them. **Attach files** in the composer sends one along with your message. * **MCP** — `find_files` lists what is attached, `read_files` reads PDFs and images. See [Zero's MCP server](/developers/mcp.md). * **REST API** — `GET /api/files`, and `POST /api/files/upload` for a multipart upload. See [API](/developers/api.md). --- # 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.zero.inc/tracking-context/files.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.