> 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/central-users/setting-up-central-user-accounts.md).

# Create Central Manager user accounts

This topic describes how to create user accounts for employees who use the Central Manager app.

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

1. Click **Setup**.
2. Expand **People and Security**.
3. Click **Central Users**.
4. Click **New**.
5. Enter the following information:

<details>

<summary><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2FpopbobAPoZyocahbnRhK%2FMORE%20INFO.png?alt=media&amp;token=b6405f3b-3d08-43d4-8bb4-9e98e4de32b3" 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">User ID</td><td valign="top">The ID that the user will use to log in to Central Manager.</td></tr><tr><td valign="top">Name</td><td valign="top">The user's first and last name.</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 Central Manager. Passwords are optional but recommended.</td></tr></tbody></table>

</details>

6. From the **User Roles** drop-down, select the Central Manager user role you want to assign to the user.
7. Select privileges that you want to assign to the user:

* Approve worksheets
* Acknowledge worksheets
* Create/edit worksheets
* Delete worksheets
* Administrator privileges

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

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

```
GET https://docs.rmhpos.com/central-manager/manage-employees/central-users/setting-up-central-user-accounts.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.
