Permission & Access Issues

Fix SharePoint Item-Level Permissions in Power Automate

Maira Mehtab Sep 22, 2026 868 views

Question details

A Power Automate flow successfully grants item access to managers, but the managers receive an 'item not found' error when attempting to view the SharePoint list item.

Product: Power Automate
Device & OS: not provided
Scenario: Automating expense request approvals where each manager needs view and approve access to specific SharePoint list items via Power Automate.
Observed behavior: The Power Automate flow completes successfully without errors, but the target managers cannot access the item and receive an 'item not found' error.

Before you start

Ensure you have Site Owner or Full Control permissions on the SharePoint site to verify list inheritance settings, and confirm the manager's Microsoft 365 account is currently active.

Solution 1Recommended

Verify the Item ID and Direct URL Mapping in Your Flow

This is the most common cause of the error. You must ensure the flow is assigning permissions to the exact item ID and generating a direct link rather than a generic list view.

Even if a flow succeeds, it might be granting permissions to the wrong item or sending an improperly formatted URL, leading the manager to a dead link.

Edit the Power Automate Flow

Open Power Automate, navigate to 'My flows', and click the Edit button for your expense approval flow.

Check the Grant Access Action

Locate the 'Grant access to an item or a folder' action in your flow. Verify that the 'Id' field is populated with the dynamic content 'ID' from the initial SharePoint trigger (e.g., 'When an item is created').

Verify the URL Formatting

Check the email or Teams notification action sending the link to the manager. Ensure you are using the 'Link to item' dynamic content so it points directly to the specific list item.

Run a Test with a New Item

Create a brand new expense request in the SharePoint list to trigger the flow. Review the flow run details to confirm the correct Item ID was processed.

Solution 2

Review Unique Permissions and Broken Inheritance

Use this solution if the flow maps the correct ID but list-level security settings are overriding the flow's permission grants.

Solution 3

Isolate Link Errors from Permission Errors

This troubleshooting step helps determine if the issue lies within the Power Automate notification link or the backend SharePoint permissions.

Free Microsoft Office alternative

Manage Expense Reports Seamlessly with WPS Office

While Power Automate handles your complex workflow routing, managing the actual expense spreadsheets and approval documents is effortless with WPS Office. As a free, lightweight, and highly compatible alternative to Microsoft Office, it ensures your data remains perfectly formatted across all devices.

1. Download the Software: Visit the official WPS website and click Download WPS Office Free for your operating system.
2. Install and Launch: Run the installer and open WPS Spreadsheet to review your expense report data.
3. Edit with Full Compatibility: Open any exported Microsoft Excel files from SharePoint without worrying about formatting loss.

Fully compatible with Microsoft Excel, Word, and PowerPoint file formatsLightweight installation that runs smoothly on Windows, Mac, and LinuxFree alternative to natively view and edit exported SharePoint list dataFamiliar user interface requiring zero learning curve for rapid deployment

microsoft office alternative - wps office

Frequently Asked Questions

Why does my Power Automate flow succeed but managers still get an 'item not found' error?

A flow only reports failure if an action physically fails to execute. If the flow successfully grants permissions to the wrong Item ID, or if it generates a malformed URL, the flow will report as 'successful' even though the manager cannot access the intended item.

Does changing the SharePoint list to unique permissions break Power Automate flows?

It doesn't break the flow itself, but broken inheritance can cause conflicts. If list-level settings aggressively restrict access (like 'users can only see items they create'), it might override the item-level permissions your flow is trying to grant.

Will granting access to the entire SharePoint list resolve item-level permission errors?

While granting access to the entire list or creating a standard view will bypass the 'item not found' error, it does not replace item-level permissions. For sensitive workflows like expense approvals, this exposes all requests to everyone, which is usually a security violation.

Does content approval status hide items from managers?

Content approval is not generally required simply to grant view access. However, if draft item security is enabled in the list settings, pending items might be hidden from users who only have Read access until the item is fully approved.

Document & File Issues