Roles and permissions

Four roles, each seeing exactly their job

A tech does not need your revenue, and a dispatcher should not complete field visits. Roles here are enforced at the server, so what a teammate cannot see was never sent to their screen in the first place.

Least access, without the lecture

Every screen, query, and export respects the role. That is a security posture, but it is also just a better workday: nobody wades through screens their job never touches.

  • Server-side, not hidden buttons. Data a role cannot see is never computed for them, let alone sent and hidden.
  • Grows with you. The standard four cover most operations; custom sets arrive when your org chart outgrows them.

Everything in roles

Four roles that match real jobs

Owner, office manager, dispatcher, tech. Each role opens to the screens that job touches and nothing else.

Financials gated at the server

Revenue and receivables are computed only for roles allowed to see them. A tech literally cannot load your MTD number.

Dispatchers schedule, techs perform

A dispatcher can build routes and move visits but cannot start or complete field work, so the record of who did what stays true.

Custom permission sets on Scale

Past the standard four, Scale and Enterprise let you shape permission sets to your org: a bookkeeper role, a regional lead, a read-only auditor.

Invites that carry the role

Invite a teammate by email with their role attached. They land in the right experience on first sign-in.

Billing follows activity, not seats

An active employee is anyone who signed in during the billing period. Dormant accounts cost nothing; active ones are $10 a month past your allowance.

Put it on a truck this week

HoundStack is available now. Start today with a 14 day free trial, no credit card, and your first 3 teammates included.

14 day free trial · No credit card · Cancel anytime