This feature request is working its way through the backlog queue. No new details are available yet.
Hi Suphatra, I don't know what is meant by a Modern Group (I can't find any information on it anywhere) but this review doesn't look like it's going to provide the flexibility needed for Teams to be used in existing environments. E.g. Link a Channel to a specific folder.
If I can't bring along my existing infrastructure, Teams remains unusable...
Scenario A - for Team and Channel - with the OPTION of creating a new Site Collection, creating a New Site within an existing Site Collection or linking to an existing site. When linking to an existing site, the OPTION to create a new folder or link to an existing folder within a Document library should also be available.
Scenario B is also available now and should remain - with the option of linking to a specific folder.
Q1: I wouldn't want to auto-generate channels from folders myself... but i can see how it might be useful as an option!
When creating a Team or Channel, and selecting an existing site i would want to be able to select a Document library and/or expand the Document Libraries and select a folder or subfolder.
Q2: 10 - We have put a lot of effort into building our Document Management topology and impressing on all users that there should be one and only one version of a document within the organisation and all documents must be in specific locations Sharepoint. We cannot deploy Teams as it does not meet our DM policy - there would be myriad locations for documents and individual documents could end up in multiple locations.
Q3: I'm using the Teams client as an end user - I'm not familiar with the coding or deployment environment for the API.
In my opinion, a general rule for Microsoft developers should be - if developing something that links, give an option for the user to select/customise. We have had the same issue in the past with CRM to SharePoint integration and the OneDrive sync client - Microsoft set the link parameters and allowed little/no customisation. As a result, although we are a Microsoft VAR, impressions of the Microsoft product suite in our organisation is neutral to negative and adoption is very low!
Close - but not close enough unfortunately! And, as a result, still unusable for us... We need to be able to link channels to folders - not sites or Libraries.
When adding a Sharepoint Tab, the dialog states that you can add a link to a Site or Folder. But you can't link to a folder.
Microsoft Dynamics CRM creates folders in a Document Library in SharePoint. Teams needs to be able to link to a folder to be compatible with other Microsoft products! A few years after it was originally requested, OneDrive for Business finally made folder level processing a possibility in the last few weeks. Hopefully it won't be years before the same functionality comes to Teams.
We have spent a lot of time designing and implementing an existing Document Management infrastructure in Office365/SharePoint Online. Teams Files approach has driven a Coach and Horses through this!
When you create a Team, a new SharePoint Site is created. When you create a Channel, a new folder is created.
But we already have the Sites and Folders we need and have been successfully using for a number of years!
In order to deploy Teams, we need the OPTION to be able to link to existing artefacts within Office365 - Teams Files to Document Libraries/Folders; Teams OneNote to OneNote Section/Page.
I presume the defaults are fine for those coming new to Office365 and Teams. Integration with and adoption by existing users needs to cater for their existing infrastructure...!
It should be as simple as adding a link to an existing Sharepoint document - it doesn't need to be in a Tab or whatever.
I get the impression that Teams, despite the links to other products, is seen as a standalone product.
How it should work: a new Channel is set up to complete a new coding Document Project/Task. Apart from identifying the team, this would involve completion of various setup docs and forms (e.g. budget, quote, approval, functional specification, technical design, etc.). These are already completed stored in Sharepoint and should not be copied into Teams. Instead, a link to a folder and/or links to individual documents hould be included in the conversation.
The Upload/attach icon in the Conversation window should allow a link to an existing Sharepoint document.
We encourage our users to place customer/project documents in defined folders within Sharepoint. Sharing of documents is always done by sharing a link to the document in the defined Sharepoint folder. This ensures that all users refer to the master version of a document and not an out of date copy.
Creating a copy of a document in each channel to which it is uploaded is valid in certain circumstances but will also lead to document sprawl.
Hi everyone, I wanted to check in on this ask because it’s died down since GA, and also because the ask is not totally clear to me.
Right now, we provide a way during the team creation process for you to select an existing Office 365 group. Are you asking to be able to do this same thing, but outside of Teams?
Do let me know!
I see this is planned. I hope it takes into account the feedback outlined in
https://microsoftteams.uservoice.com/forums/555103-public-preview/suggestions/16988692-assign-members-to-channels which (I think) is related. Assigning Members to Channels would set default notifications - with different defaults being set for the Team.
This request has been declined by the feature team.
Private channels may help with items such as this request once they are released. The Private channel topic is tracked at http://microsoftteams.uservoice.com/forums/555103/suggestions/16911079
Please note the handling of “Guest Accounts” is a separate ask and can be found at: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16911109-guest-access
The request about “Guest Access at the Channel” level is being tracked by this request: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31374577-guest-access-should-be-implemented-at-the-channel
Thank you all for the feedback.
I think this is a preferred approach to provide the same functionality outlined in "Allow different notifications options on teams and channels" feedback.
A team should have (default read only?) permission to a channel but we should be able to assign specific members to a channel.
Scenario: We have a team of 10 people with different skillsets. A variable combination of people is assigned depending on the particular project (channel) requirements.
This is still being worked upon. I hope to have more details in the next couple months.
Please know the team is actively working on this feature.
- Should be able to create Tasks in Outlook/Planner/etc and assign to a Team. Should then be able to see these under a Channel and/or in a Tab
- Should be able to include a link to Sharepoint in a Chat - this should show under the Files Tab as a Link. Note: Link should open in Sharepoint using default Webapp or Client
- Team/Channel Calendar should be available in both Teams and Outlook
Hate to be the bearer of bad news. This item has been declined. There will be no work to hide or remove the reply button.
As many people have commented, a big ask is to help improve how people distinguish between giving a reply and starting a new message.
For that the focus will be on this item. “Better visual delineation between `Reply` and `Start a new conversation`”