# Settings

The Settings section lets you manage the configuration of your Flowlity workspace. Access it from the **Settings** entry in the left sidebar. Pages are organized into three groups.

### General

Core workspace configuration — your company identity, site definitions, and user management.

* [**Company**](/settings/company.md) — View your company name.
* [**Sites**](/settings/sites.md) — Create and configure sites (locations, currency, demand distribution, closures).
* [**Users**](/settings/users.md) — Manage user accounts, roles, and site access.

### Parameters

Master data and planning parameters that drive demand forecasting and supply planning.

* [**Products**](/settings/products.md) — Manage your product catalog and configure forecast and inventory strategies per product.
* [**Suppliers**](/settings/suppliers.md) — Define suppliers with contact information, lead-time constraints, and closures.
* [**Tags**](/settings/tags.md) — Organize products into tags and tag categories for filtering and analysis.
* [**Forecast events**](/settings/forecast-events.md) — Create events (promotions, seasonality shifts, etc.) that adjust the demand forecast.
* [**Buffer Policy**](/settings/buffer-policy.md) — Set default supply buffer policies for each inventory strategy.
* [**Site closures**](/settings/site-closures.md) — Declare periods when a site is closed and cannot receive or ship goods.

### Data

Import and export tools.

* [**Downloads**](/settings/downloads.md) — Export planning data to CSV or Excel files.

{% hint style="info" %}
Your personal profile (name, language, password) is accessible via your **avatar** in the top-right corner of the app, not from Settings.
{% endhint %}


---

# Agent Instructions: 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.flowlity.com/settings.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.