Redact employee details before you share an HR screenshot
Salary, national ID, and home address in an HR tool screenshot should be barred, not scribbled.
HRIS screenshots are a personnel file with extra pixels: salary, national ID, home address, emergency contact.
Payroll and people-ops tools are built to show the row. Slack is built to share it. If legal asked for “the error,” give the error. If a vendor needs a repro, give a barred image and a ticket number, not a spreadsheet of SSNs and wages.
Black bars belong on compensation, government IDs, dates of birth, bank account fields, home addresses, and the names of employees who are not the subject of the ticket. Crop the rest when the UI chrome is the bug. Do not “anonymize” a salary with a light blur. Digits survive blur. Opaque rectangles do not.
Slack is not an HR vault
Forwarding is the feature. A People Ops thread ends in a vendor Slack or a board deck. Bar before paste. Write the employee id in the ticket if you must correlate; do not leave the national ID in the pixels “so they can find the record.” They can find it in the HRIS.
Shared screens in a huddle are live personnel files. Someone will capture your share. Present a barred crop, or share a window that contains only the sanitized PNG. Notifications that slide in with another employee’s name are part of the frame; disable them or bar them after the fact.
What to cover on a people-ops capture
- Salary, bonus, equity, and band labels next to a name
- National ID, tax numbers, passport, visa, and license IDs
- Home address, personal email, personal phone
- Emergency contacts and dependents
- Bank account and routing fields in payroll
- Performance ratings and investigation notes in the sidebar
- Other employees in a directory search or org chart crop
A “system down” screenshot of the whole HRIS dashboard is a directory leak. Crop to the spinner or the error code. If the error only appears on one profile, bar the profile header, then show the broken control. The vendor does not need the address to fix a button.
Vendors, legal, and “just this once”
Processors will ask for a screenshot because it is faster than a HAR file. Send a barred PNG plus a ticket id. If they insist on unredacted data, use their secure upload, not email, and log who received it. Never post the raw capture to a public status page or community forum.
Legal holds still do not require salary numbers in a 200-person channel. Put the exhibit in the matter folder. The PNG that explains “the page crashed” can be the same UI with bars on every identifier.
Should I redact my own compensation in a benefits question?
Inside a ticket with HR, your own figures may be required. Inside a #benefits Slack thread, they are a gift to gossip and to anyone who screenshots the channel. Bar your salary and your account numbers before you ask why a deduction looks wrong. Keep the line item name and the error.
FAQ: we only showed last four of the national ID
Last four plus name plus employer plus date of birth in the same frame is still a lot. Bar the ID entirely in images that leave the HRIS. The last four can live in the private ticket text if policy allows. Images get thumbnails. Thumbnails get forwarded.
FAQ: can we mosaic the salary column in a report?
No. Mosaic and blur on a column of numbers are the textbook failure. Paint a solid bar over the column or export a CSV with those fields removed. If leadership needs the numbers, send the file through the compensation system, not through a JPEG in chat.
FAQ: an employee sent a selfie with their badge
Badges are IDs. Bar the photo, the employee number, and the office address if the file is going anywhere beyond the original ticket. Do not reuse the selfie as a “culture” slide. Access-control photos are not marketing.
Support teams already practice this on customer records; the support screenshot habit transfers. Phone and mail in headers: hide numbers and email. Before the next payroll toast hits Slack, bar the row in the editor and paste only that file.