> For the complete documentation index, see [llms.txt](https://inscada.gitbook.io/ins/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inscada.gitbook.io/ins/en-1/user-interface/reports.md).

# Reports

Using Reports, you can see, print, and set to automatically print the reports that you defined for your project. From the Settings menu, you can bring up the desired report of the selected project on the date you selected.

&#x20;

![Figure 1 : Reports](/files/-LOUg4YWTe82B8B5sZBj)

#### &#x20;Projects

The project is selected.

#### Reports

The report defined for the project is selected.

**Start Date**

The start date of the report is selected.

#### Scheduled

Enables automatic printing of the report from the default printer.

#### Print

Prints the report instantly from default printer.

#### Preview

Displays the report on the screen with given project, report, and date information.

{% hint style="info" %}
To understand the inSCADA report model, see the Reports section under Development.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://inscada.gitbook.io/ins/en-1/user-interface/reports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
