# Overview

The Truck module stores and manages all trucks owned or used by the company, including vehicle details, documents, and inspection records. Trucks are divided into Active and Inactive states, with status color-coding for compliance tracking.

Trucks can be either:

* **Company-owned**, with full technical and document inputs, or
* **Owner's trucks**, with limited field visibility (e.g., no purchase info).

Access to the Truck module is available to users with assigned permissions. Drivers do **not** have access to the web module.

***

### Active vs Inactive Trucks

| Status   | Description                                                                        |
| -------- | ---------------------------------------------------------------------------------- |
| Active   | Default state. Fully operational and usable in dispatch.                           |
| Inactive | Truck is archived. Cannot be assigned. Document warnings still visible but grayed. |

To deactivate a truck, it must not be part of any active dispatch.

***

### Key Features

* VIN uniqueness across the entire system
* Truck ownership affects which fields appear (e.g., Owner’s truck hides cost fields)
* Commission mode only applies to Owner’s trucks
* Expired documents trigger warning states on list view and details
* Each truck is linked to FHWA, Registration, Insurance, and Title

***

### Color Indicators

* Truck color is visible in the dropdown selector and list/card views
* Used for quick visual identification by dispatchers

**Image Placeholder:**\
`![TruckOverviewColors](../assets/truck-title-card-states.png)`\
\&#xNAN;*Figure: Example of color indicator on truck title card and dropdown.*


---

# Agent Instructions: 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://rute.gitbook.io/carrier/truck/overview.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.