Running the businessTeam roles and access

Give people what they need and nothing else

Decide dial by dial what each person can see and change, and keep a record of who changed what.

Your first 14 days are free, and nothing is charged until they are up.

What this takes off your week

Giving the new estimator access means giving them your whole client list and every price you charge.

Access is set dial by dial. Nobody gets the client list because they needed the calendar.

A control was hidden from someone, and that turned out not to be the same as them not being able to reach it.

Permission is enforced on the server. Hiding a button is not access control here and never has been.

Something changed on a quote and nobody remembers doing it.

Every send, edit and approval is recorded with a name and a time against it.

Presets get somebody working in a minute; the dials are there when a person's job does not fit one.

The same permission is checked again when the request arrives, so a hand-written request gets the same answer the screen gave.

Requests reach the manager who should see them, balances build up on their own, and the calendar knows about the days that are gone.

Decide, dial by dial, what each person can see and change — and it holds on the server, not just on screen.

Thirteen dials: Ten ladders — schedule, time, payroll, notes, expenses, clients, requests, quotes, jobs and invoices — and three switches for prices, job costing and taking payment. Thirty-eight settings between them.
Two of them are not settings: Client communications and reports are shown as consequences of the others rather than as dials of their own, because a dial that decides nothing is a control that does not work.
Position on the ladder, not a name match: A level is compared by where it sits, so view and edit satisfies view without anybody listing the combinations.
You cannot grant what you do not hold: What one person may give another is capped at their own level, on the server. The editor hides what they cannot offer so nothing fails on click, and the server clamps it again anyway.
The refusal direction is no: A member who cannot be loaded fails every check. A stored level that is not on the ladder fails. Somebody scoped to their own records with no identity matches nothing rather than everything.
Role changes go through a different door: Sending a role or a set of permissions to the ordinary member update is refused with the reason, rather than accepted and ignored.

Every plan includes all of it. Plans differ by how many people can work in the account, not by which features they are allowed to use.

Team roles and access
Decide, dial by dial, what each person can see and change — and it holds on the server, not just on screen.
Who changed what
A running record of every send, edit and approval, with a name and a time against it.
Time off and holidays
Requests go to the right manager, balances build up on their own, and the calendar knows.
Employee files and compliance
A file per person: tickets and licences with expiry reminders, a new-hire checklist, policies signed by name, and a compliance view of who is missing what.

The first 14 days are free. Bring your own rates, your own logo and the client list you already have.

Contractors reading this also read