Tag Info

Hot answers tagged

4

No, that is not permitted. You could add security groups into the Sharepoint groups if they exist though, distribution lists are not supported.


3

If you only want to hide the list from "All Site Content", the SPList class has a "Hidden" attribute. If you set this attribute to true, nobody will see the list via "All Site Content", but you can still access the list with the direct link. You could set the "Hidden" attribute with Powershell or a console application, for example (or do it at feature ...


2

You need to Stop Inheriting permissions from the parent site, and then you will see Anonymous Access option, click the option and set to None.


2

You can use spsecurity.runwithelevatedprivileges to edit the list from the application. Go through the below link on how to use the above method. No need to give user any special permissions. Give edit permission to the application pool account. That should solve it. If you want to save the user name as well in the list you can do by creating a new column ...


2

So I figured out that the html for the "PurchasingSearch" page was not published. Both the .js and the .html need to be published.


2

You are out of luck. a SP group cannot contain any other SP group. It’s a big limitation.Although SharePoint groups can contain (AD) users and AD groups. Check this Technet: http://technet.microsoft.com/en-us/library/cc262690%28v=office.15%29.aspx http://www.spdockit.com/blog/permissions-management-sharepoint-2013-part-two/


1

I would just make one document library with three folders, uninherit those folders to make unique permissions, and then create a workflow that takes the document and moves it to a different folder. You can create a view that looks at all documents and the folder it's in.


1

In a feature event receiver upon FeatureActivating, get a handle on your list and set it to hidden, http://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.splist.hidden(v=office.14).aspx This will hide it from the All Site Content and still give users the ability to add items to it. If anyone did know the underlying list name, they could ...


1

Break permissions from top site. Then either make a new SP group and add a user to the group or Invite a user to the page and give him permissions. First method is much easier to maintain in the long run. Worth remembering: The Top level admin can read this page and if you are using SharePoint online the global admin will still be able to read ...


1

The "contribute" access rights consists of "add", "modify" and "delete" access rights. You may try to create a customized access right to allow only "modify", i.e. without "add", nor "delete" access rights. User who is assigned to this customized access rights would be only able to update the existing entries in the list, so as to trigger a workflow, but ...


1

Mike's alternative is the easiest to implement. You can also implement a Web Service to do the required actions for you and lastly (and I guess what you really want), you can try to implement the calls listed in this article in successive HTTPSend activities. The JQuery version of the REST calls are listed below. // Change placeholder values before you ...


1

One way of elevating code is, as you already mentioned, using SPSecurity.RunWithElevatedPrivileges which will run SPSecurity.CodeToRunElevated with Full Control rights. From MSDN documentation of the method for SP 2013 (http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsecurity.runwithelevatedprivileges.aspx) you can see that this code runs ...


1

I assume you do have the group in another site collection where you can look up what permissions the group have, and just create a new group with the same permissions. Go to another site collection where you got the group intact and go to Site settings > site permissions > permission levels. From here select "Style resources reader" to see exactly what ...


1

Powershell You can use Remove-SPUser command as shown below: Remove-SPUser "Contoso \jdoe" -web http://test/web1 The following script can also be used (and converted into relative C# code) Function RemoveUser($LoginName,$SiteUrl) { #Get site $Site = Get-SPSite | where {$_.url -eq $SiteUrl} If($Site) { $Web = $Site.openweb() ...


1

you can set the filter on the list view, like this Having done that set the modified view as default and delete all others views, as administrator create a new view but as Personal View, so only you can see it. And for disable the alerts, follow this link None of this solutions are 100% efficient if the user are not set in groups Good louck with that.


1

I made this same mistake and selected the two key users who would be administering the site in the future, assuming my domain admin account would still be able to log into the site. In Central Admin, go to Application Management > Change site collection administrators. Set one of them (primary or secondary) to yourself.



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