# Documents and files For projects to be eligible for registration, they need to upload documentation. There is further difference in what documentation is required for different stages. Please refer to ICR process requirements for details about necessary documentation for different project statuses. From the project home screen or the project side panel, you choose **Documents and files**. {% embed url="" %} Documents and files {% endembed %} ### Documents When you enter the Documents tab, you'll see multiple options.

From the upload button, you select the type of document you want to upload. {% embed url="" %} From the upload window, you need to disclose the type of document you're uploading.

From the upload screen you select the document type and then select if the document is a draft document or a final document. Then you select if the document is a private or public document. When you have provided the basic info you either drag and drop the file to the upload field or browse for it in your file explorer. When you have selected the file you need to apply a file name to the document. {% hint style="info" %} Please consider file name guidelines from template documents. {% endhint %}

From the documents overview you can manage your documents (until validation). Amend them, upload new versions and other documents. Also you can manage if documents are publicly available or not. {% hint style="info" %} Some documents need to be publicly available, while they're in draft they may be private for some stages. {% endhint %} --- # Agent Instructions: 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://documentation.carbonregistry.com/documentation/carbonregistry.com/registry-user-guide/project-proponents-and-developers/registering-a-project/create-a-new-project/documents-and-files.md?ask= ``` 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.