# Step 2 – Additional Settings

In Step 2 of the Setup Wizard, the company owner configures operational settings that affect how Carrier behaves across modules. These preferences apply globally but can later be overridden at the division level (where allowed).

***

### Common Configuration Options

| Setting                  | Description                                        |
| ------------------------ | -------------------------------------------------- |
| Timezone                 | Used for all date/time inputs and reporting        |
| Unit System              | Choose between Imperial or Metric                  |
| Enable IFTA Module       | Activates IFTA fuel/mileage tracking and reporting |
| Enable Factoring Company | Toggles factoring-related UI and invoice logic     |
| Enable Division Mode     | Allows creation of internal subdivisions           |
| Dispatch Settings        | Select default load grouping, stop layout, etc.    |

***

### Behavior

* Each setting is saved immediately upon selection
* Some toggles affect available options in later wizard steps (e.g. Payroll)
* Division Mode, if enabled here, unlocks Division-related setup later

***

<figure><img src="/files/AK55ENQ52phjn4sj3SA5" alt=""><figcaption><p><em>Figure: Operational settings defined in Step 2 of the Setup Wizard.</em></p></figcaption></figure>

***

### Notes

* These settings can be edited later in **Company Settings > Configuration**
* Not all users have permission to change these after setup—only owners/admins

> ⚙️ Tip: You can keep modules like IFTA or Factoring disabled at launch and activate them later as your operations scale.


---

# 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/setup-wizard-first-login/step-2-additional-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.