A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Hi Kirill,
Yes, this is expected with that setting.
"Read items that were created by the user" is more than just a filter. Even if someone has Read permission on a specific item, SharePoint can still block them because they didn't create it.
Microsoft's documentation confirms that this restriction applies unless the user created the item or has Manage Lists permission.
I wouldn't give an extra approver Manage Lists, since that would also let them see other requests.
For your scenario, I'd use individual item permissions instead:
- Change the list's Read access setting to "Read all items". This removes the creator-only restriction, but doesn't automatically give everyone access.
- Set up separate permissions for each request, giving access only to the requester and the appropriate approvers.
- When an extra approver is needed, give them access to that specific item.
You can automate the permissions using Power Automate.
One important point: because these are financial requests, be careful with a flow that changes permissions after an item is created. The item could briefly inherit wider access before the flow runs. Make sure the list is secure from the start, and test the process before using it with real financial data.
Also, if the list will contain thousands of requests, keep in mind that SharePoint has limits on unique item permissions.
Microsoft documentation: tp_ReadSecurity (SharePoint protocol documentation)