# PIN Pad

A numeric PIN entry pad for authorising restricted actions. Configure who can authorise — by role, by named user, or both — and the block enforces those rules on PIN submission.

PIN Pad pairs with **Action Button** (PIN-gated actions), **Discount Header** (PIN-gated discounts), **Customer Hold Status** (manager override), and **Submit Button** (PIN-gated submits).

![PIN Pad block as a numeric keypad with backspace and submit, ready for the user to enter a PIN](/files/eyvQczuoQlYItz5FeQWq)

## Available in

* Page modules
* Order Form modules

PIN Pad isn't available in Catalog, Modal, Reports, or Navigation modules. Use **Modal** + Action Button to surface a PIN prompt in those contexts.

## When to use

* Workflow-wide PIN gates (e.g. clock-in / clock-out screens).
* A standalone PIN authorisation page for sensitive operations.
* Anywhere you need a numeric PIN input that isn't already provided by another block (Discount Header, Customer Hold Status, and Action Button each have their own built-in PIN trigger).

## Settings

| Setting                         | Description                                                                                                       |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Type**                        | Currently only *Module* is available — the PIN gates the whole module.                                            |
| **Authorization Role**          | Pick a NetSuite role whose users are authorised.                                                                  |
| **Authorized Users (Managers)** | Multi-select of specific users authorised to enter a PIN here, in addition to the role.                           |
| **Field**                       | Which RecordField on the page the PIN result is bound to (auto-populated from the page's RecordField components). |
| **Title**                       | Heading text shown above the pad. Default: *Enter PIN*.                                                           |

## How it works

1. The block renders a numeric keypad.
2. The user enters their PIN.
3. The PIN is validated against either the role-based list or the explicit user list (or both).
4. If valid, the configured Field is updated with the PIN value (or a flag indicating success).
5. Downstream logic (e.g. Submit Button validation) reads the field to gate behaviour.

In edit mode, the block shows a preview with a configuration summary so you can verify the role/user setup at a glance.

{% hint style="info" %}
For per-action PIN gating (e.g. PIN-protect a single button or a discount above a threshold), don't drop a separate PIN Pad — those blocks have built-in PIN modals. PIN Pad is for module-wide gates or standalone PIN-required pages.
{% endhint %}

## Examples

**Manager-only override page.** A Page module dedicated to manager actions. PIN Pad at top, Action Buttons below for void / refund / discount-override actions. Authorization Role = *Store Manager*.

**Clock-in screen.** A standalone PIN Pad on a Page module — staff enter their PIN to register clock-in. Field bound to a RecordField that drives the clock-in action.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>PIN Override</strong></td><td>The full PIN-protection setup across the workflow.</td><td><a href="/pages/ZB1p1C3xoZi8Tr9w4b1S">/pages/ZB1p1C3xoZi8Tr9w4b1S</a></td></tr><tr><td><strong>Action Button</strong></td><td>For per-button PIN-gated actions.</td><td><a href="/pages/eJnsvUn6cKd9Lt95bP9b">/pages/eJnsvUn6cKd9Lt95bP9b</a></td></tr><tr><td><strong>Customer Hold Status</strong></td><td>Uses PIN to authorise overriding customer holds.</td><td><a href="/pages/CqpoPOnhKc67FeMefdKr">/pages/CqpoPOnhKc67FeMefdKr</a></td></tr></tbody></table>


---

# 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://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/entity-components/pin-pad.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.