Chamo

My feedback

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

    We’ll send you updates on this idea

    under review  ·  35 comments  ·  Public » Meetings  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  2. 64 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Public » Meetings  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  3. 350 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    50 comments  ·  Public » Meetings  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  4. 14 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Public » IT Pro - Controls and Knobs  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo shared this idea  · 
  5. 702 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    67 comments  ·  Public » Tabs  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Warren responded

    This item is still in the works.

    Also, thank you for the additional feedback. I will circle back to the feature team and provide a new update soon.
    -Warren

    Chamo commented  · 

    I agree too!

    Here is my use case, which I suspect others are facing as well:

    * I don't want our users to save their files in lots of different SharePoint sites, which makes it harder to find things. I want them to save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)

    * We have already created and used for years an awesome SharePoint document library with a taxonomy managed metadata and views everyone loves

    * Therefore, in Teams, I want users to only be able to upload files to our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)

    Here are the problems I faced that Microsoft could fix, and the workarounds I did to get it to (kind of) work the way I wanted it to -- you're welcome, Microsoft Team users :)

    Problem 1: When I add our existing SharePoint document library in a tab, it does not include the fields and metadata I need.

    Workaround 1: Create a new tab not as a SharePoint site, but instead add it as an ordinary website, and put in the URL of your document library. (The UI is not ideal, since there is a left hand nav bar in teams I have to do more scrolling to the right to see all of the SharePoint Document Library view, but at least we can access our views and metadata.)

    Problem 2a: I can't hide the default File tab. This means that, instead of going to the new tab I created above to get to our existing SharePoint site, some users will see the files tab and upload file to it, leaving a mess ("wait, did I add the file to my new Team file area or to my existing SharePoint document library?")

    Problem 2b: I can't change it so that, when you click on the default Microsoft Teams File tab and upload a file, it actually gets saved in our existing SharePoint Document Library instead of the automatically created new Microsoft Team site.

    Workaround 2: In the Team File area, I add a link that goes to the URL of my existing SharePoint document library. I name the link "Use this link to the place to save files." I think click on the top nav bar item Open in SharePoint, and from there I clicked on Site Permissions, and set Site Members' permissions to Read-Only.

    Result: Users save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically when I created the team, and users have full access to the taxonomy, metadata and views they already know and love from their existing SharePoint site.

    Chamo supported this idea  · 
  6. 75 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  7. 123 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Public » IT Pro - Controls and Knobs  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  8. 909 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    86 comments  ·  Public » Planner  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    This request is still in the backlog, no new details are available at this time.

    I’ll continue to watch for new information from the feature team to share with you.
    -Warren

    Chamo supported this idea  · 
  9. 105 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Public » Bots  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  10. 46 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Chamo supported this idea  · 
  11. 1,358 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    183 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  12. 59 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  13. 138 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  Public » IT Pro - Controls and Knobs  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  14. 69 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Public » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  15. 98 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Public » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  Warren responded

    This feature request has been declined.

    Currently if you have the Teams app set to run in the background upon clicking the “X” in the upper right, the app stays active only in the system tray. If you receive chat messages, it still remains in the SysTray.

    However, if you get an @mention, the focus pulls it to the Taskbar. This is by design since you are getting directly mentioned and some action is typically expected. This is a key design element which the team does not wish to deviate from.

    We appreciate the suggestion but will respectively decline it at this time.

    Thank you for the feedback and suggestion.
    -Warren

    Chamo supported this idea  · 
  16. 280 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  Public » Planner  ·  Flag idea as inappropriate…  ·  Admin →
    Chamo supported this idea  · 
  17. 70 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Public » Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    we have this!  ·  Warren responded

    When you start a meeting and click the share button you are presented the option to share your whole desktop or choose a specific application to share.

    -Warren

    Chamo supported this idea  · 
  18. 295 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    Thank you all very much for the great response. The survey is now closed. The feature team will be reviewing all the data that was gathered and responded based on the findings.
    Again, thank you for helping us make Microsoft Teams the best it can be.
    -Warren

    Chamo supported this idea  · 
  19. 1,073 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    104 comments  ·  Public » Files  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Warren responded

    This feature request is still in the works. No additional updates are available at this time. I’ll keep you posted as I hear more.

    -Warren

    Chamo supported this idea  · 
  20. 3,326 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    298 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    This feature request is working its way through the backlog queue. No new details are available yet.

    -Warren

    Chamo commented  · 

    Here is my use case, which I suspect others are facing as well, along with my current work-around:

    * I don't want our users to save their files in lots of different SharePoint sites, which makes it harder to find things. I want them to save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)

    * We have already created and used for years an awesome SharePoint document library with a taxonomy managed metadata and views everyone loves

    * Therefore, in Teams, I want users to only be able to upload files to our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)

    Here are the problems I faced that Microsoft could fix, and the workarounds I did to get it to (kind of) work the way I wanted it to -- you're welcome, Microsoft Team users :)

    Problem 1: When I add our existing SharePoint document library in a tab, it does not include the fields and metadata I need.

    Workaround 1: Create a new tab not as a SharePoint site, but instead add it as an ordinary website, and put in the URL of your document library. (The UI is not ideal, since there is a left hand nav bar in teams I have to do more scrolling to the right to see all of the SharePoint Document Library view, but at least we can access our views and metadata.)

    Problem 2a: I can't hide the default File tab. This means that, instead of going to the new tab I created above to get to our existing SharePoint site, some users will see the files tab and upload file to it, leaving a mess ("wait, did I add the file to my new Team file area or to my existing SharePoint document library?")

    Problem 2b: I can't change it so that, when you click on the default Microsoft Teams File tab and upload a file, it actually gets saved in our existing SharePoint Document Library instead of the automatically created new Microsoft Team site.

    Workaround 2: In the Team File area, I add a link that goes to the URL of my existing SharePoint document library. I name the link "Use this link to the place to save files." I think click on the top nav bar item Open in SharePoint, and from there I clicked on Site Permissions, and set Site Members' permissions to Read-Only.

    Result: Users save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically when I created the team, and users have full access to the taxonomy, metadata and views they already know and love from their existing SharePoint site.

    Chamo commented  · 

    I think I have a similar use case as others who commented on this, so I thought I would share my current workarounds (far from ideal, but a temporary solution until Microsoft completes this feature request.

    Use case:
    * I don't want our users to save their files in lots of different SharePoint sites, which makes it harder to find things. I want them to save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)

    * We have already created and used for years an awesome SharePoint document library with a taxonomy managed metadata and views everyone loves

    * Therefore, in Teams, I want users to only be able to upload files to our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)

    Here are the problems I faced that Microsoft could fix, and the workarounds I did to get it to (kind of) work the way I wanted it to -- you're welcome, Microsoft Team users :)

    Problem 1: When I add our existing SharePoint document library in a tab, it does not include the fields and metadata I need.

    Workaround 1: Create a new tab not as a SharePoint site, but instead add it as an ordinary website, and put in the URL of your document library. (The UI is not ideal, since there is a left hand nav bar in teams I have to do more scrolling to the right to see all of the SharePoint Document Library view, but at least we can access our views and metadata.)

    Problem 2a: I can't hide the default File tab. This means that, instead of going to the new tab I created above to get to our existing SharePoint site, some users will see the files tab and upload file to it, leaving a mess ("wait, did I add the file to my new Team file area or to my existing SharePoint document library?")

    Problem 2b: I can't change it so that, when you click on the default Microsoft Teams File tab and upload a file, it actually gets saved in our existing SharePoint Document Library instead of the automatically created new Microsoft Team site.

    Workaround 2: In the Team File area, I add a link that goes to the URL of my existing SharePoint document library. I name the link "Use this link to the place to save files." I think click on the top nav bar item Open in SharePoint, and from there I clicked on Site Permissions, and set Site Members' permissions to Read-Only.

    Result: Users save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically when I created the team, and users have full access to the taxonomy, metadata and views they already know and love from their existing SharePoint site.

    Chamo commented  · 

    Here is my use case, which I suspect others are facing as well:

    * I don't want our users to save their files in lots of different SharePoint sites, which makes it harder to find things. I want them to save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)

    * We have already created and used for years an awesome SharePoint document library with a taxonomy managed metadata and views everyone loves

    * Therefore, in Teams, I want users to only be able to upload files to our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)

    Here are the problems I faced that Microsoft could fix, and the workarounds I did to get it to (kind of) work the way I wanted it to -- you're welcome, Microsoft Team users :)

    Problem 1: When I add our existing SharePoint document library in a tab, it does not include the fields and metadata I need.

    Workaround 1: Create a new tab not as a SharePoint site, but instead add it as an ordinary website, and put in the URL of your document library. (The UI is not ideal, since there is a left hand nav bar in teams I have to do more scrolling to the right to see all of the SharePoint Document Library view, but at least we can access our views and metadata.)

    Problem 2a: I can't hide the default File tab. This means that, instead of going to the new tab I created above to get to our existing SharePoint site, some users will see the files tab and upload file to it, leaving a mess ("wait, did I add the file to my new Team file area or to my existing SharePoint document library?")

    Problem 2b: I can't change it so that, when you click on the default Microsoft Teams File tab and upload a file, it actually gets saved in our existing SharePoint Document Library instead of the automatically created new Microsoft Team site.

    Workaround 2: In the Team File area, I add a link that goes to the URL of my existing SharePoint document library. I name the link "Use this link to the place to save files." I think click on the top nav bar item Open in SharePoint, and from there I clicked on Site Permissions, and set Site Members' permissions to Read-Only.

    Result: Users save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams), and users have full access to the taxonomy, metadata and views they already know and love from their existing SharePoint site.

    Chamo commented  · 

    Is there someone we could contact on the SharePoint team to help speed them up?

    Chamo supported this idea  · 
    Chamo commented  · 

    B, especially if combined with the point Chris Tobler made "How can I remove the default Files in Teams?" It would do no good to add sharepoint document library as a channel, if some people were saving things there and others were saving in the default team files area. We would like to replace the functionality, so it they click on the team files area it instead shows them, and save to, the sharepoint folder of your choice.

    Chamo commented  · 

    In particular, managed metadata needs to be added to teams, so you can search and tag items using an organizational term store (ideally the same one that is configured in SharePoint)

← Previous 1 3

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.