2

If you go into one of the libraries and to the good old advanced permissions view you can use the "Check permissions" button in the ribbon and type in the user in question. This will tell you which group the user has access through. The Office 365 group is automatically added into the SharePoint Groups, owners in the owner group - members and guests into ...


2

Thanks @RuneSperre for your solution. It worked. Below is the working script Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue $users= "" $users = import-csv D:\User.csv foreach ($user in $users) { Add-SPOUser -Site $user.SiteURL -LoginName $user.UserEmailAddress -Group "$($user.group)" Write-host "User added:" $user.SiteURL $...


1

Best way to handle permission is create a SharePoint access group name as access database group with Read or Contribute permission as per your your need - add all the authorized users there, then as Rune suggested in previous answer, go to the list permissions setting page, stop inheritance to break the parent permission structure, remove all users and ...


1

If you go to List Settings, then Permissions for this list, you will see how the permissions for the list is configured. It is probably inheriting permissions from the site (that is the standard setup). What you want to do is to click the button Stop inheriting permissions. This will leave the permissions intact, but any changes to the permissions to the ...


1

The Access Denied error is possibly triggered because the workflow itself doesn’t have permission to edit the list item. Please check if you have Workflows can use app permissions feature activated via Site Settings > Site Features. You can also try writing the workflow actions in App Step in SharePoint Designer 2013 to grant elevated permissions to the ...


1

As an alternate way to overcome this issue, we can add user or group at the site level, then on folder level apply "stop inheriting permission", finally remove all users or groups which you do not need at the folder level, and retain the one which you want to assign permissions. And also, try deactivating the feature "Limited-access user permission ...


1

Not possibly purely in SharePoint, as you suspected.


Only top voted, non community-wiki answers of a minimum length are eligible