 Matthew says, with modern SharePoint Online, I have a hub site and associated sites. I upload an image to an associated child site, create a page news item on the associated child site, but then can't seem to get at that content on the parent hub site. My question is, within a site collection, is it possible to use content from one site that has been uploaded to another? I know using subsites, I can share content, but I can't seem to do it with the hub sites and associated sites, which I think are referred to as site collections, so I can only assume I am doing something wrong. It's the filtering in the audience on their web part. When you add a news web part to a page, you can just decide the scope and you can also apply filters on either attributes of the page, but across sites, if the scope is beyond that site, you can't use like page properties as a value that you can filter by if it's within the same site and the news you can use the page properties as a filter, but it's how they're filtering in the scope of their content that's coming up on their page. So in the news web part, in the web part setting. Yeah, hub sites are good for navigation, they're good for search scopes, but as far as content sharing at a broader level, you're still gonna be bound by site or site collection level permissions. You're not gonna get the helpful little accelerators that pop up to allow you picking across sites typically. If you have all the permissions that everything's set up and you have the URL of the item you wanna use, you can use it across. But again, there is an implication that if you're doing that, you need to make sure that your audience, whoever's gonna see this stuff, has access to data in both places. So it's generally not a good idea. Yeah, I've tried to use the managed metadata as a property so you could go across site collections and use those as filters, but it's a whole other thing. That's not like it used to be where you have the content hub and it would give you all the, it would inherit and it would update. And yeah, it doesn't work like that. That managed metadata, the way they have it configured now, I don't think is very user-friendly personally. Yeah, so the only comment I would add to all of that is if you are trying to get to a place where you want to be able to access content from across multiple sites, there is this thing called an organizational asset library. And I put the link in to share that for how to set it up. But essentially it's really like, I mean, like this much PowerShell, you copy and paste it, it's super easy. And you can basically define one library in your site to be that library. So like when you're going to collaborate your news and add images, it defaults to that one place across the entire tenant, which is really handy so that you're not like, where did we put that? Which site do we put it on? They can just pull it from one place. And then as long as, to your point, as long as your target audience, as long as you're scoping, as long as your provisions are set up correctly, you should be good to go. But I have really found this to be really, really nice. And I've got one set up for templates, one set up for images like site assets and things like that, that you can pull into different things that then they can access it from across the entire tenant. That's awesome, because honestly, right now I'm going through 68 sites and rounding up all the little icons that they used on their buttons. Because we're migrating and now we have to recreate all those. And I gotta figure out, where did they stick all these little images in 68 different sites so that we can recreate them? Yeah, and some of them are the same ones in different places. So having the central icon library, awesome. So to that point, when you're architecting, if you define one site collection, essentially to host all of your images and assets for the entire tenant, as long as everybody has read access to that site collection and that content, you can actually use this and then people can share and use those assets. And essentially, you know that no matter kind of where it is, at least they have access to the asset itself. Okay, and you put the link in the... I did. Yeah. And you have the choice. I'm so doing that. You can either create an image, you can create an image library that's specific for images or a template library that's specific. And hey, fun fact, new feature is if you create an organizational asset library for templates, when you go into PowerPoint or Word or whatever, it automatically shows up in the application under your tenant name. So it's like an assets, like maybe call it the tenant slash assets might be the, I don't know, org assets maybe, or be the URL and get me thinking. Yep, yep. No, and I've... Sharing for the win today. I've got several clients with this and we use it and it's a really, really neat little thing that, it's one of those, you know, a lot of people just don't know it's there, but it makes a big difference when you're trying to manage things like images and templates across a tenant because you can't do the cross-site sharing. Okay, I get it.