From recording to step-by-step guide.

Point it at a recording. It picks the meaningful frames, drafts a step for each one, and hands back a public link.

Why

A recording is a starting point, not a deliverable. Someone still has to scrub through it, pull stills, and caption each step. ScreenScoop Guides does that pass for you, then ships a result a portal user can open without an Odoo login.

How it works

Start from a recording
Pick any ScreenScoop in your library. The guide generates alongside it, original untouched.
Frames get scored
Sampled a few times a second, each frame compared to the last with a perceptual hash and histogram diff.
Only the changes survive
Near-duplicates drop out. What remains is the moments where the screen actually changed.
Steps get drafted from clicks
Click selectors become readable captions: "Click the 'Save' button", "Switch to Sales tab".
Publish, share the URL
Token-based link opens for anyone — no login. Or scope to portal followers and embed.

What's in the box

Smart frame selection

dHash and histogram thresholds, both tunable. Sensitivity slides between "every visible change" and "only the big ones".

Odoo-aware step text

Selectors map to common Odoo classes — btn-primary, breadcrumb, o_field_widget — so drafts read like a human wrote them.

Token-based sharing

Every guide gets a unique access token. Share URL works without login; rotate the token to revoke.

Three-tier visibility

Followers, all employees, or portal users — same model as Odoo projects. Embed is open unless followers-only.

Portal listing under /my

Published guides surface on the same recording page portal users already visit.

Adaptive thresholds

A nightly cron tunes detection thresholds per company from your edits. Next batch needs less cleanup.

Compatibility

Odoo 19.0 ScreenScoop ≥ 19.0

Requires screenscoop, portal, and website. Frame extraction uses OpenCV with an imageio fallback (both pulled from requirements.txt).