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


2

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


0

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


0

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


0

Eureka! I figured it out! Apparently claims expiration needed to be set to a lower time window. I don't understand why a bunch of Microsoft patches would require that but apparently SharePoint was having an issue verifying my permissions with AD. I ran the following commands from the link below. Command Prompt: stsadm.exe -o setproperty -propertyname ...


-1

I don't know what you are passing in $web. But If you groups from specific subsite than you need to give specific subsite URL in your $web to get all groups for given subsite URL. UPDATED CODE //Pass Subsite URL to get only subsite groups $web = Get-SPWeb http://server/sites/yourSubSite function GetWebGroups($web){ ...


0

did you find any solution to this? We are experiencing this same behavior in a customer's environment. We added some libraries with individual permissions and they show up in every user's Site Content and navigation. Those users cannot see any content of the libraries, but simply being able to see them is not welcome. This only affects some librariess and, ...


0

Move the project list from the subsite to the top site and have a link to the subsite. If they can read the list they can see the data in the list even tho they cannot access the subsite.


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


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


0

Maybe someone will have a better solution, but for me I would create a simple SharePoint Group in your subsite, with few permissions (just for example "enumerate permissions") granted for all authenticated users. And after a full crawl see if it works.


0

Yes the Site Collection Images and Site Assest/ Style library have a different set of permission when created. Because 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 general users are forbidden to access /or ...


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"]; ...


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


0

SharePoint groups are defined on Site Collection level, not on list level, so what you did was that you deleted the User Group from the site collection, thus it was removed from all items within that site collection.


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


0

This is simple and the way is the same in all SharePoint versions. You use SharePoint groups to manage permissions for users. In each site you'll find groups, and each group has a different set of permissions. For example the Owners group, which has full control permissions level on your site, would be your choice for let's say user1. You would use Visitors ...


0

Have come across this in one environment. We tried to solve it with MS Support, but were not successful. The last thing MS said was that SharePoint was OK, it was just getting wrong token from the AD - so the error was outside SharePoint in our case. They did not provide us with root cause analysis anyway, so we still are facing this issue and using ...


0

For 1st question, you can open your site with SharePoint Designer > Lists and Libraries > Company. In Custom Action click create. Then create an action maybe call "start workflow" and in type of action choose initiate a workflow. In the Rights Mask field you may insert "ManageWeb" so that only user with "Manage web" permission can see the action button. ...


0

You can't achieve this out of the box. Work arounds I can think of Create views for each group Create a page and add those views into the page as web part. Audience target each web part to each group. This will hide web part current user is not part of. Disadvantage is if user is part of more than one group then user will see multiple views on the page. ...


0

Check Drop off library, if users break inheritance and remove users from it, this is exactly what happens, it just happened to me today


0

If you are the Site Collection Administrator of the site you should be able to delete the items, else contact the Site Collection Administrator to perform it.


0

I have also now fixed the error which the script had that was unrelated to the question and this script should now work as intended. ### Get the user credentials $credential = Get-Credential $username = $credential.UserName $password = $credential.GetNetworkCredential().Password $securePassword = ConvertTo-SecureString $password -AsPlainText -Force ### ...


0

Make sure that the 'Read' permission level in your site actually has Read Permissions. Follow these steps : Site Settings>Site Permissions>Click 'Permission levels' in ribbon>Click 'Read'>Ensure it has correct list and site permissions for viewing(For example,"View pages in a Web site") You can also fine tune here how your 'Read' permission level will ...


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


0

The problem was Library Settings -> Versioning Settings -> Draft Item Security -> Who should see draft items in this document library? I found the answer in some replies to a closely related issue posted on Technet. I thought it was a permission problem with anonymous users and lookups but it affected all new data entry in the libraries. My lookups were ...


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


0

Make sure your anonymous user can browse to and view both lists - the list in question here and the list where you're creating the lookup from. There is a special setting to allow anonymous users to view list contents that can only be set in powershell.. SPList.AnonymousPermMask


0

Unfortunately no, that is one of the drawbacks. Each time you create an app, the database is actually created in azure. There is no way to separate user’s ability to edit and read various tables. In other words, it does not support role based permissions.


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


0

Maybe I'm missing what you are trying to accomplish but why wouldn't you just create a table or div in the top of the in the table after the </sharepoint:SPSecurityTrimmedControl> <!--Hide Ribbon if Read Only Permissions --> <Sharepoint:SPSecurityTrimmedControl ID="SPSecurityTrimmedControl2" runat="server" ...


1

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


0

A user with Contribute permissions cannot delete a public view. They need at least Design permissions to do that. Be sure to check the permissions on the list, since it may not inherit the perms from the parent site. don't know that one Why don't you restore the view from your backups? Also, a list view should not be too hard to create. List views are not ...


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.


0

I thinks that the SPService is the way to go, it looks like something easy enough to implement, and there seems to be alot of guids on how to. Another question. If one wants to go a step further and populate some of the lists with some external data (make them dynamic), instead of manually create the items. Maybe use some Navision tables to derive data from ...


1

It is not possible to have cascading dropdowns (behavior that you are describing) in OOTB SharePoint forms. There are third party solutions (both farm solution and add-ons) that add this functionality to lists. You can also have a look at SPServices jquery library and add this functionality yourself to the form. This does require some javascript development ...


0

[SharePoint Online] I've had this problem too, it was not the App principal that was returned but the site admin as current user. The problem for me was that I had not yet added this to the app manifest: <AppPermissionRequests AllowAppOnlyPolicy="true"> <AppPermissionRequest Scope="http://sharepoint/content/sitecollection" Right="FullControl" ...


1

If you can use custom solution then please refer the following steps Create a custom SharePoint solution Create an Event Receiver with ItemAdded and ItemUpdated event In the event handling use BreakRoleInheritance(false) function Now set the custom permission which you want over the item created and iten updated The problem which might be exists here is ...


0

Refer this link: http://spcycle.blogspot.in/2012/01/how-to-create-workflow-to-change-item.html It will show you how to set item permission manually and using workflow.


1

I reviewed your code but i think your top bar control should be within SPSecurityTrimmedControl Tag not CssRegistration Tag. Please go through this article Hide ribbon from users without Edit Permission let me know if this is helpful or not Thanks


1

If the sub sites are inheriting permissions from the root parent site.then giving permissions at the root site via group should be sufficient - simplest way If not there is no other easy way as you need to give either manually to each sub site or write a custom powershell /C# console via object model or CSOM and give the permissions through code.


0

You'd need to setup the token timeout expiration. Via PowerShell script it would look like: $sts = Get-SPSecurityTokenServiceConfig $sts.FormsTokenLifetime = (New-TimeSpan -minutes 10) $sts.WindowsTokenLifetime = (New-TimeSpan -minutes 10) $sts.LogonTokenCacheExpirationWindow = (New-TimeSpan -minutes 1) $sts.Update() iisreset Explanation ...



Top 50 recent answers are included