> For the complete documentation index, see [llms.txt](https://docs.morpheusemulator.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.morpheusemulator.com.br/dashboard/logs-and-audit.md).

# Logs and audit

**Logs & Audit** is the append-only history of the critical actions on your server: who started or stopped a service, who saved which file, who created or restored a backup, and more. Entries cannot be edited or deleted afterwards, so you always have a trustworthy record of what happened.

## Reading the audit list

Open **Logs & Audit** in the sidebar. The **Audit** card shows the most recent entries (up to the last 500), newest first, and a header like `128 entries` with a chip per category (`files · 54`, `service · 30`, `backup · 4`…).

Each entry shows:

| Part          | Meaning                                                                                                                     |
| ------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Category chip | The first part of the action, e.g. `files`, `service`, `editor`, `backup`, `token`, `auth`, `user`.                         |
| Action        | What happened, e.g. `files.write`, `service.start`, `backup.restore`.                                                       |
| Actor         | The account (e-mail) that did it.                                                                                           |
| **target**    | What it was done to: a file path, a service name, a backup ID…                                                              |
| Time          | When it happened.                                                                                                           |
| Risk pill     | **Low risk** for normal actions; **High risk** when the action was **rejected** (for example a save blocked by validation). |

### Common actions

| Action                                                                  | Meaning                                          |
| ----------------------------------------------------------------------- | ------------------------------------------------ |
| `files.write`                                                           | A file was saved (File editor or Configuration). |
| `editor.doc.write`                                                      | A visual editor saved its files.                 |
| `service.start` / `service.stop` / `service.restart` / `service.reload` | Service control from the dashboard.              |
| `backup.create` / `backup.restore` / `backup.diff`                      | Backups created, restored or compared.           |
| `server.logo.*`                                                         | Server logo changed or removed.                  |
| `auth.login`                                                            | A sign-in to the panel.                          |
| `user.*`                                                                | Account changes (profile, 2FA reset, AI access). |
| `clienthub.pending.cancel`                                              | A pending client update was cancelled.           |

## Searching

Type in the **top bar search box** (`Filter services, files, logs...`). The list is filtered as you type — by action, actor, target or any text in the entry — and the header shows **filtering "\<text>"**. If nothing matches: **No entry matches "\<text>".**

Examples:

* `GameServer/Data/Custom` – every change in the custom folder.
* `restore` – every restore.
* `staff@` – everything done by a staff account.

## Tamper protection

The **Hash chain** card explains how the audit protects itself: every entry carries a fingerprint computed from the previous entry plus its own content. Changing or removing a single line breaks the chain, which makes tampering detectable.

## Using the audit day to day

* **After an incident**: search for the file or service involved to see who changed what, then compare or restore from [Backups and restore](/dashboard/backups-and-restore.md).
* **Staff review**: filter by a staff member's e-mail to review their changes.
* **Before a big update**: check that no unexpected changes happened since the last backup.

{% hint style="success" %}
Give each person their own account. Shared accounts make the audit useless, because every action appears under the same name.
{% endhint %}

## Related pages

* [Server logs](/dashboard/server-logs.md) – the log files written by the MuServer programs themselves (game events, connections, hacks).
* [Server dashboard](/dashboard/server-dashboard.md#morpheus-gameserver-console) – live GameServer console.


---

# 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://docs.morpheusemulator.com.br/dashboard/logs-and-audit.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.