How-to / 4 min read
Setting up meeting profiles for each kind of call
Use a ScreenVeil profile to save private-app choices for a particular audience, such as a client demo or an internal standup. Select the profile before sharing, review its app list and check the receiver view. The profile does not inspect document contents or select Privacy Screen in the meeting app for you.
Save a different set of private apps for standups, client demos and recordings, then switch before you share.
By ScreenVeilUpdated
A profile for each kind of callWhat belongs in a meeting profile?
A profile should describe which apps stay private for a particular kind of session. Choose names that tell you the audience, such as Client demo or Internal standup, so the choice is understandable when you are about to join.
Start with the audiences that change your privacy decisions. An internal messaging app might be appropriate in a team meeting but private during a customer demo. Personal messages may stay private in both.
A saved app list does not classify documents. If an allowed browser contains another customer’s account, selecting a Client demo profile will not identify or remove those records.
These are fictional configuration examples, not preset guarantees. Keep the list of profiles short enough that you can review the selected one rather than trusting its name.
| Example profile | Review before the session |
|---|---|
| Client demo | Keep internal chat, deal notes and personal apps private; prepare a fictional or approved demo account. |
| Internal standup | Decide whether team chat belongs in the feed; keep unrelated client and personal material separate. |
| Recorded walkthrough | Review the recording source, app transitions and audio inputs as well as the app exclusions. |
| Livestream | Check every scene and source in the streaming tool, including overlays outside Privacy Screen. |
Can a profile keep one browser tab private?
No. An app exclusion acts on the app; ScreenVeil does not redact one tab or text inside a shared browser window. Separate public and private browser work before you rely on a saved profile.
For a whole-window exception, use Hide a window or Settings → Sharing → Specific windows. Those selections reset when Privacy Screen stops. Review them for each new session instead of treating them as permanent content rules.
Check the app list after you install a new messaging client or move notes into another app. A profile based on last month’s tools may not match what is open today.
How should you switch from an internal call to a client demo?
Stop the old share before changing the audience or setup. Then select and review the profile for the next session, prepare its public content and start a fresh share with the intended source.
For example, an internal standup might show a planning board that includes unreleased work. A client demo needs its own prepared board. Changing the private-app list cannot remove internal information already displayed inside the browser you intend to show.
- 1
End the previous share
Use the meeting app’s stop-sharing control before rearranging windows or opening the next account.
- 2
Select and inspect the profile
Confirm the intended private apps, then review any whole-window exclusions needed for this session.
- 3
Prepare the opening view
Put a clearly identifiable, customer-safe first slide or demo page in the public workspace.
- 4
Select and verify the source
Share Privacy Screen in the meeting app and inspect a receiver view before consulting private material.
How can you rehearse a profile safely?
Use fictional labels to make mistakes visible without exposing real information. Create a Sample Client Deck, a notes window labeled SAMPLE INTERNAL NOTES and a personal message labeled SAMPLE PERSONAL MESSAGE.
This is a suggested exercise, not a customer result. Select the profile, start Privacy Screen and share it to a second device or a short recording. Switch among the deck and private apps as you would in the meeting, then inspect the actual received output.
Practice the default ⌘⇧B Cover feed shortcut and the meeting app’s stop-sharing control. Cover feed affects Privacy Screen only; the meeting app’s selected source remains a separate decision.
If you restart Privacy Screen, revisit individual window choices. If you change the display arrangement or sharing source, check the receiver view again.
What still needs checking outside the profile?
Notification behavior, audio inputs and the meeting source still need their own review. A private-app profile does not mute the microphone or prevent a sound from entering a recording.
ScreenVeil excludes Notification Center banners by default in the tested macOS 26.1 setup, while app-drawn popups need separate attention. A Focus mode’s allowed people and apps can also change which interruptions occur.
For a recorded session, review the finished recording before distributing it. For a livestream, inspect the other scenes and sources too. The app profile covers one part of the workflow, so a final source check remains useful even when you use the same profile every week.