Tag Info

Hot answers tagged

10

Answer: One of the groups is not setup as a security group in Active Directory. This still applies to all versions of SharePoint and is most common for nested sub-groups. To verify: Contact the team which maintains AD or check yourself using a tool like ldp: Ldp Overview. Then, change the group to be a security group! Other issues: If you cannot find ...


10

This script should do the trick after few adjustments as its adding new permissions to group which you don't want so you can skip them, function Add-SPPermissionToListGroup { param ($Url, $ListName, $GroupName, $PermissionLevel) $web = Get-SPWeb -Identity $Url $list = $web.Lists.TryGetList($ListName) if ($list -ne $null) { if ...


9

Yup, you've found another SharePoint-ism. You'll need to the add the group like you're doing and then update the item in the SiteUserInfoList. We use the following static method: public static void UpdateGroupDescription(SPWeb spWeb, SPGroup group, string descriptionString) { SPListItem item = spWeb.SiteUserInfoList.GetItemById(group.ID); ...


7

No, you cannot add one SharePoint group into another Sharepoint group. You'll need to use AD security groups within the SharePoint groups to achieve that affect if you don't want to manually add members.


7

AFAIK, it's only possible to use getByName in SharePoint 2013, not in 2010. See MSDN reference for more information var groupCollection = clientContext.get_web().get_siteGroups(); visitorsGroup = groupCollection.getByName("SomaGroupName");


5

You can use AD security groups for setting permissions on Sharepoint sites, lists and items. Some additional recommendations can be found at http://technet.microsoft.com/en-us/library/cc261972.aspx It is possible with some simple permissions planning. You can create Sharepoint group HelpDesk and then set this group to have admin permissions on every site. ...


5

You can't count on that number, as it's just the index within the collection. The AssociatedMemberGroup and AssociatedOwnerGroup properties on SPWeb should give you what you're looking for without having to know the actual name of the group.


5

You can get all authenticated users like below SPUser allusers = web.EnsureUser("NT AUTHORITY\\authenticated users");


5

Prints out all the groups for the SPWeb and the group's role names: using (SPSite site = new SPSite("http://server/sites/sitecollection/")) { using (SPWeb web = site.OpenWeb("test")) { foreach (SPRoleAssignment roleAssignment in web.RoleAssignments) { if (roleAssignment.Member is SPGroup) { ...


5

SPWeb root = site.RootWeb; SPGroup group = null; // Check if the group exists try { group = root.SiteGroups["The Group Name"]; } catch { } // If it doesn't, add it if (group == null) { root.SiteGroups.Add("The Group Name", member, root.Author, "Your Group Description"); group = root.SiteGroups["The Group ...


5

Internally, all users resides inside a special list known as "user information list" at the root site (/) of any SharePoint site collection. This list can be accessed through http://yoursitecollection/_catalogs/users/simple.aspx Groups are virtual collections of users against this list maintained inside the SharePoint Content Database and have different ...


5

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


4

Yes, the owner is important because other than site collection admins, they are the only ones that can manage that group. Yes, you can have another sharepoint group be a group owner.


4

yes it is, look at this Post or this Video showing how to create contact list for sharepoint 2010 EDIT Just got what you wanted to do If the idea is to just use that list as a web part, then i suggest you to look at Site Users web part and add the web part to the landing page, this web part allows you to configure the SharePoint groups that you ...


4

You can use SPContext within a "RunWithElevatedPrivileges" block, but objects you get from "SPContext" such as: SPUser, SPWeb, etc. are not running in elevated privilege, they just take the current user security context. So why not just use "scweb" to get to the "Group". Since "scweb" object is initialized within the "RunWithElevatedPrivileges" block just ...


4

Groups are created at the site collection level only. It is only what permissions that group has in the sub site that is maintained (in a sub site with broken inheritance) in the sub site See this for more information: ...


4

Move this line var groups = currentUser.get_groups(); To your getCurrentUser method and make sure to load it this.clientContext.load(groups); before executing the request, this way you will have it loaded in your success-function


3

If you convert that view to a data view web part in Sharepoint Designer, you can build your own sorting logic and you should be able to sort by the nodeset average.


3

Were any other changes made outside of SharePoint? I know Exchange has an option to set distribution groups to only be available for use by "authenticated or trusted senders" (this prevents email/spam from the internet from being sent to internal distro groups). We ran into this problem, because SharePoint does not "authenticate" to the Exchange server, it ...


3

It can be achieved by editing the permission level for a group and revoking the View user information permission.


3

A few guidelines/best practices: Apply security at the highest level possible; so first set permissions at the site collection level or even the farm. Then set permissions on the site, then, if necessary, set unique permissions on objects (pages, lists, etc.). SharePoint security works much like Windows folder security: Children inherit from parents unless ...


3

In general, security groups are used for permissions, but distributions are not. You can overcome this by mail-enabling security groups. In this manner, they can be used both for permissions and audiences. PLUS for an Exchange admin, you don't have the hassle of dealing with multiple groups with the same members for the two purposes.


3

To clarify SharePoint's permission behaviour: Sites collections contain the people (users, AD groups) and groups (SharePoint groups) that are available for all sites within the site collection. The idea is a site collection contains sites that have some overlap in user membership or business function. They are a collection of like-minded sites (in some ...


3

The LCID number is wrong (the fourth parameter), it should be one of this list instead than 123: http://msdn.microsoft.com/es-es/goglobal/bb964664.aspx The US-English is 1033. Remember also that if you try to create sites with a non administrator user you should use RunWithElevatedPrivileges method.


3

You need SPWeb.SiteGroups (MSDN link) which includes all groups that exist in the site collection. For further details, please refer to: http://blog.tylerholmes.com/2007/09/spwebgroups-vs-spwebsitegroups.html


3

I just did something very similar to this, should be plenty of pointers. Code below. You are welcome. My code is running as a timer job and synchronizes user groups across several site collection sharing a managed path in a web application. The code uses the following variables: _webApplicationToSynch is the absolute url to the web application. ...


3

You can't. SharePoint groups are only available to sites within the same site collection. You can use AD groups if you want to have groups that span multiple site collections or farms.


3

You are most likely receiving this error because the group membership can only be modified by the group owner. If you open the Group settings page - you will see a setting that governs who can edit the group membership. There are two options; Group owner and Group members. In the object model it is governed by the Boolean property ...


3

After much research, we found that SharePoint not only caches the token for the logged in user, but also for the groups to which that user does or doesn't belong. Setting the cache expiration as described here fixed everything up. $stsc=Get-SPSecurityTokenServiceConfig $stsc.LogonTokenCacheExpirationWindow = (New-TimeSpan -second 30) $stsc.Update() ...


3

If you want to assign permissions to particular pages (think hard about this if you are going to have a lot of pages as you can run into performance issues) you need to break the permission inheritance on the page library, remove all the permissions in the library except for the Full Control/Owners group, then add your pages with your desired permissions. ...



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