> For the complete documentation index, see [llms.txt](https://prisma-logs.gitbook.io/prisma-logs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prisma-logs.gitbook.io/prisma-logs/docs/en/readme.md).

# Welcome

Everything about Prisma Logs, the logs for your FiveM server.

Prisma Logs logs everything that happens on your FiveM server and puts it in a clear web panel. You add one resource to your server and the rest happens by itself: the categories are created, your scripts are scanned and logs arrive within seconds.

## What you get

* **12 built-in logs.** Joins and leaves, chat, deaths, money, jobs, items (including trunks, gloveboxes and stashes), vehicles, explosions, spawned entities, resources and txAdmin actions.
* **Script scan.** The resource reads your scripts, finds every action players can trigger and logs it. Your scripts are never changed.
* **A panel you can search.** Search a player, license, item or plate, pick a period and filter per script with one click.
* **Discord.** Add a webhook to a category and its logs also land in your Discord channel.
* **For your whole staff.** Invite admins with their Discord account. They see the logs, only you manage the server.

## Works with

| Framework / resource | What gets logged                                                                                                                                       |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| ESX Legacy           | money, jobs, items, character loading                                                                                                                  |
| QBCore / Qbox        | money, jobs, character loading and unloading                                                                                                           |
| ox\_inventory        | moving items, trunks, gloveboxes, stashes, buying, crafting                                                                                            |
| txAdmin              | kick, warn, ban, heal, DM, announcement, restart                                                                                                       |
| baseevents           | deaths, kills, entering and leaving vehicles                                                                                                           |
| Any other script     | through the [script scan](/prisma-logs/docs/en/configuration/script-scan.md) or [your own events](/prisma-logs/docs/en/configuration/custom-events.md) |

## Start right away

Follow the [quick start](/prisma-logs/docs/en/getting-started/quick-start.md): your first logs are in your panel within five minutes.


---

# 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://prisma-logs.gitbook.io/prisma-logs/docs/en/readme.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.