> For the complete documentation index, see [llms.txt](https://zloma-scripts.gitbook.io/zloma-scripts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zloma-scripts.gitbook.io/zloma-scripts/zloma_vehicleshop-paid/features/admin-tools.md).

# Admin Tools

## Admin Access

Admin access is controlled by `Config.AdminGroups`.

Primary command:

* `/vehicleshopadmin`

Utility commands:

* `/fixshop` to recover a stuck client UI
* `/refreshshops` to reload dealership data from the database

***

## Salon CRUD

Admins can create, update, and delete dealerships without leaving the game.

Salon configuration includes:

* Shop name and label
* World location and heading
* Showroom position
* Vehicle spawn position
* Camera config
* Ped model and ped position
* Blip visibility and style
* Test drive coordinates
* Trade-in settings
* Job/grade restrictions
* Optional business settings

***

## Visual Editor Tools

The admin UI includes dedicated in-world helpers for precise placement.

Included tools:

* Location picker
* Vehicle spawn editor
* Showroom editor
* Ped/prop editor
* NPC chooser

These tools reduce manual coordinate editing and make dealership setup much faster than static config-based resources.

***

## Vehicle Management

Vehicle CRUD is salon-scoped.

Admins can configure:

* Spawn name / model
* Display label
* Category assignment
* Price range and active price
* Discount percent
* Stock values
* Default primary/secondary colors
* Showroom visibility
* Sort order
* Enabled state

***

## Category Management

Each salon can have its own category tree.

Category fields include:

* Name
* Sort order
* Icon

This allows luxury, import, bike, utility, emergency, or job-specific salons to stay fully separate.


---

# 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:

```
GET https://zloma-scripts.gitbook.io/zloma-scripts/zloma_vehicleshop-paid/features/admin-tools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.