7

Manage Files With No Checked In Version: Go to Library Settings and click the "Manage files which have no checked in version" link. If users have uploaded files but not checked them in, the users who uploaded the documents will be the only ones who can see them. Fortunately, the site owner can take ownership of checked out files, then check them in. Version ...


5

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>


5

Permission inheritance, and the breaking of inheritance, is in the realm of user access. A user authenticates herself to the environment, usually Active Directory, which verifies that the user is authentic. The user proves to the system that the user really is the one she claims (pun intended) to be. So now the system knows who she is. The next step is ...


4

OOTB not possible. To generally describe, your requirement would be to show list items from a parent site in the way the built-in Promoted Links do display. Because we can only query list items from a parent site by using Content Query Web Part, the Promoted Link's way of displaying the links is not available. If you are open for customization, you may ...


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

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 the ...


3

First, you don't declare Content Types via CAML. You declare them using XML. CAML is the Query-Language used to query lists. If you declare Content Types via XML and deploy it by a Feature, the Content Type is created/updated on site collection level. However, if you use a Content Type in a List, then the list contains a child of that Content Type, which is ...


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

Users need to have access to the site. That's why there is a permission level called Limited Access. Looking at the description of the Limited Access permission levels, you’ll see that it allows users to access objects “when given permissions”. With that permission level they will be able to see the objects they can access, but not the site itself. Users ...


3

Yes, breaking inheritance does not affect the content type or site columns which are created in parent site... Content type connection will retain between parent and child. Hope this helps...!!! Please mark it as answer if helpful.!!!


3

If you stop inheriting permissions, the users with access remain to have access. You need to remove the users that are copied over from the parent. Next to that option, some users have persmissions as a site collection admin, or on the web application level in Central Admin.


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 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

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

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

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

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

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

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

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 ...


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

If you reestabilish the inheritance, the folder with broken inheritance will keep the broken inheritance. So, it doesn't break unique permissions on children. Anyway, you can try it yourself simply creating a new test library and setting and breaking inheritance. I tried it my self too...


2

If I understand your question properly then, If you click Delete Unique permissions, then all the permissions you've set uniquely will be deleted. After breaking the inheritance, if you want to remove the groups then select the names of the groups/users and click Remove User permissions. The group/users (you delete here) will not be deleted but their ...


2

The user will need at a minimum read permissions to the library. If they go into the library, they will only see the folder they have permissions to. If you want them to be able to edit files, then you'll need to give them read access to the site. What exactly is being called by the client applications (Word, Excel) I don't know, but in testing super ...


2

When you use BreakRoleInheritance with $true or $false you do the following : you are assigning the folder with unique permissions. Any new permissions added to the item are only applied to the item. Only the difference : $true to copy role assignments from the parent object to this object; $false to assign only the current user to security roles. So For ...


2

Since you're the one that created the library and are able to adjust the permissions in the first place, are you and your team site collection owners? If so, that would supersede other permission assignments, meaning those users would always retain access to all content within that site collection (essentially, Full Control). The other possibility would be ...


2

Your setup looks correct and should behave like you are imagining. It has been our experience that using AD groups sourced from on premises AD can take upwards of 72 hours for the permissions to actually fully propagate from Azure AD to all services in Office 365. This has been a particular pain point for a few of our sites where automated processes in ...


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