Tag Info

New answers tagged

0

The answer is very simple . just go to List 1 >list setting >permissions for this list> grant permission > Enter the group name "Group 1" ,select permission level "read" N.B: you have to break inheritance before doing all this. Repeat this steps for list 2 and give "contribute" permission


0

Beauty of SharePoint is that you can assign different permission to Item Level Break inherit permission for both list and than assign permission to both list manually. To break inheritance for a list or library and restrict access to it, follow these steps. 1) Navigate to the site that contains the list and open it. 2) Choose the List tab to open the ...


1

There's a thousand ways to skin a SharePoint site structure but I think the best is by permissions. When you create your structure, group sites, libraries, and lists together, based on permissions. You do this to avoid running into the administrative nightmare of updating permissions in 355435634 different places. The easy way out (that'll cost you in ...


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


0

Break the permissions on each list and then reassign the permissions on each list for that group


3

Use ItemUpdating instead of ItemUpdated and set properties.Cancel = true. You can add optional message using properties.ErrorMessage. Edit: Now I see it's obsolete in SP2013 and you should use properties.Status instead. Possible values are decribed here: SPEventPropertiesBase.Status. Added: If error message is displayed as an Exception with CallStack make ...


0

For SharePoint 2007, there is the SharePoint Administration Toolkit which has a Permissions Reporting Tool. If you need the Visio aspect, you could possibly try taking the output of this into a data connection in Visio.


2

You could create a custom permission level that did not give users add rights. They would simply have edit rights. This would allow them to curate content, but not be allowed to add new wiki pages. Only those with the default contribute address would be able to add new pages. Outdated screenshots, but the process is the same, ...


3

Click on "Settings > List settings" On the settings page choose the view "Detail View" Check "Selection Checkbox (checkboxes) " Click OK


0

I'd done this task with Designer workflow 2013 and REST API as follow reference sites - link [link2] (http://www.fabiangwilliams.com/2014/06/19/gotcha-on-sharepoint-designer-workflows-in-app-step/) Hope this should work for the same!!


1

Usually for resources in the Style Library, they must be published before normal or anonymous users can see them. Through your browser, on your windows authentication site, go to Site Contents and then your Style Library. Find the items that are not appearing for anonymous users, check them out, and when you check them back in make sure you choose to publish ...


0

Audience Targeting would be your best bet if you're using a web part since it will only load the part if a user falls into specific groups.


1

Using out of the box workflow actions you can't do it because of security limitations. As solution I would like to suggest to have a look at a Plumsail Workflow Actions Pack. It is extended set of workflow actions for SharePoint Designer which also contains a set of workflow actions for permission management. I'm one of developers of the product and I'm ...


1

There is no OOTB feature in sharepoint that let's you hide columns from specific users based on permissions. If you want to do that, you have to create script code with MS powershell on your server farm to do this. You can use workaround - create two lists. First of them should has unique permission for the specified user, second - lookup column to the ...


0

in SharePoint Workflow 2010, there is action called "Replace", it will stop inheriting all parent permission to current item , and assign new permission to current list item in below i have replace Current item level permission , group XYZ with Contribute permission , Here is workflow action:- "Replace Contribute of item in Current Item" u can do same ...


0

This is very easy to do. Just select a folder/library and hit the "share" button. Simple. Though, check out Office 365 Groups, as they provide essentially a team site with pre-baked functionality. It may meet your needs better than a customized team site.


8

The simple process of setting item level permission is not available for SharePoint 2013 workflows. The only way I was able to do was through REST api called under Appstep. There are 2 calls made: BreakRoleInheritance AddRoleAssignment This blog by Yuri Leontyev​ ​ over at spssite.pro can be a good start. Excerpt: BreakRoleInheritance​ ...


1

under Advanced options in webpart options, you have at the bottom option named Target audience. you can look there and check if that can help you.


0

The following JSOM code worked for me to get all the users of a 2013 site, not sure about 2010. Openn the site in chrome. Copy the whole code and run in console. Doesn't work in IE. var JSONToCSVConvertor = function (JSONData, ReportTitle, ShowLabel) { var arrData = typeof JSONData != 'object' ? JSON.parse(JSONData) : JSONData; var CSV = ...


1

Open with explorer uses Windows Authentication to work. Even if you disable it in SharePoint, any user with proper access in the server will be able to map it and read documents. That said, there exists a way to disable that option in SharePoint at least. Check: http://ballyhoo4u.com/disable-open-in-windows-explorer-on-sharepoint/. This is for 2007. For ...


1

Yes Yes And smart people who read this will understand Open with Explorer is just a WebDav connection to a server where they have at least Read rights. Maybe the easiest lockout is to extend a MasterPage script with: window.NavigateHttpFolder=function(){alert('Open with Explorer is prohibited')}; That will scare of most users.


0

You can simply loop through all SPRoleAssignment in item.RoleAssignments. The Member property gives you the user (actual user or AD group) or the SP group, and the RoleDefinitionBindings gives you the associated role(s) for that member.


-1

User must check in document (and publish) it so other users can see and edit it.


2

Has the user checked in the documents? The documents he added might still be checked out to him. Go to Library settings -> Manage files which have no checked in version to see these documents.


2

"Limited Access" permission is not a permission in itself. It is simply a prerequisite for being granted any other permission on content within the site. For example, if you take a person that currently has no defined access on the site at all, and grant them Read or Contribute permission to an individual list item, they will automatically also receive ...


6

Only limited access don't work. Read is the minimum required access on the site. Also make sure permission of the list is not broken.


0

User with Site Collection Permission will be able to grant you back your lost permissions.


2

Provide READ permission to this group on the site first. Then it will work for sure.


0

Ask to someone who has higher permissions on the site. Or if you can access to the centra admin, set you as site collection administrator for that site.


1

ask someone who has permission to the site or the site collection administrator. There is no other way


3

I just tested this on SharePoint 2010 and for OOTB permission levels, it looks like you would need the Design permission level at a minimum to access the Workflow Settings in a list/library. You can also have the Manage Hierarchy permission level, but this would give you a lot more access than to just the Workflow Settings.


0

I have confirmed with Microsoft Support that he can reproduce the issue. I think it is just another poor design Microsoft did.


0

I found two solutions on this site: Accessing Group Permissions From PowerShell Using Reflection One solution is with powershell and other one with C#. Both methods use reflection so you should not use it in a production system, in other environments use it at your own risk. # inject fake context $site = Get-SPSite("http://intranet.contoso.com") $web = ...


0

Maybe the group does not have any permission, run this to get the permission for the group: $urlWeb = "http://yourPortalUrl" $web = Get-SpWeb $urlWeb foreach($roleAssignment in $web.RoleAssignments) { write-host -foregroundcolor green "Group Name: "$roleAssignment.Member.Name "..." foreach($roleDefinition in ...


1

You can check the permissions of a user using the 'DoesUserHavePermissions' method. See code sample below. However in order to return all the sites you need to loop over all the sites and site collections. This is very resource intensive! I would not recommend it on a webpage or when the code will execute a lot. On a webpage you risk getting slow page ...


0

"Items" and pages can have different permissions. You should break permissions of the document libraries and surveys first, then compile the pages that hosts those items. At this point you do not really need to split permissions on pages because even if people navigate to the page with items they should not see, they will not see it (they will see the page ...



Top 50 recent answers are included