> For the complete documentation index, see [llms.txt](https://visionstore.gitbook.io/visionstore-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visionstore.gitbook.io/visionstore-docs/scripts/badges/guides/commands-and-keys.md).

# Commands and keys

Every command and key binding on one page.

## Commands

| Command                      | Who                                                     | What it does                                                                                         | Setting                      |
| ---------------------------- | ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ---------------------------- |
| `/badgestudio`               | Admins                                                  | Opens the Badge Studio                                                                               | `Config.Admin.studioCommand` |
| `/badge`                     | Everyone                                                | Shows a badge you carry (menu when you carry several)                                                | `Config.Present.Command`     |
| `/issuebadge <badge> [self]` | Admins (or every issuer with `Command.anywhere = true`) | Issues a badge without a desk. `self` or `me` = your own. No argument lists the badges you can issue | `Config.Issuing.Command`     |

Each command can be renamed, or turned off with `false`.

## Keys

| Key           | Action                 | Where                                                                                                                 |
| ------------- | ---------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Backspace** | Put the badge away     | Default of `Config.Present.CloseKey`. Players can rebind it in Settings → Key Bindings → FiveM ("Put the badge away") |
| **E**         | Open the desk prompt   | Only when no ox\_target / qb-target is running                                                                        |
| **ESC**       | Close the Badge Studio | Asks before throwing away unsaved changes                                                                             |
| **Enter**     | Search the Registry    | In the Studio's Registry tab                                                                                          |

## Permissions

| Ace / setting                                        | Grants                                                         |
| ---------------------------------------------------- | -------------------------------------------------------------- |
| `vision_badges.admin` (`Config.Admin.ace`)           | Admin: Badge Studio, issue every badge, `/issuebadge` anywhere |
| `Config.Admin.groups` (`admin`, `god`, `superadmin`) | The same, through your framework's admin groups                |
| `vision_badges.job.<name>`                           | Standalone only: gives the player that job (grade 0)           |

```properties
add_ace group.admin vision_badges.admin allow
```


---

# 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://visionstore.gitbook.io/visionstore-docs/scripts/badges/guides/commands-and-keys.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.