An HRIS is built to show the row. Slack is built to forward it. A payroll error can move from a people-ops tab to a vendor huddle in under ten minutes, with salary, national ID, and home address still in the pixels. The bug report did not need those fields. The channel got them anyway.
This is practical sharing hygiene, not legal advice. It is not a substitute for your employment counsel, your privacy office, or the retention rules on the actual personnel file. The FTC’s business guidance on protecting personal information is blunt about employee records: collect what you need, keep it somewhere designed for it, dispose of it on purpose. A Slack screenshot is none of those three.
Black bars belong on the row, not a polite smear
Open larger image in a new tabCompensation, government IDs, dates of birth, bank account fields, home addresses, and the names of employees who are not the subject of the ticket all belong under opaque rectangles. 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. The general rule is blur versus black bar.
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.
Redact an HR screenshot before it leaves the HRIS
- Crop to the broken control or the error toast. Leave the directory search and the org chart out of the frame.
- Duplicate the file. Keep any unbarred original only where personnel files already live, with access control.
- Paint black bars over salary, bonus, equity, national ID, tax numbers, bank fields, home address, personal email, and personal phone.
- Cover emergency contacts, dependents, performance ratings, and other employees in the sidebar. Cover the profile header if the subject is not supposed to be named in that channel.
- Export PNG from BlurThis or your approved editor. Zoom. Paste only that file. If a huddle needs the UI, share the barred PNG window, not the live HRIS.
Open larger image in a new tabWhat you should see in the vendor ticket: an error code and a barred profile chrome. What you should not see: a national ID plus a home street in the same PNG that hundreds of people can forward.
Shared screens are live personnel files
Someone will capture your huddle 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. A “system down” screenshot of the whole HRIS dashboard is a directory leak. Crop to the spinner. The vendor does not need the address to fix a button. Notification traps: notifications in screenshots.
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
Phone and mail in headers: hide numbers and email. Support teams already practice a similar habit on customer records. The support screenshot checklist transfers, with compensation and national ID added to the list.
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. Prefer PNG so chat recompression does not ring around thin bars. PNG versus JPEG.
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.
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.
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.
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.
If the barred file still shows a wage
Enlarge the rectangle. Check descenders and the space between digit groups. If Slack already cached an unbarred preview, delete what you can and treat the channel as having seen the figure. Then stop using Slack as the vault. That is still not legal advice. It is how screenshots actually move.
Recap
Salary, national ID, and home address do not belong in a Slack PNG. Slack is not an HR vault. This page is not legal advice. Before the next payroll toast hits the channel, bar the row in the editor and paste only that file.
