> 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/readme/customization/custom-properties/add-custom-properties-to-images.md).
# Add custom properties to images
Add custom image properties - like date fields, text entries, and drop-down selections - based on your business needs.
1. Create a new report by clicking **New** > **Report**.\
2. Check the *Customize* box below the report description.\
3. A list of properties will appear. Click the **New** button in the *Item Properties* section on the right side of the screen. \
4. Choose the property type from the drop-down menu:
* *Text* for new text entry field
* *Choice* for a new drop-down selection
* *True and False* for a new true/false variable
* *Date* for a new date field
\
5. Add the title, description, and options. Click **Create**. \
6. Click **Update**.\
7. When you add a new image to the report, the custom properties you created will be available beneath the image description.\
8. In a published report, custom properties appear beneath an image. 
---
# 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/readme/customization/custom-properties/add-custom-properties-to-images.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.