> For the complete documentation index, see [llms.txt](https://docs.vames-store.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vames-store.com/assets/vms_cityhall/faq.md).

# FAQ

Below you’ll find answers to the most frequently asked questions related to setup, usage, and integration. We recommend checking this section before opening a support ticket.

***

<details>

<summary>Do I have to use all the options from City Hall?</summary>

No, you don't have to use all the options coming from City Hall, you can customize the displayed sections using config.lua or you can even split each section into a different interaction space.

</details>

<details>

<summary>Do I need to use Invoices and Tickets?</summary>

No, if you don't want to use our ticketing system and invoices, you can opt out of them by setting up a `Config.UseBillings = false` in config.lua.

</details>

<details>

<summary>Is the VIN required on vehicles?</summary>

Yes, VIN is the base value by which we manage vehicles, through it will be available the history of vehicle owners, re-registrations and much more.

</details>

<details>

<summary>Do I also have an SSN on the QB-Core?</summary>

No, on qb-core we decided not to introduce the SSN requirement, instead we use the already built-in citizenid, which is also fully supported by vms\_cityhall.

</details>

<details>

<summary>Can I use the tax and resume system in other scripts?</summary>

Yes, you can use the tax system and get resumes from citizens, but you'll need **vms\_bossmenu** for that, which is a very extensive boss menu for companies and gangs.

However, in our scripts - vms\_vehicleshopV2, vms\_stores, vms\_tuning, vms\_gym, vms\_barber, vms\_tattooshop is also built-in tax and resumes compatibility, this means that in the above scripts you do not need to use vms\_bossmenu.

</details>


---

# 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.vames-store.com/assets/vms_cityhall/faq.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.