Create a checklist

A checklist shows users a list of tasks. Items check off as users complete them, and the checklist remembers progress across sessions. Common use cases:

• Give new users a clear list of setup tasks
• Persist a set of next steps users can return to across sessions
• Coordinate team setup with shared tasks that complete once per company

Start a new checklist

In your dashboard, click Flow Editor. Click Start from scratch in the editor panel and choose Checklist.

The checklist opens in the bottom-right corner of the page with one item ready to edit.

Write the items

Click into an item on the page and type the task. The preview is live: changes show as you type and save automatically. Click + Item to add another.

Decide what completes each item

Under Completion, each item has its own settings for how completion is tracked and what marks it complete.

Scope

Choose how completion is tracked:

• Per user: each user completes the item independently. Their teammates start with it unchecked.
• Per company: when any user in a company completes the item, every teammate sees it as complete.

Condition

Choose what marks the item complete:

• Click to complete: users click the checkmark on the item to mark it done themselves. Use this when FlowNavi can’t detect the action automatically. For example, “Verify your email”. A new item starts with this condition.
• Click element: the item completes when users click an element you pick, on a URL you specify. Use this when completion maps to a visible click. For example, clicking the “Invite teammate” button.
• Custom: the item completes when your code emits a custom event. Use this to auto-complete items that would otherwise need Click to complete. For example, when a chat conversation finishes, a payment confirms, or a third-party tool tells your app something happened.

Make an item take users to the task

An item can do something when users click it. Under On click, turn on Run actions when clicked and click + Add action:

• Open URL: send users to the page where the task happens.
• Start: start a tour or a pop-up that walks them through it. A guide you add this way appears under Guides in Flow settings at the top of the editor panel. Click it there to edit it.

Clicking the item doesn’t complete it. Completion still follows the item’s Condition.

Choose where the checklist sits

Display mode

Choose how the checklist appears in your app:

• Floating: the full checklist pinned to one corner of the screen. Best when you want it visible alongside the user’s normal work.
• Embedded: the full checklist sits inside a page, before or after an element you pick. Best when you want it to feel like part of the page itself. For example, embedded into a dashboard.
• Compact: a small card with the checklist’s title and progress, placed before or after an element you pick. Clicking it opens the items. Best for a spot that’s on every page, like a sidebar or a header.

URL targeting

The checklist appears only on the pages set under Show on URL. A new checklist is set to the page you created it on, so it won’t follow users to other pages until you change this. Three match types:

• All pages (Floating and Compact only): the checklist follows the user across every page.
• Exact: for fixed URLs like /dashboard.
• Pattern: * is a wildcard for variable parts. Each * wildcard matches one dynamic segment. /projects/* matches /projects/1 and /projects/2, but not /projects/1/details.

Items with the Click element condition have a Show on URL field of their own. It doesn’t change where the checklist shows. It sets the page where clicking the element completes the item: with /settings/team, a click on that element on any other page doesn’t complete it. It takes the same Exact and Pattern match types.

Choose when the checklist appears

A checklist can start in two ways. Both are listed under Starts in Flow settings at the top of the editor panel. To see how a flow, its guides, and their settings fit together, read How flows work.

On page load

A new checklist starts this way: it appears on its own when a user opens a page it’s set to show on. Click On page load to set who it appears for and how often. Segmentation and frequency are settings of On page load, so they only affect the checklist when it starts on its own.

Segmentation (audience)

By default, the checklist appears for every user. Add rules under Segmentation to limit it to specific groups: first-week signups, users on a particular plan, users in a particular role.

Each rule compares a property your app sends to FlowNavi (role, plan, signup date, etc.) with a value:

Condition	Example
= / !=	plan = "pro"
> / <	seatCount > 10
contains	signupSource contains "google"
before / after	signedUpAt after "2026-01-01"
within last N days	signedUpAt within last 7 days

If you add several rules, a user must match all of them.

Frequency

Users dismiss a checklist by clicking its ×. Minimizing it doesn’t count: the checklist stays on the page.

Under Display Rules, decide what happens after a user clicks the ×:

• Show Every visit: the checklist is hidden for the rest of that visit and is back on the next one. Choose this for a checklist that should stay available until it’s completed.
• Show N times: each click on the × counts toward N. After N, the checklist stops appearing for that user.

A new checklist is set to show 1 time, so it’s gone for a user the first time they click the ×, even if they haven’t finished it. For an onboarding checklist, switch it to Show Every visit or add a launcher.

Launcher

To let users open the checklist themselves, click + Way to start and choose Launcher, then click an element in your app. FlowNavi adds a small button to that element, and clicking it opens the checklist.

The launcher is there for every user on its page, and it opens the checklist every time it’s clicked. Segmentation and frequency don’t apply to it, so users can bring back a checklist they dismissed.

Preview

Click Preview in the footer to test the checklist before publishing. You’ll see a panel where you can set fake user and company properties to test segmentation rules. For example, set plan: "pro" to verify a “Pro users only” rule matches.

Click Start Preview to run the checklist. URL targeting, segmentation, frequency, and item completion all behave the same as a published checklist. Dismissing the checklist in preview doesn’t affect anything outside of preview mode (it’s a sandbox).

Use Stop to halt and tweak the properties. Use the back arrow to exit preview entirely.

Publish

Click Publish to make the checklist available to your users. When you edit the checklist later, your users keep seeing the published version until you click Publish again.

For the checklist to actually appear, the FlowNavi SDK needs to be installed in your app. See Install the FlowNavi SDK if you haven’t already.

Confirm it’s working

Published checklists are paused in your browser while the editor is open. Click ⋮ at the top of the editor panel and choose Log out of editor, then open your app on a page the checklist is set to show on, signed in as a user it appears for. The checklist should appear in the corner you chose (Floating) or next to the element you picked (Embedded and Compact).

If your checklist isn’t showing

If your checklist doesn’t appear on its own, check:

• The editor is open: published checklists are paused in your browser while the editor is open. Log out of the editor first.
• Not published: your users only see the published version. Edits made after publishing don’t reach them until you click Publish again.
• FlowNavi isn’t installed: the checklist can only appear in your app once the SDK is installed.
• Built on the demo app: a checklist you built on the demo app still points at the demo app’s pages and elements. Open it in the editor on your own app, update Show on URL, and pick new elements for an Embedded or Compact checklist and for items with the Click element condition.
• URL doesn’t match: verify the page URL matches Show on URL. A new checklist only shows on the page you created it on. If using Pattern match, double-check the wildcards.
• The element isn’t on the page: an Embedded or Compact checklist needs the element it’s placed next to. If a page doesn’t contain it, the checklist has nowhere to sit.
• User is outside the segment: confirm the user matches all segmentation rules set on On page load.
• On page load was removed: a checklist that starts only from a launcher never appears on its own.
• Already dismissed: a checklist closed with the × doesn’t come back during the same visit. With Show N times, it stops for good after N. A new checklist is set to 1, so clicking the × once while testing is enough to hide it. Use Preview to test without using up a view.
• Already completed: a checklist the user has finished doesn’t appear again.