New answers tagged

1

You just need a small change to your PowerShell script. $web = Get-SPWeb http://webUrl $groupOwner = $web.SiteGroups["GroupA"] #this group will own "GroupB" $groupTarget = $web.SiteGroups["GroupB"] $groupTarget.Owner = $groupOwner $groupTarget.Update()


0

The original error indeed occurs when digest has been expired or it could not be retrieved ( e.g. SharePoint:FormDigest control is not available on the page) on the page. There are some another issues with the provided example. For updating list item the following parameters need to be specified: method: "POST" headers: "Accept": ...


0

I've just upgraded my SharePoint Server 2016 Beta 2 to Release Candidate, and so far this option isn't available. In Office 365, you have this option: Trying to do the same in SharePoint Server 2016 RC, you get the message that you need to disable a feature first: Said and done, lets disable the feature: Now we have our Sharing option, but still ...


1

This simply isn't supported. SharePoint needs to be able to make those calls as well, e.g. PowerPivot (call is translated from NT AUTHORITY\ANONYMOUS to the target caller). You will just need to communicate this to your security folks.


0

did you tried adding authorization rule in web.config file. eg. for specific sitecollection <location path="sub-site/_vti_bin"> <system.web> <authorization> <deny users= "?" /> <allow users = ”*” /> </authorization> </system.web> </location> refer below link for further details : ...


0

Your Directors example suggests you need to be able define a one-to-many group relationships and then check within these groups to verify if the person accessing a list item has been granted access. This type of logic is not available by simply "customizing" permissions settings in the user interface. But if by "customizing" you mean writing code, then ...


1

Deny All - Anonymous users cannot have any access, even if site administrators specifically attempt to grant the anonymous user account access to their sites. For more information about it, see Manage permission policies for a web application in SharePoint 2013 and also Overview of security groups in SharePoint 2013


0

Policy will change. Management will change. Everything will change. Deny all option give you a quick way to change back if necessary.



Top 50 recent answers are included