Tag Info

New answers tagged

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


0

Once I added Rate Form Owners to the permissions for the page (parent), and gave them Read permissions, my Dev User3 was able to view the page.


0

// get a reference to the folder (this assumes path points to a valid folder) SPFolder folder = SharePointConfiguration.Site.GetFolder(path); // get a reference to the Sharepoint group collection SPGroupCollection spc = SharePointConfiguration.Site.SiteGroups; // get a reference to the group who’s permissions you want to modify for the folder above ...


0

So you could write some CSOM code in C# to set permissions on your folder structure. This code can be run remotely. An example of helpful code though not a solution is here: https://samlman.wordpress.com/2015/02/28/using-the-sharepoint-2010-client-object-model-part-5/ Other approaches running Powershell for example against the SharePoint object model ...


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


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


0

Permissions reset for Access requests The solution was to re-run the original permissions setup of the site, and specify the new Site Owners group as the Owners of the site. To get there, construct a URL like this: http[s]://[HostName]/Sites/[Path-To-Site]/_layouts/15/permsetup.aspx This will open up the groups for the site. Click OK. Once you've ...


0

I'm assuming this is either SP 2010 or 2013 on-premise. You can create an EventReceiver with Visual Studio to listen to the WebProvisioned event, and in this event you give read-only permissions to a user or group etc. Your code in the WebProvisioned EventReceiver could look something like this: public override void WebProvisioned(SPWebEventProperties ...


0

You can grant a user read only access to a site using the following PowerShell. If you're creating the site using PowerShell, tag it onto the end of your script. If you're creating the site through the SharePoint GUI you can run the script from the SharePoint Management Shell afterwards. Set-SPUser -Identity 'domain\user_name' -Web http://yourNewSite/site ...


0

I think you have two options here (although I'm less sure about whether the second option will work): You can set unique permissions on the document library so that it no longer inherits permissions from its parent site. To do this you would go to document library > library settings > permissions for this document library > stop inheriting permissions. ...


0

http://yoursharepointwebsite/_layouts/15/editrole.aspx?role=Contribute But if you uncheck the Edit Items permission, your users will not be able to edit any items or documents. So this doesn't fit your requerement. But htere are no other option to do that OTB, as Edit Items - Edit items in lists, edit documents in document libraries, and customize ...


0

You can go and make a copy of the Contribute permission level and the remove the Edit Items permission. See Configure custom permissions in SharePoint 2013 To specify the special permission level at the Pages library see SharePoint 2013: Break Document Library Permissions Inheritance


0

So... this had nothing to do with SharePoint apparently, as other users with Edit permissions WERE able to add web parts to the (visible) web part zones. We're guessing that out test user has some sort of IE policy setup that is different to regular users. So thanks to all for their help!


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


0

In this scenario I can think of two options: Break inheritance on all files under the Package1 folder so that each file will have unique permissions. Perhaps this option is not practical, though, considering you say there will be potentially thousands of files under the Package1 folder. Make all files under the Package1 folder inherit permissions from ...


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


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


0

You can grant another person permissions to view all items in the list by granting that person Manage Lists permission on your list.


0

If you are looking for granting the user permission through SharePoint Object Model Programming then the below code should help you. Not sure how you would prefer executing the below code. But yes you may put this code in an Event Receiver or Console Application, the choice is yours. SPSecurity.RunWithElevatedPrivileges(delegate() { using(SPSite spSite = ...


0

You could use PowerShell to do this: Set-SPUser -Identity 'domain\user_name' -Web http://siteCollection/site -AddPermissionLevel Read


0

We need to check the user login or anoymous access, then check the permission: SPUser currentUser = SPContext.Current.Web.CurrentUser; if( currentUser != null && !string.IsNullOrEmpty(currentUser.LoginName) { bool permit = item.DoesUserHavePermissions(currentUser,SPBasePermissions.Open); }


0

Go to site collections settings Permissions levels. This is a direct link to it http://yoursite/_layouts/15/role.aspx There press "Add a Permission Level" and configure your custom permission level. Then go to Users and Groups and create a new SP Group with permissions your created in first step. And add users to that group.


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


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


0

We had the same issue in past, In our case it was Browser issue. After removing the user still showing up. so we did the below steps to fix the issue we clear the browser cache restart the browser You can try from different PC.


0

Maybe this PowerShell script helps you to find where the rough permission comes from? It gives you a table of user only permission, and permission via group membership. $urlWeb = "http://sp2010" Get-SPUser -Web $urlWeb | select UserLogin, @{name=”Exlicit given roles”;expression={$_.Roles}}, @{name=”Roles given via groups”;expression={$_.Groups | ...


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


0

Be sure you didn't remove the Style Resource Readers group. This group provides necessary access to the Master Page library and Style Library. To check, go to the site in question Site Actions > Site Settings (or http://yoursite/_layouts/settings.aspx) > Master pages and page layouts > Library tab > Click on Permissions > Check Permissions. Next, check ...


0

Site feeds Activities are publicly accessible unless the activity refers to content that the user does not have access to. If feed functionality is required for a restricted group of users, a site feed should be used. Site feeds display posts and replies among the users of the group. Site feed posts and replies display in the Newsfeed of a user only if the ...


0

You don't need Event Receiver, rather you can do this with custom code along with your InfoPath form. Open your form template in InfoPath Design mode. Under Tools, choose Form Options -> Category -> Security and Trust -> Full Trust. Form Options -> Programming -> C# Now Drop a Button -> Properties -> Edit Form This will bring up Visual Studio Add ...


0

I don't see any other solution other than giving read permission to the root of the Library and then uniquely securing items in the Library so those users will only see Document Set. Below is another Solution you can try out - I hope it should work. Document Set is a kind of Folder. So idea is - Using SharePoint Designer open out-of-the box Welcome Page, ...


0

Users who has minimum Read permissions will be able to see the results. SharePoint security model uses permission inheritance. So top level permission get propagated to bottom levels. So to tackle this you can remove permissions for those users. Or break permission inheritance and add only required users to the site.


0

There is a site feature called Following Content (Enable users to follow documents or sites.). Does disabling this give you what you want?


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.


0

You can make the customize permission in the view only. Then save it as a new permission. There is one thing to open the document in Client Program by default under the advance setting of the document library. So it won't open in the Webapp. Please let me know for more questions.


0

try below code( complete details) function Get-SPUserEffectivePermissions( [object[]]$users, [Microsoft.SharePoint.SPSecurableObject]$InputObject) { begin { } process { $so = $InputObject if ($so -eq $null) { $so = $_ } if ($so -isnot [Microsoft.SharePoint.SPSecurableObject]) { throw "A valid SPWeb, ...


0

Try this Script. I use this for my sharepoint farm in my company. ############################ # # Author: Manish Oswal # Created: 2011-01-07 # Description: Retrieves the users and their permissions from a Site # ############################ # Clear the screen CLS # Stop on errors $ErrorActionPreference = "Stop" ...


0

Use List.EffectiveBasePermissions property to retrieve the effective permissions on the list that are assigned to the current user Use BasePermissions.Has method by specifying PermissionKind.ViewListItems to determine whether current user could access List The example shows how to determine whether current user could access list or not: function ...


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


0

For me the solution was simply to have the user (that was added to the AD group) to log off and on again on his workstation. That updates the group membership.


0

You can set permissions directly for your page layout within SharePoint Designer, but it's no a solution for you. (SharePoint Designer -> Page Layouts -> Permissions -> Stop Inheriting) You have to give 1. full control 2. Contribute 3. Designers Group Permissions in order to be able to work on webparts


0

According to this blog: http://nickheylen.com/2014/05/15/sync-error-we-cant-connect-to-the-specified-sharepoint-site/ You must either give the following persmission: Use remote interfaces Use Client Integrations features Open or If you disable the ‘Limited-access user permission lockdown mode’ feature via ‘Manage Site Collection Features’ at the ...


0

Have you tried adding a Pause in your SharePoint Designer workflow? Add a Pause between copying the the user name string to the People or Group column and your impersonation step. It should last at least 1 minute. I had this same problem and adding the Pause to let the Person or Group column resolve the string did the trick.


0

In the end I got around this issue by having permissions at item level rather than folder level. Originally, permission inheritance was being broken on the folder and all files in the folder were inheriting permissions from the folder. Now, the folder inherits permissions from its parent (the list) and the files within the folder all have inheritance ...


0

Would not this DeactivateProvisioningFeature(); (if it does what it says it does) require higher permissions than AddAndCustomizePages? For example, you would need FullControl at least to enable or disable site collection scoped features.


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



Top 50 recent answers are included