Explain roles and permissions in a product demo

Write the question narrowly: “Can a contributor approve this request?” is testable; “Is the product secure?” is far broader than a short screen demonstration can establish. Obtain the actual role rules and any workspace-specific configuration from the product owner.

Separate view, edit and approve rights in the production notes. A disabled button may indicate a missing prerequisite rather than a permission restriction. Verify the reason before labeling it as a role boundary.

In this fictional example, Contributors can view their sample request and edit its note, while Reviewers can record an approval decision. These are invented planning rules, not a claim about Animro or another application.

• Contributor view: label the account “Example contributor — Contributor.” Open R-024 with its status Awaiting review. Show the note field and the actual permitted edit action.
• Boundary: show the verified absence or disabled state of the approval control. Explain “Approval requires the reviewer role” only if the rule is confirmed.
• Handoff: hold a transition card, “Switching to Example reviewer.” Keep R-024’s identifier visible as the thread connecting both views.
• Reviewer view: label the new role, open the same R-024 and demonstrate the actual approval action.
• Result: return to the contributor view and inspect the resulting status, if visibility of that change is part of the documented behavior.

An editorial transition between accounts is not a product control that lets a user become a reviewer. Say “Reviewer view” or “Separate reviewer account” instead of animating the contributor avatar into a new role without explanation.

If administrators configure the permissions beforehand, state that prerequisite. A film about using a permission is different from a film about granting it. Keep the administrator settings sequence separate unless it directly answers the viewer’s question.

Compare what each role can see: fields, comments, attachments and history may differ. Showing an administrator screenshot while labeling it Contributor can misrepresent access even if the featured button is correct.

For a compact version, use matched screenshots with explicit role labels. For training, show the account handoff and the correct next action when access is unavailable. Do not generalize one configured example into a guarantee about all organizations.