Tag Info

Hot answers tagged

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.


6

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


4

this worked for me. var ctx = SP.ClientContext.get_current(); var list = ctx.get_web().get_lists().getByTitle('Calendar'); var item = list.getItemById(121); item.resetRoleInheritance(); ctx.executeQueryAsync(function(){alert('success')},function(s,a){alert(a.get_message())}); if you are opening the OOTB EditForm from a link on your custom CEWP, execute ...


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.


2

Step 1: For Level 1 - Open Library in the ribbon at top under Library option . There is Share With as shown in below image Share With --> Advanced --> Stop inheriting. Here you will manage level 1 permission Stop inheriting permission and give read access. Step 2: For Level 2 - Click ... next to folder at level 2 and again ... like below image - There you ...


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


2

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


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


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

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.


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.


1

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


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


1

Set the default page in SharePoint You can set the page as your home page. There should be an option in the ribbon for this when at the page in question. Publishing features need to be enabled for this option to appear. Alternatively, you could check site settings. In look and feel you should be able to set a welcome page. You can also set this in ...



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