A checklist gives new users one place to start. Each item opens a short tour that walks them through a task inside your product, then brings them back to the checklist to pick the next one.
This guide covers building the checklist, connecting the tours, and testing the full loop in your application.
Before you start
You have a checklist built with native components. If not, see Creating Checklists.
Each tour you want to launch is published in On Trigger mode. See Advanced Tour Settings.
Step 1: Decide what a checkmark means
Each item can mark one of three things: the user opened the guide, finished the guide, or completed the real task in your product. Pick one per item and be consistent. A button click can only prove the guide was launched. If you want the checkmark to mean the task is done, complete the item with the event your application sends to Candu.
Step 2: Add an overview video and a minimized state
Place a short Watch overview button above the items so users can see the whole flow before they start. Test playback inside your application, not only in the editor. If the embed is blocked by your app's content security policy, link out to the video until the policy is updated.
Give the checklist two Flow steps: an expanded step with the full list and a minimized step with a single Open checklist button. Connect that button back to the expanded step. Decide whether the Flow should remember which step the user was on when they return. See Build Multi-Step Flows.
Step 3: Connect each tour
Select the item's button and open the Interactions panel. Add two interactions in this order:
Move the Flow to the minimized step, so the checklist gets out of the way.
Trigger Tour, and choose the published tour.
If the tour applies to whatever record the user has open, do not point it at the example record you used during setup. If it needs a record to exist first, say so in the item's description. See Trigger Content from CTAs and Events.
Step 4: Match tour steps to your interface
When a tour step depends on a tab, menu, or modal, the interface has to actually change before the next step can show. Use click-to-advance on the real control rather than a Next button. See Place Content on Specific Pages for targeting the right page.
Step 5: Give users a way back
Test what happens when the tour finishes and when the user dismisses it early. Keep the minimized Open checklist control visible in both cases, and mention it in the tour's final step.
Test before you widen the audience
Log in as a test user who matches the checklist audience and the tour audience. Check both.
Start from the checklist and run the full loop: launch, minimize, every step, finish, return, replay.
Make sure the minimized control does not cover app controls or sit above a modal.
Reload the page and confirm the checklist progress behaves as you chose.
Check one eligible user and one ineligible user.
Snapshots and share links are good for reviewing layout and copy. They do not test live triggers or product events. Do the final run in your installed application.