Teams shares only the window inside its highlighted border, and Docognito hides ChatGPT or Claude as a document there. Turn the disguise on before you click share, choose window sharing rather than your whole screen, and the stream carries nothing but a page that reads as ordinary paperwork. Notifications and other apps outside the border can still slip into view.
What Teams actually puts inside the border
When you choose Share content in a Teams call, Teams asks which window or screen to send. Pick a single application window and Teams draws a highlighted border around it, then streams only the pixels inside that border for as long as the share stays live. Microsoft's own support page describes that outline only as highlighted and does not name a colour, though it is commonly seen as red on screen, a detail worth knowing rather than treating as official. Everything else on your monitor, your email client, your other browser tabs, your desktop background, stays off the call entirely.
That is different from choosing your entire screen, which streams the whole monitor regardless of what sits on top of it. Window sharing is the narrower option, and it is the one that makes a disguise worth setting up in the first place, because there is a defined boundary for the disguise to sit inside.
The border updates in real time
Teams keeps that border visible on your own screen for as long as you share, and it reflects whatever the window shows in real time. Disguise ChatGPT or Claude as a document before you share, and the border simply frames a document. Switch tabs inside that window mid call, and whatever loads next is what streams next, with no delay and no second confirmation from Teams.
That immediacy runs both ways. There is no gap between changing what sits on screen and what your audience sees, which is exactly why turning the disguise on before you share is the one moment where you hold a real advantage over the stream.
What still gets exposed outside the window
A few things sit outside the border no matter how carefully you choose what to share. Chat and call notifications from Teams itself can appear as a banner across the top of the screen, and depending on your operating system settings, other apps can post system notifications the same way. Those banners come from the operating system, not from the shared page, so nothing inside the browser controls them.
A second monitor is the other gap. If Teams shares a window on your primary display while a message thread sits open on a second monitor, that second screen never enters the stream unless you deliberately choose to share it too.
Why a shared window shows your tab strip
Choosing your Chrome window rather than your entire screen sends everything belonging to that one window, and that includes the tab strip running along the top of it. Teams does not stream the live content of your other tabs, only the page you have active, but the title of each other tab stays readable in that strip for as long as you share.
This is one more reason the tab title matters beyond hiding a chat window on its own. the browser tab title, so a colleague glancing specifically at what else you have open finds a row of ordinary sounding tab names rather than one that reads ChatGPT or Claude next to whatever else is open.
Switching from a window to your entire screen removes every boundary at once
The moment you change the share from one window to your whole desktop, or to a second monitor, the disguise is still active on the page but everything around it becomes visible too, other tabs, your file system, any other open application. the address bar, which still reads claude.ai or chatgpt.com regardless of which mode you choose.
Set the disguise up before the call
Turn the disguise on first
Open the tab, install Docognito if it is not already added, and toggle it on before you join the meeting rather than mid call.
Share the window, not the screen
When Teams asks what to share, choose the single browser window, not your entire screen or a second display.
Mute notifications for the call
Turn on focus assist or do not disturb before you share, so a banner from another app cannot cross the border mid conversation.
Where this genuinely stops working
None of this changes what sits in the browser's own chrome. the address bar, which still reads claude.ai or chatgpt.com for the whole time the tab stays open, share or no share, because the disguise redraws the page content and leaves the browser frame alone. Window sharing in Teams already crops that frame out of the stream on its own, which is why the two work well together: Teams removes the chrome from view, and Docognito changes what is left inside it.
Full desktop sharing is the switch that undoes everything
Share a single window in Teams, never your entire screen, and turn Docognito on before you click share rather than during the call. Those two choices cover what each piece of software actually controls. Notifications, a second monitor and the moment anyone switches to full desktop sharing stay yours to manage separately, because nothing running inside a browser tab can reach any of them. Shift and Escape, which both hides the disguise and brings it back whenever the real page needs to come back for a second.