How to Blur Snowflake (Snowsight) During Screen Sharing (Hide Query Results & Schema)
Presenting from Snowsight on a call? Here's how to hide query results with customer PII, the SQL and table names in your worksheet, the database object explorer, your account identifier, warehouse costs and shared users before you share your screen.
To hide data and warehouse details in Snowflake's Snowsight UI on a screen share, blur the items in the page before you present — the query Results grid with customer PII, the SQL in your worksheet that names tables and schemas, the object explorer, and your account identifier. BlurFirst paints each blur into the page as real pixels, so it survives Zoom, Google Meet, Microsoft Teams, Loom, OBS and even a screenshot of the shared feed.
Snowsight is a single-page app that re-renders every time you run a query or open a worksheet, so anchor region blurs over the fixed panels — the left Databases explorer and the Results grid area — and use element blur or Scan for individual values. Start blurring with Ctrl/⌘ ⇧ Y and keep the panic hotkey Ctrl/⌘ ⇧ H in reach for a result set you didn't expect.
What Snowsight shows that you didn't mean to share
- Query results — the Results grid under a worksheet shows raw rows: customer names, emails, order values and IDs — the real PII you just queried.
- Worksheet SQL — the editor exposes your table and schema names, joins and business logic, e.g.
SELECT … FROM analytics.prod.customers. - Object explorer — the left Databases panel names every database, schema, table and view, laying out your whole data model.
- Account identifier and region — the account identifier and org/region in the account menu (and in the
org-account.snowflakecomputing.comaddress), which identify your Snowflake account. - Warehouses and costs — the Warehouses admin and Cost Management / Usage pages show warehouse names, sizes and credit spend.
- Shared-with users — the Share dialog and the Users & Roles admin list teammate names and email addresses.
Blur Snowflake Snowsight step by step
- 1
Open the worksheet or page you'll present
Load the exact worksheet, dashboard or admin page before the call, and note which role and warehouse are selected so nothing surprises you mid-demo.
- 2
Box-blur the object explorer
Drag a BlurFirst box over the left Databases panel so the database, schema and table tree is hidden. As an anchored region blur, it stays put as the app re-renders between worksheets.
- 3
Box the Results grid before you run PII queries
Put an anchored box over the Results area rather than a single cell — that way it keeps covering the grid when a new query returns a fresh result set. Element-blur individual cells when you only need to hide one column.
- 4
Element-blur the SQL that names sensitive tables
If the editor query reveals a client schema or table you'd rather not name, element-blur that line, or box the editor and talk through the query shape verbally.
- 5
Run Scan, then keep panic ready
One click runs Scan (Pro), which detects emails, phone numbers, credit-card numbers, SSNs and API keys in the visible results locally. It won't recognise table or schema names, so cover those yourself, and press Ctrl/⌘ ⇧ H if a result appears unexpectedly.
| Sensitive item | Where it appears | Best gesture |
|---|---|---|
| Query results (customer PII) | Worksheet Results grid | Box the results area, or Scan |
| Table + schema names | SQL editor, object explorer | Element or box blur |
| Databases + schemas tree | Left Databases panel | Box-blur the panel |
| Account identifier + region | Account menu (and URL) | Blur the account menu in-page |
| Warehouse names + credit spend | Warehouses, Cost Management | Box-blur the figures |
| Shared-with users | Share dialog, Users & Roles | Element blur per row |
Why RBAC and masking policies don't cover a screen share
Snowflake RBAC, dynamic data masking and row-access policies decide what the querying role can retrieve. On a screen share the querying role is yours, so the Results grid shows exactly what you're entitled to see — full PII if your role can read it, and masking policies that unmask for privileged roles will render plaintext to you, and therefore to your viewers. Those controls govern who can access the data, not what a viewer watching your screen reads. In-page blurring works at the presentation layer instead: it controls what the viewer sees, whatever your role can query.
Reuse your Snowsight blurs on every data review
If you review data or run demos in Snowsight regularly, set the structural blurs once. BlurFirst Pro's per-site auto-apply re-applies your saved boxes — the object explorer and the Results area — automatically each time you open Snowsight, and they survive the single-page-app re-render as you move between worksheets. The profile stores only a CSS selector for each region, never the rows or table names inside it, so nothing sensitive is written to disk or uploaded.