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

# Users and roles

Control who can access Flow Retail and what they can do.

Every person who needs access to Flow Retail requires a **user account**. Each user account is assigned one or more **roles** that determine what the user can see and do.

### How it works

**Users** are individual accounts for your team members. Each user has their own login and personal settings.

**Roles** bundle permissions together so you don't have to set them up individually. Instead of configuring permissions for each person, you assign a role that includes everything they need.

Flow Retail includes six pre-configured roles:

| Role                       | Job function                           |
| -------------------------- | -------------------------------------- |
| Administrator              | Business owners, IT administrators     |
| Backoffice                 | Head office staff, operations managers |
| Store Manager (Butikksjef) | Store managers, shift supervisors      |
| Salesperson (Selger)       | Sales associates, retail staff         |
| Accounting (Regnskap)      | Accountants, financial controllers     |
| Warehouse (Lager)          | Warehouse staff, stock controllers     |

Roles can be assigned at different levels — giving access to the whole company, a group of stores, or just one specific store.

{% hint style="warning" %}

#### Migrating from Store Access?

Flow Retail previously used a simpler "Store Access" system. This is being phased out in favor of the more flexible "Roles and access" system. See Users for migration steps.
{% endhint %}

### Where to go next

| I want to...                        | Go to                                                                                                |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------- |
| Set up a new team member            | [Users](https://docs.flowretail.com/docs/getting-started/users-and-roles/users.md)                   |
| Understand how access control works | [Roles](https://docs.flowretail.com/docs/getting-started/users-and-roles/roles.md)                   |
| See all available permissions       | [Permissions](https://docs.flowretail.com/docs/getting-started/users-and-roles/roles/permissions.md) |
| Learn about login and PIN codes     | [PIN code](https://docs.flowretail.com/docs/getting-started/users-and-roles/pin-code.md)             |


---

# 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.flowretail.com/docs/getting-started/users-and-roles.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.
