New answers tagged

1

Have you tried restoring the site from a different web application/farm recently? One of the things I would try is to change the site collection administrator from the central administration or may be using the account admin, which is already working and try to give the access to admin2 again. Let me know what error you get.


0

Yes, break inheritance on the List and assign them directly via individual or group permissions.


2

I think that this could be your solution: Add a User or Group to the SPWebApplication User Policy for all Web Applications in the farm The interesting code should be Get-SPWebApplication http://sharepoint2010 | foreach { $webApp = $_ $policy = $webApp.Policies.Add($userOrGroup, $displayName) $policyRole = ...


1

Do I have to call executeQueryAsync twice? Once to get the list items and the 2nd to act on all of them? Yes. Your first query gets the list of items (declare them in the parent scope, obviously, so that they are accessible on the success callback), and in the function of success callback, you can iterate through them to fire individual queries to modify ...


1

If you delete a user from site collection then user will not able to access the site collection. But that user will not be deleted by SharePoint, his profile will stay in User Profile Service. If you delete the user profile from SharePoint(UPA) then next import run will bring it back. If you remove the User from AD group then it will removed from ...


0

That depends on what level of protection you need. If the Excel file has a workbook password to even open and read, then no, that won't fly. Consider removing the workbook password and use sheet protection instead. People will be able to use formulas that reference locked cells on a protected sheet. If they open the workbook they will not be able to make ...


1

This can be done using a Designer WF and REST. The hard part is going to be if you need to allow multiple users to have access. Basically, you will need to add a field to your forms that you can enter the users. A people picker or text field will do. The text field can make it more likely that mistakes will occur, but I think will be easier to parse out ...


1

Yes, you can go back into the group settings after you have created the group and set the group owner to the group itself.


0

Just create a page and add a List view web part - in 2013 this is just insert -> Web Part -> select library. You can customize the view on this page and then set permissions to this page. Don't use audience targeting as mentioned above as this isn't security. SharePoint is security trimmed, so if you add the page to the quick launch, if a user doesn't have ...


0

You can catch permissions changing just in SharePoint 2013 (I did it in On Premise version) : public class MyClass_PermissionEventReceiver : SPSecurityEventReceiver { public override void RoleAssignmentAdded(SPSecurityEventProperties properties) { base.RoleAssignmentAdded(properties); } public override void ...


0

I was also looking for some options along the same lines but obviously individual permission is the only solution available. Another workaround - the way I designed the site was based term store navigation and then a sub-site for each term-set. Once we have achieve this we can set up the rules to move the documents to the individual site's document ...


0

Have you checked the permissions on the list itself, by the sounds of things, the list may have different permissions to the page


0

As explained before, but I will summarize it in here, the user of the workflow can't make REST calls to other sites or subsites by default, you should give the sites and subsites the permission to the workflow to make those calls. To be able to do it, first Allow your workflow to be used as an App by activating the feature Workflow can use app permissions ...


0

Found a solution myself: It does not seem to be possible to create a new Group using CSOM. Nonetheless: This is not neccessary to create a new taxonomy. Instead the default Group of the sitecollection can be used: termGroup=termStore.GetSiteCollectionGroup(siteCollection, true);


0

We can inherit the user permission from the site collection by site actions-> site permission. There you will find the inherit permission option in the top ribbon. It will inherit all the access permission from your base site. But before that you must the access group like "Visitors", "Consatruc in your base site (site collection) Then only it will inherit ...


0

This has worked for me also. You will need the O365 Management Shell also if not installed. It will need to be run as Administrator. https://www.microsoft.com/en-gb/download/details.aspx?id=35588 Somewhat surprised issue has not been fixed!


-1

Take a look at SPDash, it does exactly what you're looking for. I've used it to manage multiple site collections and it works great.


0

I had the same symptoms on a SharePoint 2013 On Premise SP1 and October 2015 CU problem was I ensured the user using the windows login name: domain\username e.g: var user = clientContext.Web.EnsureUser("dev\administrator"); with this user, IsSiteAdmin returned False (he was definitely directly added to site collection admins) also with this user I did ...


0

If you are breaking the permission, then you need to assign unique permission to the folder, When you are creating the folder, take the folder object and use this folder.BreakRoleInheritance(false, true);... This will break the inheritance of the folder, now you have to define a role and do the role binding to the folder.


1

You won't be able to give different permissions then what is set on the entire site without breaking the inheritance. That's exactly what you are looking to do is break inheritance. If you use the Share button it will automatically break inheritance for you if you do it from the list view of the Site Pages or Pages library (wherever your page exists). ...


3

Yes, it's still valid, as it's still a SharePoint. You can read more about the limits at TechNet site: https://technet.microsoft.com/en-us/library/cc262787.aspx As you can see limitation are the same for SharePoint 2013 on premise and SharePoint online


0

Step 1: Navigate to your site. Step 2: Go to Site Actions ->Site Permissions Step 3: Click Stop Inheriting Permissions button. Step 4: Remove all the groups Step 5: Create Group named managerUser using Create Group button from ribbon. Check Contribute option in Give Group permission to this site section Step 6: Create Group named VistorUser using Create ...


0

Have you checked that within the Set Permissions module, that you are not removing the already existing permissions on that item (breaking inheritance). The list item permissions will most likely inherit from the List to begin with.


0

SharePoint doesn't provide a facility for securing individual columns, I mean OOTB. The lowest level SharePoint operates at is security on a whole list item. We can modify the NewForm.aspx or EditForm.aspx or DispForm.aspx to restrict certain columns to be read only or hide by checking permissions with the help of ECMA script and JQuery. Another possible ...


0

When you create a document library, it by default, inherits permissions from the parent site. This means all the groups continue to have the same access on the doc lib that they have on parent site. However, you can set unique permissions on a doc lib and set necessary access to selected groups. Manage permissions for a list, library, folder, document, or ...


0

If you checked all the SharePoint Groups for your domain group an then there could be at least three additional ways these users could have access: You have the Authenticated Users group in one of your SharePoint Groups You have Anonymous Access configured You have an AD group configured for access in the Web Application's Permission Policies


1

This often happens when you have the "require checkout" option enabled on the library. To check this, try uploading a file and see if it immediately gets the little green overlay on its icon, indicating that it is checked out. From the Library Settings page, click the link to manage files with no checked-in version. You should see a view of all the ...


-1

I was able to pull the membership of a 2013 SharePoint permission group that had 2035 members using the following steps. Note that I wanted the account name only. You may need to modify this process slightly if you want a different field, or more than one field: Page through the group to find out how many members it has Go to Settings/Site ...



Top 50 recent answers are included