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

# Setup & configuration

> Authenticate, configure your operating context, and prepare FUEL for order injection and event simulation.

## Authentication

FUEL uses its own account system separate from the FIRE platform. Navigate to the FUEL login page and sign in with the credentials provided by your team administrator.

<Note>
  FUEL accounts are managed by a superadmin. If you do not have credentials, ask your administrator to create an account for you via the **Admin** panel.
</Note>

## The operating context

Before using any FUEL tab, you must establish an **operating context** using the sidebar. The context tells FUEL which FIRE environment and store to target for all operations.

The sidebar contains four sequential dropdowns and a store picker:

<Steps>
  <Step title="Select an environment">
    Choose the FIRE environment you want to target (e.g., staging, production, a client-specific sandbox). Environments are configured by a superadmin and each one points to a specific FIRE base URL with its own API credentials.
  </Step>

  <Step title="Select an account">
    Pick the account within that environment. Accounts group vendors under a single operator entity.
  </Step>

  <Step title="Select a country">
    Choose the country of operation. Country selection affects fiscal document formats, currency handling, and channel availability.
  </Step>

  <Step title="Select a vendor">
    Pick the vendor (brand or concept) you are testing. Each vendor has its own API key scoped to the selected environment.
  </Step>

  <Step title="Select a store">
    Use the store picker to choose the specific location. The store picker lists only stores that belong to the vendor you selected above.
  </Step>
</Steps>

Once all five selections are made, the operating context is active and every tab will target that environment + store combination.

<Warning>
  Tabs such as **Single order**, **Batch**, and **Cancel order** are disabled until a complete operating context is set. Make sure all five dropdowns show a value before proceeding.
</Warning>

## Environments

Environments are the bridge between FUEL and a FIRE deployment. Each environment record stores:

* A **FIRE base URL** (e.g., `https://api.staging.firepos.io`)
* One **API key per vendor**, scoped to that environment

Only a superadmin can create or edit environments. If you need a new environment (e.g., a new client sandbox or a UAT environment), contact your superadmin.

## Admin panel (superadmin only)

The **Admin** panel is accessible from the sidebar by users with superadmin privileges. It contains three sections:

<CardGroup cols={2}>
  <Card title="Environments" icon="server">
    Add, edit, or deactivate environments. For each environment you can configure the FIRE base URL and set per-vendor API keys.
  </Card>

  <Card title="User management" icon="users">
    Create FUEL accounts, assign roles (user / superadmin), and deactivate accounts when team members leave.
  </Card>

  <Card title="Test menus" icon="utensils">
    Create and manage test menus — product catalogs used by **Single order** and **Batch** to build order payloads.
  </Card>

  <Card title="Stores" icon="store">
    View and sync the store list for each vendor/environment combination.
  </Card>
</CardGroup>

## Test menus

A test menu is an admin-managed product catalog that defines which products, channels, and payment processors are available when building an order in FUEL.

Each test menu is scoped to a specific environment and vendor, and contains:

* **Products** — items with name, price (in the currency's minimum unit: centavos for BRL, dollars for USD), and optional modifier groups (sauces, sizes, extras)
* **Channels** — the order channels available for that vendor: `POS`, `KIOSK`, `APP`, `AGGREGATOR`
* **Processors** — the payment methods the vendor accepts

<Warning>
  **Single order** and **Batch** require at least one test menu assigned to the active vendor and environment. Without a test menu, FUEL cannot build order payloads and the injection controls will be unavailable. Ask your superadmin to create a test menu if none appear in the selector.
</Warning>

<Tip>
  Test menus can model multiple product lines and price tiers. Create separate menus for different test scenarios (e.g., a "happy path" menu with simple items and a "modifiers" menu to stress-test modifier groups).
</Tip>

Once your operating context is set and a test menu is available, you are ready to start injecting orders. See [Single order](/en/fuel/single-order) for a step-by-step walkthrough.