 We've got a question here from Banny. I have a team site and a communication site for the client or client site. I'm having difficulty displaying any of my team site info, so most up-to-date policies, guidance books, best practices, etc., on my communication site. I try to use web part documents, highlight content, etc. But when I go to edit the web part, I cannot locate any of the info pretending to my team site. Does anyone know why? I guess my question really is, if I have a team site, which we have items we would like to share on our communication site, cannot be done without having to upload it to the communication site. I would like it to just do auto-update as we update the team site, and he apologizes if that sounds confusing. But he thinks it's an advance. It's not confusing. It makes sense. It's a common scenario. It's very common scenario. That web part does exactly what he intends. It opens up a window, if you will, to that other site. In that other site, you have the option to, or through the web part, I should say, through the web part, you have the ability to locate a particular site that you have access to. I think the keyword there is access, or a particular document library. It's very configurable, and a lot of it can be GUI-driven, so you're just clicking through an interface. That's well-designed. I don't use it that often, but I've used it before, and I know there's a more advanced way of doing it, besides a click configuration, and that's through a custom query, like AML or KQL. Definitely possible. But if you're not seeing your sites, maybe you don't have access. What do you think, Sherry? Yeah, I think it's 100 percent either permissions issue, and also the question I would ask is, should people actually have access to the active documents that are in the team site? Because when I build a documentation strategy, you have where you build the things, where you make the things and maintain the things, and then the communication sites where the published version of those are. People shouldn't be able to find things if they're not completed, published. So A, should they have access? B, do they have access? That needs to be incorporated into their documentation strategy. That's my- We're getting into the document management document life cycle aspect of it. Yeah, retention policy. Yes. Should you do it? I guess it depends on your scenario, but if it's like what Sherry describes, you may not want to surface your policies in a editable form. I go back to my HR days, my recovering HR days, I'm not being a HR professional anymore, but I would have policies and procedures that were stored and they evolve after they've been released, published, ratified, whatever, and things change usually based on a legal incident, and you have to republish them. People should not be able to find the working copy of that policy, only the current published version of the policy. So within the communication site though, I mean, so it could be the configuration of the web part, so that's only showing those things, which show as the state, the life cycle as published, and other labels and things. So it's going to be triggered by, it's just a way that the web parts configured. Yeah. Back in the classic days, we were able to publish documents and create copies of them, basically child copies around different SharePoint sites, but they took that away in modern. I don't know that we have that ability anymore, but that was a great way because you have your primary one, and when you shared it to another location, it would say, oh, if you update, it's like, do you want to update the babies? You say yes, it would update the babies. That was a nice thing to have, but I think with Power Automate, we could probably accomplish the same thing now, but it just takes a little bit more than it was an out-of-the-box functionality. I think you bring up an interesting point about the classic SharePoint, and maybe we're trying to connect into a non-modern site through the web part. Ooh, that's a good point. Maybe the documentation therein is not the modern versions of Excel, Word, PowerPoint, and so on. Maybe it's the .doc file, not the .doc.x file, that type of a modern file type. Maybe that's something. Those are things that you'd want to check. You're eliminating variables at this point, but the web part does work. I've seen it, I've used it, I know it works. Yeah. It's like the old web query web part, where you could say in this scope, this type of document, this metadata, display these or view. Is that what you're talking about? Yeah. Yeah. Okay. Cool. It depends. I don't you love the answer when it's always true. Not what they want to do. Should we just make sure we work that into every response? It's like, well, you know, it depends. Exactly. Very good. So Norm, can you read what's on the sticky? No, you can't, because it's a secure view. I have a view of it. You do not. Yeah. There we go. Based on rules, based on rules. There you go. Based on rules. Based on my hand blocking it.