# Shared vs Isolated Data

Division Companies can operate in either **shared** or **isolated** mode, depending on how your organization wants to manage access to records like loads, trucks, drivers, and payroll.

***

### Modes of Data Access

* **Shared Mode**\
  All divisions can view and manage the same pool of data across core modules like Loads, Trucks, and Payroll. Ideal for centralized dispatch or back-office operations.
* **Isolated Mode**\
  Each division only sees its own records. Suitable for companies where divisions act as independent entities with separate dispatchers, assets, and reporting.

***

### Comparison Table

| Data Type      | Shared Mode       | Isolated Mode     |
| -------------- | ----------------- | ----------------- |
| Trucks         | Global visibility | Division-only     |
| Drivers        | Global pool       | Assigned by unit  |
| Loads          | All loads visible | Only own loads    |
| Payroll        | Combined totals   | Division-level    |
| Fuel & Repairs | Centralized logs  | Per division      |
| Telematics     | All visible       | Division-filtered |

***

### UI Behavior

* Load boards, reports, and entity lists will reflect only the relevant scope
* Filters like "My Division" and "All Divisions" appear when in shared mode
* Admins can toggle isolation mode in the Division setup screen

***

**\[Insert visual comparing shared vs isolated mode dropdowns or load board filters] (../assets/shared-vs-isolated-filters.png)**\
\&#xNAN;*Figure: Division view toggles and filtered list indicators.*

***

### Best Practices

* Use **shared mode** if your dispatch team works across all divisions
* Use **isolated mode** for clean reporting separation and limited access
* Set expectations with team leads before switching modes

> 🔒 Note: Changes to data isolation affect visibility for all division users and may impact reporting and payroll logic.


---

# 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/company/settings/division-company/shared-vs-isolated-data.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.