Can individual item permissions override "Read items that were created by the user" restriction?

Kirill Tsaava 0 Reputation points
2026-11-03T05:39:06.2866667+00:00

Hello everyone,

I'm trying to implement a specific permission model for a SharePoint Online list used to manage financial requests, and I've encountered an unexpected behavior when sharing individual list items.

1. Required access model

We need three categories of users:

  • Request creators: Each employee should only be able to view requests they created themselves.

Permanent process participants: A designated group of approvers and service staff should be able to view all requests in the list.

Additional approvers: Occasionally, an individual employee is assigned as an additional approver for a specific request. They should be able to view only that particular request, including its attachments, without gaining access to other requests.

2. Current list configuration

The list has unique permissions at the list level.

Under List Settings → Advanced Settings → Item-level Permissions, we configured:

Read access: Read items that were created by the user

Create and Edit access: Create and edit all items

Permanent process participants have Full Control permissions at the list level and can access all items.

3. The issue

We tested sharing an individual list item with a user who does not have general access to the list.

The following steps were performed:

Opened Manage Access for a specific list item.

Granted the user Can view access.

Verified that the user appears in Manage Access with direct view permissions.

Opened the item's Advanced Permissions page and confirmed that the user has an explicit Read permission.

However, the user still receives Access Denied when trying to open the item. The same happens when attempting to access its attachments.

The user does not have general access to the list.

4. Questions

Is the "Read items that were created by the user" setting expected to prevent access to an item even when another user has been explicitly granted Read permission on that specific item?

Does this setting take precedence over unique item-level permissions and individual sharing permissions?

Is this expected behavior by design, or could it be a SharePoint Online issue?

Is there a supported way to grant an exception for an individually assigned approver, allowing them to view one specific item without granting access to all items in the list?

Has anyone successfully implemented this exact permission model using SharePoint Online Lists?

5. Microsoft documentation

Microsoft documentation states that individual list items can be shared with people who do not otherwise have access to the list, allowing them to view only the shared item:

https://support.microsoft.com/en-us/sharepoint/lists/sharepoint-sharing-and-permissions/share-a-list-or-list-item

We would appreciate any clarification, especially from people who have encountered this interaction between item-level permissions and individual item sharing.

Thank you!

Microsoft 365 and Office | SharePoint | For business | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Billy Peralta 0 Reputation points
    2026-11-16T04:52:25.52+00:00

    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:

    1. Change the list's Read access setting to "Read all items". This removes the creator-only restriction, but doesn't automatically give everyone access.
    2. Set up separate permissions for each request, giving access only to the requester and the appropriate approvers.
    3. 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)

    Was this answer helpful?

    0 comments No comments

  2. Michelle Nguyen 3,045 Reputation points Independent Advisor
    2026-11-03T07:17:52.47+00:00

    Hi @Kirill Tsaava

    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

    1. 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).
    2. Make sure employees don't have broad read permissions at the list level, only enough permission to create items.
    3. 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.
    4. 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.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.