Who this is for: Teams explaining administrator setup.
What to prepare
- Admin configuration screens
- Verified role definitions
- Save confirmation
- Actual user-view evidence
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–8s
Identify the administrator
Show the sample admin account, workspace and configuration task.
On screen:Administrator · Prepare Sample review workspace
- 02
8–20s
Configure one setting
Use the actual controls to select the verified review policy or default view. Preserve scope labels.
On screen:Configure the review setting
- 03
20–31s
Assign the intended role
Show Example contributor receiving the documented role through the real interface.
On screen:Assign the intended user role
- 04
31–39s
Save and inspect
Perform the actual save action and inspect the configured state.
On screen:Configuration saved
- 05
39–47s
Preview the user experience
Use the product’s actual preview capability if available; otherwise show a clearly labeled separate user account.
On screen:Check the intended user view
- 06
47–56s
Verify the handoff
Show the user locating the prepared review area and only the controls their role permits.
On screen:Example contributor can reach the prepared area
- 07
56–60s
Close with scope
Hold the user view and identify the completed setup boundary.
On screen:Workspace prepared for this sample workflow
Make it your own
- Configuration and scope
- Select one real setting and identify whether it affects a person, project or workspace.
- Intended role
- Supply the documented user role and the actual assignment procedure.
- User-view evidence
- Use a verified preview capability or a clearly labeled separate account with its actual permitted controls.
Prepare both views
Supply the actual setting, role definition and saved state. A preview mode must be verified; if it does not exist, use a separate account capture. Never fabricate an impersonation control for convenience.
Adapt the setting
Choose one configuration that materially affects the user task. For 30 seconds, begin with the role already assigned and state that prerequisite. Keep the user-view verification because it proves the handoff rather than just the administrator’s form entry.
Review scope and rights
Check whether the setting is personal, workspace-wide or limited to one project. The user’s view should show actual available fields and actions. A successful setup example does not prove broader security or policy compliance.
Review checklist
- Setting scope is explicit.
- Role assignment matches documented rights.
- The intended user view is actually verified.