Share your screen without sharing the salaries
You know the meeting. Somebody needs to walk the room through headcount, or margins, or renewal risk, and the numbers live in a screen that also happens to contain something nobody in that room should see. So the meeting happens with a screenshot somebody cropped, or an export with a column deleted, or a manager reading figures aloud from a laptop nobody else can see.
Every one of those is worse than the real screen, and every one of them takes somebody twenty minutes beforehand.
Hide the values, keep the meeting
Right-click a column heading and choose Redact. The values blur. Everything that makes the screen useful stays exactly where it was: the row count, the sort, the filters, the totals, the grouping, the column itself. You can still say “we are at ninety-four people, here is the split by team, and these eleven are open roles”, because all of that is still on the screen. The one thing the room does not need is the one thing that went.
Turn it off after the meeting and the values come back. Nothing was exported, nothing was copied to a second sheet that now needs deleting, and nobody had to prepare anything.
Try it on the grid above. Right-click Salary, or Total cost, and keep talking.
Why this matters more than it sounds
The reason teams end up with cropped screenshots is not that redaction is hard. It is that the grid they are using has no concept of it, so the work moves out of the tool and into somebody’s afternoon. Multiply that by every recurring review a company runs and it is a real cost that never appears on anybody’s roadmap.
It also removes a bad habit. When sharing the real screen is awkward, people build a second version of the data to share instead, and second versions go stale, get emailed, and end up somewhere they should not be. The safest place for sensitive data is one place, with a way to not show it.
What it is, and what it is not
Redaction is for the room, not for the attacker. It hides values from forty people on a call, which is where the real leak happens. Where a value must never reach the browser at all, permissions handle that by not sending the column.
The redacted values are still in the page, so somebody determined, with the developer tools open, can read them.
For most meetings, where the problem is “not on the projector, please”, this is one right-click and you are done.
Your users get this because it ships in the grid. Nobody on your team builds it, maintains it, or explains why the export script broke.