> For the complete documentation index, see [llms.txt](https://ayznnn.gitbook.io/waveshield-v4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ayznnn.gitbook.io/waveshield-v4/documentation/how-to/bypass-staffs.md).

# Bypass Staffs

We'll use **ace permissions** so that your staff can execute in-game commands or be bypassed on anticheat. You can use any identifier supported by FiveM (license, discord, steam, etc). You can also use groups (cf [FiveM Docs](https://docs.fivem.net/docs/server-manual/server-commands/#add_ace-principal-object-allowdeny)).<br>

{% hint style="warning" %}
However, we'd like to point out that you don't necessarily need to add the bypass to your staffs, as the **anticheat normally knows how to differentiate between actions performed by a staff or a cheater.**
{% endhint %}

Head to your server.cfg file, this is few examples on how you can add permissions to your staffs:

{% code title="server.cfg" %}

```
add_ace identifier.license:xxx "WaveShield.Commands" allow
add_ace identifier.steam:xxx "WaveShield.Bypass" allow
add_ace group.mod "WaveShield.Bypass" allow
```

{% endcode %}

| Permission Name       | Description                                                                            |
| --------------------- | -------------------------------------------------------------------------------------- |
| `WaveShield.Bypass`   | Bypasses the entire anticheat system. The person can't be banned.                      |
| `WaveShield.Commands` | The person will be able to execute the different commands in the chat (or F8 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ayznnn.gitbook.io/waveshield-v4/documentation/how-to/bypass-staffs.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.