> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/fleet-management/garages.md). # Garages Create and manage garage (depot) profiles in Navixy, storing location, mechanic, and dispatcher details for better multi-site fleet coordination and reporting. Garages (also referred to as "Depots") in Navixy are crucial for organizations with larger fleets spread over multiple locations. They help organizing and managing fleet operations, such as dispatching operations, generating reports, and ensuring compliance with documentation requirements. Garage profiles contain detailed information about each garage, including the fleet owner, location, and key personnel such as mechanics and dispatchers. ## Garages tab The **Garages** tab provides comprehensive information about the garages within your organization. ### Adding a new garage To add a new garage, click the **Add garage** button. The garage profile includes essential details such as the garage’s name, address, and the names of the mechanic and dispatcher. This information is instrumental in improving task management and coordination across your fleet. --- # 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://navixy.com/docs/user/guide/fleet-management/garages.md?ask=&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.