Content professionals live in the CMS: drafting posts, staging pages, configuring plugins, migrating client sites. WordPress admin, Webflow designer, Contentful entries — every one of them holds unpublished content and client projects, and every screen share, walkthrough, or Loom from a content desk risks showing the pending web: drafts not ready, staging not announced, client work not launched.
The Standard Setup (And Why It Fails)
"I share the published page, not the admin."
Why it fails:
- The fix for "the staging page looks broken" is a screen share of the staging page — and the share renders the URL bar: staging.clientbrand.com, announcing the unannounced.
- Admin panels show the drafts list, the media library, and the recent edits with author names — your whole editorial pipeline in one sidebar.
- Window titles name the site: "Edit Post — [draft title] — WordPress," readable in every switcher frame during the client call.
- Notifications: a plugin update alert, a comment notification with a commenter's name, an editorial Slack ping about the draft — rendering over the shared screen.
The CMS is where unpublished becomes published by accident — the screen share is the printing press.
The NoCapture Setup for CMS Desks
Cloak the admin. The wp-admin, Webflow designer, and Contentful app windows go on the protected list for any shared or recorded session. You demo the published page, the front-end, the curated view — and the admin was never in the capture stream. Drafts stay drafts even when your screen is live.
Mask the titles. Tab and window titles carry site names, draft titles, and environment labels. Title masking sanitizes them in the window manager — switchers and enumeration show a generic label, so staging URLs and unannounced project names stop being metadata.
Shield the session. WordPress, Webflow, and team-channel notifications held during client calls and recording blocks — released after. The comment notification with a reader's name never banners over the client demo.
A routine per client call. Calendar shows a client meeting → routine fires: admin surfaces cloaked, titles masked, banners held. Armed by the meeting, not by remembering which meeting it is.
Live preview before sharing. The preview pane confirms the share shows the published page and nothing else. Ten seconds before the call beats ten minutes of damage control after it.
The Honest Limitation
Cloaking protects the surfaces around the content — the draft itself still needs editorial discipline. A staging URL shared deliberately in an email leaks regardless of what's cloaked, and unpublished content you show a client is unpublished content the client has seen. Keep staging access controlled, share drafts through review links with expiry, and treat the CMS like the newsroom it is. The tool keeps the admin off camera; your publishing workflow decides what the client sees.
The Bottom Line
The CMS is the newsroom: drafts, staging, and launches-in-waiting, all one screen share away from premature publication. Cloak the admin, mask the titles, hold the banners, preview the share — and let the only thing your screen ever announces be what you meant to ship.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
