> 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/general-settings.md).

# General settings

General holds the Flow Service settings that apply to every store in your company.

Five settings that apply to every store: whether staff need their own PIN code, the status new service orders start on, how long the customer's portal link works after a case is finished, your accent color, and an emergency switch that pauses every message to customers. None of them can be changed per store.

Go to **Settings → General** (under **Company**). Users with the **Service configuration** permission see the menu entry and can change the settings. Settings are closed on a shared screen. See [Permissions and roles](https://docs.flowretail.com/docs/service/permissions-and-roles.md).

***

## Settings

![Settings → General with all five cards: Security, New service orders, Customer portal, Appearance (with Preview), Advanced; Save button under them](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FUv6QZGbq0VJZb8cS1JdX%2Fservice-general-settings.webp?alt=media)

| Field                                                                       | Meaning                                                                                                                                                                                                                                                                  |
| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Security** → Require a PIN code from staff                                | When on, staff enter their own PIN code every time they show a password stored on a service order, and a screen can be set to **Use as shared screen** in the sidebar, so each person unlocks it with their own PIN and what they save is in their name. Off by default. |
| **New service orders** → Start status for new service orders                | The status every new service order starts on. Only active statuses in <kbd>Awaiting product</kbd> or <kbd>Not started</kbd> can be chosen. Default <kbd>Not set</kbd>; see the warning below.                                                                            |
| **Customer portal** → Portal link works after the service order is finished | Days the customer's portal link keeps working after the service order reaches <kbd>Complete</kbd> or <kbd>Cancelled</kbd>. A whole number, 0 or more. Default 0: the link stops working the moment the case is finished.                                                 |
| **Appearance** → Accent color                                               | The color of buttons, links and highlights in Flow Service and in the customer portal. Pick a ready color or enter a code such as #f97316. **Use default color** goes back to Flow's own. **Preview** shows a button and a link in the chosen color before you save.     |
| **Advanced** → Pause every message to customers                             | Emergency switch: while it is on, no store sends any message to customers. Off by default.                                                                                                                                                                               |

**Save** stores only the fields you changed, so two admins on the page at once don't overwrite each other. A new accent color applies across Flow Service as soon as it is saved.

***

## Good to know

{% hint style="warning" %}
**With the start status on Not set, you need exactly one active Not started status.** New service orders then start on that status. With none, or more than one, new service orders cannot be registered until you choose a start status here.
{% endhint %}

* **Portal link.** The link on an open case never expires. Reopening a finished case brings its link back. With 0, a portal link in a message sent as the case is finished does not work.
* **Pausing messages.** Automatic status messages wait while the pause is on and are sent when you turn it off. A waiting message is skipped if its service order has since moved to another status. Nothing can be sent by hand: on the service order, sending on the Message tab is closed with the reason shown, and a new portal link can only be replaced without sending it. Notes are saved as usual.
* **Accent color.** An amber mark warns when a color is too pale to see on white, or close to the warning color. You can still save it. Printed papers, e-mails and text messages never use the accent color, and status colors stay as they are.
* **PIN codes** (4 to 6 digits) are set on each user in Flow Admin.


---

# 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/general-settings.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.
