I have a custom list inside SharePoint online site collection. and i have the following requirements:-

  1. Allow all users to submit new items, but they can not view any item (even the one they have created).

  2. Certain users will have permission to view/edit all items.

  3. when an authorized user edit an item >> they can add users inside a People or Group field named "Item Readers">> after that the users added inside the People or Group field will have read permission on the item

now for point 1 & 2 i will create a custom permission level to allow submit only on the list. but for point 3 i am not sure what is the best approach to follow? can i benefit from WorKflow 2013 or MS Flow? previously i use to do such a requirement using server-side event receivers, but in SharePoint online, remote event receivers are no longer been a preferred approach, especially that there is not any approach to debug them (after Microsoft has depreciated the Azure Service Bus)..

  • Have you thought about infopath and SPD or nintex?
    – Deepika
    Commented Nov 28, 2019 at 13:45

2 Answers 2


Microsoft Flow is recommended to achieve this requirement.

Since you already have unique permission on this list, you can skip the “Break Inheritance” part.

Please see the references below.

Setting sharepoint item list permissions with flow.

How to manage permissions on a SharePoint List Item using Microsoft Flow – changing Item permissions.

  • 1
    ok thanks for your reply. in my case i still need to define unique permission for the item upon creation + assign the users defined inside the People or Group as Readers inside the item permission. then on update, i need to check if the People or group field was modified (or is not equal to the users defined inside the item permission), and then modify the item permission accordingly... looks like this is too much for flow or SP workflow ? is this correct?
    – John John
    Commented Nov 25, 2019 at 11:52
  • @SharePointTestDev You can see the following link for definition limits for workflows: docs.microsoft.com/en-us/power-automate/… I don't think you will ever reach the limit but surely it’s a lot of work to do. Commented Nov 26, 2019 at 9:29

This can be implemented by the SharePoint 2010/2013 workflow. Add impersonation step then remove all permission from the created item. Also, give permission to the relevant groups/users.

Possible bug: If the user needs to submit an attachment, in some cases workflow will fail due to removing permission from the user. You need to implement a system pause that the user has enough permission to submit the attachment.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.