Tag Info

Hot answers tagged

6

You have to break permission inheritance on each document that you want to protect. Go to the document library, select the options menu (...) and the additional options (...) and select Advanced > Shared with. On that view select advanced and click on the ribbon button "Stop inheriting permissions". Add the group/users who should have access to the ...


2

If you have custom security definitions defined inside your source site, they will not be retained in the template as they cannot be expressed using the declarative language the template uses internally. Your only option really is whether or not to inherit from parent at site creation, as Ransher suggested above. You'll need to manually recreate the ...


2

By default a Visitor group assigned to Read Permission level. Read permission level has following permissions: View Application Pages Browse User Information Use Remote Interfaces Use Client Integration Features Open View Items Open Items View Versions Create Alerts Use Self-Service Site Creation View Pages So, their is no add item permission it. Now, if ...


2

I've had this happen to me and it's because I started a new IE browser that thought I was still logged in with owner permissions. I always test with Chrome or Firefox so that I know there are no cached account details.


2

You can add users to multiple groups, as well as you can give direct permissions. So once user login SharePoint will evaluate the permission and assign the top most. For ex: If user is in Reader Group and user is an owner of library. Then user can add documents only to that Library while he will be able to read from all other places (like list, pages etc.) ...


2

Visitors with read permissions cannot add normally. I would try logging into the site in a different browser, preferably Chrome in Incognito mode to be sure that is the case. Sharepoint has an awful habit of caching credentials even though you think you've signed out.


2

You can write an event receiver for your list that handles permissions of the item. You should use ItemAdded event receiver. Some links event receivers: https://msdn.microsoft.com/en-us/library/office/ms437502(v=office.14).aspx https://msdn.microsoft.com/en-us/library/office/ms453149(v=office.14).aspx and link about managing permissions ...


2

I feel you, I had the same problem, therefore I only can tell you about my experience and you need to see whether it matches your problem. What I need to mention at the beginning is, that the visibility of those settings come with the "Permission Level" of a group. I have implemented a Document Library on a site, where users can post document sets and ...


2

In order to get this to work, the user doesn't have to be a member of the site, but the user need the permission level Manage Hierarchy on the document to be shared. In your case that applies to the Document Set. To enable this, browse to the Document Set in question (with a user having Full Control of the Site/Web/Document Set) and select the Manage-tab at ...


1

The problem is probably that SPRoleAssignment is using the ID of the passed in oUser, but the user with that ID in http://<<server>>/websites/gwp/ is very unlikely to be the same user as the one with that ID in SPContext.Current.Web unless SPContext.Current.Web is http://<<server>>/websites/gwp/. So you need to change ...


1

Using listItem.BreakRoleInheritance(false, false); to break inheritance for Folder1 is correct, if you want to have unique permissions set from this level on. But if you want Folder2 to inherit from Folder1 and Folder3 from Folder2 (which basically means both inherit from Folder1) you CANNOT use BreakRoleInheritance. This will break inheritance of ...


1

To get the access inside the Site collection you need be as Site collection admin or Full control. You get this done by this. This will give the access to one site collection: From central admin > application management > change site collection admin On this page from drop down select the web app > site collection which admin you want to change, ...


1

In Central Administration, follow the Application management link and select Change site collection administrator. Change to your site collection and set yourself as site collection administrator (primary or secondary doesn't matter). Being a Farm Admin doesn't automatically give you all the permissions on site collection level. Direct URL: ...


1

You can create a subsite under site collection, which will be a parent subsite, and then your other subsites can be children subsites to the newly created parent subsite under site collection, In this way you can define groups at parent subsite which can be inherited by all child subsites OR you can break permission at all level and Run this script to give ...


1

Limited Access is a permission level that is automatically assigned to SharePoint users and groups when they are granted access to an item/objects which causes permission inheritance to break. For example, if you grant a user access to an item on a list but not the list itself, then the user is assigned Limited Access to the list and it's parent site/s. ...


1

if (fldrItem.RoleAssignments.Count > 0) { SPRoleAssignmentCollection assignColl = fldrItem.RoleAssignments; foreach (SPRoleAssignment assignment in assignColl) { if(assignment.Member.Name == group.Name) { //Now you can look into the associated RoleDefinitions from assignment } } }


1

Out of the box SharePoint only supports receiving email to specific types of lists and libraries. For instance, you can receive email on an Announcements list, calendar list,discussion board and libraries. However, you cannot receive email on custom lists. As a workaround, either you use an announcement list or library and customize it according to your ...



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