How to Blur the Vercel Dashboard During Screen Sharing (Hide Env Vars, Domains & Tokens)
Walking a client or teammate through Vercel on a call? Here's how to hide environment variables, deployment URLs and domains, team and project names, your account email and access tokens in the Vercel dashboard before you share your screen.
The safest way to hide project data in the Vercel dashboard during a screen share is to blur the specific items in the page before you present — the values under Settings > Environment Variables, your deployment URLs and custom domains, the team and project names, and your account email. 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.
The dashboard is a single-page app that re-renders every time you switch project, team or tab, so lean on anchored region blurs for the fixed chrome — the team switcher and account avatar in the top bar — and use element blur or Scan for individual values. Start blurring with Ctrl/⌘ ⇧ Y and keep the panic hotkey Ctrl/⌘ ⇧ H in reach for anything that flashes into frame.
What the Vercel dashboard puts on screen that you didn't plan to share
- Environment Variables — Settings > Environment Variables holds your real secrets:
DATABASE_URLconnection strings, third-party API keys and auth secrets. A value stays masked only until you click the reveal eye or open Edit to check it. - Team and project names — the team switcher and the project grid name your clients, internal codenames and unreleased products.
- Deployment URLs and domains — the Deployments tab lists preview URLs like
project-git-branch-team.vercel.app, and Settings > Domains shows the production domains you host. - Account email and members — the account menu and the Members page show your email and your teammates' emails.
- Git connection — the connected GitHub or GitLab repo, branch and commit author shown under the project's Git settings and on each deployment.
- Access tokens — personal tokens under Account Settings > Tokens, plus integration tokens, that grant API access to your account.
- Analytics and usage — the Analytics and Usage tabs show traffic, bandwidth and function-invocation figures that quietly disclose your scale.
Blur the Vercel dashboard step by step
- 1
Open the project and tab you'll demo
Navigate to the exact page before the call — Deployments, Settings, Domains, wherever you're headed — and note which team and project are selected so nothing surprises you mid-demo.
- 2
Box-blur the top bar and team switcher
Drag a BlurFirst box over the top-left area that holds the team switcher and project name, and over the account avatar and email. Because it's an anchored region blur, it keeps covering that chrome as the single-page app re-renders between projects.
- 3
Element-blur env var rows before you open Settings
On Settings > Environment Variables, click each variable's value or row to frost just it, and leave the values masked rather than clicking the reveal eye. The variable names stay readable so you can still talk through your setup.
- 4
Run Scan to catch keys, connection strings and emails
One click runs Scan (Pro), which detects API-key patterns, connection strings and email addresses locally and blurs them. It won't recognise project names or
vercel.apppreview URLs as patterns, so cover those with an element or box blur yourself. - 5
Keep panic ready for a revealed secret
If a secret appears unexpectedly — you clicked the reveal eye, or opened the wrong deployment — press Ctrl/⌘ ⇧ H to blur the whole page instantly, then re-frost the specific items.
| Sensitive item | Where it appears | Best gesture |
|---|---|---|
| Env vars (secrets, DB URLs) | Settings > Environment Variables | Element blur before revealing |
| Team + project names | Top-bar switcher, project grid | Box-blur the chrome |
| Deployment URLs + domains | Deployments, Settings > Domains | Element blur per row |
| Account email + members | Account menu, Members page | Box or element blur |
| Access tokens | Account Settings > Tokens | Element blur before revealing |
| Traffic + usage figures | Analytics, Usage tabs | Box-blur the charts |
Why 'hidden' env vars aren't hidden on a screen share
Vercel masks environment-variable values in the UI and encrypts them at rest, but that protects storage — not your presentation. The moment you open the Environment Variables screen to check or edit a value, or click the reveal control to copy it, the plaintext is on your screen, in the shared feed and in any recording. Those protections gate who can read the value inside the account; they don't manage what a viewer watching your screen sees. In-page blurring works at the presentation layer instead: it controls what the viewer sees, regardless of your own access.
Reuse your Vercel blurs on every deploy review
If you review deploys or support from the dashboard regularly, set the structural blurs once. BlurFirst Pro's per-site auto-apply re-applies your saved boxes — the team switcher, the account chrome — automatically each time you open vercel.com, and they survive the single-page-app re-render as you move between projects. The profile stores only a CSS selector for each region, never the secret or domain inside it, so nothing sensitive is written to disk or uploaded.