> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/mobile/add-files-notes-and-access-info.md).

# Add files, notes, and access info on mobile

Technicians can add context from the field without returning to the office.

## Notes and access info

Use the edit icon beside Notes or Access Info to update property notes or entry instructions. Notes are for general property context. Access Info is for practical entry details such as gate codes, lockboxes, or site access instructions.

## Files

The Files section has tabs for Job Files and Property Files. Tap Add to upload a file or photo to the active tab. Job files stay with the job. Property files stay with the property and can carry visibility settings for who can see them. Generated files from inspection reports and work acknowledgments cannot be deleted from the normal file list.

> **Where to find it:** Mobile app > Visits > visit detail

## Related guides

* [Add and name photos in the mobile app](/field-operations/mobile/add-and-name-photos.md)
* [Open a visit in the mobile app](/field-operations/mobile/open-a-visit.md)
* [Add a visit summary on mobile](/field-operations/mobile/add-a-visit-summary.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://learn.withessential.com/field-operations/mobile/add-files-notes-and-access-info.md?ask=<question>&goal=<user_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.