> For the complete documentation index, see [llms.txt](https://docs.accentpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.accentpos.com/hub/users.md).

# Users

AccentPOS has 6 different user types with different permissions suited to roles within an organisation. Here is a description of the user types:

<details>

<summary>Organisation admin</summary>

The top level of the tree, organisation admins can view and edit all locations inside the organisation. Organisation admins can assign location managers. Organisation admins **cannot** sign in to the AccentPOS app.

</details>

<details>

<summary>Location manager</summary>

Location managers can view details, settings and orders/accounts from their own location. If they have been given permission by an organisation admin, they can also add and edit menus. Location managers can invite users to their location.&#x20;

Location managers can sign in to the AccentPOS app, where they have the following permissions:

* Create new orders
* View existing orders
* Take payments
* View the kitchen and bar live view
* Void items
* Apply discounts to orders
* Remove the service charge from individual orders (if applied)
* View the Cash-out and run X and Z reports for the current shift

</details>

<details>

<summary>Waiter</summary>

Waiters can sign in to the AccentPOS app, where they have the following permissions:

* Create new orders
* View existing orders
* Take payments

Waiters cannot void items, apply discounts or remove the service charge.

</details>

<details>

<summary>Head chef</summary>

Head chefs can sign in to the AccentPOS app, where they have the following permissions:

* View the kitchen live view
* Set items, categories or orders as ready

</details>

<details>

<summary>Chef</summary>

Chefs can sign in to the AccentPOS app, where they have the following permissions:

* View the kitchen live view
* Set items, categories or orders as ready

</details>

<details>

<summary>Bartender</summary>

Bartenders can sign in to the AccentPOS app, where they have the following permissions:

* View the bar live view
* Set items, categories or orders as ready

</details>

{% hint style="info" %}
Organisation admins and location managers can invite users
{% endhint %}

To add a invite user, [sign in to the Hub](https://hub.accentpos.app), then choose a location to add the user to:

1. Go to the users page
2. Click the '+'
3. Enter the new user's first name, last name and email address
4. Click 'next'
5. Choose a user type
6. Click 'next'
7. Confirm the details and submit

Shortly after submitting the request, the new user will receive an invitation to the specified email address containing a temporary password. They should click the link in the email, then use the temporary password to setup a secure password which is unique to them. Once this process is complete, they will be able to login to the system.

{% hint style="info" %}
If you forget your password, click 'forgot password' on the Hub sign in page to reset it
{% endhint %}

{% hint style="info" %}
Organisation admins and location managers can enable or disable a user at any time by clicking on their profile in the Hub and toggling the 'Active' switch
{% endhint %}


---

# 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:

```
GET https://docs.accentpos.com/hub/users.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.