Learning paths

A learning path is an ordered list of courses with:

• a rule for who gets it (Who gets it),
• optional market, vehicle type and nationality filters,
• a number of days to complete it (the deadline),
• whether riders must finish each course before the next one unlocks.

Riders see each assigned path as a route on their Training tab, with the deadline. The Learning paths list shows each path with its badges (Active or Inactive, In order, number of days), its rule, and for riders in your markets: how many riders have it, the share completed, and how many are overdue.

1. 1

   Go to Learning paths.

2. 2

   In New learning path, enter a Name.

   Riders see the name. The Description is only shown to admins.

3. 3

   Choose Who gets it.

   See the four rules below. If you choose “When a rider gets a flag”, also choose the Flag that triggers it.

4. 4

   Set Days to complete.

   0 means no deadline. The maximum is 365.

5. 5

   Select Create path. The path page opens.

6. 6

   Add courses, check the rules, tick Active and save.

1. 1

   On the path page, go to Courses, in the order riders take them.

2. 2

   Choose a course in the list and select Add course.

   New courses are added at the end. Drafts are marked “(draft)”. Archived courses aren’t listed.

3. 3

   Use the up and down arrows to change the order. The × button removes a course from the path.

• A course that isn’t published shows “Not published: riders skip it until it is”. Riders don’t see it, and the course after it isn’t blocked by it.
• Removing a course from a path doesn’t delete riders’ records for that course.
• A path is finished when a rider has passed every published course in it (see How assignments are completed). Adding or removing a course re-checks riders’ assignments for that path.

The “Auto-assign” and “Riders in onboarding status” rules are checked for active paths:

• when you save the path (the message says how many riders were enrolled),
• after every CSV import of riders (for all riders),
• after your systems send riders through the API (for all riders),
• when you add a rider, and when you save a rider’s details.

The flag rule runs each time a flag is added. It skips a rider who already has that path open (not finished yet).

An assignment is complete when the rider has passed every published course in the path. Draft and archived courses don’t count.

Completion is checked again:

• right after new assignments are created (by rules, flags, Assign now or the API),
• each time a rider passes a quiz,
• when a course is added to or removed from the path,
• when a course is published, unpublished, archived or deleted,
• before reminders are sent, so riders who have finished aren’t reminded.

A completed assignment is never reopened, for example when you add a course to the path later. The completion date is when the rider finished the last course, never earlier than the assignment date.

On the rider’s home screen, a path that was assigned again shows its new, open copy. A course due for a retake starts from the beginning, without a “Completed” mark on its quiz, and doesn’t count in the rider’s “courses done” number until it is passed again.

In Rules: Only riders in these markets, Only these vehicle types and Only these nationalities.

• Leave a filter empty to include everyone.
• Tick several options in one filter to include riders matching any of them.
• A rider must match every filter that has something ticked.
• The filters apply to the automatic and flag rules. Assign now has its own filters.
• A rider’s nationality must be exactly the same text as the option (Pakistani, Indian, Bangladeshi, Nepali, Sri Lankan, Egyptian, Jordanian, Iraqi, Sudanese, Syrian, Filipino). “pakistani” or “Pakistan” won’t match.

The deadline is set when a rider is assigned: the assignment date plus Days to complete. Changing the days later only affects riders assigned after the change. With 0 days there is no deadline, and the path never shows as overdue.

When Riders must finish each course before the next one unlocks is ticked (the default for new paths), a rider can only open a course after passing the published courses before it in that path. The server checks this, so a rider can’t skip ahead with a direct link.

Untick it to let riders take the courses in any order. If a course is in two of a rider’s paths, it opens when either path allows it.

1. 1

   On the path page, change what you need in Rules.

2. 2

   Tick Active: assign it to riders automatically to start (or untick it to stop).

3. 3

   Select Save path.

   For an active “Auto-assign” or “Riders in onboarding status” path, matching riders are enrolled straight away: “Saved. 250 matching riders were enrolled.”

• Active matters for the automatic and flag rules. Assign now and the API work whether the path is active or not.
• Unticking Active stops new automatic assignments. Riders who already have the path keep it.

Assign a path to a group of riders straight away, whatever its rule.

1. 1

   Open the path. Go to Assign now.

2. 2

   Choose who gets it. Use any of these:

   • Markets, Vehicle types, Rider status.
   • Cities: comma separated, spelled exactly as in the rider records, for example Doha, Al Wakrah.
   • Specific rider IDs: paste rider IDs separated by commas, spaces or new lines, or upload a CSV file with rider IDs in the first column. A first row whose first cell contains the word “rider” is treated as a header and skipped.
3. 3

   Select Assign riders.

   The message shows the result, for example “Assigned to 1,250 riders in 0.8s. Riders who already had it open were skipped.”

• Everything you choose is combined: a rider must match every filter you used, and be in the ID list if you gave one. Within one filter, any ticked value matches.
• To assign every rider, tick every market. With nothing chosen you see “Choose who to assign…”.
• Riders with status inactive are never assigned. Rider IDs that don’t exist are ignored.
• Riders who already have the path open are skipped. Riders who finished it before get it again; courses they already passed count, so the new assignment may complete straight away (see completion).
• The deadline is today plus the path’s Days to complete.
• Market managers can only assign riders in their markets. If you tick no market, your markets are used.

your systems can do the same through POST /api/v1/assignments. The path ID they need is the last part of the path page address: /admin/paths/<path ID>.

• Onboard a new batch of riders from CSV
• Assign corrective training after a safety flag
• RidersthenFlag an issue: Flags