How to Blur Notion During Screen Sharing (Hide Client Databases, Roadmaps & Financials)
Presenting from Notion? Here's how to blur client names in databases, roadmap and strategy pages, financial models, comments and sidebar page titles before you share your screen.
To hide sensitive Notion pages and databases while presenting, blur the left sidebar (page titles and the workspace name) and the specific database columns, cells or blocks that name clients, reveal financials or expose internal comments — before you share. BlurFirst bakes the blur into the page as real pixels, so it survives Zoom, Meet, Teams, Loom and any recording; just re-apply your region blur after you switch pages, because Notion re-renders the view each time.
What a Notion workspace exposes on a shared screen
- The sidebar — every page title, teamspace and the workspace name, mapping out projects and clients you may not want in the room.
- Client and deal names in databases — a table, board or list view where the Name column is the customer, and property columns hold status, owner or amount.
- Roadmap and strategy pages — unreleased plans, priorities and rationale written for the team.
- Financial models — budgets, pricing, runway or revenue in a table or an embedded block.
- Teammate @mentions — inline mentions and assignees that name people across the doc.
- Comments — the comment thread and the sidebar comment count expose candid internal discussion.
How to blur Notion before you present
- 1
Open the page you'll walk through
Get Notion (notion.so) to the exact page or database view before the call.
- 2
Start BlurFirst
Press Ctrl/⌘ ⇧ Y. Blurring runs entirely in your browser; only a license check touches the network.
- 3
Box-blur the sidebar
Drag a rectangle over the left column so page titles and the workspace name stay hidden while you navigate.
- 4
Blur the sensitive columns or blocks
In a database, box-blur a whole column (the client Name column, an Amount property) so it stays covered as rows scroll; element-blur a single cell, callout or financial block when you only need to hide one.
- 5
Re-apply after switching pages, and keep panic ready
Notion re-renders when you open a new page, so re-drag your region blur (or let Pro auto-apply do it), and press Ctrl/⌘ ⇧ H if a comment or the wrong page appears.
Notion re-renders on every page switch — plan for it
Notion is a single-page app: opening a page, switching a database view, or going full-page all replace the content in place rather than loading a fresh URL. A box blur is anchored to a region, and BlurFirst re-applies anchored blurs when the page re-renders — but when you jump to a genuinely different page, the layout underneath changes, so the reliable habit is to re-drag the region for the new view (over the new column, the new block). If you present from Notion regularly, Pro's per-site auto-apply re-applies your saved structural blurs — the sidebar, the workspace name — automatically each time, so you only blur page-specific content per session. For anything that surprises you — a comment popping open, an @mention you forgot about — the panic hotkey frosts the whole page at once.
Databases often hold emails, phone numbers or even API keys in properties. BlurFirst's Scan (Pro) detects those patterns locally and blurs them in one click. Scan matches patterns, not free-text names, so box-blur the Name column to cover client names too.
| Notion element | Best gesture | Notes |
|---|---|---|
| Sidebar (page titles, workspace name) | Box/region blur | Re-apply after switching pages; Pro can auto-apply it |
| A whole database column (Name, Amount) | Box/region blur | Keeps covering the column as rows scroll |
| A single cell, callout or financial block | Element blur | Click to hide one block, click again to reveal |
| Emails, phone numbers, keys in properties | Scan (Pro) | Detects the pattern locally, blurs in one click |
| Comment thread / @mention popup | Panic (Ctrl/⌘ ⇧ H) | Blurs the whole page instantly, then toggle back |
Why blurring beats duplicating your workspace
The usual workaround is to build a sanitized 'demo' page or duplicate a database with fake data — hours of work that goes stale immediately and risks presenting the wrong version. Notion's own permissions don't help either: sharing settings control who can open a page in their browser, but on a screen share the audience sees your session, with your full access. Blurring lets you present the real, current workspace and simply control what the viewer sees — and because the blur is baked into the page, screenshots of the shared feed are covered too. The honest limit: BlurFirst affects content inside the browser tab, so the Notion desktop app (a native window) isn't covered; use notion.so in your browser, or wait for the BlurFirst desktop app in development.