Forum Discussion
Chad_V_Kealey
Aug 13, 2018Iron Contributor
Allow Custrom Scripting on a specific SP site
Some of our departments have made use of custom templates in SP doc libraries in our old 2010 environment and want to do the same in their Group-connected site in Office 365. However, trying to uploa...
Anonymous
Aug 13, 2018try Set-SPOSite -identity "site here in quotes" -DenyAddAndCustomizePages $false
Chad_V_Kealey
Aug 13, 2018Iron Contributor
Deleted, no dice. Same message. Based on what it says, it seems like the change can only be made to site which are "managed paths" in the tenant, but I'm not sure exactly what that means or how to make a site a managed path. To me, it seems logical that sites created by a SharePoint admin (via the admin center or Powershell) would, by default be considered "managed", while Group-connected sites (created by end/non-admin users) may not.
- AnonymousAug 13, 2018Group connected and classic sites should all work the same that's odd your getting that message.
- Chad_V_KealeyAug 13, 2018Iron Contributor
I'm trying this using an account with the SharePoint Admin role (not Global Admin). I wonder if that has something to do with it? It shouldn't (IMO), because it's strictly a SharePoint thing I'm modifying; it shouldn't have any bearing on anything else in O365.
- AnonymousAug 13, 2018Ahhh, yeah that's probably going to be it then. They still haven't quiet got that ironed out yet with the roles. Does it let you explicitly assign your user account as site admin using
set-spouser -loginname user@user.com -site "siteurl" -issitecollectionadmin $true
I know if your just a group owner and not explicitly assigned that can cause issues too. If you get same error trying to do that for yourself then it most likely is the global admin issue.