SP Designer 2013 to use for a specific site collection not for whole web application

Question

I want to use SharePoint designer but as we know by using it we have an access to the whole web application.Is it possible to use SP Designer2013 for only one(single )site collection?Is it possible to lock other site collections ? If then how?

Please help Thanks

Answer 1

As a site collection administrator, you can specify for each site collection if SPD should be enabled or not from the site collection administration page in each site collection.

/_layouts/15/SharePointDesignerSettings.aspx

So if you really have to enable SPD for just one site collection, i would use PowerShell to loop through all the site collection and disable SDP and then enable it for the single site collection where you need to use the designer.

Add-PSSnapin microsoft.sharepoint.powershell

$webapp = get-spwebapplication http://yourwebapplication

foreach ($site in $webapp.sites)
{
    $site.AllowDesigner = $false
}

And then you can set the single site that you wanna use.

$site = get-spsite http://yoursitecollection

$site.AllowDesigner = $true

Update

To re-enable SPD on all the site collections again, simple just run the first script again but change $false to $true

Add-PSSnapin microsoft.sharepoint.powershell

$webapp = get-spwebapplication http://yourwebapplication

foreach ($site in $webapp.sites)
{
    $site.AllowDesigner = $true
}

Answer 2

You can manage how Microsoft SharePoint Designer is used at two levels:

• Web application level which is applicable to all site collections in the web application and to the site collection administrators.
• Site collection level (managed by site collection administrators) which is applicable to all sites in the collection along with the Designers and Owners group.

Note:

In SharePoint, only the Designers group and above can open SharePoint sites in SharePoint Designer 2010.

As Chris Mentioned the Powershell, alternatively you can use the Site settings and Disable it.

Once you disabled it at web app then nobody can use the designer even Site collection administrator. But if you enable at Web app level and try to disable on site collections level then anyother Site collection admin can enable it again.

Another Approach is, it cause more overhead on server, if you move the site collection( which required Designer access) into own web app then disable it on other web apps. But it is expensive in term of server resources.

https://support.microsoft.com/en-us/kb/2592376