Skip to content

docs: add privacy-safe screenshot checklist for Cross-Project Dashboard #511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jmirchh75 wants to merge 1 commit into
base: Feature/Cross-Unit
Choose a base branch
from
+28 −0
Open

docs: add privacy-safe screenshot checklist for Cross-Project Dashboard #511

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/CPD-Q06-privacy-safe-screenshot-checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Cross-Project Dashboard Privacy-Safe Screenshot Checklist

Use this checklist before sharing a dashboard screenshot in a pull request, Teams message, report, portfolio, presentation, or handover document.

## Before sharing

- [ ] Real student names have been removed or replaced with mock names.
- [ ] Student IDs and email addresses are not visible.
- [ ] Personal account details and profile images are not visible.
- [ ] Unit and project information does not reveal a student's private enrolment details.
- [ ] Task titles do not contain sensitive or personally identifying information.
- [ ] Marks, feedback text and individual assessment results are hidden or replaced with mock data.
- [ ] Extension details and changed due dates do not reveal private student circumstances.
- [ ] Browser tabs, URLs, tokens, local file paths and account information have been cropped or hidden.
- [ ] Mock or seeded data has been used wherever possible.
- [ ] The screenshot contains only the area needed to prove the result.

## Safe example

A screenshot of the dashboard populated entirely with seeded demo data — for example, students named "Test Student 1" and "Test Student 2" with placeholder emails, generic task titles, and sample marks that were never tied to a real person — cropped tightly to the feature being demonstrated, with no browser chrome, URL bar, or login/account menu visible.

## Information that should be hidden

A screenshot taken from a real unit that shows an actual student's name, ID, or email next to their real mark, feedback comment, or an approved extension with a reason attached. This kind of detail should be blurred, cropped out, or replaced with mock data before the screenshot is shared, even if the rest of the screen is unrelated to the point being made.

## Recommendation

The safest default for future contributors is to always demonstrate features using mock data rather than real student or account data, even when it takes a little longer to set up.