MountDev Ops Walkthroughs
How MountDev Ops Walkthroughs works, page by page. Updated November 13, 2026
MountDev Ops Walkthroughs documentation | Updated November 13, 2026
Walkthroughs are guided tours and hints that show people what to click, step by step, on the real page. Every company can add Walkthroughs and write its own, the same way.
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 3,859 automated checks before it ships, and every screen change is walked through before release.
Tested Every Release
All 16 of Walkthroughs's own automated checks run on every update.
What they cover: AI agents and API keys | Roles and permissions | Spam and abuse protection
What Walkthroughs Is
A walkthrough is a list of steps, each tied to an element on a page. There are two kinds:
- Guided: the page dims, only the highlighted element can be clicked, and a card says what to do. The tour moves on when the person clicks the element, a pop-up opens, a form is saved, or they press Next.
- Hints: nothing blocks the page. Small beacons and cards appear as their elements appear, after a delay, or when the person first visits a page.
Each walkthrough says where it runs (your workspace, your client portal, a demo, or a website), the page it runs on, when it starts, and who sees it. A walkthrough only holds the words you wrote. It never holds HTML or code, so a walkthrough cannot run anything on a page.
In These Docs
- Building Walkthroughs: the steps, where a walkthrough runs, when it starts, who sees it, turning one on, and removing one.
- Showing Walkthroughs: how the right walkthroughs reach each person, and what is kept when someone finishes or skips one.
- Walkthroughs for Your AI Assistant: the tools your own AI assistant can use, and what stays with people.
- Walkthroughs Settings: who can see, build, and turn on walkthroughs.
Where It Is Kept
Your walkthroughs are kept in your own company's database, in your region. Nothing about what a person does on a page is recorded, except whether they finished or skipped each walkthrough, so it is not shown to them again. There are no analytics.
The Walkthroughs Page
Walkthroughs has its own page in the workspace: every walkthrough with where it runs, when it starts, and who sees it, with On, Try It, Edit, and Delete, and New Walkthrough to start one (see Building Walkthroughs). The builder opens over the real page, with the element picker and Preview. People who may only see walkthroughs find the ones shown to them there, with Try It.
The Website Script Planned
Put It on Your Website (the one script line for your other websites, with the domains it is allowed on) comes in a later release. It is shown on the Walkthroughs page and in its Settings, marked Coming Later.