How to Blur the BigQuery Console During Screen Sharing (Hide Project, Datasets & Results)

To hide query results and project data in the BigQuery console on a screen share, blur the items in the page before you present — the GCP project ID in the top bar, the dataset and table explorer, the Results grid with user PII, and the SQL that names your tables. BlurFirst paints each blur into the page as real pixels, so it survives Zoom, Google Meet, Microsoft Teams, Loom, OBS and a screenshot of the shared feed.

BigQuery lives inside the Google Cloud console, so the top blue bar carries the same identifying chrome as every other GCP service — the project picker that shows your current project ID. Anchor a region blur there and over the left Explorer panel, then use element blur or Scan for values. Start blurring with Ctrl/⌘ ⇧ Y and keep the panic hotkey Ctrl/⌘ ⇧ H ready for a result you didn't expect.

What the BigQuery console exposes on a call

• GCP project ID — the project picker in the top bar shows the current project ID and name, which identifies your Google Cloud project across every service.
• Dataset and table explorer — the left Explorer panel names your datasets, tables and views, e.g. myproject.analytics.users, laying out your data model.
• Query results — the Results tab under the editor shows raw rows: emails, user IDs and revenue — the real user PII you queried.
• SQL editor — the query editor exposes your table names, joins and logic to anyone watching.
• Saved and recent queries — the Saved queries panel and query history reveal past analyses and the tables they touch.
• Cost signals — the This query will process X bytes validator, bytes-billed totals and slot/cost figures that disclose your data scale and spend.

How to blur BigQuery before you screen-share

1. 1

   Open the query or page you'll present

   Load the exact editor tab, saved query or dataset before the call, and note which project is selected in the top bar so nothing surprises you mid-demo.

2. 2

   Box-blur the top project bar

   Drag a BlurFirst box over the project picker in the top blue bar. As an anchored region blur, it keeps covering the project ID as you navigate — and because it's the shared Cloud console chrome, the same blur helps across other GCP services.

3. 3

   Box-blur the Explorer panel

   Put an anchored box over the left Explorer so your dataset and table names stay hidden while you work in the editor.

4. 4

   Box the Results grid before running PII queries

   Anchor a box over the Results area rather than one cell, so it keeps covering the grid when a new query returns fresh rows. Element-blur a single column when that's all you need to hide.

5. 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 dataset or table names, so cover those yourself, and press Ctrl/⌘ ⇧ H if PII flashes into frame.

Why IAM and column-level security don't cover a screen share

BigQuery IAM roles, authorized views and column-level access control decide what your account can query. On a screen share your account is the one running the query, so the Results grid renders whatever you're entitled to read — full user PII if your access allows it. Those controls gate who can query the data, not what a viewer watching your screen sees. In-page blurring works at the presentation layer instead: it controls what the viewer sees, regardless of what your IAM roles permit.

Reuse your BigQuery blurs across the Cloud console

If you review queries in BigQuery regularly, set the structural blurs once. BlurFirst Pro's per-site auto-apply re-applies your saved boxes — the top project bar and the Explorer — automatically each time you open the console, and they survive the single-page-app re-render as you move between tabs. Because the project bar is shared chrome, the same box also helps on other services; see blurring the Google Cloud console. The profile stores only a CSS selector for each region, never the rows or table names inside it.