Authentication, Access & Roles

How a person signs in (see Login & Authentication below), and then how the panel decides what each person can see and do. Access works entirely through roles: every signed-in user is given exactly one role, and that role decides which pages they can open and which actions (buttons, fields, controls) they can use on each page. Roles can build on one another, so a senior role automatically gets everything its more basic roles can do, plus its own extras. This is the foundation every other flow sits on — if someone can't reach a screen or use an action, the reason is almost always here. (All of this is decided in the browser; see the note at the end of the Exact Role Configuration section on why the server must apply the same rules too.)

How a person signs in. Sign-in is handled by Google Firebase Phone Authentication, not a custom in-house OTP system. The panel collects a phone number, Firebase sends and checks the one-time code (OTP), and once verified Firebase hands back a token. The panel then calls its own backend once with that token to load the user — and from there the role logic below takes over. Important for the OTP/Twilio decision: the panel itself never generates or sends the OTP and never talks to Twilio directly. Firebase does that, with Twilio plugged in inside Firebase as the SMS delivery provider. See the replacement note at the end of this section.

The precise, build-ready definition of every role, copied exactly from the panel's own access settings. Each card shows the role's default home page (where it lands after sign-in), which roles it builds on (inherits from), the pages it can open on its own, and the actions it can perform on its own. "On its own" means granted directly by this role — a role's full access is what it grants directly plus everything it picks up from the roles it builds on. To recreate the system exactly, reproduce these definitions and the build-on relationships between them as shown.

The complete list of individual exceptions, copied exactly from the source in original order. These are specific people pinned to a role by their personal user ID, checked before job type. For each person below, the rebuilt portal must make that exact user ID resolve to the listed role — using the same IDs as today. The third column shows the original source identifier for the role, so each entry traces 1:1 back to the code. Total: 37 entries.

Managing Doctor Records

Allows BD Admin to add new leads and update existing doctor or lead records directly from the panel via an Excel upload — replacing the current process of editing the backend database manually.

{
  "success": true,
  "success_count": 12,
  "failed_count": 1,
  "failed_rows": [
    {
      "row": 5,
      "name": "Dr. Sharma",
      "reason": "google_place_id not found"
    }
  ]
}

{
  "data": {
    "upsert_client_by_id": {
      "rowsInserted": 1,
      "rowsUpdated": 0,
      "data": {
        "clientName": "Dr. Khushboo Gosalia",
        "internalClientID": "07db4526-983f-4658-970b-8b210cb2e9a6",
        "lat": 19.195,
        "lng": 72.836,
        "phoneNumber": "+91-9191919191",
        "city": "Mumbai"
      },
      "err": null
    }
  }
}

Lead List & Meeting Scheduling

The BD person's daily workhorse screen. Shows all assigned leads with meeting history at a glance, and lets them select and schedule visits for the day in one action.

{
  "success": true,
  "data": [
    {
      "id": "07db4526-983f-4658-970b-8b210cb2e9a6",
      "name": "Dr. Khushboo Gosalia",
      "phone": "9191919191",
      "speciality": "Obstetrics and Gynaecology",
      "lead_stage": "in_progress",
      "days_since_last_successful_meeting": 67,
      "no_of_successful_current_month_meetings": 0,
      "no_of_attempted_current_month_meetings": 0,
      "no_of_successful_meetings": 7,
      "no_of_attempted_meetings": 19,
      "owner": {
        "id": "7c1dad97-...",
        "name": "Cureverse North Mumbai"
      }
    }
  ]
}

{
  "success": true,
  "scheduled": [
    { "unolo_client_id": "0364c720-...", "task_id": "9347" },
    { "unolo_client_id": "3d5132ae-...", "task_id": "9348" }
  ],
  "failed": [
    {
      "unolo_client_id": "3eda9dc9-...",
      "reason": "Unolo API error: employee not found"
    }
  ]
}

{
  "data": {
    "upsert_task_external": {
      "rowsInserted": 1,
      "rowsUpdated": 0,
      "data": [{
        "internalTaskID": "9347",
        "internalEmpID": "EC2615",
        "date": "2026-06-16",
        "adminAssigned": true
      }]
    }
  }
}

Lead Profile

Opens when a BD person clicks on any lead's name from the list. Shows the lead's basic details at the top and a full chronological timeline of all past and upcoming meetings below.

{
  "success": true,
  "count": 19,
  "is_last_page": false,
  "data": [
    {
      "id": "b3e2...",
      "date": "2026-06-10",
      "meet_status": "Met Doctor",
      "check_in_time": "2026-06-10T10:22:00Z",
      "check_out_time": "2026-06-10T10:48:00Z",
      "meeting_notes": "Discussed onboarding timeline",
      "manager_audit_notes": null,
      "recordings": [
        {
          "recording_file": "https://s3.amazonaws.com/.../raw.m4a",
          "mp3_recording_file": "https://s3.amazonaws.com/.../rec.mp3",
          "ended_due_to_call": false
        }
      ],
      "attachments": [
        { "attachment_file": "https://s3.amazonaws.com/.../photo.jpg" }
      ]
    }
  ]
}