 Vinath asks, hi, is there any expert out there who can help me personally with a problem in teams that I'm facing for a long time? I'm uploading documents and giving it limited access, but the members aren't able to view it. I tried doing everything to solve this, but the problem still persists. In fact, I'm confused of the options. I'll be grateful if someone extends their help to me and I'm ready to pay a professional fee. Okay, the bottle up for consultation. So there, let me just get this straight, says they're uploading documents, giving it limited access, and the members aren't able to view. Well, the fact that these had limited access, the head just goes straight up on my neck. Yeah, no. It's too limited, is what you're saying. Well, it means that they've gone in to potentially remove everyone's permission if they're doing limited access and they're using teams to do it. Teams is inherently about giving permission to everyone that's inside that group, the security group, for permission. So if they're saying limited permissions, one are they internal or external? It's not saying, because that can change things as well. Because if it's not enabled for external access, then they've created a team, then trying to give some of the, yeah, so there's all sorts of, I have more questions, as we say. Right, this is one of those classic, like wish we could ask some follow up questions here. So what, where are the, what are the users? Are they internal or are they external? Is it what type of channel is it? I mean, what kind of library or do you have the content in? What kind of permissions, then what did you go and modify or potentially break within that? I mean, if you're trying to, because teams, by nature, is meant to be very flat. So I'm a member of a team, if it's a public or private channel, I have access to that. And then you can, you know, control access down to the document level. I mean, are you doing document level permissions? And breaking inherited permissions. Right. Right, yeah. But you, you can do that. You can create a SharePoint library, create very specific permissions to a sub. Like if you want to be able to share the link in or share a library, to put it in a tab within teams, to openly discuss it, but only the people that have permissions can access that. You can do that in a, in a library. And just, you know, only those named resources can have access to it. So it really depends on who they are, where, where they are, and what permissions that you've set. And the big thing to remember, yeah. As I say, the big thing to remember too for SharePoint is a lot of times when you're doing limited access, this used to be somewhat important and with teams it's more important. But if they don't have access to the site at the site container level, there's a lot of, especially there's a lot of new stuff in the modern interface that if you don't have access to the site level, you will not be able to do certain things. So I can give you access to only one document in the entire site. The only way you can access that is if you have the direct link to that document, otherwise you will never be able to get to it. So if you have access to a document, but you don't have access to the site and you're trying to access it through teams, you will not be able to get to that document because the document interfaces through the site interface. And so what's likely happening is he's giving them access to one document and then he's cutting off their access to the site and then they're not able to see it through the team. Or they're looking for it through the team when they should just look at it through the have him resend the link to the document. Yeah, well, and it's also, so a lot of times people do unique, so there's unique permissions and then there's link permission. So there's, you can have access to a document through a link, you can have access to a document through your login. And those are actually two separate things and what will happen is the URL. There's like three separate URL parameters that will happen around permissions. And if you're sharing one link as a tab in Teams, but you've given access to a different link, that link actually won't work even though you think it's the same link. So I mean, you literally have to actually look at the entire grid for that entire link. Otherwise, it may actually be the wrong link that you're sharing anyways. So permissions, like you said, permissions, I agree with you, Sherry. The many you say limited access, like the hairs on my neck stand up. You can even go higher than that. What's the organization set for the whole tenant to go, can you even do external links and you're trying to do a specific person thinking it's going out if it's an external party and it might all just be completely shut down. I said, I'm sending them a link. I've created a link thinking that they can get to it, but being external and they then can't get in. So how did they have to do authentication to come in? Are they coming in through the right authentication with the right email address? Is someone getting in and the other one's not? There's so many things around links that can get so complex fast. And until you know exact scenarios, we've got a lot we can really talk about on that one. And I just wanna clarify something that you said, Christian, because we're talking at kind of a higher level, but what I find all the time is people don't even realize, A, there's a SharePoint site behind the scenes that stores the documents in Teams. And B, you could have different libraries in that team. So there's one default one that feeds the channels, but there's actually, you can create in that SharePoint site a whole another library that has different permissions. And that might be the answer because by default that main library, everybody has collaborative. And if you start messing with that and the permissions around that, you're gonna break your team. Yeah, that was kind of my point. Like, depending on what he's done to the standard site, which you should never mess with, go create, again, if there's a need for, if there's a sub team within that larger team and you wanna create a whole another site, maybe you don't even wanna create a private channel for those conversations. You just wanna be able to share with three people as part of the larger team, a library with one or more documents that are only for the four of you to discuss, that's fine, knock yourself out and do that. But yeah, it's when you start messing with the other standard locations, that's where it gets me nervous. Don't mess with that general, don't mess with that general stuff, don't mess with that first primary library, let teams own it, that is teams is, we don't need to take it away. Yeah. Yeah, and you see that. And then they do a shared channel or a private channel and then trying to work out and then go, I need the document under the private channel to go out now. And then you start to see a whole another raft of stuff going on, not understanding what happens with the private channel and then it's a whole another SharePoint site with lockdown permissions, because it is a private. Don't talk to each other anymore. Don't talk to each other at all. Yeah, yeah. Yeah, so we start to see all sorts of complexities going on. So I don't understand why this is a problem, I just email that document to those people. I was joking people, I'm just trying to be funny. Don't do that. No. And when they can't find it Christian email it again. So it's at the top of their inbox. And can you now email again the more current version because the one that I have is from so six months ago. Yeah, that's awesome. It's funny because it's true and it hurts. But is it the final one? And I've got another final, it's today's date, but did you have one for tomorrow's date? So we're all in final envy. Final, final, final. Final, final, final.