> ## Documentation Index
> Fetch the complete documentation index at: https://help.opmaint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings overview

> Where to find Opmaint's settings and what each one controls.

To open settings, click your organisation name at the top of the left sidebar and choose **Settings**.

Settings apply to the branch you are in, shown in the branch selector at the top of the sidebar. If you run several [branches](/branches), set each one up separately.

## What is in settings

| Section | What it controls |
| - | - |
| **Branch Preferences** | Currency, dashboard colour, timezone, language, date and time format. See [Branch preferences](/branch-preferences) |
| **Organization Logo** | Your logo |
| **General Preferences** | How work orders, assets and stock behave (see below) |
| **Required Fields Settings** | Which fields people must fill in. See [Required fields](/required-fields) |
| **Custom Fields** | Your own extra fields on any module. See [Custom fields](/custom-fields) |
| **Overdue Reason Settings** | Ask for a reason when a work order runs late (see below) |
| **Notification Settings** | Which events send email and in-app notifications. See [Notifications](/notifications) |
| **Request Portals** | Public forms for reporting problems. See [Request portals](/request-portals) |
| **Bulk Import** | Load data from spreadsheets. See [Bulk import](/bulk-import) |
| **Taxes** | Tax rates and tax groups for purchase orders. See [Taxes](/taxes) |
| **Downtime Schedule** | Periods when preventive work orders should not repeat. See [Downtime schedule](/downtime-schedule) |
| **App Language** | The language the app is shown in. See [Branch preferences](/branch-preferences#language) |
| **Terms and Conditions**, **Privacy Policy** | Legal documents |

## General preferences

Turn these on or off to suit how your team works:

| Setting | What it does |
| - | - |
| **Auto-add request creator as monitor user during work order creation** | The person who raised a request is added as a monitor user on the work order made from it, so they can follow progress |
| **Show details page in a dialog** | Opens work order and request details in a focused pop-up instead of a separate page |
| **Ask for close-out notes when marking Done** | Shows an optional text or voice prompt when someone completes a work order. When off, completing works normally |
| **Parent and child assets** | Allows one level of parent and child assets, and rolls child maintenance data into the parent |
| **Require cost for stock in** | Makes a cost per unit compulsory when recording incoming part stock |
| **Single deletes per hour** and **Bulk-delete requests per hour** | Limits on how many deletions can happen in an hour, as a safety net against accidental mass deletion |

> [!TIP]
>
> Turn on **Ask for close-out notes when marking Done** if you want technicians to say what they actually did. It makes the asset history far more useful later.

## Overdue reasons

Turn on **Require a reason for overdue work orders**. Once a work order is overdue past the threshold you set, an overdue reason field becomes available on its details page. Over time this tells you why work runs late: spares, manpower, access or approvals.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.