This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I like to keep my teams small so previously, with 80% zoom and the teams window as small as possible, I realized that the chat panel would auto hide and it would show only when I hover my mouse over Chat.
However, recently chat panel would stay open so it is taking up quite a space in my small teams window. Does anyone know how to make this chat panel auto hide itself?
Only way to make it hide is if I make the zoom 115% which is ridiculously large for me...
Conversations involving multiple participants, allowing collaboration and information sharing in Teams
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Ok, it only lasted a couple of days. We need a permanent solution to this issue.
I totally agree, they already made the window where you can go small, so people walking by can easily read your converstaions. And now with not being able to hide the chat names is insane. A small place to type, and who wants to make it a full screen?? It already takes up so much of my screen as it is. I hope this gets fixed and soon. Would rather just delete it and use email.
I just adore when Microsoft messes up and calls it a feature. It is not a feature, development messed up. Auto hide is an important feature for many people forced to use your products at work.
This worked for me without needing to Reset. Repair was enough. I did sign-out and back in to restart the app. What a relief!
Until they update the teams again and fix this. the only work around I found is going back to the old version -