> For the complete documentation index, see [llms.txt](https://help.visuary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.visuary.com/guide-visuary-en/data/files.md).
# Files
To add files to your project:
1. Click the "**Files**" located on the right side of the screen
2. Click the "**Add a file**".
3. Click the "All" drop-down menu to filter files by:
* Photos
* Documents
* Comment photos
To download these items, click the photo or file icon.
#### Download a comment photo
{% embed url="" %}
To download a photo, whether it was added during the Scan or later:
1. Click on **Files** on the right side of the screen
2. **Click the image you want to download;** the image file downloads instantly.
View all project information
{% embed url="" %}
Enter project information
{% endembed %}
To add and view project information:
1. From the "Projects" page, **click on a project name**.
2. In the "**Details**" you can fill in:
* The project name
* The project address
* The client name: click the "+" icon to add it
3. In the "**Attachments**", you will find all the files linked to the project
1. To add files, click the "Add a file" button
4. To save, click the **save icon located in the "Details" tab**
The project information will automatically appear on the "Project description" page in the PDF report (available with Intégral)
Share files with your collaborators
To share files with your collaborators:
1. Click the **3 dots** located at the top right of the screen
2. Click "**Share**"
3. In access rights, **check the "View attachments" box**
---
# 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.visuary.com/guide-visuary-en/data/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.
