> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/central-manager/manage-employees/store-users/setting-up-store-user-password-policy.md).

# Configure a store user password policy

You can set up a password policy for store users to control how frequently passwords expire, whether to lock accounts after failed login attempts, and to set requirements for password complexity.

{% hint style="success" %}
If cashiers or sales representatives must log on to POS for each transaction, it is best practice to lower the password complexity requirements so these users can create simpler passwords that are easier to enter in POS.
{% endhint %}

1. Click **Setup**.
2. Expand **People and Security**.
3. Click **Password Policy**.
4. If you want passwords to expire after a period of time:
   1. Select **Password expire periodically**.
   2. In the **Maximum age of password (days)** field, enter how many days a user can use a password before they are required to change it.
   3. In the **Show reminder (days before)** field, enter how many days notice users are given before they are required to change their password.
5. If you want to prevent store users from reusing old passwords, in the **Number of password to save** field, enter how many previous passwords will be saved for each user.
6. If you want to lock out accounts after failed login attempts:
   1. Select **Use account lockout**.
   2. In the **Fail logon attempts allowed** field, enter how many failed login attempts are allowed before the user's account is locked.
   3. In the **Lockout period (minutes)** field, enter how many minutes the user's account is locked before they can attempt to log in again.
7. If you want to set requirements for password complexity:
   1. Select **Password complexity**.
   2. In the **Minimum password length** field, enter the minimum number of characters required for passwords.
   3. In the **Required uppercase** letter field, enter the number of uppercase letters (e.g., A, B, C, etc) required in passwords.
   4. In the **Required numeric digit** field, enter the number of numeric characters (e.g., 1, 2, 3, etc) required in passwords.
   5. In the **Required special character** field, enter the number of special characters (e.g., !, @, #, etc) required in passwords.
8. Click **Save And Close**.


---

# 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://docs.rmhpos.com/central-manager/manage-employees/store-users/setting-up-store-user-password-policy.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.