A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Thank you for the detailed description. I'm only a community member, so I can't check your site, but I tried to reproduce this on a test site and also looked at what the community has reported.
I created a test list with unique permissions, an Employees group with Contribute permission, an Approvers group with Full Control permission, and Item-level Permissions set to "Read items that were created by the user" and "Create and edit all items". I then shared one item (Can view) with a user who had no other permissions on the list or site. In my test, that user also could not open the item. The error I received was the generic message "Sorry, something went wrong" rather than "Access Denied". I haven't compared this with a control list using the default settings, so I can't be sure that the setting is the cause in my test.
I couldn't find official Microsoft documentation that describes the order of precedence between this list-level setting and the unique permissions of individual items.
Your questions, in short
- With "Read items that were created by the user" enabled, I couldn't find an out-of-the-box way to give an additional approver permission to view exactly one item. A permission level that includes the "Override List Behaviors" right would allow reading all items, which is what you want to avoid.
- Yes, this model is commonly implemented, usually with Power Automate rather than with the list settings.
A commonly used approach
- Set Read access to Read all items (and review the Create and Edit option too, because the "created by the user" option for editing can also override item permissions).
- Make sure employees don't have broad read permissions at the list level, only enough permission to create items.
- Use a flow triggered by When an item is created to break permission inheritance on the new item, remove the general permissions, and explicitly grant permissions to the creator of the item and to the permanent approver group.
- When there is an additional approver, add that person to the item's permissions, either through the flow itself or through Manage Access.
You should test this on a sample list first, especially whether attachments follow the item's permissions, and keep in mind that SharePoint limits the number of items with unique permissions in a list, so please check Microsoft's limits documentation if you expect a large number of requests.
In addition, a quick way to confirm the cause is to switch Read access to Read all items on a test copy of the list and try again with the same item shared with the additional approver. If the user can open it, then the setting is what blocked access.
To narrow down the cause, could you let me know:
- Whether the shared user is an internal user or a guest.
- Whether the shared user can open the site's home page.
I hope this information is helpful.