> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/settings/setup/documents.md). # Documents Review the documents your organization provided during the Anedot application in Settings > Setup > Documents, and learn how to send updated versions. **Documents** lists the supporting documents your organization provided during the Anedot application to verify its identity and eligibility. You'll find it in **Settings > Setup > Documents**. This article covers what the page shows and how to update a document. ## Before You Begin * To view Documents, you need **Account Management: Edit Account Details and Configuration** permissions. ## What The Documents Page Shows The page is read only. For each document, it shows: * **Document:** the document type, such as an IRS letter or articles of incorporation. * **File:** the file name. * **Size:** the file size. * **Status:** the review status. * **Link:** open the document. The document types shown depend on your organization's category, for example nonprofit, church or ministry, education, or political. ## Update A Document You can't upload or replace documents on this page. To send an updated version, contact our Support team at . ## Related Articles * [Setup](/settings/setup.md) * [What Do I Need to Apply for an Account?](/get-started/apply-for-an-account/what-do-i-need-to-apply-for-an-account.md) * [Organization Information & Account Ownership](/settings/setup/organization-information-account-ownership.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.anedot.com/settings/setup/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.