> ## Documentation Index
> Fetch the complete documentation index at: https://docs.solya.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Navigation & roles

> How the sidebar is organized, how it can be tailored per organization, and what each role can access.

## How the app is organized

The left sidebar groups the product into sections:

* **Apps** — Tasks, AI Agent, Analytics (master-data cards & dashboards), Signals
  (alerts), Activity.
* **Inventory plans** — restock, rebalance, markdown, pre-season, supplier
  return/exchange, and the approvals queue.
* **Orchestration** — Workflows.
* **Intelligence layer** — business rules & rulesets, budgets, size curves, markdown
  calendars, supplier constraints, approval/return policies, and more.
* **Data platform** — data sources, ingestion specs, datasets explorer, tags,
  taxonomy.
* **Settings** — users, teams, roles, organization, API tokens, navigation templates,
  preferences.

## Configurable navigation (per organization)

The sidebar is **template-driven**. Rather than a fixed menu, each organization uses a
**navigation template** that decides which items appear — and in what order — for each
role. Administrators can:

* Show, hide, and reorder menu items per role (admin vs user).
* Rename sections and submenus.
* Create multiple templates (e.g. *Buyer*, *Merchandiser*, *Operations*).

On login, the sidebar renders from your organization's template for your role, so two
users in the same org can see different menus.

<Note>
  Navigation templates are managed under **Settings → Navigation templates** (admin).
</Note>

## Roles & permissions

Access is governed by **permissions** grouped into **roles**. A user's role determines
which sections they can open and which actions they can take.

### Roles

| Role                         | Focus                                                         |
| ---------------------------- | ------------------------------------------------------------- |
| **Org admin**                | Full access to everything in the organization.                |
| **User manager**             | Manage users, teams, and roles.                               |
| **Data platform admin**      | Configure data sources, ingestion, sandbox; view analytics.   |
| **Intelligence layer admin** | Configure rules, budgets, policies; view analytics & signals. |
| **Inventory manager**        | Manage all inventory plans; view analytics & signals.         |
| **Shop manager**             | View plans for assigned shops; view analytics & signals.      |
| **Shop viewer**              | Read-only on assigned shops + analytics.                      |
| **Analyst**                  | Analytics & signals across all shops.                         |
| **Plan approver**            | Decide on plan approval requests.                             |

### Permission domains

Permissions are fine-grained and grouped by domain — for example
`inventoryPlans.view`, `inventoryPlans.manage`, `inventoryPlans.approvalsDecide`,
`dataPlatform.configure`, `intelligenceLayer.configure`, `signals.manage`,
`analytics.view`, `org.settings.edit`, `users.view`. Shop visibility is controlled by
`shops.viewAll` vs `shops.viewAssigned`.

<Note>
  The same permission model governs the API: a [service-account token](/en/developers/authentication)
  carries a set of these permissions and can only do what they allow.
</Note>