In this case, you already know that we're asking SharePoint to add permissions to a specific item/file. Make sure the method is Post (this means we're sending information to the server and asking it to store it somewhere or make a change).
However, since we're either setting the permissions to a SharePoint group or User, there are two different scenarios we'll need to cover.Īdd the Send an HTTP request to SharePoint actionįor the Site Address, select or enter the site where your list or library is. To do this, we'll just use the Send an HTTP Request to SharePoint action Next, we'll use an HTTP request to get the Group or User Principal ID
So here, all we need to do is use the Initialize Variable action, give our variable a name (I'd call it something like varGroupNameID to keep things more organized), and make sure that the variable type is an Integer. Luckily, we can do this using an HTTP Request.įirst, we need to Initialize a Variable so that we can store the Principal ID somewhere. We need this Principal ID so that SharePoint will know what group we're setting the permissions for.įor example, if I have a group named " Sovereign Employees Group" that I want to just be able to just have Read rights, I would first need to get the Principal ID of the "Sovereign Employees Group". The next thing we need to do is get the Principal ID of the group or person that we want to set the permissions for.
#MICROSOFT PRINCIPAL DEFINITION HOW TO#
Without further delay, let's see how to do this using an HTTP Request: So, if your list/library has permissions set to a specific group, all the items/files/folders will "inherit" that permission setting and have the same permissions, unless the inheritance is broken and you want its permission settings to be something else (which of course we do).Įssentially, breaking the inheritance means the item/file won't have any permission settings for the moment. If you don't know what breaking inheritance means, remember that breaking inheritance on an item in SharePoint means that the item (or file) will no longer "inherit" its permission settings based on the list (or library). That being said, if you follow these next steps, you should be updating your permissions in no time. Of course, this does make them more complicated and tricky to implement correctly. The great part about them HTTP Requests is that they can be customized to do more than just the Out-of-the-box functionality that the Stop sharing an item or file or Grant access to an item or file have to offer. To help us change the permissions (update data) for a specific item in SharePoint. So, as you can imagine, we're going to be using the Send HTTP request to SharePoint. They do more than that, but for our purposes, we'll just keep it to these three things. HTTP Requests essentially add, update, and get data. If you haven't heard anything about HTTP Requests, here's the simple run down: Using HTTP Requests to Change Item Level Permissions I imagine there will be a day when Power Automate will just have available all the permission actions that are needed, but for now, we can at least be grateful for HTTP request that can get the job done for now. Grant access to an item or a folder in SharePoint to specific people. Power Automate has a few "Security Actions" that allow you to do simple permission changes as you can see below: That being said, if your situation isn't too complex, you might be in luck. Using the Security Setting Actions Already Available Take it from me, who learned Power Automate and Power Apps without any previous coding knowledge AT ALL.īecause of this, I hope my explanations of what we'll be doing will make more sense to you, as it has only just recently made sense to me. But be assured, once you've done this a few times, it will make much more sense and you'll have it down in no time. This solution does require a bit more "coding" or whatever you'd like to call it. This post will also help you become more aware of what Power Automate is capable of as well as replace more of your SharePoint Designer workflows - if that's what you're trying to do, of course. In this post, we'll be going over how to do all of these things using Power Automate (Flow)! If you've used SharePoint designer before, you know how easy it is to change item level permissions by first breaking the inheritance (List/Library Level Permissions on the item/file) and then adding new permissions for a person, people, or a specific SharePoint Group.