Seat: what it means
DefinitionA seat is one licensed login to a software product, held by one person. Software priced per user counts seats, so adding a new office manager or technician with their own login adds one seat to the bill.
How it works in a service business
Seats look simple until you ask who needs one. Sharing a single login between several staff saves money but wrecks accountability: no one can tell who changed a job, and a departing employee still has the password. The tradeoff is cost against traceability. A common mistake is a shared office login that everybody knows. Give each person their own seat and a role matching their work, so a technician sees their jobs and an office manager sees billing. Ask whether the product counts inactive users, whether seats can be reassigned, and whether limited field logins cost less. Review the seat list quarterly and remove anyone who has left or no longer needs access.
Example
A cleaning company gives each crew lead a seat limited to their own schedule and gives the office manager a seat with billing access, while the owner keeps full control.
Where Apex touches this
Rolling out
The screen and the rules are built and tested. Saving real customer data is not connected yet. Status as of 2026-10-07; the badge shows the least-built feature involved.
- AD01Roles and permissions(Built)
- AD13Admin activity visible to owner(Rolling out)
Apex Flow Scheduler is in early access. See how we label status.