The apprentice does not need to see your margins
Every person gets their own set of permissions — what they can open, what they can change, what they can delete, and whether they see money at all. The part that matters is where it is enforced.
There is a difference between a price being hidden and a price never beingsent. Only the second one is real.
The number is fetched, sent to the browser, and then not drawn. Anyone who opens the network tab in their own browser can read it. Nothing was protected; something was painted over.
The database blanks the price on every line item before it leaves the server, for anyone with that box ticked. There is nothing in the page to find, because it was never put there.
A two-shop business, five kinds of login
Nothing here is a fixed role you have to accept. These are just the shapes shops usually end up with — every switch is per person.
| Who | Which jobs | Sees money | In other words |
|---|---|---|---|
| The owner | Everything, everywhere | Yes | Both shops, every job, every price, and the settings that decide the rest. |
| Office & counter | Every job, both shops | Yes | Takes work in, builds quotes, chases parts. Needs the money to do the job. |
| A shop foreman | Their own shop | Yes | Runs one location. Sees its board and its numbers, not the other site’s. |
| A mechanic | Their own shop | No | Does the work, logs the time, adds the notes. Never sees what it was sold for. |
| An apprentice | Their own shop | No | Same again, and cannot delete anything they did not mean to. |
Two shops working at once, and no collisions
Somebody tied to one location sees that location's board and not the other's. Job numbering is per site too — Freehold's jobs and Atlantic City's jobs cannot land on the same number, however busy both counters are.
A person can hold several locations, or all of them. It is a list, not a single choice.
⚠️ Two locations must never share a site code. That is what keeps the numbering apart.
What this does not cover yet
If your company adds its own custom fields and marks one of them as a currency, that field is not covered by the blanking yet. Prices on line items, on the job, and in the activity log all are. Custom currency fields are known, logged, and being worked on — and they are the sort of thing you would find on your own in week two, so you may as well hear it now.
Want to see it from a mechanic's login?
The most useful half hour is watching the same job from your login and then from theirs. We'll set both up before we show you.
Book a walkthrough