> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-patienttransport/configuration/wheelchair-access.md).

# Wheelchair Access

Anyone can sit in a wheelchair. Pushing it is for EMS. The brakes and folding it back into the inventory are for EMS and for players EMS gave access to, for example a patient who uses a wheelchair for their character.

EMS opens the menu with `/wheelchairaccess`:

* **Give Access to a Nearby Player**: players within 5 m, access is permanent
* **Manage Given Access**: everyone with access, online or not, and who gave it

Access is saved by character (citizenid on Qbox and QBCore, identifier on ESX) and survives restarts.

```lua
-- config/cfg_wheelchair.lua
permissions = {
    enabled = true,               -- EMS can give players permanent brake and inventory access
    command = 'wheelchairaccess', -- command that opens the access menu
    grantDistance = 5.0,          -- max distance to the player getting access (m)
},
```

## Brakes

With the brakes locked, the wheelchair cannot be driven. When the brakes are released, the player sitting in it gets the keys and can drive it. Keys are given with the `vehiclekeys:client:SetOwner` event (qb-vehiclekeys, qbx\_vehiclekeys). For another key script, set `Config.GiveKeys` in `config/config.lua`.


---

# 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://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-patienttransport/configuration/wheelchair-access.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.