 Okay. Nicole asks, I have a few questions. We all have questions. Don't waste time for all everyone to get their voice all be heard. Is there a way to create a link to an office file and make it force the user to make a copy of it like on Google Docs? Can I just start by saying that having assisted with a Google to M365 migration, those sharing links, the level of craziness that is the Google sharing links, that is a mess. I say this as part of my answer. The copy versus move link versus print link, they have all these pieces that can get put into the URL that just make migrations a disaster from a permissions perspective. But that's not really an answer to Nicole's question. Just commentary. It doesn't make it a struggle then when you're doing, because on the Google migrations I've done, it makes it a struggle because they expect it to act the same when they come over. I always do, if you're going to start training them, don't train them on what's the difference between the two. It's like, well, what have you got now? Because if you try to do comparison, they're either going to get something they like or something they don't like, and you live in the negative more than you live in the positive. Usually I say, if you're going to do a link, create one where it's a view only, but they're allowed to download, so then they have to create a copy. If they can't actually edit it and they can't do much else with it, then they're forced ultimately to do a download. Yeah. Well, I mean, in SharePoint, one thing is that you can provide a link to a file, but require them to check it in, check it out, or check it out. It's true. Yeah. I think there's- Go ahead, Sherry. There's two SharePoint features that offer you the option for that too. On the SharePoint library, you can select the checkbox that says, it doesn't open in the browser window, it has to open in the client. Well, that would require them to have the licensing to have the client application as well. So there's a little gotcha, but you can also save it as a template format, and then they won't be able to save it back either. That's true. That's the default setting for folks that don't know that with Word or with Office documents. If you have the original file as a template, then when somebody wants to go and utilize that and they go to save, then it would be as a standalone document. They would have to, you know, additional steps to go and save it as a new template or what have you. But that's a creative way around doing that. So when you do file save as, it'll ask you to browse, and then it'll take you back to the web location, but that's the only place you can save the file format. If you want to save it as a PDF, don't save it as a macro-enabled. Macro-enabled is bad, but if you save it as a template, you'll be fine. What is Nicole trying to do? What's the purpose of that question? That's the real question. Yeah. Well, if it's a form or something, maybe she could use forms instead. Like, there's other... But is it like a versioning question? Just making sure that if people are making edits, that they're making edits to a net new? Because this is one of the reasons why Microsoft promotes so heavily, and you have now Microsoft Loop, which even more ways of co-editing on material is that we do these things through co-editing, but you have the ability to go back when you, yeah, versioning on and to see what was there before. Well, I mean, it does concern me because creating a copy of a file, I mean, we've been talking about doing a link to a document so that you got one source of truth. So it kind of detracts from, why don't you just email an attachment then, and it's their own copy? Because I mean, you're effectively removing some of the great features of sharing a link. So, you know, it comes down to, if it was a template, then you're right. Like Shari said, then sure, you know, you want to keep something that's consistent. But then I go, you're just taking away all that the version history, which you talked about, the one source of truth and co-editing, and to me, that creates a nightmare because you've got a copy of a copy and how many of copies, yeah. Well, and I think it goes back, Jay, to what you said. You know, are we trying to recreate that previous experience by moving over? You're over in this world now, it's different, and we should talk about, what are you trying to accomplish? Why are you doing that? Is the reason why she's even asking for this, is it more of a, it's a crutch because you did things a certain way because of limitations of the previous technology? What are you really trying to do? What's your goal here? Cause there may be a completely different way to do it, and probably more secure and compliant way of doing it over in Microsoft 365. Not that I'm biased. Shari, I think you mentioned a form earlier, right? Like if you can look at the Microsoft 365 stack and improve whatever you were doing with the rest of the capabilities, form, power, platform, flows, all sorts of things that you can do that are so much better than just make a copy. Yeah, I think, yes. I think what's happening, and I can imagine this cause, you know, being from the end user world, somebody is opening a file and they're adding the original and they're messing up the original and they're tired of reverting it back or fixing it. And I totally get that. You know, like a leave request form. But, you know, again, we have other ways that we can make that easier. But one little thing about the SharePoint, opening it by default, that is a library setting. It's not a document setting. So if they're really wanting to centralize templates so that they're in one place, I'd create a separate document library because that limits like co-authoring and somebody being able to use the web version of the document that I've been doing. Shari, could you also do a markers final? If you kind of do a markers final and you're locking it maybe for editing with a markers final, then they're kind of having to do another document off the back of it potentially. Yeah, I guess if the market is a record, it can be edited. So I'm not sure what you mean by markers final. Oh, like in Word, you can let anyone know it says final document. Often it's kind of, it can be a little bit more locked down or you can put some protection around the document itself so it would force them as well, might be another way from the actual app itself rather than through your link, whether it's SharePoint or OneDrive, sort of do it more from the application rather than the actual app. Yeah. I did a whole course on LinkedIn. I'll give you a link to that, Christian, of how to use templates with SharePoint libraries. In this spreadsheet, Shari, you know, we've provided this spreadsheet. I don't think that now that we've discussed this, I mean, I think to this scenario, it sounds like it, and maybe Nicole will watch this and let us know we'll do part two of the video. But is that idea of having, you know, like the templates and wanting people not to mess up that, that, you know, kind of parent, you know, version of that. And I mean, my guidance has been coming from the project portfolio management world and building out PMOs for multiple clients, multiple companies. The idea of creating a template library and locking down the library, but allowing people to go and pull down a template and then modify that. So I can go in and update the template as the owner of those things, but every time you go in as a project manager, download the version, it saves you a local copy and it's a subset of that. You've got to rename that, but it can never mess with the template. And so there's plenty of ways of doing that if that's the scenario and SharePoint, and then of course in Teams, which is still SharePoint. Yeah. Yay.