> 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/service/permissions-and-roles.md).

# Permissions and roles

Three role permissions decide what each person can open and change in Flow Service.

Access to Flow Service comes from roles in Flow Admin. A role carries permissions, and you give the role to a user for the whole company, an organization or a store. Flow Service reads three permissions.

***

## Which permissions does Flow Service use?

| Permission in Flow Admin    | Code                   | Can be given for                   | What it opens in Flow Service                                                                                                                                                                                                                |
| --------------------------- | ---------------------- | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Service                     | `SERVICE_ORDER`        | Whole Company, Organization, Store | Overview, Service orders and **New service order**, Serial search and Statistics, at the stores it reaches. Also needed to use a shared screen.                                                                                              |
| Service store configuration | `SERVICE_STORE_CONFIG` | Whole Company, Organization, Store | **Settings** with Intake forms and Stores: the store's own intake forms and store settings, for the stores it reaches. Can add and edit fields in the Field library.                                                                         |
| Service configuration       | `SERVICE_CONFIG`       | Whole Company only                 | All of **Settings**: General, Holidays, Staff notice, Statuses, Service types, Intake forms, Job types, Insurance companies, Terms, Message texts and every store under Stores. Only this permission archives a field or marks it sensitive. |

The configuration permissions do not open service orders. Someone who sets up Flow Service and also works on cases needs **Service** as well.

In Flow Admin's role editor, **Service configuration** carries the <kbd>Tenant only</kbd> badge.

***

## Which roles carry them?

Roles are set up in Flow Admin. Add the permissions to the roles your staff already use, or create new roles for service work. A person who works on service orders needs **Service**. A manager who edits one store's settings also needs **Service store configuration**. Whoever sets up Flow Service for the company needs **Service configuration**.

***

## Where are permissions given?

Both are in Flow Admin:

* **Users → Roles** sets which permissions a role carries.
* **Users → Users**, a user's **Roles and access** tab, gives the user a role under **Whole Company**, **Organization** or **Store**.

See [Get started](https://docs.flowretail.com/docs/service/get-started.md) for the order to do it in.

***

## Shared screens and PIN codes

When **Settings → General → Require a PIN code from staff** is on:

* Staff enter their own PIN to show a stored password on a service order.
* **Use as shared screen** appears in the sidebar at a store where you have **Service**. It locks the screen to that store, and staff unlock it with their own PIN. What they save is in their name.

See [Shared screens](https://docs.flowretail.com/docs/service/shared-screens.md) for how to turn it on and off and how staff unlock it.

| What           | Where                                                 | Rule                                                                                                                     |
| -------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| A person's PIN | Flow Admin, the user's **PIN-code, 4-6 digits** field | 4 to 6 digits.                                                                                                           |
| Who can unlock | The shared screen's lock screen                       | Someone with **Service** at that store and a PIN. Anyone else is told they have no access to Flow Service at this store. |
| A locked PIN   | Flow Admin, the user form                             | After too many wrong attempts the PIN locks. Set a new PIN to unlock it.                                                 |

**Settings** cannot be opened on a shared screen. Use a personal screen to change settings.

***

## Good to know

* **A user with no role gets no access.** The old **Store Access** tab in Flow Admin does not count. They see <kbd>No Service access</kbd>.
* **Give Service configuration under Whole Company.** Given for an organization or a store, it opens only Intake forms and Stores, not the company's settings.
* **A role whose permissions reach no store** shows <kbd>No store to act in</kbd>.


---

# 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/service/permissions-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.
