# Custom Reports

The <mark style="color:$success;">**Custom Reports**</mark> feature allows MSSPs and end users to automatically extract structured data from Inopli, focusing on <mark style="color:$success;">**Incidents**</mark> and <mark style="color:$success;">**Requests**</mark>. It ensures full data portability, enabling the export of all relevant records from the platform whenever needed, supporting external analytics, billing, compliance, and audit purposes.

**What It Does**

* <mark style="color:$success;">**Automates data export**</mark>**:** schedules recurring reports so incident and request data is generated without manual CSV/Excel exports.
* <mark style="color:$success;">**Scopes the dataset**</mark>**:** lets you select the <mark style="color:$success;">**company**</mark> and **reference period** that should be included in each report.
* <mark style="color:$success;">**Defines frequency**</mark>**:** supports <mark style="color:$success;">**daily, weekly**</mark>, or <mark style="color:$success;">**monthly**</mark> generation at a specific time, aligning exports with operational and reporting routines.
* <mark style="color:$success;">**Notifies stakeholders**</mark>**:** sends a notification with the generated report to the configured recipients, using the chosen subject for easy identification.
* <mark style="color:$success;">**Controls the schema**</mark>**:** provides a column selector where you choose the <mark style="color:$success;">**type**</mark> (*Incidents* or *Requests*) and the fields to include, such as `id`, `name`, `severity_name`, `status_name`, `created_at`, `updated_at`, `sla_expiration_time`, and `closed_at`.

**How It Works**

* In <mark style="color:$success;">**Report Info**</mark>, activate the report, select the <mark style="color:$success;">**Company**</mark>, choose the <mark style="color:$success;">**Period**</mark> you want to export, and add a short <mark style="color:$success;">**Description**</mark> to identify the purpose of that report.
* In <mark style="color:$success;">**Frequency**</mark>, choose whether the report will run <mark style="color:$success;">**Daily, Weekly**</mark>, or <mark style="color:$success;">**Monthly**</mark>, and set the exact time (and day, when applicable) for generation.
* In <mark style="color:$success;">**Sent notification to**</mark>, define the <mark style="color:$success;">**Subject**</mark> and add the <mark style="color:$success;">**Recipients**</mark> who should be notified every time the report is generated.
* In <mark style="color:$success;">**Columns**</mark>, set the <mark style="color:$success;">**Type**</mark> (e.g., *Incidents*) and select the fields that will compose each row of the export, tailoring the dataset to the consuming system or audience.

<figure><img src="/files/JZlWEFE6ty9R7Dm7uoCM" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/2HaGHtODcx2R9htMhLFt" alt=""><figcaption></figcaption></figure>

**Why This Matters**

Because the exported data contains the <mark style="color:$success;">**entire treatment trail of incidents and requests**</mark>, each generated file can also serve as a <mark style="color:$success;">**complete audit trail export**</mark>, providing traceability over every recorded action, update, and resolution stage.

This capability ensures that operational data stored in Inopli does not remain locked inside the platform. By automating the export of incidents and requests with precise control over scope, frequency, and schema, organizations can integrate Inopli data into BI tools, client reporting, audit processes, and long-term records, maintaining full visibility and ownership over their security operations data.


---

# Agent Instructions: 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:

```
GET https://docs.inopli.com/response/custom-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.