Forum Discussion
Creating unique permission on custom List based on column in the item
I have created a custom list. Users are able to go to the SharePoint site and submit an item. I have enabled Item-Level Permissions so they are only able to see the requests they submit. Members of my team are able to see all of the items. This is the need:
1. Members of the Team should be able to all requests - This works
2. Users should only be able to see the requests they have submitted - This works
3. If a User who did not create the item and is a member of the Team, should be allowed to only see the items that they are added to from a column within that item. - This I have no idea how to implement.
I would like to create a column where multiple users can be selected. That column within that item would then extend permissions to those individuals to see the item.
The Assigned SA should also be able to see the item created by someone else.
I have found the answer that I was looking for. You are correct that out of the box is not possible. I had to use SharePoint Designer to get the functionality I needed to work. As a note the workflow must be created as a 2010 workflow, because it is able to item level permissions. 2013 uses app permissions which only apply at the list level.
This is a link to where I found the answer: http://truapps.portalfront.com/how-toset-sharepoint-item-level-permissions-based-on-column-or-field-values.html
This is a link to the difference in item/list level permissions:
https://melihubb.com/2017/04/11/app-step-vs-impersonation-step/
2 Replies
Hi zascherl,
This is not possible with out of the box functionality. List item security is open or restricted to item creator. A custom solution using security groups and workflows may meet your needs.
Probably not what you wanted to hear. I hope this helps.
Norm
I have found the answer that I was looking for. You are correct that out of the box is not possible. I had to use SharePoint Designer to get the functionality I needed to work. As a note the workflow must be created as a 2010 workflow, because it is able to item level permissions. 2013 uses app permissions which only apply at the list level.
This is a link to where I found the answer: http://truapps.portalfront.com/how-toset-sharepoint-item-level-permissions-based-on-column-or-field-values.html
This is a link to the difference in item/list level permissions:
https://melihubb.com/2017/04/11/app-step-vs-impersonation-step/
