> 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/faq/c150/c155/q489.md).

# How do I create a new report template with custom fields?

You can create a report template with custom fields in the Report and Run: Cloud web portal. 

1. [Create a report template](/manual/readme/customization/report-templates/create-a-new-report-template.md) and check the *Customize* box. 
2. Add existing custom fields or create a new field from this screen. 
3. The template you create in the web portal will then [show as an option](/manual/report-and-run-integrate/content/reports/create-a-report-from-template.md) in the Report and Run: Integrate mobile app. 

The report template feature is not available in the offline app. 

## Related

* [Article: Create a new report template in Report and Run: Cloud](/manual/readme/customization/report-templates/create-a-new-report-template.md)
* [Article: Convert an existing report into a template in Report and Run: Cloud](/manual/readme/customization/report-templates/convert-an-existing-report-into-a-template.md)
* [Article: Create a report from a template in Report and Run: Integrate](/manual/report-and-run-integrate/content/reports/create-a-report-from-template.md)
* [FAQ: How do I save commonly used text so that I don't have to type it each time?](/manual/faq/c150/c155/q488.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/faq/c150/c155/q489.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.