19
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)
{
// ...
17
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.
14
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");
11
Try below code:
This will remove group permission full control
$web = get-spweb http://url/to/your/web
$group = $web.SiteGroups["Owners"]
$ra = $group.ParentWeb.RoleAssignments.GetAssignmentByPrincipal($group)
$rd = $group.ParentWeb.RoleDefinitions["Full Control"]
$ra.RoleDefinitionBindings.Remove($rd)
$ra.Update()
$group.Update()
$web.Dispose()
This will ...
10
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 ...
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);
item[...
9
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
8
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)
{
...
6
Those groups will not be able to access the folders if the permission for the folder is broken and only the group "XYZ" has permissions to the folder and rest all are removed.
UPDATE
Sample powershell code:
$folders = $list.Folders
foreach ($spFolder in $folders)
{
$PermissionLevel = "PermissionName" ;
$group = $web.SiteGroups[$GroupName];
...
6
Yes, it is possible in 2010 to find out who added a particular user to a group and when.
You do need to be collecting audit data.
You can query the audit data with Powershell, for example, to return the information you seek.
Here's a good sample script taken from this blog post:
$site = Get-SPSite "http://yoursite.company.com"
$startDate = Get-Date "...
6
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
6
No, that is not permitted. You could add security groups into the Sharepoint groups if they exist though, distribution lists are not supported.
5
If your AD group is a security group and you are using SharePoint 2013, the way that AD Groups work are a little different. Each time a user logs into to SharePoint, they receive a token that is their identity for the AD groups they are involved with. There is a property of the Security Token Service called Windows Token Lifetime which is the expiration of ...
5
You can get all authenticated users like below
SPUser allusers = web.EnsureUser("NT AUTHORITY\\authenticated users");
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
A crawl is never started by anything changing in SharePoint, neither content nor security changes.
A crawl is either started manually or according to the specified schedule.
If you're using search, then you probably have a crawl schedule set up which does incremental (and sometimes full) crawls. The full crawls with crawl everything and the incremental ...
5
Late answer but, The User Profile is not responsible in this case.
SharePoint recognizes AD security groups and attaching permissions to these groups will cause the permissions to be granted to the User.
Unfortunately, due to SharePoint caching the user's memberships on login, changes made to a security group are identified only after the cache has expired,...
5
You have to include the AD Groups in the user profile sync connection. If your AD Groups are not sync'd with the UPS, then it won't be possible. Make sure the UPS Sync connection includes the containers that the AD Groups are in.
5
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/
5
You can use below snippet
Get-SPUser -Web http://server/sites/yoursite | Where { $_.IsDomainGroup }
AD group is treated as a special user. So this can be find using the filter IsDomainGroup
Update
$SPWebApp = Get-SPWebApplication https://*******.com/
foreach ($SPSite in $SPWebApp.Sites)
{
write-host -foregroundcolor green "Working on Site Collection:...
5
$spWeb = Get-SPWeb "https://spdev"
$GroupName="Group 1"
if($spWeb.SiteGroups[$GroupName] -ne $null)
{
$spWeb.SiteGroups.Remove($GroupName)
$spWeb.Update()
Write-Host "Group Deleted!"
}
else
{
Write-Host "Group doesn’t Exists!"
}
5
You just need a small change to your PowerShell script.
$web = Get-SPWeb http://webUrl
$groupOwner = $web.SiteGroups["GroupA"] #this group will own "GroupB"
$groupTarget = $web.SiteGroups["GroupB"]
$groupTarget.Owner = $groupOwner
$groupTarget.Update()
For all groups in a web:
$web = Get-SPWeb http://webUrl
$groupName = "SharePoint Group Name" #this will ...
5
This is something we built in-house:
function Add-SPGroup {
<#
.SYNOPSIS
Use Add-SPGroup to create a SharePoint Group.
.DESCRIPTION
This function uses the Add() method of a SharePoint RoleAssignments property in an SPWeb to create a SharePoint Group.
.EXAMPLE
Add-SPGroup -webUrl "http://sharepoint.local" `
-groupName "Test ...
5
Considering that you are using a SharePoint group and presuming that the Assign a task step is not running inside an App Step, then make sure that everyone can view the membership of the group.
Go to the group settings page and the select Everyone option under the "Who can view the membership of the group?" question.
The reasoning behind this is that the ...
5
I guess you found "Something went wrong..." in creating the group. The whole point of Office 365 groups is that adding users to the group as members instantly give the access to the sites resources, including files in the document library.
You don’t have to worry about manually assigning permissions to all
those resources because adding members to the ...
4
Sending SharePoint 2010 alerts to an Exchange distribution list.
Create the distribution list/group in Active Directory and assign an email address. Do not use any dashes "-" in the group name.
Edit the properties of the group to change its Group Type to Security (from Distribution). Make sure the group is a Universal group. Only security groups show up in ...
4
I had the same problem, but this solution worked for me
SP Designer WF Email doesn't go to SP Group
All you have to do is:
- Give everyone view acces to the group
Go to the Group Settings, then, set everyone on "Who can view the membership of the group?", click OK
- Add read permissions for the Sharepoint group to the site.
Just be sure to give "read" ...
4
Cause: There is different way to delete permission group, mistakenly I have deleted the group from "Permission Tool->Remove user permissions" which shows permission group deleted but it still doesn't allow creating a new group with the same name
Cause/Solution-> Deleting group from "permission Tool-> remove user permissions" doesn't delete the group if you ...
4
There is no event receiver for users or user groups. So you'll have to create a timer job and do the checking for new groups yourselvers.
Or you can add some javascript to a delegate control (AdditionalPageHead) which checks for the current page being _layouts/newgrp.aspx and if it is hooks the clicked event of ctl00_PlaceHolderMain_ctl06_RptControls_btnOK ...
4
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. ...
Only top voted, non community-wiki answers of a minimum length are eligible
