Articles tagged permissions

Roles drift. Once a quarter, walk through the role catalog with fresh eyes — what to look for, what to clean up, and the questions that surface real problems.

Suprata ships with a small set of seed roles meant to cover common service-business shapes. Here's what each one is for, the permissions it grants, and when it's the right pick.

Business units split one company into locations or departments, such as six shops, or Residential and Commercial. Each person works in one unit at a time, and lists and totals open on it. Nothing is walled off: search an...

Field techs need just enough access to do their work — and not access to pricing, customer payment data, or other techs' jobs. Here's the right permission set, the device considerations, and the safety practices.

Add staff users with the right roles and team assignments. The judgment calls — when to use built-in roles vs. custom ones, when to share vs. split — matter more than the clicks.

How to run customer and internal requests as tracked tickets: the queue, claiming vs assigning, public replies vs internal notes, statuses and auto-close, and the per-category permission matrix that trips most teams up.

A tour of the major permissions in Suprata: what each one actually controls, the ones people commonly mis-grant, and how to think about them when building roles.

Custom roles are powerful but easy to overuse. Three signals tell you when a custom role is the right answer, and the cloning pattern that keeps your role catalog manageable.

One list of every customer you need to reach: renewals, appointments to pin down, on-site jobs with no visit booked, calls, and follow-up surveys. How to set up views for each job you do, call one customer after another,...