Forum Discussion
Dynamic item-level permissions?
Sai Gutta Thank you!
The article links to a great instructional video explaining exactly how to fulfil my requirement :D
- Kosmos180Apr 23, 2019Copper Contributor
- DanielaHMay 07, 2019Brass Contributor
Just a quick update on this - I logged a premier support ticket with MS and the response was that what I am trying to achieve is not possible at the moment (unless perhaps using the flow I referenced earlier).
How are others solving this kind of scenario then??
Imagine a purchase order needs to be submitted, but the submitter should only have read-access after submitting. However someone else (the approver) needs edit access in order to update its status and perhaps add a comment. This approver is usually specified within the form/list.
-> Requirement: Item level permissions enabling submitter to view, and specified approver to edit.
Such a simple requirement and yet so difficult to achieve?
- SK_TanSep 08, 2021Copper ContributorHi DanielaH,
You managed to resolve this?
- DanielaHApr 16, 2019Brass Contributor
Thank you jcgonzalezmartin.
Sai Gutta - I had a go at the shared article and it looks quite involved.. since I am not coming from a technical background I am not actually clear whether this does fulfil my purpose - i.e.:
The only people who should get contribute access to the item are those as specified in specific columns within the list?
- Sai GuttaApr 18, 2019Iron Contributor
DanielaH - I briefly went through the article and you cannot follow the article as is, you might need to make small changes like getting the user details from sharepoint list to whom you assign contribute access.
- DanielaHApr 23, 2019Brass Contributor
I am curious - how are others solving this specific business problem?
- Employee submits a new item that requires approval
- After submission employee cannot edit submitted item
- Approver(s) can edit submitted item and approve it.
- Approvers are specified by entering their email address into a column within the item itself
The requirement really is just a simple approval cycle, which involves access restrictions as described above. The only challenge is that the approvers differ for each item, and are supposed to be 'listed' by the employee as part of submitting the item.
I am surprized that this is so 'difficult' to achieve... or are SPO lists simply not the right platform for this?
Curious to hear feedback from others on this?
- DanielaHApr 16, 2019Brass Contributor
Thank you jcgonzalezmartin.
Sai Gutta - I had a go at the shared article and it looks quite involved.. since I am not coming from a technical background I am not actually clear whether this does fulfil my purpose - i.e.:
The only people who should get contribute access to the item are those as specified in specific columns within the list?