Short answer

A Field Operative can view assets, see and complete the jobs and inspections assigned to them, raise defects when they spot something needing attention, and not much else. They can't create or edit assets, they can't see the routines layer above their daily task list, and they can't manage other users. It's the right role for the day-to-day grounds team — minimum to do the job, nothing extra to break.

Detail

The Field Operative role is the standard non-admin role for the people actually doing the work — bin emptiers, grass-cutters, litter-pickers, inspectors. The role is designed around the mobile app, where the user just sees the list of jobs for the day, taps in, captures the data, and moves on.

What a Field Operative can do:

  • View assets — see the asset register on the map and in the list view, on both mobile and web. Useful when they need to find an asset by name or browse what's in a park.
  • View, update, complete, and delete inspections and jobs assigned to them. That's the core workflow on the app: open today's list, work through each task, mark done.
  • Raise defects. When they spot something — a damaged bin, graffiti, a broken bench — they create a defect record on the app, attach a photo, and assign it to whoever's the right person to action it (usually the Services Manager or Supervisor). This is the main route by which on-the-ground intel feeds back into the work-tracking system. See How does the defect workflow work — from a failed inspection to resolution?.

What a Field Operative cannot do (by default):

  • Create or edit assets. Asset capture and the asset register are reserved for admin-tier users. If you want a field-tier user to capture assets, it's usually a separate "asset capturer" person on a higher role (or a one-off elevation during a capture sprint). Worth keeping separate so the asset register stays clean.
  • Create routines or recurrence templates. They consume what they're given.
  • See the routine layer above their daily task list. From the mobile app they just see jobs — they don't know which routine each job belongs to. So the routine names, structure, day patterns are entirely a supervisor concept.
  • Manage other users, change account settings, or see the admin panel.

Setup: when adding the user — Add User → name + email → role: Field Operative. They get an invite email; once they accept and install the app, the work begins to flow.

Watch-outs

  • Don't give an operative TENANT_ADMIN out of convenience. It's the most permissive role and means they can accidentally edit or delete things they shouldn't. If you find Field Operative too restrictive, raise the gap — often the right answer is a small permission addition, not a full admin grant.
  • Field Operatives need camera location permissions if they're going to do any asset capture — but if they're not capturing, they don't need it. See How do I set up a phone so its photos carry the GPS location for asset capture?.
  • When a Field Operative leaves, the only way to remove them is to delete them — there is no deactivate option (delete/bin icon on the Manage Users list). Reassign any outstanding jobs first, since deletion is permanent. See How do I migrate a Civic.ly user to a new email address?.
  • Defect-raising is an underused capability. Operatives often don't know they can raise defects until you train them on it. Worth a 10-minute walkthrough on the day they get the app — it's the single feature that most leverages their being out in the field.