 Michelle asks, I've created an Excel spreadsheet with lots of SharePoint links. I've copied the link from SharePoint and pasted it into Excel, but others in my organization are unable to open the documents. What am I doing wrong? I've created lots of documents like this recently. We'll have to update them all if I can't find a solution. I'm not the owner on the site, but I am a member. I have added other members onto it. What do I need to do to make the Excel spreadsheet work so others can see the links? Define C. C to me means they can't see the links in the spreadsheet as a hypertext link. I don't understand why they wouldn't be able to see the links, but if they can't open the links, that's going to be a permissions issue. Yeah, I was assuming it was open, so see the links, see them in Resolve. Yeah. I wonder if it's open in Protective View or content, external content is somehow at play here, and you need to click an extra button to get the, I don't know. Could also be the default sharing link type, so only specific people, any people, whatever is set at the organizational level. And that could be preventing the link itself from being available to non-specified members or members of the site or people that you explicitly name. That's likely, more than likely what's happening, Norm. I envision Michelle building this curated list of SharePoint links, right? And when they go to click on it, it doesn't open. And that, yeah, that, if that's the case, yeah, you've got to be very careful on that ShareLink. Number one rule in anything SharePoint is check permissions first. You've built it, you can click and get to it. That means nothing. If you've built it in a location and everyone else doesn't have access to the site, to each of those assets. If you're pulling from across the SharePoint environment, guarantee you that not everybody has access to all of those things. Just because you can see it doesn't mean other people can see it. It's all, it's based on permissions. Have you seen organizations, clients, be so disciplined about the container being the site collection now? And you do not, you do not do anything more granular than that with permissions. Have you guys seen that? Is that a trend that you're noticing? No, that's why they flattened the structure because permissions and broken permissions were such a problem. I think that's why they decided, subsites are bad. But yeah, I always tell them if you need a different audience, don't do a document by document. Create another library in the site and change the permissions there and then move the document into that library, but yeah. So what I'm noticing is it would be a new site entirely if you needed a different audience for that. Oh, that's bad governance, my opinion. But the other thing, here's my backwards hack for her. If you change to classic view and copy the link using it from there, it actually gives you the clean link and not the big encoded encrypted gobbledygook that they add 500 characters at the end of your file path. And I prefer to use those because it just takes it correctly to the document. And if you have permission, you have permission. If you don't, you don't. So that's my backwards little 20-year-old SharePoint hack. And Sherry, just to clarify, is gobbledygook a technical term or? Yes, it is, yes. I think we'll have to add that into the glossary for the video, yes. Let me try to get this one right there. That's right. I mean, the other thing too is that if you have, if your organization has one of the third-party tools, I mean, AppPoint has this, the ability to go in. There's really quick to go in and do a search on what permissions are available for this location for each of those, or go to an individual user that is unable to get into multiple links and use that as a test and see very quickly your locations and whether you've just added content into locations that no one else has access to.