S. Paschall

My feedback

  1. 4,146 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    230 comments  ·  Public » Search  ·  Flag idea as inappropriate…  ·  Admin →
    S. Paschall commented  · 

    I'd love to be able to tag entire teams this way so we could group project teams by application, etc.

    S. Paschall supported this idea  · 
  2. 9,683 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1421 comments  ·  Public » Linux  ·  Flag idea as inappropriate…  ·  Admin →
    S. Paschall supported this idea  · 
    S. Paschall commented  · 

    This is an absolute requirement for us. Several of our internal devs and many of our contract resources are exclusively on Linux desktops, and we can't take full advantage of Teams until there's a native client (or Teams makes use of browser-based integrations with common X notifications frameworks).

  3. 10,211 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1182 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    S. Paschall commented  · 

    Yikes, MS. Yikes. This seems like a pretty basic architectural flub.

    Best I can tell, you don't _provide_ any tools for "moving content around," period. So we're essentially stuck with our past bad (or no longer optimal) decisions.

    As another guy said, allowing us to override permissions at the channel-level could help in some cases, but it doesn't help us organize things better as we learn the product, team structures change, etc., etc.

    Maybe if you share a little more about why the architecture makes this difficult we could provide suggestions.

    S. Paschall supported this idea  · 
    S. Paschall commented  · 

    As our organization is learning and trying to build best practices around Teams while incorporating it into our workflow, *not* being able to shift channels between teams is proving to be a real stumbling block. We need to be able to easily restructure things as we explore different organizational options. As it is, it seems we're stuck with the choice of either living with decisions we made in ignorance or losing history.

  4. 9,071 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    587 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    S. Paschall supported this idea  · 
  5. 317 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    42 comments  ·  Public » Linux  ·  Flag idea as inappropriate…  ·  Admin →
    S. Paschall commented  · 

    This would be a reasonable, temporary plug for the hole the lack of a native Linux client leaves in Teams' offering.

Feedback and Knowledge Base



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.