How to Blur the Twilio Console During Screen Sharing (Hide Account SID, Auth Token & Numbers)
Demoing Twilio on a call? Here's how to hide the Account SID and Auth Token, your purchased phone numbers, API keys, message and call logs with recipient numbers, verified caller IDs and billing before you share your screen.
To hide credentials and customer data in the Twilio console on a screen share, blur the items in the page before you present — the Account SID and Auth Token on the dashboard, your purchased phone numbers, API keys, and the recipient numbers and message bodies in your logs. 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.
The console is a single-page app that re-renders as you move between the dashboard, Phone Numbers and the log Monitor, so use anchored region blurs for the fixed account credentials card on the dashboard and element blur or Scan for values in tables. Start blurring with Ctrl/⌘ ⇧ Y and keep the panic hotkey Ctrl/⌘ ⇧ H ready for anything that appears mid-demo.
What the Twilio console reveals when you present it
- Account SID and Auth Token — the console dashboard shows your Account SID (
AC…) and a click-to-reveal Auth Token. Together they are full API credentials: anyone who reads them can send messages and place calls billed to you. - Purchased phone numbers — your active numbers and their friendly names under Phone Numbers > Manage > Active numbers.
- API keys — Standard and Main API keys (SID
SK…plus a one-time secret) under Account > API keys & tokens. - Messaging and Voice logs — Monitor > Logs > Messaging and Calls list recipient phone numbers, SMS message bodies and call metadata — real customer PII.
- Verified caller IDs — the outbound numbers you've verified under Phone Numbers > Verified Caller IDs.
- Billing — account balance, usage and spend figures on the Billing pages that disclose your volume.
How to blur the Twilio console before you share
- 1
Open the page you'll present
Navigate to the dashboard, Active Numbers or the log you plan to show, and note which project or account is selected in the top-left switcher.
- 2
Box-blur the credentials card
Drag a BlurFirst box over the dashboard panel that holds the Account SID and Auth Token. As an anchored region blur, it keeps covering that card even after the single-page app re-renders.
- 3
Element-blur numbers and log rows
Click a phone number, a recipient cell or a message body in a log to frost just that element while the surrounding columns stay readable. Click again to reveal one if you need to point at it.
- 4
Run Scan for numbers, keys and emails
One click runs Scan (Pro), which detects phone numbers, API-key patterns and email addresses locally and blurs them across the visible page. Free-text message bodies aren't patterns, so cover those with an element or box blur yourself.
- 5
Keep panic ready before you reveal the token
If you must reveal the Auth Token, blur the value first or avoid clicking the reveal control on camera. If it flashes into frame, press Ctrl/⌘ ⇧ H to blur the whole page instantly.
| Sensitive item | Where it appears | Best gesture |
|---|---|---|
| Account SID + Auth Token | Console dashboard | Box-blur the credentials card |
| Purchased phone numbers | Phone Numbers > Active numbers | Element blur, or Scan |
| API keys (SK…) | Account > API keys & tokens | Element blur before revealing |
| Recipient numbers + message bodies | Monitor > Logs (Messaging/Calls) | Element blur per row, or Scan |
| Verified caller IDs | Phone Numbers > Verified Caller IDs | Element blur |
| Balance + billing figures | Billing pages | Box-blur the totals |
Why revealing the Auth Token once is the whole risk
Twilio keeps the Auth Token masked until you click to reveal it, and scopes it to your account — but that's access control, not presentation control. The instant you reveal it to copy it into a code snippet on a call, the full credential is in frame and in the recording, and anyone who reads it can send SMS and place calls on your account until you rotate it. The masking gates who can view the token inside the console; it doesn't manage what a viewer watching your screen reads. In-page blurring works at the presentation layer: it controls what the viewer sees, no matter what your own access is.
Set your Twilio blurs once and reuse them
If you demo or support from the console often, set the structural blurs once. BlurFirst Pro's per-site auto-apply re-applies your saved boxes — the credentials card on the dashboard — automatically each time you open console.twilio.com, and they survive the single-page-app re-render as you switch sections. The profile stores only a CSS selector for each region, never the SID, token or phone number inside it, so nothing sensitive is written to disk or uploaded.