← All features
Field Ops

👥 Team & Role Management

Two independent controls, deliberately kept apart: what a role is allowed to do, and whose records a person can see. A bug in one must not open the other.

Team & Roles5 members
Mateo R. Adminfull access
Sam K. Managercatalog
Jess T. Technicianfield
Lee P. Customer Svcscheduling
What you get

Permission, certification, visibility

Six roles, sixteen permissions

Admin, Manager, Customer Service Advisor, Setter, Technician and Super Admin, against sixteen named permissions in four groups. The defaults are sensible and every one of them is yours to change per company.

A technician can recommend, not approve

By default a tech gets field notes, checklists and recommendations — and not the permission to accept the work they just recommended. The person who benefits from the upsell is not the person who signs it off.

Certification is a hard lock

Until a manager, advisor or technician has passed their required courses, every permission returns false and they are sent to Training on login. Not a nag banner — the app will not let them work.

A six-rung technician ladder

Intern, Apprentice, Tech I, Tech II, Senior, Master — each with a recommended number of completed jobs behind it, enforced only if you choose to enforce it.

Visibility is a separate axis

Switched off by default. Switched on, everyone but an admin sees only records where they are the setter, closer, advisor or technician — and a manager sees their whole downline, however deep the org chart goes.

Honest about what this is

These controls are in the app, not in the database. They stop the honest mistake and they keep people in their lane; they are not a substitute for the access controls a security review would ask about, and we will not pretend otherwise.

See Team & Role Management in your workflow

Get a personalized demo of Sun Service CRM for your team.