Seat Licence

Team software is often sold by seat: an organisation buys a number of access slots and assigns them to people, and a seat is a licensing measure, not necessarily a physical chair or a person currently logged in. A fictional design firm that buys ten seats for an editing app assigns them to ten staff members, so an eleventh person needs an available or additional seat under those terms and finance checks when it becomes billable.

Some products use named-user seats while others use concurrent access, device seats or role-based pricing, so do not assume a term from one vendor applies to another and read the current licence agreement. A fictional business with 20 employees but only five simultaneous users may find a concurrent plan fits, while a named-user plan may count all 20 people requiring access.

Polar describes a payer buying assignable seats, with pending, claimed and revoked states, and it distinguishes the billing customer from the people who use the product. A seat's price may be monthly, annual or one-time, and additional seats can change the bill immediately, at renewal or through tier pricing, so a fictional team that sees a low per-seat monthly quote checks the annual commitment and minimum seat count before approving it.

Billing and access are not always simultaneous: Atlassian's cloud licensing page says product access can make a user billable, and that its particular removal rules affect counts, which is a product example, not a universal software rule. A fictional admin who invites someone to a work app verifies when that invitation starts billing rather than assuming no accepted login means no cost.

Assign access deliberately, since team members should receive only the products and roles they need and an administrator seat can carry greater risk than a member seat. Keep an inventory of assigned, available and inactive seats, because an employee leaving the company may retain access and continue costing money if offboarding is incomplete, so when a fictional staff member leaves in March, IT disables access and finance checks the next invoice for any continuing seat charge.

Reassignment can have restrictions, as a vendor may enforce a minimum assignment period or allow immediate moves, and frequent sharing of one named seat may breach terms even when only one person logs in at once. A fictional business that rotates one account among several contractors checks the licence and moves to individual authorised access rather than sharing passwords.

Separate the licence seat from the user account, because removing someone from one project may not remove their product-level access or billing, so check the relevant administration level. Audit usage carefully, since inactivity suggests review, not automatic deletion, and intermittent needs and role ownership should be checked before revocation.

Tiered prices can make marginal cost surprising, as buying one more seat may shift a plan tier or add a minimum package, so a fictional company growing from nine to ten seats checks whether the entire subscription enters a new price tier and which billing cycle includes the change. Contractual limits may include geography, device, affiliates or permitted use, so a seat count alone does not describe the full right and the agreement should stay accessible to admins.

Shared service accounts need special review, since a vendor may provide a bot or automation licence with different rules and human use should not be hidden behind a machine account. Watch renewals and true-ups, because a vendor may count peak users or current users under specific billing rules, so snapshot assignments and reconcile invoices to the contract, and check whether a fictional team that reduces seats halfway through the month receives a credit now or only at the next cycle, since a seat licence is a defined right to use software whose scope and billable moment come from the vendor's actual terms, not the casual meaning of "seat."