> 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-accounts.md).

# Create store user accounts

If you typically manage store users in Central Manager, follow this procedure to set up store users and synchronize the users to the applicable store groups. However, if you prefer to manage users at the store level, you can set up users in Store Manager and they will synchronize to Central Manager.

{% hint style="info" %}
You must set up manager or POS user roles before you set up Store Manager or POS users.
{% endhint %}

1. Click **Setup**.
2. Expand **People and Security**.
3. Click **Store Users**.
4. Click **New**.
5. Enter user properties and register properties.

<details>

<summary><img src="/files/Bdprh8VktJ8YD1YS6AjL" alt="" data-size="original"></summary>

<table><thead><tr><th width="249.5555419921875" valign="top">Field</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">Login ID</td><td valign="top"><p>The ID that the user will use to log in to Store Manager or POS.</p><p>Tip: The Login ID prints on the customer's receipt. To protect the privacy of employees, consider using a numeric ID. (An added benefit is that numeric IDs are also easier to enter in POS.) You might also consider using a number series for IDs that aligns with the user's role. For example, all 100's are cashiers, 200's are floor managers, 300's are manager, and so on.</p></td></tr><tr><td valign="top">User Name</td><td valign="top">The user's first and last name.</td></tr><tr><td valign="top">Telephone</td><td valign="top">The user's telephone number.</td></tr><tr><td valign="top">Email</td><td valign="top">The user's email address.</td></tr><tr><td valign="top">Password</td><td valign="top">A password that the user must enter to log in to POS or Store Manager. Passwords are optional but recommended.</td></tr><tr><td valign="top">Cash Drawer</td><td valign="top">The cash drawer the user is permitted to access.</td></tr><tr><td valign="top">Floor Limit</td><td valign="top">The maximum non-cash transaction amount the user is allowed to process.</td></tr><tr><td valign="top">Return Limit</td><td valign="top">The maximum return transaction amount the user is allowed to process.</td></tr><tr><td valign="top">POS Task Pad</td><td valign="top">The POS Task Pad assigned to the user.</td></tr></tbody></table>

</details>

6. If you are setting up cashiers:
   1. In the **User Roles** section, select the **POS Role** you want to assign to the user.
   2. If desired, you can override privileges assigned to the POS Role by adding or removing them in the **POS User Roles** overwrite list.
   3. If desired, you can override the **Over/Short Limits** assigned to the POS Role by adding or removing new limits.
7. If you are setting up managers, in the **User Roles** section, select the **Manager User Role** you want to assign to the user.

{% hint style="info" %}
You can also assign a **POS Role** to managers if you want them to be able to process transactions in POS if required.
{% endhint %}

8. On the **Store Groups** tab, select the store groups where you want to add the user.
9. 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-accounts.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.
