Skip to main content

Crews see their jobs. Managers see the money.

Field staff need the address, the scope, and the access notes. They do not need the margin, and in most businesses they should not have it. Roles decide who sees what.

Pro and upOrg-scoped on every query
Role · field crew
  • Assigned jobs and visitsvisible
  • Property access notesvisible
  • Job margin and costshidden
  • Client payment detailshidden

Illustrative — sample data

Least privilege

Field staff never see margin or payment details

A crew member opening a job should see what the work is, not what it earns. Restricting that is not distrust — it is the difference between an accident and an incident when a device goes missing.

Enforced in the data layer

Scoping is not a UI decision

Every query is organisation-scoped server-side. Hiding something in the interface is presentation; enforcing it where the data is read is security, and that is where this happens.

Request path
  1. 1

    Request arrives

    With the caller’s identity attached.

  2. 2

    Organisation scope resolved

    Before any data is read.

  3. 3

    Role checked on writes

    Not just on the button that was clicked.

  4. 4

    Sensitive actions audited

    With an attributable trail.

Illustrative — sample data

Where this sits in the day

  1. Get Found
  2. Win Work
  3. Run the Day
  4. Get Paid
  5. Run the Business

Questions people ask

Start using Roles & Permissions.

Set up your first crew, route, and quote today. Bring the clipboard if you must.

Get started