e

My feedback

  1. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Public » Presence  ·  Flag idea as inappropriate…  ·  Admin →
    e supported this idea  · 
  2. 68 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    e commented  · 

    I just...I don't see how simple usability things like were missed (or I guess just flat out ignored to shove it onto people as fast as possible?). Teams is so painfully clunky and it's the cumulative little clunk like this that makes it that way. UX is not a new concept...why is this kind of garbage allowed to make it past QA?

  3. 259 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    71 comments  ·  Public » Settings  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    e commented  · 

    This is not only a usability issue, but a privacy and a security issue. I don't want some rando reading my last chat because Teams happens to open to it as they walk up. What if I'm discussing an infosec issue or proprietary company info and that rando is a user/client/vendor? What, now I have to manually delete conversations constantly because Teams wants to tell all my secrets? Teams is a mess and this is just one example of why I have been resistant to move away from S4B.

    e supported this idea  · 

Feedback and Knowledge Base