How to Blur ServiceNow During Screen Sharing (Hide Records, Caller PII & Work Notes)

To present ServiceNow safely, blur the record content, caller PII and work notes directly in the page before you share your screen. Almost every ServiceNow screen names a real person and a real problem — the Caller / Requested-for name and email at the top of an incident, the description of what broke, the CMDB asset behind it, and the internal work notes where agents write candidly. Because ServiceNow is a browser-based ITSM tool with no presenter mode, your audience on Zoom, Teams or Meet sees exactly what you see. Blurring the sensitive fields in-page lets you walk through a ticket, demo a workflow or run a training session without exposing an employee's details or a colleague's internal notes.

The blur is painted into the page as real pixels, so it holds up across Zoom, Google Meet, Microsoft Teams, Loom, OBS and screenshots of the shared feed — it is not an OS overlay and needs no per-app setup. Nothing you blur ever leaves the browser; the only network request BlurFirst makes is a license check.

What's sensitive in ServiceNow

• Incident, case & request records — the short description and description fields that name a user and spell out exactly what's wrong, plus attached screenshots.
• Caller / Requested for — the caller name, email, phone and location in the record header, repeated on Cases and HR/CSM records.
• Work notes & activity stream — the internal work notes where agents leave candid, non-customer-facing commentary, plus the full comment history.
• Assignment group & agents — the assignment group and the assigned-to agent name, which reveal your team structure and who's handling what.
• List views — the incident / case list showing dozens of records at once: numbers, callers, short descriptions and priorities in one dense table.
• CMDB & assets — configuration item names, serial numbers, IP addresses and asset owners on the CMDB and Asset Management screens.
• Knowledge base — knowledge articles that carry internal procedures, credentials or customer specifics not meant for an outside audience.

How to blur ServiceNow for a screen share

Here's the flow with BlurFirst:

1. 1

   Share the ServiceNow tab only

   Present just the browser tab with your instance (yourcompany.service-now.com) — keep email, Slack and other tabs out of the feed.

2. 2

   Start BlurFirst

   Open the record or list you'll present and press Ctrl/⌘ ⇧ Y to bring up the control bar.

3. 3

   Box-blur the list view

   On an incident or case list, drag a rectangle over the caller and short-description columns so the whole table of records stays frosted. The box re-anchors as the list re-renders and as you scroll.

4. 4

   Element-blur the caller and work notes

   On a single record, click the Caller / Requested-for field, the email, or the work-notes panel to frost just that element. Click again to reveal it when you need to.

5. 5

   Scan before caller PII is on screen (Pro)

   One local Scan finds and blurs emails, phone numbers and other patterns on the page — worth running before you open a record full of caller details.

6. 6

   Keep the panic shortcut ready

   If you click into the wrong incident, press Ctrl/⌘ ⇧ H to blur the whole page instantly, then reveal only what you meant to show.

Why ServiceNow's own roles don't cover this

ACLs, roles and domain separation in ServiceNow control what the logged-in user can open. During a screen share, the logged-in user is *you* — often an admin or a senior agent with broad access — so anything you can see is exactly what your audience sees. Those controls were built to govern access, not to manage what someone watching your screen can read. Blurring works at the presentation layer: it controls what the viewer sees, regardless of your own permissions.

Common ServiceNow screen-share moments

• Vendor or MSP calls — walking an external implementation partner through a workflow without showing them real employee incidents.
• Internal training & enablement — recording a how-to for new agents when the demo instance is actually production.
• Stakeholder demos — showing a new catalog item or flow to a project sponsor while live tickets sit in the background list.
• Change and problem reviews — sharing a CAB screen where the record names people and systems not everyone on the call should see.

One honest limitation

BlurFirst is a browser extension, so it covers ServiceNow in the browser (your service-now.com instance), not the ServiceNow mobile app or any native window. It also only affects the browser tab, so share a single tab rather than your whole screen. Scan detects patterns like emails and phone numbers — not free-text names — so blur caller names, agent names and work-note prose with element or box blur. A desktop app that covers native windows is in development.