How to Change SharePoint Folder Permissions Using Power Automate Flow
Question details
The user needs to automate a SharePoint workflow that dynamically removes a submitter's folder access, grants temporary access to multiple reviewers, and restores the original permissions once the review is completed.
- Product
- Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- Managing dynamic document folder access and permission hand-offs during a multi-stage review process.
- Observed behavior
- SharePoint lacks a simple built-in action for this complex permission toggling, requiring an automated workflow solution to handle the inheritance and access changes.
Ensure you have Full Control or Site Owner permissions for the SharePoint site, and verify that your Microsoft 365 account has the necessary licenses to create and execute Power Automate flows.
Automate Permission Changes Using Power Automate Triggers
Create a custom Power Automate flow that triggers upon list or document status changes to dynamically break inheritance and manage SharePoint folder permissions.
Because SharePoint requires custom workflows to handle complex permission toggling, using Microsoft Power Automate is the most effective approach. By configuring specific status triggers, the flow can automatically stop permission inheritance, remove the original submitter's access, and grant temporary access to designated reviewers.
Open Microsoft Power Automate and create a new automated cloud flow. Set the trigger to 'When an item is created or modified' in your specific SharePoint list or document library.
Add the 'Stop sharing an item or a file' SharePoint action to the flow. Select your site address, list or library name, and use dynamic content to map the ID of the folder or item. This isolates the folder's permissions from the parent site.
Add the 'Grant access to an item or a folder' action. Specify the email addresses of the three reviewers and assign them the appropriate role (such as 'Can view' or 'Can edit').
Configure a 'Condition' or 'Wait for an update' action that actively monitors the item to detect when the review status is marked as complete.
Once the review completes, add actions to remove the reviewers' access (using 'Stop sharing' again or HTTP requests) and use 'Grant access' one final time to restore the original submitter's permissions.
Try WPS Office for Simplified Document Collaboration
While setting up automated workflows requires complex tools like SharePoint and Power Automate, everyday document collaboration doesn't have to be difficult. WPS Office provides a lightweight, free, and highly compatible alternative to Microsoft Office, offering intuitive file sharing and editing features for your team.
- 1. Download and Install: Visit the official WPS Office website and download the free installation package tailored for your operating system.
- 2. Sign In for Cloud Benefits: Launch the application and sign in with your email or social account to activate your free cloud storage space.
- 3. Share and Collaborate: Open your documents and use the built-in 'Share' button to generate secure links, allowing you to quickly set view or edit permissions for your colleagues.

Frequently Asked Questions
Can I change SharePoint folder permissions without using Power Automate?
Yes, you can manually manage permissions by navigating to the folder in SharePoint, clicking 'Manage Access', selecting 'Advanced settings', stopping inheritance, and manually adding or removing users. However, this manual process is tedious for recurring multi-stage reviews.
What permission level is required to run a flow that changes access rights?
The user account that creates and authenticates the Power Automate flow must have at least 'Full Control' or 'Site Owner' permissions on the target SharePoint site to successfully break inheritance and modify folder access rights.
Why isn't the 'Grant access' action updating my folder permissions correctly?
This usually happens if you have not broken the folder's permission inheritance first. If a folder is still inheriting access rules from its parent library, attempting to grant or remove access at the individual folder level via flow may be overridden or fail to behave as expected.




