The same roster the Team page draws its cards from, so both screens answer 'who works here' the same way. One card per person, grouped Office, Sales and one section per crew. Open a card and you edit their details, role, work record and what they can see — all in the one panel. An admin manages everyone; a sales manager gets in too, with Edit on his own sales reps and nobody else.
Also called: who works here · staff list · employee list · user accounts · add a person
The list is grouped the way your company is
Office, then Sales, then one section per crew with the leader at the top, then anybody not on a crew yet. Rename a crew and it is renamed here. One alphabetical column of names is a list you read line by line to find one man — and the company already has a shape.
Nineteen identical full-width rows, and finding the framer whose number changed means reading every one of them to the end.
The office finds the right person in a glance instead of reading nineteen names to the end — and the owner sees the shape of his company, office to crews, the way he already thinks about it. The crew sections come from the same crew rows the Team page uses, so the two screens can never disagree about which crews exist, and each leader sits at the top of his own.
The men without an email address are still on the list
Most of a builder's roster has no work email and never signs in — the framers, the concrete crew, the man who does the dirt work. Software that treats a man and a login as the same thing shows you five people. This list shows everybody on the books and says how many of them can sign in. The crews reach their work through a texted link instead, and they are still real, editable people here.
The framer who has been with you nine years has no work email, so the screen that is meant to list your company lists five people and not one of them swings a hammer.
The framer who has been with you nine years is on the list like everyone else, so the office can keep his number and crew current — and nobody is left off a roster because he doesn't own a laptop. Whether someone can sign in is decided by a real account, and every id they have ever had is kept, so the link sent last month still reaches them.
One list, and every screen agrees with it
Try itThe Team page and this tab used to answer 'who works here' differently. On one builder's account that was nineteen men against nothing at all, which reads as the screen being broken. Both now draw off the same roster — so does the assignee picker on a job and the crew's own phone view — and a role change on one device is the truth on the next one.
You take somebody off the team at the desk, and a fortnight later the truck laptop still offers his name when you go to assign the job.
Take someone off the team at the desk and they are gone from the truck laptop too, so nobody assigns a job to a man who left in March. One shared roster costs a quick look-up each time instead of a copy kept in the browser — and that stale copy is exactly what let a removed man keep showing up.
The same man in three places is still one row
Try itA crew leader is often a crew record, a role record and a login all at once. They fold into one person — matched on account id first, then email, then name — and the strongest role wins, so a crew lead who is also an admin is listed as an admin. His colour, his tier and his field link are set on the Crews tab; this is the same man, seen from Settings.
The same foreman shows up three times — once as a login, once as a crew row, once with his email where his name should be — and nobody can tell which of the three to edit.
The office edits a foreman once and it's right everywhere, instead of guessing which of three entries is the real one. Records fold together on the strongest match first — account, then email, then name — and a crew a record claims is checked against the crews you actually have before it is believed.
Edit someone in place — their crew, their role, their record, what they can see
Open the card and it is all in one panel: details, crew, role, and his work record — hours, jobs and earnings for field crew, the leaderboard line for a rep. Nothing sends you to a second screen and nothing gets typed twice. Typing the same phone number into three screens is how two of them end up wrong.
Changing a framer's crew takes Settings for the role, Team for the crew and a third screen for his hours — and by the third one you have forgotten what you came in to change.
The office makes a change in one sitting without hopping between screens and forgetting what they came in to fix — and a phone number typed once can't be wrong in two other places. The open card widens across the grid rather than moving everything else; a login holder's name and email are shown read-only because their own sign-in owns them.
His record is on his row — hours, days, jobs, what he took home
Try itPay tier, hours logged, days on site, paid out, and what he actually made per day against the rate he is on — then a month-by-month bar and the jobs the time went to. His row shows what he was paid, not how the number was reached: the day rates, the pool and the surplus split are in day rates with shared surplus.
The pay conversation happens from memory, and the man across the desk remembers the two long weeks in March a good deal better than you do.
Pay conversations happen with the numbers on the table instead of from memory, so the owner and the man across the desk argue about the same figures — and a good worker sees his own days and earnings laid out. Earnings are worked out by the same payout maths the job uses, and shown per day because a day-rate man is measured against his day rate.
A rep gets a different card than a framer
No hours, no days on site. A sales rep's record is leads worked, deals won, close rate and his rank, read out of the same leaderboard the Sales tab draws — so the two screens cannot quote different years. An office user with neither gets one sentence saying so, not a card of dashes.
The rep's card reads nought hours and nought days on site, and the man reading it over your shoulder takes it to mean he did nothing.
A rep's card shows what he's judged on — leads worked, deals won, his rank — so it reads as a scorecard he can be proud of, not a page of zeros. Which block appears is decided by what the person actually does, and the figures come from the same leaderboard the Sales tab shows.
Permissions show up only where there is an account to hold them
A crew member with no login gets a sentence saying why, and Invite to log in, which opens the invite already filled in from his row. Not a grid of checkboxes that save nowhere. For somebody who does sign in, the grid shows their own settings — what follows their role, and any exception made just for them. Ticking boxes that quietly do nothing is worse than no boxes — you walk away believing the job is done.
You tick eight boxes for the crew leader on Friday, and on Monday he still cannot open the schedule, because there was never an account under the boxes.
The owner never walks away thinking he gave a crew leader access that doesn't exist — the screen offers the one thing that would change it. Permissions live on the sign-in account, so with no account there is nowhere to put them; how the switches and exceptions work is on roles and permissions.
The roles he is offered are the ones his record can hold
Try itA crew record holds Worker or Crew Leader — those are the two things it is. Somebody who signs in can be given any of the six roles: Admin, Sales Manager, Sales Rep, Project Manager, Crew Leader, Worker — with Admin only shown to an admin. A sales manager is offered exactly one: Sales Rep. When one person needs one thing their role does not give them, you flip that single switch on their record, and roles and permissions covers what that changes.
You promote the concrete foreman to Project Manager, the button lights up under your finger, and nothing anywhere actually changes.
Every button the owner presses does what it says, so a promotion is a promotion and not a highlighted button that changed nothing. The write goes to whichever record the person came from and returns a refusal rather than a silent success when it can't land.
Once a year somebody has to say this list is right
Everyone who can sign in, what they hold, and when they last did it — with the ones who never have called out in the margin. Marking it reviewed freezes a dated snapshot of exactly that list, against the name of whoever pressed it.
The salesman who left in February still has a working login in November, and you find out when he opens your pipeline from his new job.
The owner can show an insurer or a commercial customer a dated list of exactly who had access, instead of promising he checks — and the salesman who left in February doesn't keep a working login till November. It goes overdue after a year and says so, because nothing else on the screen would ever raise it.
Someone who leaves gets switched off, not erased
Try itCutting access today is one press — Disable — and the record stays: the stages he finished, the photos he took, the hours he was paid for, his days on site. Re-enable brings him back if he does. Removing him outright sits behind Remove permanently? and is rarely what you want — deleting the man deletes the history that says who built it.
You delete the framer who left in the spring, and the eleven checkpoints he ticked on the Byler barn are now signed by nobody at all.
The owner can shut a door the same day someone quits without wiping out who built what — so a warranty call two years on still has a name beside every checkpoint. Disabling is reversible and one press; removing is a bigger, separate act with its own confirm.
It is the first tab under Team, and not everybody gets it
Team Members sits at the top of the Team group in Settings, beside Roles & Access and Pay Structure. An admin gets the whole roster. A sales manager gets in as well — he can read the whole list but only edit and invite sales reps, and that limit is held where the write happens, not by a button being left undrawn.
Your sales manager follows an old bookmark into the team screen and changes a crew leader's role, because the only thing that ever stopped him was a button that wasn't drawn.
The owner can hand the sales bench to his sales manager without handing over the company — he looks after his reps and can't touch the crews or the office. A hidden button is not a permission, so the limit lives on the server and the screen is free to be honest about what exists.
A sales manager looks after his own reps — and nobody else
Try itOpen Team Members as Priya, the sales manager, and Edit appears on Marcus and Sheila and on nobody outside sales. She can change a rep's phone, email and address and press Save & close; the only role she can hand out is Sales Rep. The owner stops being the person every new phone number has to go through.
A rep changes his cell number, the sales manager can't update it, and for two weeks his customers' calls ring a phone he no longer has.
The sales manager keeps her team's details current the day they change, and the owner gets his evenings back — without making her a second admin who can reach the crews, the money or the account. Her reach is decided per person on the server, so the screen and the save always agree.
- 1Open Team Members and everybody on the books is listed.
- 2Cards are grouped Office, Sales, then one section per crew, and anybody not on a crew yet.
- 3Open a person's card to edit their details, role and record in place.
- 4The header counts how many people you have and how many of them can sign in.
- 5Somebody who leaves is switched off, not deleted — their record stays on the jobs they worked.
- 6A sales manager sees the whole list and can edit only his sales reps.
A builder opened Team Members on his own account and it was empty — while the Team page showed three crews and his salespeople, nineteen men. Both screens were answering the same question and giving different answers, because one counted sign-in accounts and the other counted people. Most of a builder's roster has no work email and never signs in. Software that treats a man and a login as the same thing shows you five people and charges you for five people.
- Two screens answered who works here with different numbers.
- Field labour with no login was invisible in Settings.
- A browser-local copy of the team list survived long enough to show a stale list after someone was removed elsewhere.
Roster grouped the way the company is
Instead of one long alphabetical list, men are bucketed by where they actually work. Crew names come off the same crews the Team page uses, so renaming a crew there renames it here. Each section header carries a count.
Edit a person in place
One editor for every kind of person on the roster. A man with no account still has his name, email, crew and role edited here. A man with a login has those held on his own profile, and gets the permission grid instead. Either way his record is right there — hours, jobs and earnings for field crew, the leaderboard line for a rep.
Saved, or save failed, on every edit
Edits save themselves, which is invisible unless the screen says something. A small marker on that man's row turns green for a second on success and red for four seconds on a failure, then re-reads the list so the rejected value is not left sitting on screen.
Permissions only where there is an account to hold them
What a man can see is held on his account. If he has not got one, that half of the panel is replaced with a short line saying so — and noting that crews reach their work through a link and most never need a login. The button beside it opens the invite already filled in from his row.
Switch someone off, or remove him
Two controls at the bottom of a man's card. Off cuts his access today and leaves everything he did on the job. Remove clears him out for good and cancels any invites you sent him. A retired crew member shows as switched off rather than vanishing.