From 5407aa618f828ae3690e6e55db7517ab14562edc Mon Sep 17 00:00:00 2001 From: jmirchh75 Date: Mon, 17 Aug 2026 03:49:24 +1000 Subject: [PATCH] docs: add privacy-safe screenshot checklist for Cross-Project Dashboard (CPD-Q06) --- ...D-Q06-privacy-safe-screenshot-checklist.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 docs/CPD-Q06-privacy-safe-screenshot-checklist.md diff --git a/docs/CPD-Q06-privacy-safe-screenshot-checklist.md b/docs/CPD-Q06-privacy-safe-screenshot-checklist.md new file mode 100644 index 0000000000..2b907bfaf9 --- /dev/null +++ b/docs/CPD-Q06-privacy-safe-screenshot-checklist.md @@ -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. \ No newline at end of file