Tag Info

New answers tagged

1

I would just make one document library with three folders, uninherit those folders to make unique permissions, and then create a workflow that takes the document and moves it to a different folder. You can create a view that looks at all documents and the folder it's in.


0

It might not be te most elegant solution, but this will get them into which ever group you put as $group. If your AD is on-prem follow this first. If they are already synced to your Azure AD, then just run the below code. function Connect-SPOSite() { param ( $admuser = "user@tenant.onmicrosoft.com", $admsite = ...


0

Using EnsureUser works http://msdn.microsoft.com/en-us/library/office/dn499819(v=office.15).aspx#bk_WebEnsureUser Just pass the GroupName and you can get the principalId of the group


2

You are out of luck. a SP group cannot contain any other SP group. It’s a big limitation.Although SharePoint groups can contain (AD) users and AD groups. Check this Technet: http://technet.microsoft.com/en-us/library/cc262690%28v=office.15%29.aspx http://www.spdockit.com/blog/permissions-management-sharepoint-2013-part-two/


4

No, that is not permitted. You could add security groups into the Sharepoint groups if they exist though, distribution lists are not supported.


0

There is a hidden list in your site collection at /_catalogs/users. See this explanation. If the user has yet never been assigned to a group, there is no entry for her / him in the list, that means there is no SharePoint user for the account. If the user is assigned first time to any group, the SharePoint user should be created first. If the user, who ...


0

Attach a event recevier and add item added / updated event to it for assigneing permission. First break permission on item and then add required permission as per item status / metadata.


1

There is no limit officially suggested by Microsoft on the number of Email recipients. (Check this) But, still if the recipients have not received the email. You may want to look for following, Whether none of the receipient received the mail or its just few of them. They may want to check the Junk folder :) There could be firewall issues(blocking the ...


0

The issue is that my environment allows both Claims and Forms authentication. Because of this, it is necessary to convert a LoginName to a WindowsClaim. I did this by hardcoding "i:0#.w|" to the start of the LoginName and everything worked. I don't know if this string is the same for everyone, but you can find it by looking at the details of a user that ...


0

If the problem is still occurs, try this PowerShell script: Add-PSSnapin "Microsoft.SharePoint.PowerShell" $site = Get-SPWeb -Identity http://<Your site address> $listname = "Members" $list = $site.Lists[$listname] $users = Get-SPUser -Web $site -Group "<The name of the required group on $site>" -Limit all foreach ($user in $users){ ...


0

Instead of changing the STS configuration as suggested in the blog posts, I'd suggest to just clear the Logon Token Cache. Clear-SPDistributedCacheItem –ContainerType DistributedLogonTokenCache



Top 50 recent answers are included