Skip to content
Rechaj Design

design

Onboarding Agent — flow

Section titled “Onboarding Agent — flow”

Atlas’s UI for the onboarding agent persona. This is the design that an onboarding agent sees when they log into Atlas.

Live interactive prototype: /products/atlas/flows/onboarding-agent/ — the canonical onboarding-agent flow rendered as a single-file HTML demo.

Persona summary

Section titled “Persona summary”
Name Onboarding Agent
Audience Field-and-office staff who process new rider / agent / partner applications
Surface Atlas (web, desktop-first 1440px)
Auth context Internal employee SSO; role-scoped to the onboarding queue

Primary jobs to be done

Section titled “Primary jobs to be done”
  1. Pick up the next application in the queue
  2. Verify KYC documents (ID, address, contract)
  3. Approve, reject, or send back the application
  4. Track personal throughput against onboarding SLAs
  5. Release a retrofitted vehicle to its rider once every release condition is met

Post-Onboarding — Release Vehicle

Section titled “Post-Onboarding — Release Vehicle”

A standalone Post-Onboarding sidebar group (below the existing Pipeline group) holding one item, Release Vehicle — per the Post-Retrofit Vehicle Release · PCA Module PRD (v3.0, Aug 2026). This is a separate entry point from the day-to-day pipeline screens, not a drill-down from Completed Riders.

  • Riders List — a searchable, full-pipeline list (every rider, every status — see PATTERNS.md’s proposed status set), so the release view stays honest about where every rider actually stands. Row click opens the Release Record; only riders with status Retrofit Completed are release-eligible.
  • Release Record — header (name, plate, phone, status, date onboarded) + three tabs (Rider Details / Keke Details / Wallet). For a non-eligible rider the record is read-only visibility only. For a Retrofit Completed rider, a persistent two-column layout adds a Release Checklist panel (six pass/fail items with a live “X of 6 passing” counter) that stays visible across all three tabs.
  • PCA actions (each flips its checklist item to passing): Assign/Remove Battery (typed serial, not a picker), Update Swap Station (a picker showing capacity, full stations disabled), Create Wallet & Virtual Accounts (exception-path only — hidden once a wallet exists).
  • Release Vehicle — disabled (grey) until 6 of 6 pass, then active (green). On click the release executes immediately (no confirmation prompt); a success toast fires and the checklist counter is replaced with a “Released on [timestamp]” record. Releasing does not change the rider’s account status.
  • VCU assignment is read-only here — owned by another team/system; no PCA action is ever shown for it, passing or failing.

Why this flow exists separately

Section titled “Why this flow exists separately”

Atlas is multi-persona. The onboarding agent’s job is narrow and high-throughput; cluttering their default view with case-management, fleet, or KaaG-telemetry surfaces would slow them down. This flow is the dedicated entry-point shown to anyone with the onboarding-agent role.

Source

Section titled “Source”

The interactive prototype lives at ./index.html. Edit that file directly when iterating on the flow. No build step.

See also

Section titled “See also”