> For the complete documentation index, see [llms.txt](https://docs.makapay.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.makapay.io/point-of-sale-pos/cashier-restrictions.md).

# Cashier Restrictions

Cashier restrictions let merchants control **which cashiers can log into which businesses**. This is useful for multi-business setups where you want to assign specific staff to specific locations.

## How It Works

Each business has an optional **Allowed Cashiers** list:

* **No restrictions (default):** Any active cashier can log into the business.
* **Restricted:** Only cashiers on the allowed list can log in. Others will be rejected.

## Setting Up Restrictions

1. Go to **Dashboard > POS > Businesses**
2. Click **Edit** on the business you want to restrict
3. In the **Allowed Cashiers** section, toggle on the cashiers who should have access
4. Save changes

## Behavior

### When a business has NO restrictions

| Cashier             | Can log in? |
| ------------------- | ----------- |
| Any active cashier  | Yes         |
| Deactivated cashier | No          |

### When a business HAS restrictions

| Cashier             | On allowed list? | Can log in?                                                                          |
| ------------------- | ---------------- | ------------------------------------------------------------------------------------ |
| Active cashier      | Yes              | Yes                                                                                  |
| Active cashier      | No               | **No** -- gets error: "No cashiers assigned to this business. Contact your manager." |
| Deactivated cashier | Yes              | No                                                                                   |

## Visual Overview

|           | Front Counter (Restricted) | Downtown Branch (Open) |
| --------- | -------------------------- | ---------------------- |
| **John**  | Allowed                    | Allowed                |
| **Sarah** | Allowed                    | Allowed                |
| **Mike**  | **BLOCKED**                | Allowed                |

*R1 only allows John and Sarah. R2 has no restrictions so everyone can use it. Mike is blocked from R1 but can use R2.*

## Login Decision Flow

> 1. Cashier enters PIN
> 2. Is PIN correct? **No** --> Denied: Invalid PIN
> 3. Is cashier active? **No** --> Denied: Account deactivated
> 4. Does business have restrictions? **No** --> Access granted
> 5. Is cashier on allowed list? **Yes** --> Access granted / **No** --> Denied: Not assigned to this business

## Common Setups

### Setup 1: All cashiers, all businesses (no restrictions)

Leave the **Allowed Cashiers** list empty on all businesses. Any cashier can work at any location.

### Setup 2: Dedicated cashiers per business

| Business              | Allowed Cashiers |
| --------------------- | ---------------- |
| R1 (Front Counter)    | John, Sarah      |
| R2 (Downtown Branch)  | Mike, Lisa       |
| DRIVE (Drive-through) | Dave             |

John and Sarah can only log into R1. Mike and Lisa can only log into R2. Dave can only use the drive-through business.

### Setup 3: Mix of restricted and open

| Business             | Allowed Cashiers              |
| -------------------- | ----------------------------- |
| R1 (Front Counter)   | John, Sarah (restricted)      |
| R2 (Downtown Branch) | *(no restrictions -- anyone)* |

R1 is locked to John and Sarah. R2 is open to all cashiers.

### Setup 4: Manager access everywhere

Create a manager cashier and add them to the allowed list of every restricted business. They can log into any business while regular cashiers stay restricted.

## Updating Restrictions

* Adding a cashier to the allowed list takes effect immediately for new logins
* Removing a cashier does **not** end their current session (they can finish their current work)
* Deactivating a cashier removes their access from all businesses regardless of restrictions


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.makapay.io/point-of-sale-pos/cashier-restrictions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
