 Adam says, how do you deal with folders which could belong to one site but are used by other departments which don't have access to that site? For example, each department has their own private site but needs access to a finance folder owned by finance to submit receipts, etc. I don't know if it's the best to keep the department folders in the finance site, make a finance folder on each department site, or have a finance folder in the all company intranet. What do you suggest that works best? It needs to be somewhere where finance can access all the folders easily, where departments can find them easily, and where permissions are restricted to each department. I wrote business process architect. Yes. Seriously. 100%. Well, I think the last part of that question was where all departments can find them easily and where permissions are restricted to each department. Yes. Well, that right there says, well, then you need to have it within each site. Or you could. Is it Teams? You could go one better and you could do something like a Power App or Power Automate where basically they're entering the information or uploading the files that need to happen in a system account or a privileged account is then taking that information and depositing it into the finance site so they literally have no access to be able to touch it because it's talking about 100 ways to do this, for example, but that's kind of very much a one way. It's a matter of the earlier where it goes. If they've got to access the files within it, that then is a different argument because if it's going one way information in compared to I've also got to be able to pull it back or do then that's different. That's a different answer. Pances are there are additional considerations beyond these. That's the whole idea possibly. That's crazy talk, Sean. I tell people all day long you don't have a SharePoint problem, you have a process problem. This is one of those, Sean. There are a number of different ways you could do that. Look, I've seen a shared folder where there are document level permissions and so the password protect that and give access. You could also, if it's in teams, you could go in and create private channels for each of those constituencies and then have those permissions managed. I think the downside always comes down to ease of being able to find it because if you've got a private kind of SharePoint and you open one folder up on that SharePoint site, then people try to find it after the fact and it becomes that much more challenging. Is it a site where all those common things should be sitting and you just plug that folder into your teams, for example? You can plug it in as an add a folder so you've got all access easily for you. It comes down to can you find it? Is it easy to get to where should it sit? It comes back to said business process and architect design. What's going to be the best place? Well, except for that last line about differences in permissions and access, it controls around that. I mean, I've been a huge advocate coming from a project management background of having like a centralized PMO type site which everyone has brought access to and that might have templates and other core central documentation where it's owned by the PMO, the centralized organization, the project management organization, but everybody has the ability to go in and view or to create from templates new documents off of those things. Now, I know it doesn't quite fit this scenario, but again, like anything, you look at what is the outcome? What are you actually trying to achieve? Are you putting rules and in place that really don't need to be there to meet those and those outcomes, desired outcomes? But if you have that, if you have that end level nuanced permissions and controls that you need to be in place around each one of those departments, yeah, having an information architect go through and kind of divide that, but it all leads the way that I would approach it. Be back to that where each of the functional areas has the necessary folders and as the project owner, just make sure that the finance team has project XYZ finance folders. The project team has project XYZ project folders or finance folders or whatever. And so you have those designated areas. It's about having consistent naming mechanisms and structure so that when you go and deploy it out there, that the same pieces are in each place. The finance people know where to go. The project people know to go. The executive team, the leadership team know where to go for project XYZ and every other project. Yes. So it's just a highly templated and you can do that with a provisioning solution as well. Have it very structured. Say every new project site or product site has a designated template and there are these components which include that folder structure that needs to be there with all the naming mechanisms, all of that already in place. It sounds like a lot of work, but I've worked in regulated areas where we had to, we were a same company, but we had firewall divisions. And so we had to do that. There was a lot of duplication of that structure, but we were legally required to go and do that. And it worked. It took extra clicks and things to get through to get to it, but we could do it. The other one would be, does the whole organization need to have access to it? Or just certain core components of some people because that would change where it sits to. Flat structure is always preferred if you could do that. And then let the rules, let the regulations that you must adhere to kind of guide changes, but those are exceptions. The rules should be flat. Everybody has access and then kind of add the restrictions from there as needed. Well yeah, because back to the permissioning thing is the more you poke holes in that, the more work it is, the higher your risk is, the more work it is, the less compliant it is, the less secure it is, the more you have opportunity for errors and problems and all kinds of things. So it's really in your best interest as much as possible to not do anything unique if you don't need to. Yeah, that makes for a brittle system. Let's, it's folders related. It's going to be fun. Yay. Folders are fun. Oh, yes, okay.