The assignment says “screenshot the group discussion.” The group discussion has twelve classmates’ emails. The LMS dropbox did not ask for a roster. Neither did the parent who will print the PDF next week, nor the scholarship blog that scrapes portfolios next year.
School work travels farther than the rubric. Shared folders, recycled teacher decks, class Discord mirrors, and public gists all keep a copy. This page is the habit of proving you did the work without publishing the rest of the class. It is practical pixel hygiene, not legal advice and not a FERPA opinion letter.
What the rubric is actually grading
Open larger image in a new tabMost screenshot assignments check that you used the tool, posted on time, or reached a UI state. They are not asking you to publish the study group. If the prompt is a formula, they need the formula. If it is a reply, they need the reply. Bar every other student’s address and any instructor comment that was not meant for a portfolio.
Group chats on Discord or WhatsApp are worse than LMS forums because nicknames, phone numbers, and a parent’s contact sit in the same frame. A PTA thread you were told to “just send” is still other people’s numbers. Bar or crop. If you need to prove a message existed, keep the timestamp and the relevant sentence, not the member list.
How to blur a screenshot for class
- Read the rubric first. Capture only what the prompt needs. If it is “show your formula in Sheets,” crop to the cells. If it is “show you replied,” keep the timestamp and your sentence.
- Paint opaque bars on classmate emails, usernames, student IDs, grades, and home addresses in a parent thread. Use a filled shape in Markup or Paint, or Black bar plus Box in a browser tab.
- For faces in a Meet grid the brief did not require, crop the extra tiles or use Blur / Draw on the person, then bar the name label.
- What you should see is the proof the teacher asked for, with other people’s identifiers gone at 100% zoom.
- Tap Download PNG (or save a new file). Submit that copy. Delete the raw capture from Downloads and from the camera roll if you used a phone.
Open larger image in a new tabWhat counts as someone else’s data
- Classmate emails, usernames, and student ID numbers
- Faces and real names in a Meet or Zoom grid
- Grades, comments, and accommodation notes in the LMS rail
- A parent’s phone, address, or workplace in a forwarded chat
- Your own ID or lunch-account number if the file will be public
- Repo paths and error dumps that contain a classmate’s username
Your own name on a homework header can stay if the LMS already authenticates it. Your passport photo in a “upload ID for the field trip” thread should not be screenshotted into a group chat. Black-bar ID numbers and addresses even when the photo is of you. Portfolios and scholarship blogs get scraped.
Grid calls and name labels: Meet and Zoom.
Teachers and recycled decks
A slide that shows last year’s discussion as an exemplar still shows last year’s students. Re-bar or recrop before this year’s upload. Do not rely on a yellow highlight over a name. Do not leave the gradebook in a “how to submit” demo. For an example thread, use fake names or bar every real identifier until only UI chrome remains.
Shared Chromebooks keep downloads. Export the barred PNG, submit that, delete the raw capture. Photos of the screen add location metadata and other students in the room. Capture quirks: Chromebook screenshots.
Should I bar my own email on a school screenshot?
If the file stays inside the assignment dropbox, your school email is usually expected. If you will post the same PNG on a public GitHub gist, a Discord help channel, or a college application portal that becomes a brochure, bar the address. The rule is destination, not vanity. Assume a “private” class Discord is not private.
FERPA is the U.S. student-records law. This page is not legal advice. It is the practical habit: do not volunteer classmates’ identifiers in a PNG the whole class can download. Teachers who need unredacted PII should collect it through the LMS, not through a discussion-board image. The Department of Education’s FERPA FAQ is the official overview if you need the statute’s shape, not a lawyer’s memo for your district.
Troubleshooting common assignment traps
- The professor asked for the whole window. Whole window still allows bars. Cover the roster, the mail chip, and the notification that named another student.
- Can I blur faces in a group Meet instead of bars? Faces are the one case where a strong blur is sometimes enough for “not recognisable in a hallway.” Names, emails, IDs, grades, and addresses are not that case. Use black rectangles on text.
- The code screenshot has a classmate’s repo path. Paths contain usernames. Error dumps contain emails. Cover those strings. Keep the compiler error. Pair programming still does not need their home folder in a public gist “for help.”
- I installed a random editor APK on a school profile. Do not. A browser tab can cover pixels without another install. For the LMS upload, cover the roster in the tab.
When the LMS already stores the roster
Classrooms already keep official attendance lists inside the learning system. That does not mean every PNG you upload to the stream should reprint those names. The LMS record stays behind a login. A discussion image is a download that classmates can save, forward, and post to a group chat. Your redaction habit is about the file that leaves the assignment box, not about whether the school “already knows” who is in the class.
Group projects make this worse. One student captures a Meet grid “to prove we met,” and the tile names of three classmates who never agreed to be in a public portfolio. Crop to the slide or the doc you edited. If faces must stay for a media assignment, cover names and chat sidebars first. Faces without nameplates are still a consent problem for minors; ask the teacher before you publish.
If you need a browser tab that keeps the snip on your device while you bar the roster, open the screenshot tool. Submit the PNG. Delete the raw capture from Recents so the next AirDrop does not send the wrong file.
