U
Ustawi
Device Trust · 4 min read

Enrolling and trusting a new device

The field app is effectively a cash-transaction terminal in someone's pocket. So every agent's phone must be enrolled and marked trusted before it can authenticate or post a single collection. Enrolment is a supervisor-approved step, completed from the web portal.

The security problem this solves

Because the app can record cash collections and access borrower data, an unenrolled or untrusted device authenticating to it is a serious risk — it could post fraudulent collections or expose borrower information. Device trust closes that door: an unknown phone simply cannot transact.

The enrolment flow

  1. 1
    Phone-number login
    The agent signs in by phone number — no company or email picker. The number resolves the institution, matching the platform-wide identity pattern.
  2. 2
    Pending enrolment
    A newly logging-in phone starts as pending, with collection and worklist actions disabled until it is approved.
  3. 3
    Administrator approves
    In the web portal, pending-device approvals surface as a live badge in the Field Ops sidebar group, managed in the Staff, Admin & Security app. An administrator reviews and approves the request.
  4. 4
    Device trusted
    Only once approved and marked trusted does the phone unlock transacting — collecting cash and syncing.

Revoking a lost or stolen device

If a phone is lost or stolen, an administrator can revoke the device instantly from the portal. Once revoked, it can no longer authenticate or post collections, even if it later comes back online — so trust can be withdrawn as cleanly as it was granted.

Two sides of one control

The field-side enrolment described here and the portal-side approval an administrator performs are the same control seen from each end — see “Approving a new device for a field agent” for the portal side.

Related

← Back to Mobile App