Hi
We cannot detect permission changes after the fact. But we could look at ways to prevent or make it harder for users to manually change permissions and then force all permission changes through a flow.
This is not a replacement for a true “permission changed” trigger, but it might provide you with some ideas or a workable alternative.
(1) Restrict sharing to Site Owners only (unfortunately, this is a site-wide setting) and turn off "Allow access requests".
(2) Create a flow that will share the file when a “button” in SharePoint is clicked by the site owner. The flow would share the file (but flow needs to ignore folder sharing requests) and alert other members by email. In other words, we are providing the user an alternative way to share files.
Sharing the file with Grady.
Option 2: Remove team members from the Owners group so that no one is a Site Owner. This means that they cannot share (because we limited sharing only to Site Owners). The flow service account is made a Site Owner and run the flow using that account’s SharePoint connection. Give the required team members Run-only access to the flow, with the connection set to the service account (so users can request access changes but can’t grant them directly).
This is just a "proof of concept" flow:
These suggestions are just suggestions, and you will need to decide if any of these approaches fits your way of working and security needs.
Ellis Karim
elliskarim.com | LinkedIn | Bluesky
If this solved your issue, please mark it as ✅ Accepted Answer. If it helped, feel free to give it a 🩷 Like!
