 Ali says, I'm the admin for a non-profit teams tenant and I have a channel calendar, another calendar question, set up in the general channel of our team. When I create a meeting and send to two specific members of the team, the invitation appears to be sent in addition to the whole team. Is there a way to stop this? Should I move the calendar to a different channel? We are not integrated with Microsoft Outlook currently as our emails hosted through our ISP. I love a calendar question. Yeah, we get so many calendar questions, there should be a book. Anyway, the issue is the channel, if you're having a conversation in a channel, the way that teams permissions are set up, if you're a member of a channel, you will see all communications in that channel. One of the benefits of having a meeting in a channel is we've tried to do this in migrate meetings, recruiting meetings for project teams and initiatives into the respective channels, because all the history, all the recordings, all the conversations in context, all remain in the channel, that's the purpose. I don't know about the email portion of it, but if any announcement or any change, any new meeting in that channel, all members of the channel would then see that, have access to that. I think that it to understand, if you even take it back a little bit and knowing that a team is made up of a group, and that group is based on a security group of people of which they're all invited in. When you go and add in the calendar that actually it comes as part of that team, it naturally and inherently gives permissions to everyone within it. Now, if you were sending it from your own personal outlook, then you're talking about you as an individual selling out a calendar invite. But when you're using the channel that actually comes with teams, it inherits that that's the group of people. So the moment you create something in that calendar, it will naturally and inherently then give it to everyone within it when you put it into a channel invite, because it goes based on the security group of people that are included as part of the team. Now, because we've got that, then what happens is you're trying to send it to two people, but it doesn't matter because if they're part of that group, they're getting it anyway. You don't need to send it to the two people. It's only if you were sending it to others outside of the team, which you then include the two people, because it naturally includes everyone within it. So I think that comes from that bit of confusion around, what does a team calendar actually do when you're dealing with Microsoft Teams, and how does it include everyone? Because it's not an exclusionary type thing. I think that's where they're trying to do the whole I just want these two people. It's not based on that when it comes to a channel calendar. Which is one of the reasons why I think it's so misunderstood of channel versus chat or individual. Yeah, it's a team calendar and not a channel calendar. Right. I think people have defaulted to using chats and one-on-one or through email not associated with the channel for meetings. That's just they defaulted to that and then they're having to invite everybody every time. Yes. The whole purpose. I mean, it's the beauty of the model of a channel is that we've done the permissions. These are all the people that need to be involved in this project. So anything we do within that channel will be seen by anyone that we've set up to have access to that channel. By design. So if I want to go, if I'm part of a project team or a number of different teams with channels and all of those conversations going on, but I just want the three of us in a conversation or do a quick video, a chat, something, a meeting, then I would do it through chat or I would do it through Outlook just with the meeting invite that's unassociated with any team. Yeah. So I think that that's where that confusion, it's like the difference between the me, the we, the us, and the them in a business and trying to know what sits in the me space today when it comes to your Outlook calendar and your chat, the one-on-one, and things and information sits in your one drive. It sits in your personal space compared to having a team that you bring together. And then we get into the we space. So it sits in SharePoint and it sits, do you know, so you then get. We need to stress, we. Yeah, there we, so, you know, so it comes down to understanding that difference. Wee! The me and the we. So, you know, I think that, you know, it's great to have the team calendar. It's not a channel calendar and I think that's where that word in confusion comes in. It's a team calendar, not a channel, but it's been added to your channel probably as a link. And I think the hard part would then be if you're wanting to have it sitting in the team and you're using an open calendar and you want everyone to see it, but you don't want everyone to be included, then that's not the right place for you to be inviting from ultimately. Right. I mean, there's a lot of other ways of getting into the calendar side. Like, okay, if you want to, for your example, if you want to have a calendar that you want to share within a channel or different locations, multiple locations, you can go create that separately, like as a, your SharePoint site, for example, and add it in as a tab so that it's viewable within that project. I mean, there's a lot of ways you could do it to untether it from the actual location, the team or the channel. So it just depends on what you want to do, but again, calendars, I wish there were easy answers for calendar questions. There are so many different nuanced calendar types and places and rules around them. And again, there's, we were joking because we're working on an e-book on that topic. So someday it'll be done. Great plan. One day. Mm-hmm. Yeah, one day. Mm-hmm.