> For the complete documentation index, see [llms.txt](https://www.oddle.me/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.oddle.me/docs/new-guests/terminal/security-settings.md).

# Security Settings

Protect sensitive actions on your Terminal devices with a 4-digit passcode. When a passcode is set, staff must enter it before the Terminal will process the action — preventing accidental or unauthorised operations.

Go to **Channels > Terminal** in your Merchant Admin to manage security settings for your devices.

***

## What the Passcode Protects

Each Terminal device has its own passcode. You can choose which actions require it:

| Action                          | What it protects                                  |
| ------------------------------- | ------------------------------------------------- |
| **Voiding transactions**        | Prevents unauthorised voids of completed payments |
| **Viewing batch reports**       | Restricts access to payment batch data            |
| **Starting or closing a batch** | Prevents accidental batch operations              |
| **Adjusting tips**              | Requires authorisation to modify tip amounts      |
| **Adjusting charges**           | Requires authorisation to modify charge amounts   |
| **Kiosk mode**                  | Always protected (cannot be turned off)           |

***

## Setting Up a Passcode

Select a device from your Terminal list, open the three-dot menu, and select **Edit security settings**. Enter a 4-digit passcode and toggle on the actions you want to protect.

You can also set passcodes in bulk — select multiple devices using the checkboxes, then apply the same passcode and settings to all of them at once.

{% hint style="info" %}
To reset a device's passcode, select **Reset security settings** from the device menu. This removes the passcode and all protection settings for that device.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://www.oddle.me/docs/new-guests/terminal/security-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.