A supervisor runs crews in the field: they build schedules, approve timesheets, follow their sites. They touch neither payroll, nor settings, nor access management: for that, an administrator is what you create.
Two notions combine and are often confused. The TERRITORY says which clients and projects the person acts on. The PERMISSIONS say what they do there. The two are set separately, and this article follows that order.
- Scope
- The clients and projects assigned to them
- By default
- Everything open, to be closed as needed
- Never reachable
- Payroll, settings, access management
Before you start
- An administrator account with the permission to manage access.
- The person's email address: that is where their invitation goes.
- 1
Read the supervisor list
“Supervisors”, in the Team section. Seven columns, one of which sums up all the rest: “Assignments” says how many clients and projects each person covers.
The filters at the top sort by status, department and region. As elsewhere in the product, a “Trash” tab keeps what was removed, restorable.
The framed column is the one that states the real reach of the role. One line: the person, their position and department, their region, their territory, their CCQ card where relevant, their status. - 2
Supervisor or administrator?
The record page answers that itself, and the sentence is worth reading before creating anyone.
A supervisor sees and acts on THEIR territory. An administrator sees the organisation. Giving a crew leader an administrator role to spare them a limit means opening payroll and everyone's access to them.
The limit is structural, not a permission you could tick. One person can be both
Nothing prevents the same person from having a supervisor record and an administrator account. They are two distinct roles with two sets of rights: and that is clearer than stretching one to cover the other.
- 3
Create the record
“New supervisor” opens a single-page form. The warning at the top is useful: the payroll fields specific to employees are not there, because they do not apply.
First name, last name and email are enough to create the record. The rest can be completed later.
1 the identity, shown everywhere including the audit trail · 2 the invitation, sent on save. - 4
Choose the languages
Two neighbouring fields that do different jobs. The “correspondence language” is the one for their notices, their documents and their mobile app. Left inherited, it is their account's, otherwise the organisation's.
The “spoken languages” are declarative: they say which languages the person is comfortable in. They serve to pre-fill parity committee forms, and to know who can greet a client in their own language.
1 the language you write to them in · 2 the languages they speak. - 5
Open the access
A username and a password, both optional. Leaving the password empty is the normal case: the person gets an email invitation and picks their own.
Typing it yourself only makes sense for a shared account or a person with no usable email address.
Empty password = email invitation. - 6
Describe the position
The position and the department are required: they feed the list filters and the report groupings.
“In post since” dates the start of the role. The region is for sorting and restricts nothing: the territory, at the next step, is what decides the real reach.
The region files; it does not bound. - 7
Set the territory
This section only appears once the record is saved: you create the person first, you give them their territory next.
Two lists, and one counter-intuitive rule worth knowing: no client ticked means they cover them ALL. Ticking, here, is for restricting: not for authorising.
Projects are chosen among the active projects of the ticked clients. The consequence is written under the field: removing a client also removes its projects.
1 “No client ticked: they cover them all” · 2 projects follow the clients, and disappear with them. An empty record grants access to the whole organisation
Creating a supervisor with nothing ticked opens every client and project to them, within the limits of their permissions. It is not an oversight in the product: it is the setting that suits a small organisation. As soon as there are several crews, tick.
- 8
Set the permissions
Six switches, grouped in four families, all open by default. The principle is written at the head of the section: “Everything is open by default: close what does not concern them.”
They apply INSIDE the territory, never beyond it. “Manage their clients” gives access only to the clients ticked at the previous step.
The six switches, as delivered: all open. Permission What it opens Plan schedules Create, change and publish their crews' shifts: open shifts included. Approve timesheets Approve, reject and correct their crew's hours. It is a write that freezes a pre-payroll calculation. See the field map Who is punched in, where, right now: and the replay of the day just gone. Manage their clients Addresses, notes and documents of the clients in their territory. Manage their projects Project details and geofencing of work sites, on their projects only. See rates and budgets Hourly rates, costs and project budgets. This is the one closed most often. Closing a permission does not remove the territory: the person still sees their sites, they simply no longer perform that action there.
What to remember
A supervisor can also be attached from the client
The “Team” tab of a client record lists the supervisors linked to it. It is the same attachment, seen from the other end: handy when you start from the site rather than from the person.
Internal notes are not visible to the person concerned
The “Internal notes” field on the record is reserved for administrators. It appears neither in the person's mobile app nor in the documents meant for them.
Removing a supervisor does not delete their history
The record goes to the trash and stays restorable. The schedules they built, the timesheets they approved and their trace in the audit trail do not move: which is what makes the history defensible.
Go further
Inviting an administrator and setting their permissions
Giving someone access without giving them everything: the difference between administrator and supervisor, the four families of rights, and what a removed permission actually hides.
LireClients and projects
The frame everything else hangs on: what a project is for, what it decides for the hours worked on it, and why some records refuse to disappear.
LireApproving a week of timesheets
Review punched hours against the planned schedule, understand what the decree adds, and approve: knowing what approval locks in.
LireCan't find what you're looking for?
Our team can answer your technical questions and support your rollout.

