List rules
Hi everyone, since the legacy list alerts have been retired and rules came in, users with read permissions are not able to create rules without leveraging the power automate service. in my opinion read inly users should be able to create alerts based on a separate role action. at the same time, alert related action are still active under permissions level options. is there anyone else trying to provide rule action to read only users and is so how did you proceed? Kind regards, George StylianouSharePoint Library Help Needed
I have a SharePoint Library where I would like to implement these requirements below and would appreciate your advise: Folders were created at the library level, which looks like the image below. I do not want people to be able to create any folders or upload documents or folders at the library level, but rather only when they open the folders. I have disabled folder creation and created a PowerApps form, so that users can only upload document, edit documents, view details of the documents when they open any of the folders., but I cannot seem to find the Power Apps form when I open any of the folders and try to upload a document or view a document or edit the document details. 2. I have a choice column called Fiscal Year which has options as = FY22, FY 23, FY24, FY25, FY26. By March 2026, I would like to create an automate flow which will auto create FY27 and remove FY22 from the choice, so that the choice column is always limited to only 5 years.
SharePoint permission change notifications not working
Problem: Trying to get Microsoft Graph change notifications when permissions change on SharePoint/OneDrive drive items (sharing, inheritance breaks, access grants/revocations). Using Prefer: includesecuritywebhooks on subscription creation as documented subscription creates successfully, but the header appears to be silently ignored (notificationQueryOptions is always null in response, Preference-Applied header is always empty). What works: Regular content change notifications fire fine. What doesn't: Zero security notifications on any permission change. Subscription request: POST https://graph.microsoft.com/v1.0/subscriptions Prefer: includesecuritywebhooks { "changeType": "updated", "notificationUrl": "https://...", "resource": "drives/{driveId}/root", "expirationDateTime": "2026-06-12T00:00:00Z" } Permissions (all with admin consent): Files.Read.All, Files.ReadWrite.All, Sites.Read.All, Sites.FullControl.All, Directory.Read.All Already tried: Both v1.0 and /beta endpoints same result Every relevant permission combination But the official document says it should work: Link to documentation: https://learn.microsoft.com/en-us/onedrive/developer/rest-api/concepts/scan-guidance?view=odsp-graph-online#receiving-webhook-notifications-for-security-events Any working example or confirmation of current status would be extremely helpful. Happy to share more details or test specific configurations.
Moving Files from a Shared Drive to a SharePoint site
Hi, I've seen the moving of files from a Shared Drive to a SharePoint site can be tricky, depending on the size of the files that are to be moved. What is the best and most effective way to move folder, files. I'm not sure yet of the number of folders and size of the files that will need to be moved? Can anyone provide an advise on this, please.. Regards ChrisHow to hide the Modify this view and Create View as per users available in groups
Hi All, I have classic view of SharePoint in list/libraries. I have group(for Managers). I just want want to show and hide the Create View/Modify View/Modify this view depends on users available in group. If user available in group(for Managers) then they can do anything like Create View/Modify View/Modify this view but if user is not a part of the group(for Managers) then they can not modify any Public views but the can create Personal view. Is there any way how I can achieve this functionality?Accessing External Sharepoint Site
I am able to access internal Sharepoints within my company and have up until now been able to access Sharepoints outside the company. When I now try to access an external Sharepoint, I get the following message on the external company's landing page. "Your account has been locked. Contact your support person to unlock it, then try again...." The external company states they have not made changes any access protocols. Likewise, my company says nothing has changed with respect to the rules/ability to access external Sharepoints. Someone indicated that the Microsoft “federation” settings/setup of the two companies may (now) be incompatible. Has anyone encountered this issue?
SharePoint Permissions Management
Over the last 3 years of managing permissions across a suite of sites, I have uncovered more new issues with the way SharePoint permissioning is designed at every turn. A few examples, before the question: If I "Share" a file or folder somewhere on the site (breaking permissions inheritance), it is very inconvenient to find it again. If I "copy link" in this one particular way, permissions inheritance is broken. When looking at site-level permissions, I see site-level permissions groups, but there could be hundreds of other users who have been added to my site(s) without my knowing. If I want to reset permissions in an area (set of folders or library), I have to do it file-by-file or folder-by folder. If I want to get an excel snapshot of - anything really - IT has to pull it and it takes a couple days. Not to mention the permissions interface is incredibly clunky. All-in-all, there seem to be a million ways to break permissions inheritance, creating an access tracking and security nightmare. AND there's no easy way to truly see and understand who has access to what or what is broken, without spending hours with IT to pull a bunch of narrow-visibility reports. So my question is: what is the best way to navigate full permissions visibility? Am I doing something wrong? Is anyone else experiencing these issues? We have resorted to having a very strict "no outsides besides a few exceptions" policy and only managing permissions at the site-level, which really hampers on the collaboration benefits that SharePoint is trying to enable. It is also very administratively intensive. One of the benefits to SharePoint is that users don't really need to understand how it works to use it, but that's becoming less and less true with the increasing lack of security we feel in the platform.
