> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/report-and-run-integrate/content/images/add-edit-image-properties.md).
# Add/edit image properties
Assign properties to images, such as Assigned To and Due Date, to organize and add detail your reports.
1. Tap on a report to open it.
2. Tap on the image where you want to add or change the properties.
3. Scroll down to the *Properties* section.
4. Tap the property you want to edit. In the example below, *Assigned To* will be edited.
5. Adjust the property as needed and tap **Save**.
6. Your changes will appear on the report item detail screen.
{% hint style="info" %}
Properties with dates/times, such as *Due Date* and *Start Date*, will have calendar and clock icons you can tap to adjust. Some properties, like *Status*, will have a drop-down selection. Others, like *Assigned To*, allow text entry.
{% endhint %}
---
# 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.reportandrun.com/manual/report-and-run-integrate/content/images/add-edit-image-properties.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.
