 Hermann says, hello everyone, I would like to know if it is possible to make the files that I have in SharePoint or OneDrive be shared to a specific user automatically, depending on the name of that file, that is, if I have a file called Jhon, only Jhon can see it, they do the same for, I know it's probably supposed to be John, but do the same for 1000s, but that's not how he spelled it, so I'm pronouncing it as he spelled it. And do the same for 1000s, the files automatically, thank you very much for the help. Yeah, not much help, but the convention-based naming, I don't believe you're going to find any help from that in the platform. It's something that depending on where the emails get generated from, excuse not the emails, I'm sorry, but the files, depending on the user, you might be able to write some sort of add-in that runs somewhere to do that for you, but you're not going to get support from the platform. Well, that is a good question, which we don't ask often enough, I think. And I would suggest that I would look into it, but I bet you could do this with PowerShell, I bet you could actually PowerShell it with OneDrive and have it actually scripted outwards looking for regex strings of the files, the file names, and then changing the permissions on the share of the file. It would be quite a bit of work, but if you wanted to pay somebody to do it, I'm sure there's a way back there that would do it. We might know somebody. Yeah, well, I have an easier solution, but it may not meet what they need, but create a folder in your OneDrive that you share with John and add the files to, or Jehan, and add the files to that folder and you will automatically have access to those, but I don't recommend doing that in a SharePoint library with the folders, because that's a bad plan. They should be library level permissions, not folders. I think one of the things he's getting to here, though, is that he wants it to be auto magic, right? So if he drops a file and it's a specific file name, share it with Jehan. This is the one I've done. Remember the old document was a template in SharePoint where you could basically have a document repository and you could just drag and drop it in and then basically create rules that would automatically stick them in the right place. The Content Organizer, thank you. Yeah, the bane of my existence. Because stuff will get purgatory because people wouldn't fill out the attributes they needed to in order for it to work. And the reason I say that is exactly that reason. That's why that's a bad idea. It's definitely better to architecture content, put it in the right place. And then, for example, like, yeah, I would agree with you, Sherry, set permissions on a library folder if you have to, but at a library level, then just have each person have their own library. I mean, and just drop it in there. There's files. Have a nice life. Exactly. Yeah, there's no, I mean, well, it goes back to kind of the content that we're going to answer a comment. But if you have it tagged properly, if you have, if this is something that you want to ongoing, you've got a reasonably small team that you want to do this. But tag it in a way, as long as it's not a security issue, if everyone has access to all that content out in that site, because that's a key question there, do they have the right permissions for you to be able to move it across? You can be breaking things, breaking policies by sharing things that shouldn't be shared with individuals to don't have access to the right areas. So limited access. Hell, yes. Yeah. And if it's just a preference thing, if it's just, I want Jhon to see all of Jhon's file, you could just use a view. I mean, essentially could have a library. Like you said, if it's tagged correctly, that you can do, you can basically tag it so that it will show up in a view for only his files, which is a lot easier. Yeah. The details. Oh, I love the me view. Yep. Or what you could do is you could go and find the document IDs for every single one of those items and send an email and with a list with all of those things, maybe bulleted, maybe numbered, go crazy with your email. What happened to you? Where did that come from? Christian is not being helpful. That's your holiday gift this year. Christian has been possessed by somebody we don't know. The demons from file hell, I think. We've all lived through that. That's an anti productivity thing. Yes, it is. I'm going to tell you what man, I make a lot of, I have a lot of worker and unique permissions management. I do a lot of permission stuff and I lead so many people away from unique permissions on a regular basis. Look at this lovely team. You can be an owner. Remember, that's it. That's all you need. You don't need anything else. Yeah. But can I do this? No, you cannot. Yeah, the minute they go down that, you know, I had been working with a group and they wanted to craft their own permission levels. They wanted edit without delete and all these sorts of things. And I said, it's yours. You can do what you want with it. I'm out. That should be out of the box. Yeah, just that one though. Yeah. Just because you can contribute doesn't mean you should be able to delete. Agreed. Well, that's why if you have very specialized requirements for that's why it's different scenarios like though, the whole virtual data room, the VDR solutions where it's very specific around, you know, reorganizations, it's about mergers and acquisitions where you have highly sensitive information and keeping people separate in areas and sharing sensitive information between the different groups. Like, that's not this scenario. This is, I think this is where you can really push back in an org and say, keep things flat, keep things simple. Yeah.