Share Multiple Windows in Microsoft Teams on Mac

Start with the smallest native share

A presentation that stays inside one document usually needs only one shared window. Open the document, join the meeting, choose Share, and select the preview belonging to that window. Ask a test participant to confirm the actual document is visible before beginning.

Microsoft’s current presentation instructions describe sharing a screen or a window. A separate option lets Mac users enable Settings → General → Screen sharing → Use macOS content sharing. The setting takes effect without restarting Teams; giving and taking control are unavailable in that native sharing experience.

Check the picker your installed Teams client actually presents. Do not assume a keyboard shortcut from a Zoom tutorial selects several windows in Teams. If your native picker offers additional-window selection and handles your fixed set correctly, use that. A filtered audience window becomes useful when the job involves recurring rules about which apps or Chrome profiles may appear.

The question is what the audience should see during each transition. Two windows from one app, two apps on one display, and two people presenting are different jobs.

Check the newer Mac sharing experience

Microsoft introduced the native macOS sharing option in a December 2025 preview announcement. The current support page also documents it. That makes older instructions which describe only the traditional Teams picker incomplete for today’s Mac setup.

Microsoft Tech Community, captured September 11, 2026. The announcement identifies the native macOS sharing experience; use the current support instructions for the setting and its limitations.

Enable the option only if it suits your presentation. Then rehearse the same actions you will perform in the meeting: opening a file, changing apps, displaying a dialog, and returning to the original document. A picker preview is the beginning of that check, not its conclusion.

For a deck, native PowerPoint sharing is often enough. Do not add ScreenK9 merely to hide PowerPoint speaker notes: its ordinary-app rules cannot approve the slide-show window while independently excluding another PowerPoint window.

When one filtered audience window helps

Consider a customer walkthrough that goes from a work browser to an editor and then to a terminal. Personal messaging remains open because you still need it between calls. Sharing the physical display makes that entire desktop the presentation surface.

ScreenK9 creates a separate ordinary macOS window containing filtered capture. Teams shares that window just as it would share another application window. There is no meeting-traffic interception or special Teams integration.

Set it up before the audience joins:

1. Write down the apps required for the walkthrough. Use demo data inside them.
2. Create an Allow only profile in ScreenK9 and approve that short list.
3. For Chrome, use the companion extension to classify the intended profiles as Work. Keep personal profiles outside the approved capture.
4. Choose the system-surface visibility settings your demo needs, then start capture.
5. Inspect ScreenK9 — Audience View while switching through the complete workflow.
6. In Teams, choose Share, select ScreenK9 — Audience View as a window, and verify it from a second device or test participant.

The general guide to sharing several Mac apps explains when a native selection remains simpler. For browser-heavy work, prepare the Chrome profile boundary before recording your rehearsal.

Know exactly what the filter can exclude

ScreenK9’s ordinary-app selection is at the application level. Approving an editor does not make its second project private. Approving a terminal does not conceal credentials printed inside it. Close private documents within approved apps, use test accounts, and check newly opened windows.

Chrome has a separate local classification mechanism. Personal, unclassified, stale, or ambiguous profile matches are hidden. Its title matching is not cryptographic identity, so the correct response to uncertainty is exclusion rather than a claim that every browser window has been securely identified.

Manual redaction regions can cover a stable area in the audience output. They do not follow secrets around the screen, read text with OCR, or automatically detect sensitive information. Moving or resizing content requires checking those regions again.

Most importantly, choosing the physical Screen or desktop in Teams bypasses ScreenK9. The filter applies to the audience window you selected, not to other capture sources in the meeting software.

Keep audio and permissions separate

Apple’s screen and audio recording controls govern which apps can capture those surfaces. Check the permission for Teams, or for the browser when using Teams on the web, and for ScreenK9 when you use filtered capture. Follow the current macOS prompt rather than disabling unrelated privacy controls.

ScreenK9’s capture configuration does not capture audio. Your microphone and shared computer sound remain decisions in Teams. A hidden messaging app can still make an audible notification, so test with sound as well as picture. The notification preparation guide covers the native Mac controls.

If a share fails, first confirm permissions, the selected source, and the current Teams and macOS support guidance. ScreenK9 is not a fix for every Teams performance problem, docking-station issue, or missing share permission.

Rehearse the transition most likely to go wrong

Make a short private test call and watch the receiver’s view while you:

• Move through each approved work app.
• Bring a private app to the foreground.
• Switch between Work and Personal Chrome profiles.
• Open another document inside an approved ordinary app.
• Trigger a harmless test notification and listen for its sound.
• Stop and restart sharing, checking the selected source again.

If the receiver sees content that should be private, stop sharing and change the source or preparation. Do not depend on remembering to hide it during a live explanation.

ScreenK9’s current Mac download and requirements are the place to start if that rehearsal demonstrates a real need for an audience window. Keep the final rule specific: approve the required apps, prepare their contents, and verify the window Teams is transmitting.

Sources checked

• Microsoft Support: Present content in Microsoft Teams meetings
• Microsoft: Native macOS screen sharing in Teams meetings
• Apple Support: Screen and system audio recording permissions
• Mike Tholfsen: Teams updates, including sharing UI at 1:05

Documentation and ScreenK9’s product boundaries were checked on September 11, 2026. The video illustrates the sharing-panel update; it does not demonstrate a ScreenK9 integration.