What each person is shown is what their role can do
Your manager now changes the compliance, margin alert and service agreement settings, a dispatcher's compliance entry is complete, and nobody is offered a button their role cannot use.
A role decides what each person on your team sees and changes. Here and there a page still offered somebody a button, a list or a setting their role could not use — they pressed it and were told no. Now what a page shows each person is what they can do.
Your manager runs the first tools’ settings. Compliance’s reminder windows, Margin Intelligence’s alert thresholds, Service Agreements’ renewal settings and the reminder timings in Automations were yours alone, because they saved onto your business’s own record. Each saves on its own now, and a manager changes them. The target margin, the auto-pay failure limit and anything that sends a text stay yours.
A dispatcher’s compliance entry is complete. Recording an application on a job now lists the regulated products and the applicator’s licenses, so the record carries both, and New Appointment offers your bookable services and open times.
What somebody’s work needs from another area comes with it, by name. A bookkeeper’s expense names the job it was for, and a stock clerk’s return names its supplier, without either reading what those records hold. A role you build picks a client by name and business when it does not hold the client list.
A button belongs to the work. Writing a change order, logging time on a job, adding a kind of work, dismissing a margin alert, returning parts to a supplier: each is offered only to the person whose role changes it. Somebody who reads the job sees the change orders and the hours, with nothing to press that would be refused.
Writing proposals brings prices. On Scale, a role you build that writes proposals sees prices and costs with them, as one that keeps the invoices does — the Price Book is never drawn without its figures.