Thank you so much for this feedback. I was actually sitting with a user yesterday who was struggling to add users to a channel because she was typing in names one by one, which is a normal inclination. I showed her that she can put any distribution list into the field (for example, email@example.com) and it would invite everyone who is on that email address. Try it out and let me know if you have any more questions. I’ve also routed this feedback to design so they can implement a sign or something to show people that they can do this.
Thank you for helping us make Teams awesome!
Thank you for your feedback. We’re happy to announce that an option to choose between Windows 10 Native Notifications and Teams Notifications is included in our Dec 2020 Public Preview pack, and will be available to users who opt into Public Preview.
You can learn more about the new Microsoft Teams Public Preview program here: https://aka.ms/TeamsPublicPreview, and Teams administrators can find documentation to manage which users will see the Public Preview option here: https://aka.ms/TeamsPublicPreviewAdmin
An error occurred while saving the commentJohnRidge commented
Integration with Windows10 notification centre or not, an ability to customise the message seems vital.
For example, both MS Teams and MS Planner already have much more context data that could be used to create a much better and more tightly worded alert messages.
The following slightly unhelpful email subject lines were Observed (O) and relate to a single MS Team site “TeamProject” which includes MS Planner.
• O1> Message from MS Teams when another team member is @mentioned
o “John mentioned you in TeamProject”
• O2> Message from MS Planner when a task is coming up
o “You have upcoming tasks due.”
• O3> Message from MS Planner when a task is over due
o “You have late tasks!”
Basic initial Suggestions (S) for the subject line would be :
• S1> both sender and the receiver names should be qualified as full names
o TeamProject >[SenderName] mentioned [ReceiverName]
o Rational1 : there can be more than one person with the first name
o Rational2 : possibly a different account holder may be working as the receiver
• S2> MS Planner should provide more of the available context data
o TeamProject >[task name]>task IMMINENT 2 days
o TeamProject >[task name]>task DUE
o TeamProject >[task name]>task LATE 3 days
o Rational1: if the project has already created various due dates, the system should be able to provide the same sort of prompts, perhaps configurable, as we see in MS Calendar
o Rational2: The project name and task name uniquely define what the subject is
• S3> do away with the exclamation mark
o Rational1: relative importance of lateness is for the team to decide
• S4> provide facility for user custom logic defined subject lines
o tightly constructed subject lines facilitate rule based processing
7 votes2 comments · Public » Apps, Connectors, Messaging Extensions · Flag idea as inappropriate… · Admin →