> 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/configuration/desks.md).

# Desks

Issuing desks in config/desks.lua - where issuers hand out badges.

A desk is a spot where issuers hand out badges: an ox\_target or qb-target zone, or the built-in `[E]` prompt. One desk can serve several badge types. For each badge it serves, the desk offers **Issue `<badge>` badge** and (with `Config.Issuing.AllowSelf`) **Issue my own `<badge>` badge**. Players only see the options for badges they may issue.

{% hint style="success" %}
**Easiest way:** stand on the spot, open `/badgestudio` → **Desks** → **+ Add desk here**. See [Badge Studio](/visionstore-docs/scripts/badges/guides/badge-studio.md#desks-tab).
{% endhint %}

## The included desks

```lua
Config.Desks = {
    mrpd = {
        label = 'Mission Row - Badge desk',
        coords = vec3(441.79, -981.98, 30.69),
        radius = 1.0,
        badges = { 'police', 'sasp', 'sheriff', 'fbi', 'doj' },
        blip = false,
    },

    pillbox = {
        label = 'Pillbox Hill - Badge desk',
        coords = vec3(307.95, -595.05, 43.28),
        radius = 1.0,
        badges = { 'ems', 'fire' },
        blip = false,
    },
}
```

The coordinates are the base-game interiors. Moved Mission Row or Pillbox to an MLO? Update them.

## Options

| Option    | Default      | Limit                         | Meaning                                                                                        |
| --------- | ------------ | ----------------------------- | ---------------------------------------------------------------------------------------------- |
| *(key)*   |              | `a-z`, `0-9`, `_`, 1-32 chars | The desk id.                                                                                   |
| `label`   | the id       | 48                            | Map blip name and prompt title.                                                                |
| `coords`  | **required** |                               | `vec3(x, y, z)`. A desk without valid coordinates is skipped.                                  |
| `radius`  | `1.0`        | 0.3-5.0 m                     | Size of the zone.                                                                              |
| `badges`  | `{}`         | 32                            | Badge ids this desk serves. An unknown id prints a warning.                                    |
| `blip`    | `false`      |                               | `true` = default blip, a table `{ sprite = 60, colour = 38, scale = 0.7 }`, or `false` = none. |
| `enabled` | `true`       |                               | `false` removes the desk without deleting it.                                                  |

Blip limits: sprite 1-1000, colour 0-85, scale 0.2-2.0. `blip = true` uses sprite 60, colour 38, scale 0.7.

## Distances

| Check                              | Distance                                                                   |
| ---------------------------------- | -------------------------------------------------------------------------- |
| ox\_target / qb-target interaction | 2 m from the zone                                                          |
| `[E]` prompt shows                 | Within the desk radius + 0.5 m                                             |
| Issuer position (server check)     | Desk radius + `Config.Issuing.DeskTolerance` (2.5 m)                       |
| Recipient                          | Nearest player within `Config.Issuing.NearestDistance` (3 m) of the issuer |

`Config.Debug = true` draws the ox\_target / qb-target zones so you can see them.


---

# 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/configuration/desks.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.