> For the complete documentation index, see [llms.txt](https://docs.lenoscripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenoscripts.com/scripts/lenoreports/overview.md).

# Overview

Features, supported frameworks, and the LenoReports ticket workflow.

LenoReports provides an in-game ticket system for players and staff. Reports, messages, participant snapshots, and history are stored in the server database.

## Features

| Area             | Purpose                                                                                                |
| ---------------- | ------------------------------------------------------------------------------------------------------ |
| Player reports   | Create a ticket with category, subject, description, and involved players                              |
| Staff queue      | Review open reports grouped as Mine, Unclaimed, and Others                                             |
| Ticket workflow  | Claim, unclaim, chat, manage participants, and close reports                                           |
| Player snapshots | Capture player data for investigation, including players near the author                               |
| Screenshots      | Capture evidence with `screenshot-basic` and upload through the configured Discord images webhook      |
| Staff actions    | Goto, bring, freeze, and unfreeze when enabled                                                         |
| Staff chat       | A separate staff conversation, mentions, and an on-duty roster                                         |
| History          | Closed reports for staff and the player's own authored reports                                         |
| Statistics       | Report counts, response/resolution metrics, and staff activity for today, 7 days, 30 days, or 6 months |
| Integrations     | Public exports, server lifecycle events, and editable hooks                                            |

## Frameworks

| Framework | Resource      |
| --------- | ------------- |
| ESX       | `es_extended` |
| QBCore    | `qb-core`     |
| QBox      | `qbx_core`    |

`Config.Framework = 'auto'` selects a supported framework that has already started.

## Where to start

* Server owners: [Installation](/scripts/lenoreports/installation.md), [Configuration](/scripts/lenoreports/configuration.md), and [Customization](/scripts/lenoreports/customization.md).
* Players and staff: [User Guide](/scripts/lenoreports/user-guide.md) and [Commands](/scripts/lenoreports/commands.md).
* Developers: [Exports and Events](/scripts/lenoreports/exports-and-events.md).
* Problems during setup: [FAQ / Troubleshooting](/scripts/lenoreports/faq-troubleshooting.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 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://docs.lenoscripts.com/scripts/lenoreports/overview.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.