Onboarding Videos and the Learn Action

Attach a help video to a CRM Analytics widget with the onboarding property so users can teach themselves via the Learn action — and avoid the gotcha that the URL must be a YouTube embed link, not a normal watch link.

Onboarding Videos and the Learn Action

We've spent this section on features that push data to users. The last one pushes understanding to them — and it addresses the most common reason a dashboard quietly dies: nobody was ever sure what they were looking at.

The onboarding property

Every widget has an onboarding property in the dashboard editor. Set it, and the widget gains a Learn action in its menu. A user who clicks it gets a video explaining that widget.

  1. 1

    Record a short explainer

    Sixty to ninety seconds is plenty. What the metric means, where the data comes from, how often it refreshes, and one thing people commonly misread.

  2. 2

    Host it where your users can reach it

    YouTube (public or unlisted) is the usual choice. Unlisted is often the right call for internal content — reachable by link, not indexed or discoverable.

  3. 3

    Set the onboarding property on the widget

    Select the widget in the dashboard editor, find the onboarding property in the panel, and paste the video URL.

  4. 4

    Save and test as a viewer

    Open the widget's action menu, choose Learn, and confirm the video actually plays in the panel — not just that the action appears.

The gotcha: it must be an embed URL

The URL you paste has to be a YouTube embed URL, not the ordinary watch link from your browser's address bar.Get it from the video's Share → Embed option — that gives you the youtube.com/embed/... form. Pasting the normal youtube.com/watch?v=... link (or the youtu.be/... short link) results in a Learn action that opens to nothing, with no obvious error explaining why.

This is worth double-checking every single time, because the failure is silent. The property saves happily, the Learn action appears in the menu, and the whole thing looks configured — right up until a user clicks it and gets an empty panel. Always test the action after saving, from a viewer's perspective rather than the editor's.

What to actually put in the video

The temptation is to explain the chart. Users can usually see the chart. What they can't see is everything around it:

Definition and source

What exactly counts as 'open pipeline' here? Which object, which filters, which stages are excluded? This is the question that generates the most emails.

Freshness

When the data last refreshed and how often it does. A user comparing a dashboard to a Salesforce report needs to know they're seeing last night's snapshot.

How to read it

What the colours mean, what a click does, which parts are interactive. Faceting behaviour is invisible until someone tells you it exists.

The common misreading

Every metric has one. Name it explicitly — 'this excludes renewals, so it won't tie to the finance number' saves a quarter of confused conversations.

Why this belongs in a collaboration section

Onboarding videos are documentation that lives where the question gets asked. A wiki page explaining your dashboard is read by nobody; a Learn action on the widget someone is confused by right now is read by exactly the person who needs it.

Reserve it for the widgets that earn it — the calculated metrics, the ones with non-obvious business rules, the ones you've already had to explain twice. Attaching a video to a straightforward count of open cases is effort spent where nobody was confused.

A practical pattern: record one video per dashboard covering the two or three genuinely tricky widgets, attach it to each of them, and you've built a self-service help layer in about half an hour. It doesn't have to be one video per widget to be useful.

Wrapping up the section

Look back over what we've covered: sharing and print, notifications, annotations, exports, explore, views, subscriptions, watchlists, and now in-dashboard help. Not one of them required a line of code, a new license, or a change to your data model. They were all sitting there the whole time.

That's the theme worth carrying out of this section. Adoption is rarely a build problem — it's a communication problem. The designer who spends thirty minutes walking their audience through these features will get more usage out of an average dashboard than a designer who spends thirty hours perfecting a beautiful one nobody was taught to use.

Next, put it to the test with the graded quiz — and then rehearse the interview questions out loud.

Discussion

No comments yet — be the first to start the discussion.