Client calls / 7 min read
Private screen sharing checklist for client calls on Mac
A practical Mac screen-sharing checklist for therapists and consultants: narrow the capture, quiet notifications, test the audience view and know the limits.
By ScreenVeilPublished
Share the work, not the private contextThe short answer
Share the smallest useful source, turn on Focus, close private content inside any app you will show, and verify the live audience view from a second device. If you need to switch between public apps while private apps stay open, share ScreenVeil's Privacy Screen window—not your desktop.
Your client-call checklist
A client asks you to show a document, portal or draft. The useful window is ready, but the same Mac also has another client's notes, messages, email and calendar open. For therapists and consultants, a stray window can cross client boundaries: another client's name in a title, session notes in a recent-files menu or appointment details in a calendar preview.
The goal is not to promise perfect secrecy. It is to make the predictable surfaces part of the setup before anyone else can see the screen. This is screen-sharing hygiene, not legal or compliance advice; no screen-sharing utility makes a call, practice or workflow compliant by itself.
Scroll sideways to compare →
| Before | During | After |
|---|---|---|
| Prepare | Use sample or redacted content. Close unrelated files and private tabs. Turn on Focus and check its exceptions. | Start Privacy Screen if you need to move between several apps. |
| Verify | Read the selected source name. Check the audience view from a second device and make sure it is updating. | Keep the meeting app's Stop sharing control within reach. |
| Finish | Stop sharing before changing protected apps or stopping ScreenVeil. | Review recordings before sending them. Re-test after software or display changes. |
Start with the smallest useful sharing boundary
If the client only needs one document, share that document's window. If they only need one web page, use tab sharing when the meeting tool offers it. A smaller boundary reduces what can appear by accident and is usually simpler than adding another tool.
The tradeoff arrives when the conversation moves. A consultant may need to switch from a proposal to a spreadsheet and then a browser. A therapist may need prepared educational material while scheduling or notes stay available privately. Stopping and restarting the share for every switch is safe but disruptive. Sharing the entire display is easier, but every visible app becomes part of the audience view.
Scroll sideways to compare →
| Client-call workflow | Start with | Important limit |
|---|---|---|
| Therapist showing a prepared educational PDF | Share that app window | Keep session notes and client records closed or in a different, private app. Test separate dialogs. |
| Consultant showing one website | Share one browser tab | Anything you open in that tab becomes visible. |
| Consultant moving from a proposal to a spreadsheet while CRM and Slack stay open | Share a prepared display, or Privacy Screen | ScreenVeil does not filter a desktop share. |
| Several public apps with private apps still usable | Share Privacy Screen | It hides whole apps or selected windows, not a tab or text inside a public app. |
Prepare sensitive material before client calls
Private screen sharing starts inside the app you intend to show. ScreenVeil cannot hide one paragraph, one patient or customer name, or one browser tab while the rest of that same app remains public.
Use fictional or redacted records for a demonstration whenever possible. Close unrelated documents, clear recent-file menus if they expose names, and move private web work to a different browser that can be kept out of the share. A separate browser profile can separate accounts and history, but ScreenVeil still sees the browser as one app; it cannot filter profiles or tabs independently.
Check the desktop, Dock, window and tab titles, bookmarks bar, autofill suggestions, recent documents, calendar previews and file picker. Those small surfaces are easy to miss because they are not the main document.
Quiet notifications without confusing silence with hiding
Apple's Focus controls can reduce interruptions. Open Control Center on the Mac, choose Focus and turn on the mode you want. Review its allowed people, allowed apps and schedule before relying on it; a Focus can be configured to let selected notifications through.
Focus does not hide an email window, a Messages conversation already on screen, a browser tab title or a client name in a document. Treat it as the notification layer, not the sharing boundary. ScreenVeil does not block notification banners either. A banner from an app that remains visible can still appear in Privacy Screen.
Pick the right sharing source for client calls on Mac
The labels change as meeting apps update, but the decision is the same: choose a window rather than the full screen when you want a narrow boundary. In Zoom, select the prepared app window or Privacy Screen rather than Desktop. In Google Meet, choose Present now, then A window. In Microsoft Teams, choose the relevant window rather than Screen when one app is enough.
Apple requires separate Screen & System Audio Recording permission for apps that record your screen and audio. Giving permission to ScreenVeil does not automatically give it to Zoom or your browser, and vice versa. Review access in System Settings → Privacy & Security → Screen & System Audio Recording.
Do not infer safety from a picker thumbnail. After selecting the source, verify the live audience view.
When ScreenVeil helps—and what it does not promise
ScreenVeil is useful when one-window sharing is too restrictive. In Privacy Screen mode, it uses Apple's ScreenCaptureKit on your Mac to create a separate window that leaves out apps and windows you marked private. You share that Privacy Screen window in Zoom, Meet, Teams, Loom or OBS. Your private apps remain open on your Mac.
ScreenVeil does not filter a desktop share, block other software from recording your real display, suppress notifications, identify sensitive text or hide one tab inside a browser you are showing. It also cannot see which source you selected in the meeting app. Test again after macOS or meeting-app updates, or after changing displays.
That boundary matters for professional client work: ScreenVeil can reduce accidental exposure in the feed you choose to share, but it does not replace access controls, consent, record-handling policies or your organization's security and compliance process.
The client-call capture path
- 01
Your Mac
Public and private apps can both remain open.
- 02
Privacy Screen
The apps and windows you marked private are left out.
- 03
Meeting app
You explicitly select Privacy Screen as the source.
Verify the client's view before every session
Run the test with sample content, never with the sensitive material you are trying to protect. A frozen but apparently clean preview is not a successful test. The audience view must stay private and keep updating.
- 1
Start the real tool
Use the same meeting or recording app and the same display arrangement you will use for the call.
- 2
Select the source
Choose the prepared window or Privacy Screen. Read the source name before confirming.
- 3
Watch from outside
Join from a second device, or make a short test recording and play it back.
- 4
Exercise the workflow
Edit or scroll the public document, open a private app, switch public apps, press ⌘⇧B to cover the feed, then resume.
- 5
Confirm privacy and motion
The private app should never appear, and the public feed should keep updating through every switch.
- 6
Stop in the right order
Stop sharing in the meeting app before stopping ScreenVeil or changing the protected-app list.
Use the simplest setup that fits the call
For one document, share one prepared window. For one web page, share a tab. Add ScreenVeil when you need to move between public apps while Slack, Mail, Messages, notes or another private app remains usable on your Mac.
Run the verification steps with sample content before relying on the setup in a real client session. The point is a repeatable boundary you have actually seen from the client's side—not a privacy claim you have to take on faith.
0 of 5 checked
For your rehearsal. Selections stay on this page and are not sent anywhere.
Related guides
Start here
How to hide apps when screen sharing on a Mac
Keep Slack, email and notes out of a Mac screen share without quitting them. Compare sharing one window with ScreenVeil's filtered Privacy Screen window.
Comparison
Muzzle vs ScreenVeil: which privacy problem are you solving?
Muzzle and macOS Focus deal with notifications. ScreenVeil keeps private apps out of the window you share. Compare them and pick the simplest setup for your calls.
Guide
Screen-share privacy for sales engineers
SEs demo on live customer data, and one stray Slack message or leftover tab can derail a deal. How to set up your Mac so private apps stay out of the demo.