Use a checklist as a home base for short guides that help users act inside your product. This recipe combines an expanded checklist, a minimized return control, and tours launched from checklist buttons.
Decide what each checkmark means
Choose whether each item records starting a guide, finishing a guide, or completing a product task. These are different milestones. A button interaction can record a guide launch; it does not prove the user created a record or activated a recipient. For product completion, use the exact event your application sends to Candu and verify it for your test user.
Build the checklist and return control
Create the checklist with native components and style it using your workspace Styleguide. If you want expanded and minimized states, place them in separate Flow steps. Add an Open checklist button to the minimized step and connect it back to the expanded step. Choose whether the Flow should remember its current step when the user returns. This is separate from checklist completion.
Connect each guide
Prepare the target tour in On Trigger mode and publish it to the intended audience. In the checklist CTA’s Interactions panel, connect the Flow transition to the minimized step and add Trigger Tour for the published guide. Test both interactions together in your installed application.
For a guide that applies to the object the user has open, preserve that context. Do not link to a private example record used during setup. If the guide requires an existing record or recipient, explain that prerequisite before launch. Review the source checklist audience and the target tour audience separately.
Match advancement to the product
If the next step depends on a tab, menu or modal, the underlying interface must actually change. Use click-to-advance for the relevant app control, or a supported trigger-click interaction that you verify in the live application. Advancing a tooltip with Next alone does not establish that the next target is visible.
Give users a clear way back
Test what happens when the tour finishes and when it is dismissed early. If you have configured automatic return, verify it in the installed application. Otherwise, keep the minimized Open checklist control available and explain that return path in the final step. Keep the checklist available for replay during testing; decide separately whether to hide or replace it after the intended completion milestone.
Add an overview video
A short video can sit above the checklist. Verify playback inside the host application, not only in the editor. If the embed is blocked, distinguish the host’s content security policy from the provider’s embedding restrictions. An external video link is a useful temporary fallback. After the relevant policy or provider setting is updated, restore the inline video and test playback, sizing and controls.
Validate before expanding the audience
Confirm the SDK is available to the test user and the audience matches the actual User ID or trait sent to Candu.
Start from the checklist and verify launch, minimize, every native click transition, finish, return and replay.
Check that the minimized control does not cover app controls or appear above a modal that should cover it.
Verify the chosen progress behavior after navigation and reload.
Check an eligible and an ineligible user before a wider rollout.
Test real product effects separately and only with the intended test data and recipients.
Snapshots and share links help review layout and copy. They do not replace testing native application behavior, linked launches or product events. Save and reopen the configuration, verify publication, then run a fresh test in your application.