# Inherited vs Custom Settings

Division Companies can either **inherit** settings from the parent company or define **custom configurations** to fit unique operational needs.

***

### Key Concepts

* **Inherited Settings**\
  Settings are read-only and synced from the parent company. Any change made at the top level will automatically apply to all divisions using inheritance.
* **Custom Settings**\
  Divisions can override specific configurations and define their own local behavior. These settings are not affected by changes at the parent level.

***

### Inheritable Settings

<table><thead><tr><th width="200">Setting Type</th><th width="100" align="center">Inheritable</th><th width="101" align="center">Customizable</th><th>Notes</th></tr></thead><tbody><tr><td>Payroll Config</td><td align="center">✅</td><td align="center">✅</td><td>Override pay types or salary logic if needed</td></tr><tr><td>Fuel Markup Rules</td><td align="center">✅</td><td align="center">✅</td><td>Useful if fuel policy differs by division</td></tr><tr><td>Insurance Assignments</td><td align="center">✅</td><td align="center">❌</td><td>Always controlled at the parent company</td></tr><tr><td>Load Templates</td><td align="center">✅</td><td align="center">✅</td><td>Templates can be shared or custom per division</td></tr><tr><td>Telematics Integration</td><td align="center">✅</td><td align="center">❌</td><td>Must be centrally managed</td></tr><tr><td>Permissions / Roles</td><td align="center">✅</td><td align="center">✅</td><td>Can delegate fine-grained access control</td></tr></tbody></table>

***

### UI Behavior

* Inherited fields are displayed as **locked** with an icon
* A toggle or button allows converting to **Custom** mode
* Switching to custom disables future syncing from the parent company
* A “Revert to Parent” option is available to remove overrides

***

**\[Insert visual of inherited vs custom field states in settings modal] (../assets/inherited-custom-toggle.png)**\
\&#xNAN;*Figure: Locked inherited field vs editable custom override.*

***

### Best Practices

* Inherit global policies like insurance and compliance rules
* Use custom settings for operational or financial variation
* Keep a shared naming convention across divisions for clarity

> 🛠 Tip: Use inheritance where possible to reduce admin effort. Customize only when division logic clearly differs from the parent company.


---

# 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/inherited-vs-custom-settings.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.