Operations & Administration (Control)
Seats per customer
liveForOperator
How many seats a customer has agreed and occupied, who is invited, what is free — and what that means in the current month. Deliberately without names.
Why#
The platform sells seats. The operator sees usage, not people — and sets the limit at which new enrolments are politely refused.
How it works#
Click pathAdministrationSeats
- 1Open “Seats”. At the top four figures: seats agreed, of which occupied, billed in the current month, test seats (free of charge) — plus the base fee of the month (billed seats × rate per seat) (Fig. 1).
Fig. 1 Seats agreed, of which occupied, billed and test seats — with the base fee of the month. - 2The table per customer: agreed (as an input field), occupied, free, invited, test and the situation in percent with a word (“room to spare”, “getting tight”, “full”, “nothing agreed”).
- 3Enter a new number under “Agreed” and “Set” — the message confirms it and warns if more are already occupied.
Settings and switches#
No switch of its own in the feature catalogue — the feature belongs to its surroundings.
How counting works#
- One person, one seat — even with several courses. Whoever leaves frees the seat; the row remains as a record so that a past invoice remains traceable.
- Partial seats count in full: whoever starts on the second and stops on the fifth is on the monthly invoice.
- Without an agreement nobody gets in: if it says 0, every enrolment and invitation is refused — with a clear reason, not with an error.
- Test accounts do not occupy a customer seat: the public tour creates real accounts; they go to the provider, not to the customer.
Who may do what#
Only the operator sets limits. The page shows no names — who occupies the seats is managed by the customer themselves (workforce, student administration).
Tips#
- If the limit is set below the number of occupied seats, nobody is thrown out — only nobody new is added.
- If no rate per seat is stored, the seats are counted but not priced; the page says so.
- Usage (streaming, dialogue) is added separately — see “Usage”.
Related features#
- Modules & pricesPer customer a package of bookable modules with prices — booking sets the switches of the feature catalogue, dependencies are booked along, every change is in the history.
- Costs, usage & controllingMonthly costs and revenue, usage per student and customer, the derivation of the rendering costs and the controlling cockpit with the state of the university.
- Workforce, units & importEmployees with unit, role and manager, the organisational units and the bulk import via CSV.
