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

# Sub-users

> Split your bandwidth into sub-users, each with its own credentials and allocation. Use them to separate teams, customers, and workloads.

Sub-users let you split your main package's bandwidth into separate packages, each with its own username and password. Manage them in the dashboard at [flameproxies.com/dashboard/sub-users](https://flameproxies.com/dashboard/sub-users).

## How allocation works

When you create a sub-user, you allocate bandwidth to it from your main (primary) package. The bandwidth you allocate is deducted from the main package.

For example, say your main package has 10 GB and you create 3 sub-users with 1 GB each:

| | Main package | Sub-user A | Sub-user B | Sub-user C |
| - | - | - | - | - |
| Before | 10 GB | — | — | — |
| After creating the sub-users | 7 GB | 1 GB | 1 GB | 1 GB |

The 3 GB you allocated moves from the main package to the sub-users. Your total bandwidth doesn't change — only how it's divided.

## Top-ups go to the main package

When you top up on the website, the bandwidth is added to your **main package**. Top-ups never create a new package.

To give a sub-user more bandwidth, top up your main package and allocate from it.

## Why use sub-users

* **Per team or customer.** Give each team or customer their own credentials and bandwidth, so one can't use up another's.
* **Per workload.** Isolate a high-volume scrape from smaller jobs, so a runaway job can only spend its own allocation.
* **Per environment.** Keep staging and production traffic apart, with separate usage.
* **Contain leaks.** If a set of credentials is exposed, only that sub-user's bandwidth is at risk.

## Connecting as a sub-user

Sub-users connect exactly like the main package — same gateway, ports, and parameters — with their own username and password:

```text theme={null}
proxy.flameproxies.com:8989:<SUBUSER_USERNAME>-package-standard-country-us:<SUBUSER_PASSWORD>
```

Everything a sub-user sends is deducted from its own allocation.

## Sub-users in the Customer API

Packages returned by the [Customer API](/api/overview) include a `subuser_id` and an `is_primary` flag. `is_primary: true` marks your main package.

Every package you create with [`POST /api/customer/orders`](/api/orders/create) is created as its own sub-user, with its own credentials. Use [`GET /api/customer/packages/:id`](/api/packages/get) to read a package's credentials and live usage.

## Next steps

<CardGroup cols={2}>
  <Card title="Usage analytics" icon="chart-line" href="/dashboard/usage-analytics">
    See bandwidth and requests for your traffic.
  </Card>

  <Card title="Billing & top-ups" icon="receipt" href="/dashboard/billing">
    Pricing, payment methods, and how top-ups work.
  </Card>

  <Card title="Core concepts" icon="book" href="/getting-started/core-concepts">
    How packages, sub-users, and parameters fit together.
  </Card>

  <Card title="Create an order" icon="cart-shopping" href="/api/orders/create">
    Create packages programmatically with the Customer API.
  </Card>
</CardGroup>