> For the complete documentation index, see [llms.txt](https://documentation.rcore.cz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.rcore.cz/paid-resources/rcore_shortcuts/permissions.md).

# Permissions

#### Ace Permissions

Its required to add those permissions in your server.cfg if you want to use ace permissions

```lua
add_ace resource.rcore_shortcuts command.add_ace allow
add_ace resource.rcore_shortcuts command.remove_ace allow
add_ace resource.rcore_shortcuts command.add_principal allow
add_ace resource.rcore_shortcuts command.remove_principal allow
```

If you want to use ace permissions you need to enable it in config.lua and then you could define roles for admin access in permissions.lua

```lua
Config.UseAcePermissions = true
```

All definitions and checks are located in server/api/permissions.lua. For default ESX/QBCore permissions we use cache for better performance.

Each action has its own permissions check in server/api/permissions.lua.

#### ESX/QBCore permissions

Groups for permissions are defined in config.lua

```lua
Config.AllowedGroups = {
    'superadmin', --ESX
    'admin', --ESX
    'god', --QBCore
}
```

This permissions are used only when ace permissions are disabled


---

# 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://documentation.rcore.cz/paid-resources/rcore_shortcuts/permissions.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.