 because I'm searching if there is possible to disable user to read a SharePoint list. I created an app with PowerApp that the user needed to approve list created with SharePoint to connect with the app. But you can log in also directly to the SharePoint website and read all the information of the SharePoint directories and lists, and for me it is a problem. So how do you disable a user their ability to read the SharePoint list? Is this just a problem with you created the solution and there's that nice little button where I can go and say, well, let me view this in SharePoint and then see everything. Is that what this is? Yeah. It could be. And what you're doing is you're exposing the fact that Microsoft lists out of the box are going to give you two security options out of the box. So you and I can see everything or edit everything or I can only see my own entries and you can only see your own entries. Any other attempts to have row level security in a list doesn't exist out of the box. And so that you're using a list as a data store for an application, you start bumping into these things the more the advanced requirement is. So it sounds like, you know, list, great place to put data, maybe not the best place to secure data. So to answer the question, how can you make it so people can't see the data, right? The data. I mean, technically, he could break the inheritance on the list. That in turn will probably break the app. I'm sorry. And by, and when I say break the inheritance, I mean, remove that editing or that viewership permission. But then now your application has to account for that. Something is going to have to act on behalf of the user. So it gets kind of gets complicated. And I mean, you could, you could go down the rabbit hole and be very creative. You could do something like break the, break the inheritance, remove all the permissions, but only grant access to those individual items using something like Power Automate. But, you know, we're just adding complexity. We're, we're venturing into that space that Microsoft discourages people like, like use the capability, you know, out of the box functionality in the way that Microsoft is designed to do. It's lists are meant to be relatively flat, flat structure. So I would say then set the default permission so that I only see what my entries are and then create another view, another look into that where the people that need to have access and view all those things can see it. But by default, I should only be able to see the items that I've, you know, that I've entered in. Yeah, and that you have to get into more deeply into the permission. So it's a norms point. It only creates two default permission groups. You can, there's like 27, I don't even know anymore, different attributes that you can turn on or turn off and create custom permission settings. But, you know, if it's teams enabled site and it's a teams enabled list, now you're kind of getting into the mushy part where if you add a new member, you've got to remember to go back and change their permission in the SharePoint site that is, you know, storing and managing everything. So it's not out of the box functionality. So if that's the case, if the requirements are valid to have it, you know, and to do something that's more granular, what are the recommendations for that? Or where would you point them? I may not use lists. What's the next option? Yes, and that's it. It's a decision point, usually driven out of our real requirement around security. You're something is sensitive. It can't be shared with an entire group. Then you need to start evaluating what will make sense for you. Now, if you're in the Microsoft 365 platform, then you can look to Dataverse for teams. It's a little more complicated than lists, but you'll be able to do a little different security. You'll have a little more freedom and creation that still doesn't suit your needs, then you might have to look at Dataverse, which is, you know, part of the power platform. That's got a little steeper learning curve than Microsoft lists, but if it's your requirement that's driving the, or if the requirement is driving that need for data protection, then you're going to need a platform that can support it. People are very creative and I'm sure there's a lot of consultants out there that can work around the problem, but fundamentally... Well, it goes back to that problem. It's like, you know, Microsoft has been trying to push back on the, you know, SharePoint as a Swiss Army knife. Can you break it and go and do the things like, yeah, but then becomes an unsupportable mess. It causes problems downstream. Use the products for what they're intended and the way that they're intended. And so, if you have those more complex requirements, there are other alternatives to that, but it's going to be a little bit, you know, a heavier development load. Yeah, and, you know, we're doing this big push for community developers right now. They want people to use the Power Automate, Power Apps, the whole Power Platform, and give citizen developers the ability to create their own stuff. But should they? When you're talking about complexity, it's like, I can dive in and get some, but I'll tell you, I'm dangerous when it gets to some of this, when it gets into the coding part of it, should I am I the best person to build that solution just because maybe I'm a citizen developer, right? I don't know that that's always the best case. You know, bring in the right people to do the job, and then you're going to save yourself a lot of frustration. And the right people to do the job, and that's when Jay just shows up out of nowhere. Ta-da! Did you hear his ear for tingling? Did I hear someone call the right people to do the job? Not that that's Jay because it's not, but it's just, wow. Well, actually, I think that's a, it's a, this is a question that I've, we've heard variations on this from time to time. And I think the answer is the same. It's, you know, it's like, be clear of what you're trying to accomplish and use the right tools to solve the right problems. All right. Or ask Jay. Or ask Jay. I mean, I agree with everything you've said since I've gotten on the call. So...