Item level permission could be managed within SharePoint itself and cannot be modified in flow.
That's too bad because updating item permissions is exactly something that flow could be used for. Example, if item is 'approved' then update permissions to read-only for creator. Flow would be perfect for this.
Oh well, without flow we're back to Sharepoint Designer/Workflow.
I totally agree. Having to use the 'old' workflows to set permissions is regressive.
Setting permissions should be one of the first things that was available with Flow! I understand where MS are going with this but again they miss out the most fundamental things that users need.
Please use https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas to post or vote on ideas. Flow team reviews this topic and the most popular ideas are considered as candidates for new features.
Thanks for posting this video. This will be rough for the citizen developer if they have to jump through tokens, app permissions, http POST requests to set a list element permission.
I hope that Microsoft is working on techniques to either simply this or to adjust the flow settings to accommodate different rights.
Apparently you can call Azure Functions from Powerapps/Flow so it might be easier to write the code once to get-a-token and set-list-permission and then just call this azure-function from your flow. (sorry you can see that I'm biased to write code rather than create flows )
There is an action, called Change Permissions that gives you the ability to:
Here are a couple of examples of Flows:
Rest calls can be made from flow, and item permission is possible from rest api.
1. Rest calls to reset permissions:
2. Integrating custom API
Hope this will help you!!!
Thanks for your links.
I'll have a to set aside some serious time to try this out. Would prefer a more user-friendly option as time is not on my side here!
As a platform for 'citizen developers', having to jump into REST, tokens, and the graph/SP API are not baby steps. Given that a primary user is the PowerApps developer I hope that Microsoft is still considering a dedicated collection of 'high-level' flows to support list/doc permissions.
Yours looks a little clearer than what I've read so far so will set some time aside to try it. As I keep saying, along with others it would be nice to see this wrapped....
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Una semana de contenido con +100 sesiones educativas, consultorios, +10 workshops Premium, Hackaton, EXPO, Networking Hall y mucho más!