# How do you prepare a demo account for a screen tutorial?

Author: AUTOVID Team
Published: 2026-11-03
Updated: 2026-11-03

A demo account for a screen tutorial should use safe sample data, not real customer information, and start in a state a new viewer can follow. Separating the account and rehearsing the whole path before recording reduces both accidental disclosure and mid-recording errors.

The goal is not to fill the account with every feature. It is to show one task clearly, without distractions. Use this sequence to prepare the account, data, browser, and final review.

## Create a safe example separate from real accounts

Do not put real names, email addresses, phone numbers, addresses, payment details, inboxes, or customer records in a demo account. Use fictional names and clearly example-only items, including numbers, dates, and notes that cannot be mistaken for live business data.

Keep permissions limited to what the recording needs. Start with a standard user role unless the tutorial truly requires an admin view, and test irreversible actions such as payments, deletion, or external sending only in a separate test environment.

## Fix the starting point and outcome for one video

Before recording, define the starting screen, the choice the viewer will make, and the result they will see in one sentence. A promise such as “create an invitation link from an empty project” removes unnecessary menus and explanation.

After rehearsal, you need a way to reset the account to that same starting state. Delete or duplicate pre-created items, clear saved searches, notifications, pop-ups, and traces of earlier work, then run the path again in a fresh browser session.

## Treat the recording frame as something to review

Tab titles, bookmarks, browser profiles, notifications, autocomplete, and download lists can reveal information you did not mean to show. Open a dedicated browser profile, turn off notifications, leave only needed tabs, and fix the window size and zoom before recording.

It is safer to keep passwords, API keys, recovery codes, and private links off screen even as examples. Also confirm the rights to materials used in the video and the use conditions for any brands, images, or text visible in the recording.

## Finish with a short rehearsal and repeatability check

Run the path once from start to finish before the real take. Check click targets, waiting time, error messages, cursor movement, and whether the spoken explanation matches each screen change. If a step is confusing, correct the starting state or sequence before adding more narration.

When organizing a tutorial-production workflow in AUTOVID, projects save before moving between steps and record the last completed step. Keeping a separate test project for recording makes it easier to review and resume from the same starting state. In the final file, rewatch the opening, the most complex step, and the ending screen for stray example data.

[Learn more](https://autovid.net/vi/features)