> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/reporting-framework/reporting-framework-overview.md).

# Reporting Framework Overview

Using the Reporting Framework, Designer users can add customized reports to the LogicNets standard reporting package available on the main portal page.

### Standard Reports

With appropriate access rights, which you control through the User Management package, users can view a number of "audit-trail" type reports based on all user sessions. These are standard reports that are always available through the Reporting package. You can create any of the standard reports for all of your packages, for a specific one application, and for any range of dates. The reports include:

* Session overview. This contains a filterable summary table of session data, including start/finish time, duration, user, and package.
* Session logs. These are detailed event logs that show all triggers and data points logged by the system automatically. They also contain user-defined events created in a logicnet using the [Add Answer to Change Log](/release-9/platform-documentation/process-node-parts/add-answer-to-change-log.md) part.

Additionally, if you have the LogicNets third-party charting plug-in feature enabled in your account, you have the following charts available for you to view on screen or download as data, image, and PDF:

* Sessions per hour/day/month
* Sessions per package
* Sessions per user
* Users per package/role
* Total and average session time by user

### Customized Reports

Advanced Designers can add customized business reporting to the Reporting package. Broadly speaking the steps required to add a customized report include the following:

* Create a new project BASED on the Reporting Framework. The framework settings allow the Designer to specify a custom configuration logicnet.
* Create a data table or "view" in the resources/data folder that holds and updates the reporting data, if it is different from the existing session overview or session logs.
  * You can design the application with a logicnet that writes the appropriate business data to this data table.
* Add a logicnet into the *reports* folder. The system presents each logicnet as a custom report in the dropdown list of available reports.
* Generate the report using a dbgrid or summary tables or display chart node. See [Display Chart](/release-9/platform-documentation/form-node-parts/display-chart.md) for more information.

### Example

Download and import the example project into your Designer.


---

# 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://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/reporting-framework/reporting-framework-overview.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.