> 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.md).

# Vision Badges Creator

Badges for any job. Design them in game, issue them at desks with a photo, and show them to nearby players.

**Vision Badges Creator** gives every job on your server a real badge: police, sheriff, EMS, fire, justice, press, your mechanic shop or your gang. Admins design badges in game with a live **Badge Studio**. Issuers hand them out at desks, with the recipient's photo taken on the spot. Players show them to everyone nearby as a leather wallet with a metal badge and a photo ID card.

{% hint style="success" %}
**Get it on the** [**Vision Store**](https://www.vision-store.site/) · Questions? [Join our Discord](https://discord.gg/ZvHtyhyBp4)
{% endhint %}

{% hint style="info" %}
**Version 1.0.0** · Qbox · QBCore · ESX · ox\_core · Standalone · OneSync · ox\_lib · oxmysql
{% endhint %}

## Features at a glance

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>🎨 Badge Studio</strong></td><td>Create, edit, duplicate and disable badges with a live preview. Save, and every player has the new version at once, with no restart.</td></tr><tr><td><strong>🛡️ 5 shapes, 6 metals</strong></td><td>Shield, federal eagle, sheriff star, fire cross and seal. Star, star of life, scales or your own logo in the centre. Gold, silver, bronze, gunmetal, black, rose gold or any colour.</td></tr><tr><td><strong>📸 Photo ID</strong></td><td>The recipient's photo is taken once when the badge is issued and stored with it. The issuer reviews it and can retake it.</td></tr><tr><td><strong>🏢 Issuing desks</strong></td><td>ox_target, qb-target or an [E] prompt. Stand on a spot and click "Add desk here". Choose the badges it serves and add a blip.</td></tr><tr><td><strong>🔢 Permanent numbers</strong></td><td>A person keeps their badge number for life. Badges can share a number pool (for example SWAT and police).</td></tr><tr><td><strong>👛 Show it off</strong></td><td>Use the item or /badge. Everyone close by sees the open wallet, the holder plays an animation with a badge prop.</td></tr><tr><td><strong>✅ Live validity</strong></td><td>Viewers see VALID, REVOKED, or INACTIVE when the holder left the job. Promotions void and remove the old badge.</td></tr><tr><td><strong>📚 Registry</strong></td><td>Search every badge ever issued by name, ID, number or serial. View it with its photo, revoke one or all of a person.</td></tr><tr><td><strong>🧩 Works with your stack</strong></td><td>Qbox, QBCore, ESX, ox_core or standalone. ox_inventory, qs-inventory, qb / ps / lj-inventory or no inventory. All auto-detected.</td></tr></tbody></table>

## How a badge gets issued

```mermaid
flowchart TD
    A[Admin creates the badge in the Studio or config/badges.lua] --> B[Issuer goes to a desk or uses /issuebadge]
    B --> C[Preparing progress bar]
    C --> D[Photo of the nearest player is taken]
    D --> E[Review panel: photo, number, rank]
    E -- Retake photo --> D
    E -- Confirm & issue --> F[Badge item given, number assigned]
    F --> G[Holder shows it with the item or /badge]
    G --> H{Status for viewers}
    H --> V[VALID]
    H --> R[REVOKED]
    H --> I[INACTIVE: left the job]
```

## Nine badges ready to use

| Badge id   | Department                     | Who receives it               | Who issues it                     |
| ---------- | ------------------------------ | ----------------------------- | --------------------------------- |
| `police`   | Los Santos Police Department   | `police`                      | `police` grade 3+                 |
| `sheriff`  | Blaine County Sheriff's Office | `sheriff`, `bcso`             | grade 3+                          |
| `sasp`     | San Andreas State Police       | `sasp`, `trooper`             | grade 3+                          |
| `fbi`      | Federal Investigation Bureau   | `fbi`, `fib`                  | grade 3+                          |
| `ems`      | Los Santos Medical Services    | `ambulance`, `ems`            | grade 3+                          |
| `fire`     | Los Santos Fire Department     | `fire`, `lsfd`, `firefighter` | grade 3+                          |
| `doj`      | Department of Justice          | `judge`, `lawyer`, `doj`      | any `judge`, `doj` grade 2+       |
| `press`    | Weazel News                    | `reporter`, `weazel`          | any `reporter`, `weazel` grade 2+ |
| `mechanic` | Los Santos Customs             | `mechanic`                    | `mechanic` grade 4+               |

Change them, disable them or add your own: see [Badge types](/visionstore-docs/scripts/badges/configuration/badges.md).

## Where to go next

| I want to...                                 | Go to                                                                  |
| -------------------------------------------- | ---------------------------------------------------------------------- |
| Install the script                           | [Installation](/visionstore-docs/scripts/badges/installation.md)       |
| Issue my first badge in 5 minutes            | [Quick start](/visionstore-docs/scripts/badges/quick-start.md)         |
| Change badges, desks, colours, timings...    | [Configuration](/visionstore-docs/scripts/badges/configuration.md)     |
| Learn how admins, issuers and players use it | [Guides](/visionstore-docs/scripts/badges/guides.md)                   |
| Hook it into my own scripts                  | [Developers](/visionstore-docs/scripts/badges/developers.md)           |
| Fix a problem                                | [Troubleshooting](/visionstore-docs/scripts/badges/troubleshooting.md) |


---

# 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.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.