Hot answers tagged

9

No, you cannot add one SharePoint group into another Sharepoint group. You'll need to use AD security groups within the SharePoint groups to achieve that affect if you don't want to manually add members.


4

This has to do with how SharePoint "builds" content types I think. It needs to know where to find the parent, or more specifically, the parent's original schema (XML). If Inherits is set to true, it will include the parent's fields directly in its own schema, when this is not the case. it will always require a schema to be based on, which can be found in the ...


4

You can use <Contains> condition with CAML and filter on ContentTypeId column pass the value of "LanguageItem" ctype ID. You can also use BeginsWith <BeginsWith><FieldRef Name="ContentTypeId"/><Value Type="Text">ctypeID</Value></BeginsWith>


3

Reseting role definitions could possibly lead to an inconsistency if new definitions have been added and used in assignments. That's why, I presume, you canno't revert définitions without also reverting assignments. I checked in the SharePoint OM assemblies, and even internally there's no method to revert defintions only...


3

It is tricky, and I think there is no straight forward way to retain the unique permissions when you roll back to inherit parent's permissions. If you read and compare the definitions of SPWeb.BreakRoleInheritance and SPWeb.ResetRoleInheritance You will notice that SPWeb.ResetRoleInheritance has no parameters to pass where we can instruct SharePoint to ...


3

Create an Event Receiver. In Visual Studio, right click project => Add new item => Event Receiver => Web Events, Handle the following events: A Site is being provisioned. The following override will be generated and fire on every new site creation. Just insert the code within: public override void WebProvisioned(SPWebEventProperties properties) { ...


3

The OOTB master page uses the ~site token as the URL to surround the site logo, just change this to ~sitecollection/ (the trailing slash is necessary) or even / depending on your particular requirements. In v4.master the section to change is at line 297 and should wind up looking something like: <SharePoint:SPLinkButton runat="server" ...


3

There is nothing significant in those base classes apart from throwing ArgumentNullException when properties is null. So there is no harm in calling it, but there is no harm if you miss it. If do call it, you should call it before your code Instead of setting Cancel Property to true, you should set an appropriate value for Status property. According to ...


2

That's the way I have always understood it to work...i.e. resetting inheritance at the subsite levels causes any broken inheritance to be removed from the lists and libraries in that subsite. NOTE: That it shouldn't break the affect the inheritance setting of any folders within those lists and libraries. I don't know why for sure, but can guess that the ...


2

Get a site collection administrator to reset the permissions inheritance. This will reset permissions to what exists on the site. Then you'll have full control again and can reset permissions.


2

I know this is an old post, but incase somone comes across it, you do not have your list settings correct, or your content type is defined in the work place. In GENERAL (exclude content hubs for now) Content types are defined at the site level, and available to the sites under them. SO I typically (but not always) define the at the site collection root. ...


2

In order for this link to show up I think you need to have the Publishing Site and Web features activated. If my memory serves me I think activating the Publishing Web feature inherit at least the master page. Perhaps the Theme as well.


2

This attribute first appeared in the RC version. I'm not sure of the validity of having a custom content type with: an ID which derives from an existing one using Inherits=FALSE. I'm also not sure if an appropriate error is raised in this scenario (if it is indeed invalid). In the absence of more detailed documentation, I think the only thing we can ...


2

To answer your first question -> All SharePoint groups actually live at the root of the site collection. http://office.microsoft.com/en-ca/products/default-sharepoint-groups-in-sharepoint-server-HA102772365.aspx (Look specifically for the text "If you are on a public website, you will see Members in your list of SharePoint groups. For example, if Contoso ...


2

You can reset the subsites to inherit the master page of the parent site in the masterpage option located under Settings -> Site Settings -> Look and Feel -> Master Page. This option is disabled by default in the Team Sites to activate it you have first to activate the SharePoint Publishing features. Note: The Team Sites in the SharePoint 2013 inherit ...


2

Anytime you add a user directly to a subweb/list/folder/item SharePoint will add this user at the root with Limited Access in order to ensure that the user will have access to "Support files" like master pages, ... You could argue that this isn't needed if the user already has access by being in a group, but then SharePoint would have to check if it needed ...


2

When your app works when used by a Site Collection admin then it has the permissions it needs and adding more permissions isn't going to change anything. What you then need for it to work for ordinary users is what you started on by adding AllowAppOnlyPolicy. But just adding AllowAppOnlyPolicy won't change anything except that it'll grant the app ...


2

I know this really should not be an answer, and should be a comment on the accepted answer, but apparently I cannot add a comment. In any case, I have a potential solution to the problem of the Inherits attribute, and needing to set it to True so you can publish content types correctly vs. needing to set it to False so that you can preserve your declarative ...


2

There are two posts that may be useful (with good caveats) regarding Content Types & Inheritance: Rob Windsor's Custom Content Types and Inherits in SharePoint 2010 Serge Luca's SharePoint 2010-Content Types and Inherits : the good, the bad and no ugly


2

I'd say to use folders with unique permissions on the folders where needed but then in your views, choose to show items without folders. This will security trim everything so users still only have access to what they need but you won't run into performance problems with item level permissions. The files in the folder inherit permissions from the folder, ...


2

SPContentType contentType = curWeb.ContentTypes["Custom CT Name"]; SPField field = contentType.Fields["ArticleStartDate"]; contentType.FieldLinks[field.Id].Required = true; contentType.Update(); Use the FieldLinks property of the contenty type. There are quite a lot of examples explaining using this property. Refer msdn as well : FieldLinks


2

You can inherit the navigation via: SPWeb web = parent.Web.Add(/*params....*/); web.Navigation.UseShared = true; Use it just after you have created the site. More Information: MSDN


2

The powershell script below allows for enumeration through a SharePoint 2010 web application to identify all sites, document libraries, lists, folders and items for which the permission inheritance has been broken. This script should be executes using a SharePoint 2010 Management Shell on one of the SharePoint servers in the farm with an account allowed to ...


2

Your Level 2 sub folders will automatically inherit from your Level 1 folder. It is up to you if you want to break the permission inheritance at each Level 2 subfolder. That is also possible. However, my general recommendation to clients is not to establish folder level permissions since it is very difficult to manage with the out-of-the-box interfaces in ...


1

The answer to this problem is solved by retrieving the site collection administrator. private static void AddManagerToList(SPSite site, string listTitle) { try { var web = site.OpenWeb(); var list = web.Lists.TryGetList(listTitle); if (list != null) { ...


1

All subsites do by default inherit permissions from their parent. Someone (or something, code, workflow etc) must break the permission inheritance for a subsite to get unique permissions. This post describes how to do that in the GUI: http://m.dummies.com/how-to/content/break-inheritance-permissions-in-sharepoint-2010-t.html


1

Do you want a group to see only one list, or list to be available to only one group? Either way there's no need to break role inheritance on all lists. SharePoint groups are created on site collection level, you cannot add a group only for a list. What you need to do is: Create new group without assigning any permissions on site level Break role ...


1

For pushing changes to the children you should specify as $ct.update($true) See the function signature http://msdn.microsoft.com/en-us/library/office/ms475130%28v=office.15%29.aspx


1

Have you considered creating a new content type (CT) but just adding the same Body Column to it? That way you can treat it as a parent CT and not worry about the consequences of editing any of the OOB Columns for the Announcements CT.



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