> 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/software-clients/assistant/settings-and-your-profile.md).

# Settings and your profile

Make Assistant work the way you like on this device: sounds, fun effects, alerts and language. Your own PIN and language follow your user, and a device can be connected to several stores. Administrators can also choose the printers for the device and set up new phones.

## Settings

Go to **More** › **Settings**.

* **Fun effects** turns on Flowrex the mascot, seasonal touches and confetti. The effects never show while you scan, and they follow the phone's reduced-motion setting. Flowrex's hello on the Home tab can be swiped to the right to send him away.
* **Sounds** turns scan beeps, keypad ticks and fun sounds on or off.
* **Alert for new orders** has one switch per order handling, for this device only (see [Order handling and picking](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/order-handling-and-picking.md)).
* **Game lab** is there when fun effects are on (see below).
* The language list at the bottom changes the language of the app.

At the bottom you see the store, the till, the device and the app version. Support may ask you for these.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FoazeuQOzgohcw8EUwEix%2Fsettings-01_settings-77d43ac1.png?alt=media" alt="Settings scrolled down to Game lab, the language and the app info" width="300"><figcaption><p>Settings</p></figcaption></figure>

## Language and account

Tap your initials at the top of the **Home** tab, then **Language and account**. On the **Sales** tab, your initials open it straight away.

* **Switch store** moves the device to another store it is connected to.
* **Change PIN** gives you a new PIN.
* **Log out** lets a colleague log in. The till stays open.
* **User language** is the language of your Flow Retail user.
* **Turn on biometrics** lets you log in with your fingerprint or face instead of the PIN, on a device that supports it.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FtCFlOFvXTkXadm0PaJ8S%2Fsettings-02_account-86b149a4.png?alt=media" alt="Emma&#x27;s account: switch store, change PIN, log out and the user language" width="300"><figcaption><p>Language and account</p></figcaption></figure>

## Change your PIN

Tap **Change PIN**. Type your current PIN, then the new one twice, tapping **Next** between the steps. Tap **Save** at the end. The new PIN is used everywhere you log in to Flow Retail.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FOohTMQ76P499KSuq8hRy%2Fsettings-03_change_pin-80301578.png?alt=media" alt="Change PIN, step 2 of 3: the new PIN" width="300"><figcaption><p>Type the new PIN</p></figcaption></figure>

Forgot your PIN? Your store manager can give you a new one in Flow Admin.

## Several stores on one device

A device can be connected to more than one store, for example when you work in two shops. Tap **Switch store** under **More**, on the store name at the top of the Home tab, or in your menu. Tap the store you want. You log in again after switching.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FvOokPuyFpNHLiX6mcGVa%2Fsettings-04_switch_store-6578c705.png?alt=media" alt="Choose store with Acme Sport Oslo and Acme Sport Bergen" width="300"><figcaption><p>Switch store</p></figcaption></figure>

Tap **Add** to connect the device to another store with a new device code (see [Getting started](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/getting-started.md)), or **Manage** to remove a store from this device. Removing only affects the device: an administrator unlinks it in Flow Admin.

## Printers on this device

Go to **More** › **Printers** to choose which of the store's printers this device uses. It applies to everyone who logs in on the device. You need the **Device Management** and **Printer Management** permissions for the whole chain; without them the row shows a lock.

* Switch a printer on, and the device prints on it straight away. Switch it off, and the printer stays in the store for other devices.
* Tap a printer to see how it is connected, its label size and what it can print. **Change** edits it for every device that uses it, and **Print test page** checks that it works.
* **Add a new printer** asks for the type (receipt or label), a name, the IP address (or the printer on the store's Flowbox) and the label size. Flow prints a test page right away. When it came out, the printer is put on this device; when it did not, you get the three things to check.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2F72itKVPgQUyLwGHbCstV%2Fsettings-06_printers-c55ee6fd.png?alt=media" alt="Printers: two on this device and two more in the store" width="300"><figcaption><p>Printers on this device</p></figcaption></figure>

Without a printer on the device, the app asks which printer to use every time you print.

Assistant only offers printers that can print the job, as Flow lists it for each printer. A label printer with small labels is not offered for a pickup label or a pick note, for example. If no printer here can print it, nothing is sent and the app says so.

## Devices in the store

Go to **More** › **Devices** to see the store's hand terminals and tills: who used each one last and when, and the app version. **This one** marks the device in your hand, **Waiting for a phone** one that is made but not set up yet, and **Rarely used** one nobody has used for 14 days. You need the **Device Management** permission for the whole chain; without it the row shows a lock.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FGmaeRoVYkx5FEZERgV1s%2Fsettings-07_devices-c7e56c66.png?alt=media" alt="Devices: four hand terminals and a till in Acme Sport Oslo" width="300"><figcaption><p>Devices in the store</p></figcaption></figure>

### Set up a new phone

1. Tap **Set up a new phone**. Either tap a hand terminal that is waiting and then **Show QR code for a new phone**, or make a new one: the name is suggested for you, then tap **Create and show QR code**.
2. On the new phone, open Assistant and tap **Connect to store**. Scan the QR code, or type the code under it.
3. A manager approves with username and PIN, as before (see [Getting started](https://docs.flowretail.com/docs/getting-started/software-clients/assistant/getting-started.md)).

The QR code says **Linked** by itself when the new phone is connected. **Cancel** or going back makes the code useless.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FVZRy9pVyHjictzAHdsyM%2Fsettings-08_new_phone_qr-1ed9c85f.png?alt=media" alt="Scan with the new phone: the QR code, the code to type and the three steps" width="300"><figcaption><p>The QR code for a new phone</p></figcaption></figure>

### Move a hand terminal to a new phone

When a phone breaks or is replaced, tap the hand terminal and **Move to a new phone**. The old phone can no longer log in as it. The name, printers and settings go with it to the new phone, which is set up with a QR code as above.

{% hint style="info" %}
Tills are listed, but they are still set up in Flow Admin.
{% endhint %}

## Game lab

Game lab has two small games for your break: **Stack the pallet** and **Change master**, where you give the right change as fast as you can. You find it under **More** › **Settings** when fun effects are on.

<figure><img src="https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2F8vrdL98leDUgXWaGjod7%2Fsettings-05_game_lab-75170fbf.png?alt=media" alt="Game lab with the play time today and the two games" width="300"><figcaption><p>Game lab</p></figcaption></figure>

* Your best score and the store record are on each game, and the **Hall of Fame** further down lists the best in the store.
* The music button sets the volume of the games' own music. It never changes the phone's volume.
* A game pauses by itself when you leave it, for example to serve a customer. Tap **Continue** when you're back.
* After ten minutes of play in a day, Game lab reminds you to take a break.

{% hint style="info" %}
Results are only kept on this device. If the app is removed, they are gone.
{% 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 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/software-clients/assistant/settings-and-your-profile.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.
