Hot answers tagged

3

SharePoint permission levels are defined at the site collection level Source (2013) : https://technet.microsoft.com/en-us/library/cc721640.aspx Source (2010) : https://technet.microsoft.com/en-us/library/cc721640(v=office.14).aspx Source (2007) : https://technet.microsoft.com/en-us/library/cc721640(v=office.12).aspx Being a site owner or subsite ...


3

Allow users to add items to list from custom web part - On default new form put a script to navigate to page which says - "New item cannot be added from here" or alternately add content editor on new page with text " New item cannot be added from here" and hide (not delete) the existing web part on page Prevent same group of users to view/edit items ...


3

Break permission inheritance of that document library. Remove other users. Then only assign permission to the owners. This will hide the library from other users.


3

Answers of your questions: You will need FullControl permission to create group. No. You can take reference from here. No. SharePoint uses an App Only context it really doesn’t matter what rights the end user has on the content – all that matters is what rights have been granted to the App. Because the App can effectively run with elevated privileges ...


2

You can try the below mentioned script. This will list user with all its memebership. $user = Get-SPUser -Web https://http://server/sites/yoursite | Where{$_.LoginName -LIKE "*|domain\user"} $User Get-SPSite http://server/sites/yoursite -Limit All | Select -ExpandProperty RootWeb | Select -ExpandProperty SiteUsers | Where {user.UserLogin -EQ ...


2

Spfarm account and spadmin account following accounts required the SecurityAdmin and DB_Creator on SQL Server.When you provision any service using the farm account then SharePoint will set the permission. All the required permissions, Role automatically fixed during the provisioning process. I never saw any issue to manually set the permission within farm. ...


2

I would argue that the reason these libraries have unique permissions is precisely the opposite of what Ankit Kumar is suggesting. In Ankit's answer: these libraries deal with configuration of the site collection and is generally used for referring any scripts /site images and any style sheets. Hence these library have unique permission where ...


2

SOLVED: After lengthy research I was able to come up with a working solution. // Break Inheritance from Parent library newFolder.Item.BreakRoleInheritance(true); // Remove 'Visitor' group from permissions SPPrincipal principal = (SPPrincipal)webDst.SiteGroups["Visitor"]; ...


1

Workflows operate under the context of the initiator. You would only need to use an AppStep (which is the new impersonation model from 2010) if the user that initiated the workflow process doesn't have the ability to do what the particular actions are going to do. So in your example, no, you wouldn't need to use an AppStep to update a list item because ...


1

Here's the deal. You can create a default view with access to only a specific user group. There are ways to implement this. Also, from all views, remove link for new item and remove column with context menu. Additionally you can put some javascript to not allow advance ribbon except admin group or something. Alternatively. You can put some javascript to ...


1

Remove the NewForm and EditForm from the list. This way nobody can create or edit list items.


1

It is by design, I think this has some connection with Publishing. But one thing I know for sure, If you change the permission on any of these System Libraries, you will break the things in your Site collection. Typically peopler removes the Style Resource Reader group from the permission as this include the All authenticated User in it. But as soon you ...


1

I manage over 400 groups and faced the same issue. I don't have Farm access and use SharePoint 2010 so I don't know if this would work for 365. Our group name format uses the subsite name and permission level. I use a script in a Content Editor Web Part on the main site to display all the groups and users. Then I can Ctrl-f through the list to find a ...


1

I tested your script and found the problem. The answer is here http://stackoverflow.com/questions/35225511/sharepoint-csom-copy-roleassignment your last lines should be: # Apply the permission roles to the list. $clientContext.Load($folder1.ListItemAllFields.RoleAssignments.Add($usr, $usrRole)) ...


1

Create a form load rule that checks to see if the user is an admin or not, and switch views depending on that condition. For example if current user not admin, switch to Edit view.


1

After further search, we found out that some stored procedures might be used with Microsoft support. Examples of unsupported database changes include, but are not limited to, the following: [...] Calling existing stored procedures directly, except as described in the SharePoint Protocols documentation And the proc_SecResetItemPerm is documented in ...


1

Consider using the Repair method available on SPContentDatabase objects, documented by Microsoft here. You can invoke this from Powershell (once the SharePoint Powershell snapin is loaded) like so: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue $databases = Get-SPContentDatabase $databases | %{ $_.Repair($false) } If you're ...


1

It seems like a permission issue. Make sure the group members can be viewed by everyone and not only by group members.



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