> For the complete documentation index, see [llms.txt](https://quannsstudios.gitbook.io/quannsstudio-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quannsstudios.gitbook.io/quannsstudio-docs/dealership-creator-v1/configuration.md).

# Configuration

***

**Configuration**

All configuration lives in `config.lua`.

**Options**

| Option                          | Description                                                   |
| ------------------------------- | ------------------------------------------------------------- |
| `Config.TestDriveTime`          | Test drive duration in minutes                                |
| `Config.MinDepositPct`          | Minimum deposit percentage for finance plans                  |
| `Config.PaymentIntervalMinutes` | Time between payment plan instalments in minutes              |
| `Config.PaymentPlans`           | Array of finance plan options with payments and interest      |
| `Config.Categories`             | Vehicle categories shown in the browse UI                     |
| `Config.Blips`                  | Blip sprite, color, and scale for each zone type              |
| `Config.Showroom.vehicleCoords` | `vector4` coordinates where the showroom vehicle spawns       |
| `Config.Showroom.camera`        | Camera presets including distance, height, and angle          |
| `Config.Showroom.rotationSpeed` | How fast the showroom vehicle rotates — set to `0` to disable |

**Setting Up a Dealership**

1. Log in as admin and run `/dealership`
2. Go to **Create Dealership**
3. Fill in the name and select categories
4. Use the **Set Pos** buttons to capture coordinates in-game — the UI closes, walk to the spot, press **E**
5. Set a **Required Job** to lock it to a specific job, or leave blank for public access
6. Enable the sell location if you want players to sell vehicles there
7. Save — blips will appear on the map automatically

***

**Adding Vehicles**

Single vehicle — Admin panel → Vehicles → Add Vehicle tab

Bulk import — Admin panel → Vehicles → Bulk Import tab, paste a JSON array:

json

```json
[
  { "spawn_name": "adder", "display_name": "Truffade Adder", "category": "super", "price": 1000000 },
  { "spawn_name": "zentorno", "display_name": "Pegassi Zentorno", "category": "super", "price": 725000 }
]
```

***

**Boss Menu**

Accessible at the Boss Menu location set on the dealership. Requires the player's job to match the dealership's required job.

| Feature      | Description                                                                |
| ------------ | -------------------------------------------------------------------------- |
| Hire         | Enter a player's server ID to hire them into the dealership job            |
| Fire         | Remove a player from the job — works on offline players                    |
| Set Grade    | Change an employee's grade from the dropdown                               |
| Society Fund | View balance, withdraw to bank, deposit from bank                          |
| Restock      | Spend society funds to restock vehicle stock at 15% of list price per unit |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://quannsstudios.gitbook.io/quannsstudio-docs/dealership-creator-v1/configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.