Building Walkthroughs

A walkthrough is a name, a kind, where it runs, when it starts, who sees it, and its steps. Everything in it is plain words you wrote.

See Your Walkthroughs

Open Walkthroughs from the app switcher (it is in the Work group of the menu). The page lists Your Walkthroughs, and each row shows the walkthrough's name, then its kind (Guided or Hints), where it runs, when it starts, and who sees it, joined with | (action walkthroughs.list). A walkthrough an AI assistant saved shows Made by an AI Agent. With no walkthroughs yet, the page says so and New Walkthrough makes one.

Each row has these controls for anyone who may build walkthroughs:

• On: turns the walkthrough on or off for everyone it is for (action walkthroughs.state). Turning on one an AI assistant made asks first, in a Turn On pop up, so you can try it before anyone sees it: Turn It On or Cancel.
• Try It: opens the page it runs on and plays it there as a preview. A preview keeps nothing: nobody is marked as having finished or skipped it. Press Esc or Exit to stop.
• Edit: opens the walkthrough in the builder.
• Delete (the x at the end of the row): asks first, then removes it for good (see Remove a Walkthrough below).

Someone who may see walkthroughs but not build them sees a short note at the top and only the walkthroughs that are on and shown to them in the workspace, each marked On, with Try It and, once they finished or skipped one, You Finished It or You Skipped It (action walkthroughs.mine). There is no New Walkthrough, On, Edit, or Delete for them.

Put It on Your Website, beside New Walkthrough, is shown but not working yet, marked Coming Later: running walkthroughs on your other websites comes in a later release.

Your own AI assistant and the API read the same list, one place at a time (the workspace, the portal, a demo, or a website) and a page at a time. Opening one shows every step (action walkthroughs.get).

New Walkthrough

New Walkthrough opens a pop up with:

• Name (required): what your team calls it, for example Send Your First Invoice.
• Kind: Guided (the page dims and only the highlighted item can be clicked) or Hints (small beacons appear, nothing is blocked).
• Where It Runs: any page of your workspace from your apps' menus, Your client portal, or Your demo. Another website or web app is listed as Coming Later and cannot be chosen yet.

Make It and Open the Builder saves it turned off, with one welcome card to start from, then opens it in the builder to add steps (action walkthroughs.save). A walkthrough in the workspace starts the first time each person opens its page and is for everyone; one in the portal is for clients in your portal; one in a demo starts as the demo opens, for its visitors. You change any of these in the builder. Turn it on in the list when it is ready.

Add or Change a Walkthrough

Adding a walkthrough, or changing one, checks every part again, whoever sent it (action walkthroughs.save):

• Name: up to 120 characters.
• Kind: Guided (the page dims and only the highlighted element can be clicked) or Hints (nothing blocks the page).
• Where it runs: the workspace, the client portal, a demo, or a website, and the page it runs on. Leave the page empty for every page of that place.
• When it starts: on the page, on a person's first visit, when an element appears (name the element), from Show Me How in Help, from a link, or, in a demo, as the demo opens.
• Who sees it: see Who Sees a Walkthrough below.
• Steps: 1 to 50, in order.

A new walkthrough starts off. When you change the steps, the version goes up, so people who finished or skipped the old version are shown the new one. A new name or audience alone keeps the version.

Steps

Each step is one of:

• Card: a card pointing at an element, with a title, a few lines of text, an optional picture from Files, and a button.
• Highlight: the element is outlined, with no card.
• Welcome: a centered card that points at nothing.
• Beacon: a small pulsing dot beside an element (hints only).
• Wait: waits until an element appears, a pop-up opens, or a form is saved.

A step moves on when the person presses Next, clicks the element, a pop-up opens, a form is saved, or the element appears. A hint can show at once, when a pop-up opens, or later, after a delay of up to 10 minutes.

Each step remembers its element in a sturdy way: its step id in the workspace, a data attribute, its role and words, or a selector, with a label for you. Titles are up to 80 characters, text up to 600, and a button up to 30.

Plain Words Only

A walkthrough never holds HTML or code. Words that look like a tag or a script link are refused with a plain message, and a selector cannot hold a style. Only the steps you wrote are shown, so a walkthrough cannot run anything on a page.

Who Sees a Walkthrough

• Everyone who can open the place it runs.
• A permission from Settings, Permissions: anyone who holds it sees it, including every custom role or permission group you give it to. Someone who loses the permission stops seeing it.
• Clients in the portal, demo visitors, or website visitors: each only for a walkthrough in that place.

A walkthrough on a website is for its visitors, so it is for everyone or for website visitors.

Turn a Walkthrough on or Off

Only a person turns a walkthrough on or off (action walkthroughs.state). An AI assistant or a key never can, and anything they save is saved off.

Remove a Walkthrough

Removing a walkthrough removes it for good, with its steps and the record of who finished or skipped it (action walkthroughs.delete). It cannot be brought back.

The Builder

Edit on a walkthrough opens the builder. On a computer it sits beside the real page; on a phone or a narrow tablet it is a sheet across the bottom of the screen, and Hide folds it down to its title (Show opens it again). A walkthrough for your workspace opens on its own page, so you build it where it runs. It opens with Steps and Settings, Preview at the bottom, and Exit Builder at the top (action walkthroughs.get).

Steps

Each step shows its title, its kind, and whether its element is on the page shown now:

• Checking: the page is still drawing.
• Found: the element is on the page.
• In a Pop Up: it is inside a pop-up that opens during the walkthrough.
• Shows Later: it appears a little later, and the walkthrough waits for it.
• On Another Page: the step belongs to another page of the walkthrough. Go there to check it.
• Not Found Here: it cannot be found on this page. It may have been renamed or removed; pick it again. These steps also show Fix.
• No Element Yet: the step needs an element; pick one.

Move a step up or down with the arrows, remove it with the cross, or press Add Step to add one after the step you are on (the element picker opens for it right away).

Choose a step to change it: its kind, its title, its text, the words on its button, what moves it on (for Guided: they click the element, they press Next, a pop-up opens, a form is saved, or the element appears), and when it shows. For Hints, choose how many seconds after its element appears the beacon shows. The Element box names the element, says how it is found (its MountDev step id, a data attribute, its role and words, or, as the fallback, its place on the page), and has Pick an Element (Pick Again once one is chosen).

Pick an Element

Pick an Element outlines what is under the pointer, with its name, and a click chooses it. The page itself never sees that click, so nothing opens or saves while you pick. Press Esc or Cancel to stop. On a phone, the sheet folds while you pick and opens again after. The builder itself is never picked.

Settings

Settings has the walkthrough's name, its kind (Guided or Hints), the page it runs on (or every page in your workspace), when it starts, and who sees it: everyone, or anyone who holds a permission from Settings, Permissions, or the visitors of the place it runs. On turns it on when you save; only a person can do that.

Preview, Save, and Exit Builder

Preview runs the walkthrough on the page as people see it. Nothing is kept: nobody is marked as having finished or skipped it. When it ends (Exit, Skip Walkthrough, or the last step), the builder comes back. A Hints preview has Back to Builder.

Any change brings up the bar at the top of the screen with Unsaved changes, Discard, and Save, the same as every screen. Save checks every part again, and the builder shows the new version (action walkthroughs.save). If something is not right, the bar says why and keeps your changes, with Retry. Discard puts the walkthrough back as it was last saved.

Exit Builder goes back to Walkthroughs. If you have changes that are not saved, it asks first: Save, Discard, or Stay. Going to another page of your workspace with unsaved changes asks the same.

Walkthroughs for the client portal and demos do not run in your workspace yet: the builder shows their steps and settings, and says so, but has no live page to pick elements on or preview.

Open on My Site Planned

Open on My Site opens one of your other websites with the element picker, through a one-time build link.