Overview
Your field reps — the people who walk the beat, take counter orders, and run deliveries — need one clean list, not three WhatsApp groups and a diary. The field rep master is that list: every rep with a name, phone, employee code, and territory, kept in one place. Other features like route management and sales targets point at this master, so a rep you add here is the same rep a route walk or a target is measured against.
Opt-in Capability · off
Field Rep is switched offField Rep
You can read the guide. An owner or manager flips this Capability on in settings — it then lights up across the app.
Heads-up on enablement: the field rep master is grouped under Capabilities in the help, but it ships as an always-on Core master — it's enabled by default for every tenant, nothing to install. The permission to use it, though, sits with the Owner by default until granted to others (see Role notes).
Where to find it
The field rep master is reached from the Capabilities area of the app, on both web (desktop admin) and mobile. There is no separate top-level page in the sidebar — reps surface inside the features built on top of them, Route management and Sales targets, where you pick a rep from this same roster. Add, edit, and archive reps from there.
If you don't see field-rep actions, your role doesn't hold the grant yet — ask the Owner to give it to you.
Key concepts
- A field rep is one person in the field — a sales rep, detailing rep, dairy beat worker, or delivery hand. Same record shape covers all of them.
- The employee code is your own short label for a rep, like
FR-DEL-014. Optional, and unique amongst your active reps when you set it. - Phone is the rep's main identifier in the field. It must be a valid Indian mobile (10 digits, starting 6–9) and must be unique amongst your active reps.
- Territory is free text today —
West Delhi,Bareilly North. It becomes a structured pick-list once Route management lands properly. - A rep is either active or archived. Archiving takes a rep off the active roster without deleting their history; reactivating brings them back.
Common workflows
Role notes
Who can do what here depends on two things: the action's level (view / create-edit / archive-reactivate) and whether the role actually holds the field-rep grant. By default only the Owner holds it; the Owner can grant it to a Manager or Operator.
| Role | View reps | Create / edit a rep | Archive / reactivate |
|---|---|---|---|
| Owner | Allowed | Allowed | Allowed |
| Manager | Not allowed | Not allowed | Not allowed |
| Operator | Not allowed | Not allowed | Not allowed |
- Owner — full control: view, create, edit, archive, and reactivate reps. Owner holds the grant out of the box.
- Manager — once the Owner grants
field-rep, a Manager can view, create, and edit reps. A Manager cannot archive or reactivate — those are Owner-only. - Operator — once granted, an Operator can only view reps (look them up while taking an order). An Operator cannot create, edit, archive, or reactivate.
By default none of these grants is pre-assigned to Manager or Operator — the Owner has to hand them out first.
Tips & time-savers
bareilly pulls up every rep on that beat in one go.Re-using an old employee code or phone is fine: an archived rep's code and phone are freed up, so a new active rep can take them. You only get blocked when two active reps would clash.
Gotchas
Archiving is not deleting — there is no hard delete here, which is deliberate. A rep you archive keeps their history and can be reactivated later (the system re-checks phone and code conflicts at that point).