Find and organise guides

Ten guides fit on one screen. Sixty don't, and by then the useful question is rarely "where is the guide called Billing", it's "which of these is underperforming". The Guides page is built around both.

The Guides page

Open Guides from the sidebar. The header shows the page title, an "N total" chip, and the line "Everything you've recorded across your workspace. Click a guide to see analytics, edits happen in the Chrome extension."

Two buttons sit top right. Tweaks changes how the list looks. Record new guide opens the New guide modal, the same one the dashboard's New guide button opens.

At the bottom of the list, a footer line reads "Showing N of N guides" with counts of published, drafts, and archived. When a filter is doing more than you expected, that line is where you notice.

Status tabs

Four tabs sit above the list, each with a live count: All, Published, Drafts, Archived.

The counts are the point. Drafts tells you how much unfinished work is sitting in the workspace, and a number that keeps climbing is a sign guides are being started and abandoned. Published is what your users can actually reach right now.

Search

The search box takes a title or an author: "Search by title or author...".

Searching by author is the one people forget. On a team, "who recorded this and what else did they record" is a common question, and typing a teammate's name gives you their whole set.

Filter by performance

The performance filter has three options: Any performance, High, and Low.

This turns the page from a file browser into a work queue. Set it to Low and you're looking at the guides that need attention, sorted out from the ones that are fine.

A workflow that holds up:

1. Filter to Low

Set the performance filter to Low and switch Show drop-off on under Tweaks, so each card tells you where users are leaving.

2. Pick three, not thirty

Take the three worst and ignore the rest for now. Guide libraries get fixed in small batches or not at all.

3. Open each and find the step

On Overview, the Step funnel shows the percentage of users reaching each step. The step where the line falls off is the one to change.

4. Re-record that step

Open in Editor on the step's row takes you into Reveal for Chrome at that step. One clip per step means you replace it without touching the others.

5. Come back in a week

Filter to Low again. If the same three guides are still there, the problem is probably the product screen rather than the recording.

Has feedback / issues

The Has feedback / issues toggle narrows the list to guides that have something waiting for you: a rating or comment from a user, or a check the pixel is failing.

Use it as a daily pass. Everything under it is either something a user told you or something stopping a guide from running, and both are worth ten minutes.

Tweaks

Tweaks opens a small panel with three settings.

LAYOUT switches between Gallery and List. Gallery shows each guide as a card with its poster preview and camera bubble. List packs more rows onto the screen.

Gallery wins when you're looking for a guide you recorded but can't remember the name of, because the poster frame shows the screen it starts on and you recognise it instantly. It also makes drafts obvious, since the DRAFT · UNPUBLISHED overlay sits right across the preview. List wins once you know what you're looking for and you're comparing numbers down a column.

DENSITY switches between Comfy and Compact. Compact is for large libraries and for scanning rather than browsing.

SHOW DROP-OFF is On or Off. On adds drop-off to what each guide shows, so you can spot the problem guides without opening any of them. Pair it with the Low performance filter.

What a guide card shows

Each card carries enough to make a decision without opening the guide:

• A poster preview from the recording, with the camera bubble visible.

• A DRAFT · UNPUBLISHED overlay, on drafts only.

• The step count.

• The title and the author.

• A relative edit time, so you can see what's gone stale.

• A status chip.

• On drafts, "Finish & publish to collect analytics" with a Continue → link.

• A views count.

The edit time is the underrated one. A guide last edited eleven months ago, on a product that ships weekly, is probably showing users a screen that no longer exists.

Pinning

Pinned guides appear in the sidebar under PINNED, so they're one click away from anywhere in the app.

Pin the two or three you're actively working on rather than the ones that matter most. Anything you're recording, re-recording, or watching the numbers on this week belongs there, and the list is worth clearing out when you move on. A guide created from the New guide modal is pinned automatically, which is usually what you want since you're about to go record it.

Search from anywhere with ⌘K

The sidebar search box, Search guides..., has a ⌘K shortcut. It works from any page in the app, so you don't have to go back to Guides to jump to a guide.

⌘/ opens the keyboard shortcuts reference, linked from the app footer next to Docs and Changelog.

Next steps

• Publish, draft, and archive: What each status means for your users.

• Edit and re-record: Fix the step the funnel flagged.

• Checklists: Group related guides into one journey.

• Analytics: Where the performance numbers come from.