> 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/pt-br/faq/c150/c155/q485.md).

# Como posso adicionar um número ou identificador personalizado às fotos nos meus relatórios?

Na versão em nuvem do aplicativo, você pode criar [campos de imagem personalizados](https://docs.reportandrun.com/manual/pt-br/readme/customization/custom-properties/add-custom-properties-to-images.md), como entrada de texto e itens de lista suspensa, no portal da web, e as configurações serão transferidas para o aplicativo móvel. Essas propriedades podem ser usadas para atribuir um número ou identificador exclusivo às imagens do relatório.&#x20;

## Relacionado&#x20;

* [Artigo: Adicione propriedades personalizadas às imagens no Report and Run: Cloud](https://docs.reportandrun.com/manual/pt-br/readme/customization/custom-properties/add-custom-properties-to-images.md)
* [Perguntas frequentes: Posso editar a data, a hora ou o texto dos meus relatórios depois que eles tiverem sido criados?](https://docs.reportandrun.com/manual/pt-br/faq/c150/c153/q450.md)
* [Perguntas frequentes: Como adiciono coordenadas GPS às fotos e aos relatórios no aplicativo?](https://docs.reportandrun.com/manual/pt-br/faq/c150/c153/q465.md)
* [Perguntas frequentes: Posso destacar detalhes nas fotos dentro do relatório?](https://docs.reportandrun.com/manual/pt-br/faq/c150/c154/q472.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://docs.reportandrun.com/manual/pt-br/faq/c150/c155/q485.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.
