The Interactive Guide
A guided tour of the Blueprint on a safe sample workspace — plus the two topics it leaves to these docs
A Tour That Meets You Where You Are
The first time you sign in, RoleDream offers a short guided tour of the Blueprint — the canvas where segments, jobs, and solutions all live. A welcome dialog gives you two ways to start:
- Onboard on this workspace — take the tour right here, on your own workspace and your real data.
- Onboard on demo data — explore a personal Test Workspace preloaded with a finished example map, so nothing you touch during the tour affects your real work.
You can click Skip at any time — nothing is required. Once you pick a workspace, the tour walks through a handful of stops showing, in order, who does the work, what gets done, and how it gets done. Each stop is descriptive with a Next button — there is nothing to click or edit on the canvas to move on, so a read-only, invited, or shared-link visitor can complete the whole tour on any workspace.
On a workspace that already has data, the camera zooms along one real segment → job → solution path so each stop points at a live example. On an empty workspace, each stop instead describes what its band is for and what you would add there.
Workspace owners see the tour start on its own. Everyone else who has not finished it gets an Onboard me button in the top bar, just left of Help; click it whenever you are ready and the welcome dialog opens. The tour is deliberately brief — it teaches just enough to get you moving and points you here for two topics it leaves out on purpose, both covered further down this page.
The Demo Runs on a Safe Test Workspace
Choosing Onboard on demo data creates (or re-enters) a personal sandbox workspace labelled Test Account — filled with sample segments, jobs, solutions, and resources so you can see a finished map instead of a blank canvas. Nothing you do there affects your real data. In the workspace switcher, a demo workspace carries a small Test badge so you can always tell it apart from your real ones.
When you are ready to start your own, use Delete data on the Test Account banner to empty the workspace. That clears every segment, job, solution, and resource in it; the Test Account label stays. (Invited teammates who join an existing workspace never see the demo explainer — they land in real work.)
Restart It Whenever You Like
The tour is not a one-time event. Restart it any time from the Help menu, or from the Documentation home page, where a Restart onboarding tour button takes you to the Blueprint and reopens the welcome dialog. If you have not finished the tour, the Onboard me button in the top bar reopens it too.
Restarting brings back the same welcome choice, so you can pick this workspace or the demo Test Workspace each time. On a real workspace with your own data, the content stops simply adapt to what is there.
Two Things the Tour Points Here For
To stay short, the first-run tour teaches only the essentials and defers two richer ideas to these docs. Both live in a job's open Solutions section, and both are worth knowing once you start mapping your own processes.
- The line of automation — the second horizontal divider that separates people from systems.
- Cross-job and abstract solutions — how a solution under one job can lean on another, and how work shared by many jobs lives once with no job of its own.
The Line of Automation
An open solution shows the line of visibility — the divider that answers whether the customer sees it, with frontstage above and backstage below. It draws a second horizontal divider as well, and that one answers a different question entirely.
The line of automation answers who acts. Above it sit the people: the top row of the solution's actor column holds every step a person performs. Below it sit the systems and tools that run steps on their own — a scheduled job, an integration, a bot, an unattended machine — each getting its own row. A step's row tells you whether a person or a system carries it out.
Two Lines, Two Different Questions
The easiest mistake here is reading one line as the other. They measure independent things:
- The line of automation — who acts. People above, systems and tools working with nobody attending them below.
- The line of visibility — whether the customer sees it. Frontstage above, backstage below.
Every combination is real: a backstage step can be done by a person, and a frontstage step the customer watches can be fully automated. A step's row says who performs it; the lane its resources sit in says who can see it.
Mark a step as performed by a system in the step's form: under Performed by, switch from A person to A system or tool and pick the resource that does the work. The step drops below the line of automation into that resource's row.
Use it only for work that runs with nobody attending it. A step a person performs using a tool stays a person's step — the tool belongs in a staging lane instead.
For the full walk-through, including how steps split between the People row and the systems that perform them, see the Blueprint guide.
Cross-Job and Abstract Solutions
Real processes are rarely self-contained. A step in one job's solution often hands its work to a whole other process — an approval flow, a notification routine, a shared fulfilment pipeline. Rather than copy the same steps into every solution that needs them, the Blueprint lets you say so directly. This is what the tour's older solution-links stop taught; it now lives here.
Cross-Job Solution Links
Open a step's form and pick a solution under Uses solution to point that step at another process — including one that belongs to a different job. The step's card gains a small link badge, and a connector line runs from the step out to the solution it uses, so the delegation is visible on the canvas, not buried in a form.
Both ends come to meet you. While a section is open, every solution its steps hand work to appears beside it as a slim vertical spine — under its owner job's group — with the connector drawn in. So does every solution that hands work to the one you are reading, its line running the other way. Click a spine to open that solution and read it; click a step's badge to follow the link straight to its target.
These lines are drawn for what you have open, not for the whole company at once — close the section and the borrowed spines go with it. Clear the choice in the step's form to remove a link.
Abstract (Job-less) Solutions
Some work is shared by so many jobs that it belongs to none of them: "Send customer notification", "Escalate to on-call", "Verify identity". An abstract solution is a solution with no job — a helper process that exists to be used by others. Create one with Add abstract solution in the Solutions band's label gutter, give it steps like any other solution, and link to it from as many steps, in as many jobs, as need it.
Abstract solutions gather under the No job group — shown as a blue Abstract spine when a step links out to one. Keeping the shared process in one place means one thing to improve instead of a dozen copies drifting apart. A step in the same group draws no line — the used solution is already one of the section's own tabs, and that tab is marked instead.
More detail — following links across the canvas, and how the keyboard outline states the same facts on both ends — is in the Blueprint guide.