> 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/issuing-badges.md).

# Issuing badges

For job leaders and HR - hand out badges at a desk, take the photo and re-issue after a promotion.

{% hint style="info" %}
This page is written for **issuers**: the job leaders and HR staff allowed to hand out a badge. Feel free to link it in your departments' Discords.
{% endhint %}

## Who can issue

You can issue a badge when **one** of these is true:

* you're a server admin;
* your character id is on the badge's list of issuer ids;
* your **active** job is one of the badge's issuers and your grade matches (for example grade 3 and above);
* your gang is one of the badge's issuers and your grade matches.

Some badges also require you to be **on duty**. Holding several jobs? Switch to the right job first: other jobs don't count for issuing.

## Issue a badge at a desk

1. Go to a badge desk (for example the Mission Row front desk for police badges).
2. Have the person stand **close to you** (within 3 m). The badge goes to the **nearest** player.
3. Pick **Issue `<badge>` badge** (target option or `[E]` prompt).
4. A short "Preparing the badge..." bar runs. Your character plays an animation.
5. The recipient's photo is taken and the **review panel** opens:
   * check the name and the photo: is it the right person?
   * **Retake photo** if it isn't good;
   * "Current badge no." shows their existing number, or "Assigned on issue" for a first badge;
   * the rank comes from the framework.
6. Click **Confirm & issue**. The recipient gets the badge item and sees it once on screen.

{% hint style="warning" %}
The review panel stays open for 60 seconds. If the recipient walks away (more than 1 m beyond the 3 m range), the badge isn't issued.
{% endhint %}

## Your own badge

Pick **Issue my own `<badge>` badge** at the desk. You must hold one of the badge's jobs yourself, even as an admin.

## Without a desk

Admins (or every issuer, if the server allows it) can type:

```
/issuebadge police          -- to the nearest player
/issuebadge police self     -- your own
/issuebadge                 -- lists the badges you can issue
```

## Promotions and lost badges

Just issue the badge again. The new badge:

* keeps the person's **badge number** (numbers are for life);
* prints the new **rank**;
* **voids** their older badge of the same type and takes it out of their inventory.

A re-issue with the **same rank** while they still carry a valid badge is refused ("They already carry a valid badge with the same rank.").

## When someone leaves the job

Nothing to do: their badge shows **INACTIVE** to everyone as soon as they no longer hold the job. To void a badge for good, ask an admin to **Revoke** it in the Registry.


---

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