Seats
Some agreements are priced by the number of people who actually use them rather than by named users. This page explains how that count works — and it is worth reading before somebody reports that they cannot get in.
On this page
How counting works#
A seat-capped licence carries two numbers: how many people may use it, and an activity window. Somebody occupies a seat if they have used the app within that window.
Nobody assigns seats. There is no list to maintain, no joiner-leaver process to wire up, and no administrator deciding in advance who counts — the roster is simply who has been using it.
One person, one seat#
A seat follows the person, not the device or the session. The same user on a laptop, on a phone, in a second browser and after signing in again is one seat.
We identify them by the opaque user id FSA already issues. We do not receive a name or an email address — the security page lists exactly what is sent.
How a seat frees itself#
When somebody stops using the app and the activity window passes, their seat is available again. Nothing is deleted and nobody has to file a ticket; the count simply reflects reality.
This is the practical difference from named-user licensing: a technician who left in March stops being billable without anyone remembering to remove them.
When the cap is full#
Somebody already working is never evicted to make room. If the cap is genuinely full when a new person arrives, they get a dedicated screen — not the generic licence error — that names the count and points them at their own administrator.
Raising the cap#
We issue a licence with the new cap and you paste it into the same field. Nothing is reinstalled, and the new number takes effect as caches lapse — within the hour. It can also be done mid-term, pro-rated.
If our service is unreachable#
The user is let in. A seat check that cannot run never blocks somebody trying to work — seats exist to price fairly, not to police. This is the deliberate exception to how the rest of licensing behaves, and it is explained alongside the others on the security page.