> 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/id/guide/fleet-management/garages.md).

# Garasi

Buat dan kelola profil garasi (depot) di Navixy, simpan detail lokasi, mekanik, dan dispatcher untuk koordinasi armada multi-lokasi dan pelaporan yang lebih baik.

Garasi (juga disebut "Depo") di Navixy sangat penting bagi organisasi dengan Armada yang lebih besar dan tersebar di berbagai lokasi. Garasi membantu mengatur dan mengelola operasi armada, seperti operasi penugasan, menghasilkan Laporan, dan memastikan kepatuhan terhadap persyaratan dokumentasi.

Profil garasi berisi informasi rinci tentang setiap garasi, termasuk Pemilik Armada, lokasi, dan personel kunci seperti mekanik dan dispatcher.

## Tab Garasi

Blok **Garasi** tab ini menyediakan informasi komprehensif tentang garasi dalam organisasi Anda.

### Menambahkan garasi baru

Untuk menambahkan garasi baru, klik **Tambah garasi** tombol.

Profil garasi mencakup detail penting seperti nama garasi, alamat, dan nama mekanik serta dispatcher. Informasi ini sangat penting untuk meningkatkan manajemen Tugas dan koordinasi di seluruh Armada Anda.


---

# 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/id/guide/fleet-management/garages.md?ask=<question>&goal=<user_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.