 So Benico says, is there a way to change the URL address once a SharePoint file is restored? Some users use Office Online and every time a file is removed and then put back restored with the same name, you have to send the new link to all users who use it online. I actually just tested this out with my team because this came up and somebody was asking about this. And here's what happens. It's very confusing. What happens when you put back a document, it overwrites the original document. That's first of all, you know, it should say this document already exists. Do you want to replace it? Yes. When you click the Share link, it will give you a different unique URL, which is interesting, but the first link still works. So what you have to do is have your link, maintain that link, and not click the Share link again, but use the original link and it will continue to work when you restore it. But it will give you a new link every single time you upload that document and you click on Share again, which is insane. I don't know why it does it, but it does it. In addition, I did put a note in there. So there is something called unique doc IDs. And if you set up unique doc IDs and enable it on the site collection that you're working with, it will assign a unique ID to every single document. It's not data, so not lists, but libraries. It will assign a unique ID. And as long as it stays within the site, you can move it folders, you can move it libraries, as long as it stays in the same site, that link will stay good for the life of that particular file, whether you replace it, whether you rename it, whether you move it, it will always stay the same. So the two things I would say is, number one, know that that first link will still work, even if it gives you a different one. And second of all, enable unique IDs because, or enable unique doc IDs because it does make your life a lot easier. Sharon, on that, you know, in the way that I read it more is, and you're absolutely correct, because a lot of people don't realize that SharePoint has got like follow me links. So we'll continue to keep working. But if in this instance, it looks like what he's saying is, they've removed the file, like they've deleted the file, and they've restored the file back in. So, and if you've done something like a delete and a restore, then no, there's nothing you can do in regards to edit the link and make it the same again. It is done. The system doesn't know. It's a different document. Yes, you've actually completely removed it. It's now a whole new document, and you're done, and you're going to have to generate a whole new link. It's as simple as that. But if you do any one of the other behaviors, you know, SharePoint and OneDrive and that, all great at doing, you know, you're moving it around, it'll just follow it, whether it's in, you know, you're doing it in teams, because you got SharePoint in the back end, whether you're doing it physically from SharePoint or OneDrive, no problems. But if you go delete a file, you're done. So simple as that. Yeah. Yeah, I'm trying to think of a scenario. Besides, I mean, like deleted it. Oh, no, we needed that. I mean, going through that, that restore process, it usually went out, we, you know, we selected too many files and deleted them, and the one we needed, we just deleted, go back in and restore that. Is there another scenario where this is like, this has happened, it's commonly done? Because again, the answer is I think exactly what you said, Kirstie, is if it's deleted, you add it back in, it's looking at it as a new document. The only other scenario I can think about is if maybe there's a workflow process behind the scenes where you're changing, like doing something with the file, so maybe you're deleting it out of one place and then restoring it back to somewhere else, or you're moving that file in some way. So like maybe, so sometimes people will do this, it's not the right answer, but they do it, is that in a workflow, they will actually use that feature to hide or remove something and then bring it back to life so that it's because they don't use it permissions correctly, or they don't do it a different way. I've actually seen people use that as a workaround to get it out of the library and then put it back in a certain time frame. So I mean, I've seen people use that for the wrong reasons, but in general, yeah, typically it's because either somebody didn't realize that they deleted the wrong thing or somebody accidentally deleted a whole folder or library or something. Yeah, it's training. Training, really training. Why are they deleting in the first place? Are they thinking it's based on like last, like other ways? Do they understand that you got file versioning and that they could actually go back or like back and forward in file versioning? Often they don't understand the nature of what's going on with the file and they might delete. I mean, there could be the accidental delete, like you said, Christian, but there's also a lot of times we go, tell people don't delete it. What you could do is even just create an archive folder that's within like old file archive and just move it into that folder instead of deleting it. And then you kind of retain it and it's still there if you really need to move it rather than delete it. And then you can go back later on into the archive folder and go, is there any of these files that we still actually need? And then go, no, we're definitely not. We're six months past the project or whatever and go delete those older archive files. I just say, I don't like to delete things unless I've really got a reason to and then I'll do a big cleanup. Yeah, I wonder if this is an admin who had a large library and somebody was just like getting over zealous about cleaning up and now the admin is stuck updating all the links. Potentially. Is there a faster way to do this? Yeah. Yeah, create a brand new permission that's called no delete. Yeah, just create a SharePoint permission level that is contribute no delete and remove delete from the equation. And then you don't have to deal with that. True. True. I mean, so many organizations I'm dealing with, especially across Gov, 20 years they've got to keep their information. So nothing, even if you delete a team, it still is maintained kind of in the back end. And therefore you can't regenerate or do anything you can restore that particular one. But there doesn't delete a thing everywhere. So it kind of go, what teams have you got? Oh, geez. There's hundreds here. None are being used. Created and deleted. Yep. So know why start from the right stuff in the first place. I make sure you want to get into the storage business, doesn't it? No, no, just sounds like just pure pay down. Thanks very much, but no.