# Seats (/enterprise-offline/sc-key-server/seats)

Each new activation uses one purchased seat. The example shows an organization with 100 seats.

| Activity                           | Allocated | Available | Result                               |
| ---------------------------------- | --------- | --------- | ------------------------------------ |
| Before deployment                  | 0         | 100       | Ready to activate                    |
| First 78 installations             | 78        | 22        | Activated                            |
| 100th installation                 | 100       | 0         | Activated                            |
| 101st new installation             | 100       | 0         | Declined                             |
| Authorized replacement of seat 042 | 100       | 0         | New device assigned to existing seat |

To add seats, [contact SonicCloud](/support/contact).

## Registration records [#registration-records]

SC Key Server keeps a record for every activation: the assigned user, the seat, the device and its activation history. Administrators can find an installation by user, computer name or asset tag, when one was supplied.

| Seat | User     | Device            | SC Key ID       | Status |
| ---- | -------- | ----------------- | --------------- | ------ |
| 001  | User 1   | DELL-LATITUDE-01  | SCK-ACME-000001 | Active |
| 042  | User 42  | DELL-LATITUDE-42  | SCK-ACME-000042 | Active |
| 100  | User 100 | DELL-LATITUDE-100 | SCK-ACME-000100 | Active |

These are examples. Real device names and users come from your activations.

Next: [Device replacement](/enterprise-offline/sc-key-server/device-replacement).