I created a PowerApp with a Sharepoint custom list as the data source. I granted all 315 users of the app "Site Member" status (R/W/E).
Solved! Go to Solution.
WOW! The Kool-Aid is everywhere. All this to hack a SharePoint list and leave it vulnerable. Why not just leverage native custom list forms with no peripheral service dependencies and/or overall solution performance degradation while maintaining inherit current logged-in user context/security as well.
What if you create a Custom form for your list that has no function other than a message to use the app and add a launch link. Then in the list settings prevent editing of the list via Quick edit.
Well, note that it's it's $10 for one app, per user, per month.
I'm surprised that no one mentioned about using Target Audience and losing the modern experience in SharePoint list. Also don't see that it's not mentioned in the MS documentation about it's limitation... Love the idea of Target Audience since SP 2013 and still waiting for a bigger enhancement.
i am just wondering anyone find it there is a bigger disaster going to happen when you open MS List Apps.
All your list whether you hide or not hide is there and ready for view and edit.
Hi @seadude ,
Give the users a custom permission in SharePoint and remove "View Application Pages" and they will not be able to navigate to any view even if they know the URL.
Power Apps User Groups are coming! Make sure you’re among the first to know when user groups go live for public preview.
Did you miss the call?? Check out the Power Apps Community Call here!
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.