> 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/inspection-reports/link-a-report-photo-question-to-an-asset-photo-attribute.md).

# Link a report photo question to an asset photo attribute

A photo question on an inspection report form can be linked to a **Photo** or **Photos** attribute of the asset type, the same way a text question links to a text attribute. Linking turns a one-off report picture into a picture the asset keeps.

> **Where to find it:** Linking is set up in the report form, not while filling in a report. To add or change a link, open the Essential Assistant and choose the **Talk to a human** tab. Name the photo question and the asset attribute it should fill.

## How a linked photo question behaves

* **Prefill.** When a technician opens the report, each asset's question already shows the photos stored on that asset.
* **Capture.** The technician can keep those photos, replace them, or add more.
* **Publish.** When the report is published, the question's photos become the asset's saved photos. Photos removed on the report are removed from the asset; photos added on the report are added to it. Only pictures are saved to the asset, up to the attribute's limit (one for **Photo**, ten for **Photos**, the first ten in the question's order). Videos, and any photos past the limit, stay on the report only. A question that holds only videos leaves the asset's photos as they were.
* **PDF.** The rendered report prints the question's photos exactly as an unlinked photo question would.

A linked question needs a matching attribute type: a single-photo question links to a **Photo** attribute and a multiple-photo question links to a **Photos** attribute. A photo question can't be linked to a text attribute, or a text question to a photo attribute.

## Before you start

* The asset type must have a **Photo** or **Photos** attribute. See [Add photos to an asset (photo attributes)](/field-operations/assets/add-photos-to-an-asset-photo-attributes.md).

## Link the question

1. Open the Essential Assistant and choose the **Talk to a human** tab.
2. Say which report form and which photo question (inside an asset list) should be linked, and which **Photo** or **Photos** attribute it should fill.
3. Once the updated form is published, new reports prefill the question from each asset.

Bulk answer does not offer a linked photo question, and a linked photo question is not available as a filter in the report's asset list.

## Related guides

* [The field types you fill in on a report](/field-operations/inspection-reports/the-field-types-you-fill-in-on-a-report.md)
* [Answer a question on many inspection assets at once](/field-operations/inspection-reports/answer-a-question-on-many-inspection-assets-at-once.md)
* [Add photos to an asset (photo attributes)](/field-operations/assets/add-photos-to-an-asset-photo-attributes.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/inspection-reports/link-a-report-photo-question-to-an-asset-photo-attribute.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.
