> For the complete documentation index, see [llms.txt](https://docs.av-scripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.av-scripts.com/guides/dealerships/admin-panel/creator.md).

# Creator

To create a new Dealership click the button **Create Dealership** in the Dealerships tab, the creator menu will show up:

<figure><img src="/files/H8cynQikA66UKylZi68U" alt=""><figcaption><p>Creator Panel</p></figcaption></figure>

* **Dealership Name\*:** How the dealership is named and what players will see in the blip map.
* **Authorized Job:** Linked job to the dealership, will be able to interact with the management menu.
* **Blip Sprite\*:** <https://docs.fivem.net/docs/game-references/blips/#blips>
* **Blip Color\*:** <https://docs.fivem.net/docs/game-references/blips/#blip-colors>
* **Starting Funds:** Give the dealership a little boost so they can get some stock.
* **Buy/Sell Pre owned vehicles:** Allow the dealership to access the Pre Owned tab and print contracts to buy other players vehicles.
* **Dealership Zones:** If a zone is missing the script will detect it and print a warning, example: If you don't set the Truck Spawn zone, when players try to start an order they will receive a notification of missing zone. Make sure to add all the zones you need.

> When adding a new zone, you will be able to preview where the vehicle will spawn, use your Right/Left Arrow key to rotate it.

<figure><img src="/files/KZrkTjyvNbXYhpanARCv" alt=""><figcaption><p>Setting the Truck spawn zone</p></figcaption></figure>

> For the showroom zones you can use Up/Down arrow keys to change the vehicle model.

<figure><img src="/files/BmcpsKczOzqkyrIDDhf3" alt=""><figcaption><p>Showroom setup</p></figcaption></figure>

> You can TP to each zone or remove it if needed by expanding the zone type.

<figure><img src="/files/y5d2L9nEwgukplauR9un" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
To delete a zone you need to double click.
{% endhint %}

> When creating an interaction zone you need to place the marker in an object until it turns green

<figure><img src="/files/UYtZpu80zjwCafVC2x1G" alt=""><figcaption></figcaption></figure>

> After placing the marker a red box will render, use the controls to place it correctly.

<figure><img src="/files/l8stYcTIbpX3iLE0ARfk" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
If you're using a target system like qb-core or ox\_target, the zone will NOT work unless the box is colliding with an object. Make sure NOT to place it in the air.
{% endhint %}

> Click the checkbox and confirm button when everything is ready and setup.

<figure><img src="/files/ogR7HQgU7xWrhsZjDsqG" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
***Don't worry if you are missing some zones, you can always edit the Dealership info and zones.***
{% endhint %}


---

# 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://docs.av-scripts.com/guides/dealerships/admin-panel/creator.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.
