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

# Buying more than one seat

> Let a department buy several access codes in one checkout, and how each seat gets its own code

A **seat** is one person's worth of access. If a fire department buys Heartsaver for three people, that is **3 seats** and **3 unique codes**.

This only applies to [standalone course](/courses/standalone-courses) purchases of a course that uses student access. Program enrollment still uses one seat per enrolled student.

## Set the max on the course

1. Open the course → **Course setup**.
2. Turn on standalone sale if it is not on already.
3. Set **Max seats per purchase**.

Rules:

* Default is **10**
* You can set **1** to **50**
* The checkout page tells the buyer: **Each seat receives its own credential code or link. Up to {max} per purchase.**

<Info>
  This control only appears when the delivery model is **Access from another provider** or **Both**.
</Info>

## What the buyer sees

On the public course page, they choose **Number of seats**.

* The price updates to match (quantity × price).
* If they change the number after payment has started to load, the total refreshes. They may see **Updating total...** or **Setting up secure payment...**.
* If they somehow submit an old total, checkout is rejected with a message that the seat quantity changed. They try again with the new total.

Required [agreements](/enrollment/agreements) still apply once, for the purchase, not once per seat.

## What you see after the purchase

The purchase creates **one delivery per seat** (Seat 1, Seat 2, Seat 3).

* All seats follow the **standalone** timing rule.
* If timing is immediate, they often get **one digest email** with every code.
* In the dashboard, codes are grouped: **Access code 1 of 3**, and so on.

On **Pending deliveries**, filter to that student or course and you will see one row per seat.

## Partial refunds

You can refund some seats and keep others.

1. Open the refund dialog on the purchase.
2. Select **Seat 1**, **Seat 2**, and so on.
3. The refund amount is proportional.
4. Only the selected seats have access taken back.

See [Refunds and unused codes](/student-access/refunds-and-unused-codes).

## Stock planning

Three seats hold **three** unused codes at purchase time. If you only have two codes in stock:

* Some seats may go to **Waiting for codes**
* You get a stockout email
* Import more codes; the waiting seats fill in

If a department often buys 10 at a time, keep at least that many unused codes before you share the purchase link.

## Example

Station 4 buys your AHA Heartsaver course.

1. Max seats is 10. They choose **Number of seats: 3**. Price is \$75 × 3.
2. They pay once.
3. Three Course URLs are held.
4. Because timing is **Right after purchase**, they get one email with three links, labeled code 1, 2, and 3 of 3.
5. They forward each link to a different firefighter (or you asked them in the student message to open each link on the correct person's AHA account).

Write that last part in **Student message**. The platform cannot know which seat belongs to which firefighter unless you tell the buyer how to hand them out.