 Jordan has a question. Is it possible to insert a link to one file that is in another team? Can the link be made as a tab? Yes, it can. All right. Thank you for watching. Yeah, that's it. I think the main thing is you can insert links but then it's having the permission to the file for the individual. You've just got to make sure that when you do a link, you then go change the permissions and that's the link that you use. So you've got to change the permissions first and foremost. Once you've got the link to that file with the right people because it embeds effectively their name and coding in as to who they are, and then you put that over into the other team. You can add it as a tab, you can put it into chat, you can whatever it is you want to do, you can send a via email. It's just got to have the right people with the right permissions ultimately. Yeah. So something else to think of, if there's the potential of multiple links, you don't want a lengthy tab scenario. So then think about creating a page and adding those links to that page. Yeah. It depends on how you're using it. Yeah. Right. There's a ton of files. So there's a ton of files, create a folder, put them. I mean, I don't necessarily love doing this, but you can go to SharePoint, you can go into Advanced Permissions, you can break the inherited permissions, but make sure that you know that that folder is your broken inherited folder. Here's an example of exactly that. And you're shaking your head, no, Stacy, but this is the scenario. So when I got into SharePoint, one of my main things I was doing out in the industry was building project management organizations, PMOs for companies. I would go in, clean up their hot mess of project management, project management, and structure all that, give them rigor around their project activities. That's where I discovered SharePoint and it's very earliest, the 2003 era. But that concept in Teams works beautifully, of going and having that, yes, a broken permissions, it's not the Teams related, but you can create a PMO SharePoint site that maybe has all of your templates and have that as maybe even designed as part of your provisioning process to automatically in any project related teams that are created to include a tab that points back to that shared PMO folder with all the templates. So that scenario, and I've done that for a couple organizations, that works well in that scenario. I'm fine with document libraries and lists when breaking permissions, okay? You don't go any lower, period. Not to a specific file? Correct, never at a file area because then you're just adding extra administration for the admins. You're asking for issues when you get audited. You'll never pass an audit, just I'm gonna throw that out there because no one is gonna document well enough to identify all that. So you're gonna fail an audit. So document library, furthest you should go break permissions ever. I'm just laying it out, done, right there. So this is another one of those Jordan is like, you can, the question is, should you? Should you? Yeah, I always say that if you are going to, you literally have just one folder and that folder is the only folder that's actually it's broken inheritance. And then anything that's in, you know that it's based on the individual within there and you contain it and you know that that's the folder that's in because if they do it to the file level and I tell them all the time, you go down and you break that file and that file and that file you'll never know which one in the team that someone has access to or not has access to becomes a nightmare. Except with third party tools that are able to track that, but out of the box, it's painful, yeah. So people tell me all the time, like, they're like, but I have certain documents that only these people need to see. And I'm like, well, then create that document library called confidential or execs only or whatever and move that content there. Don't break it within the masses. If they, if in that whole entire document library, they're only accessing two documents, that is not conducive to what you're trying to do. You're just asking for trouble, asking for it. All I'm saying is, I agree with everything you've said, but there are third party tools that allow you to track all that. No, it's still like, and even they'll tell you don't do it. Like, but there are tools that can give you a view very quickly of give me a view in this tenant of every document with broken non-standard permissions and who has access and all the details around that. Like, you can do that. But the problem is with it though, Christian, the manager doesn't actually know or the individual when they start inside an organization. They never know which one it is that they're supposed to have access to and which document. The help desk is supposed to know what to do? I mean, come on. I just, like I said, you can do it, but you shouldn't do it yet. Yeah. We can go on for hours about this, but yeah. I know, exactly. But ultimately, back to the original question. Yes, just create the link with the right people, extending, giving them permissions and then post that link into your, wherever it is that you need it to go. I love when people add a tab. Yeah, I love when people add the tab and they don't extend the permissions and then, well, it's there. I can open it. I can put it there. Nobody else can open it. Yeah, you can get to it, yeah. But yeah, get a little bit else to be able to get to it, right? Yeah, yeah. Yeah, that's it. I love these conversations.