Organisation dashboard

Every organisation connected to Fieldproof gets a web dashboard for its team, whether it sends cases by push, pull or CSV. Your team can use it without writing any code:

• see your cases, field visits and payments as they happen;
• correct case data: contact details, the address and its coordinates, loan figures;
• assign, reassign or unassign a field partner on your open cases (not while a payment on the case is awaiting verification);
• export collections as CSV.

The dashboard only ever shows your own organisation's cases and payments. A case that belongs to another organisation simply does not exist for your users.

Getting access

1. At onboarding, Fieldproof gives your first user access, normally as an Owner, and shares the dashboard link. On our side, dashboard access is only ever granted or changed by a signed-in Fieldproof team member, never by an automated service key.
2. That person signs in with their work email. We email a 6-digit code, valid for 10 minutes, good for 5 tries and usable once; after 5 wrong tries, request a new code. There are no passwords. A session lasts 12 hours. The "code sent" message is the same whether or not the address has access, so it never reveals who is registered.
3. Owners add colleagues themselves on the Team page. Removing someone, or changing their role, signs them out at once.

Role	Can do
Owner	Everything a Member can do, plus add and remove people and change roles
Member	View, edit case data, assign and unassign partners
Viewer	Read-only

An organisation always keeps at least one active Owner. To move access to a different address, or if your last Owner leaves, contact [email protected].

What you'll see

Dashboard. Active cases and how many are still waiting for a partner, the outstanding amount on active cases, payments awaiting verification, collected and closed cases, and money collected today, in the last 7 and 30 days, and in total. It also shows the location quality of your active cases (see below).

Cases. Filter by status (active, waiting for a partner, in progress, awaiting verification, collected, closed, or all), by whether a partner is assigned, and by location quality (exact or approximate / not located). Sort by last update, DPD, outstanding amount or age. Search by loan number, case ID, borrower name or 10-digit mobile.

Case detail. Borrower, address with its map pin and precision, loan figures, the assigned partner, the latest 50 field visits with their outcomes, the latest 50 payments, and the last 30 activity entries.

Collections. Every payment booked on your cases, with a date range and loan filter, plus a CSV export. One export holds up to 10,000 payments; for a larger range the export is refused (EXPORT_TOO_LARGE) with a message asking you to narrow the dates and export in parts.

Location quality

Field work runs on the borrower's location. We match partners by distance, check them in against the address, and pay them by distance travelled. Each case therefore shows how precisely it is located:

Label	Meaning	Offered to partners on the marketplace?
Your coordinates	Located with the latitude / longitude you sent	Yes
Exact	Street-level: geocoded from the address, or confirmed by a partner's on-site GPS	Yes
Approximate	Pincode area only	No, until the address is located
Not located	No usable location	No

Cases marked Approximate or Not located sit in your book but are not offered to partners on the marketplace. You can still assign a partner to them directly. Fix them by adding the borrower's real coordinates, either in your next push / CSV or with Edit case data on the case. The rules are in the data contract.

Editing case data

Members and Owners can correct a case while it is open:

• borrower name, mobile, email, language, employer;
• the address (house / street, line 2, landmark, city, state, pincode) and its latitude / longitude. Tip: paste a lat, lng pair copied from Google Maps into the Latitude field and both fields fill in;
• outstanding amount, DPD, next due date, EMI and late charges.

Edits are checked against exactly the same rules as your API or CSV data. A bad mobile number or a coordinate with too few decimals is refused with the same message you'd get in errors[]. Values can be changed but not cleared, the same as a re-push. A closed case can't be edited; send the loan again to open a new case.

Each edit re-checks the case's whole address, not just the fields you changed:

• Changing the house / street line, city, state or pincode needs the latitude / longitude of the new address in the same edit; the old pin is never carried across. If your organisation is on a coordinate grace period, the change is accepted without coordinates and the case is re-placed from the new address instead.
• A case stored with only a single-line address needs the house / street line whenever you change its city, state or pincode.
• On a case that is Approximate or Not located, or is missing its street, city or state, add the missing fields and the real coordinates in the same edit, even if you only meant to change, say, the mobile number. (On a grace period these come back as warnings instead, and the edit is saved.)
• Editing the address text also rewrites the case's single-line address (once the case has a house / street line), so partners see the new one.

A dashboard edit is your own change, so it does not send you a webhook event, the same as a re-push update. Your next push or CSV for the same loan overwrites what was edited by hand. Correct the data at the source too.

Assigning a field partner

Assign partner lists active partners whose RBI track may take the case's visit type, nearest to the borrower first, within a radius you choose: 5, 10, 25 (the default), 50 or 100 km. You can search by partner name or ID. Partners already on an open case, including the partner currently on this one, are hidden unless you tick Include busy partners. If the case has no usable map location, partners who cover its pincode are listed instead, best-rated first.

When partners are matched by distance, each one shows a distance band (under 1 km, 1–3 km, 3–5 km, 5–10 km, 10–25 km or 25+ km), city, rating and number of visits. The distance is never an exact figure, because a partner's location is their live position. Partner phone numbers, photos and personal details are not shown. Assign a partner and they are notified in their app. Unassign puts the case back to waiting for a partner, and the removed partner is notified. Nearby partners can then pick it up from the marketplace if its location is Your coordinates or Exact.

You can assign or reassign while the case is waiting for a partner, assigned, visit in progress, visited (follow-up due) or payment pending. You can't while a payment is awaiting verification or after the case has closed. Unassign is available while the case is assigned, visit in progress, visited (follow-up due) or payment pending.

The same compliance rules apply as for Fieldproof's own operations team:

• Cases at DPD ≥ 90 (NPA visits) can only go to DRA-certified (Track B) partners.
• A partner who is on a visit right now can't be replaced or unassigned until the visit ends (VISIT_IN_PROGRESS).
• If the current partner accepted the case more than a few minutes ago, they may already be on their way. The dashboard asks you to confirm before reassigning, and the previous partner is told to stop.
• While Fieldproof operations are reviewing the case (for example a safety concern or a wrong address), it can't be assigned or reassigned (CASE_UNDER_REVIEW). Contact your Fieldproof integration manager.

Assigning or reassigning from the dashboard records the usual case.assigned event. It is always in your poll feed (GET /cases/updates). It is POSTed to your webhook only if you subscribed to case.assigned, because the default webhook subscription is case.received, payment.collected and case.closed. Unassigning sends no event.

Dashboard or API?

The dashboard is for people and the Partner API is for your systems. They work on the same cases, and you can use both. The dashboard can't issue API keys, change your webhook URL or change your payment mode. Those stay with your Fieldproof integration contact.