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 ...
7
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,...
7
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
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
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.
6
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:...
6
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
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 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
$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
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
if you are working on SharePoint 2013 Version, then it is easy to get current user groupcollection through rest api in javascript.
script would be like this :
function getCurrentUserGroupColl(UserID)
{
$.ajax
({
url: "/sites/dev/_api/web/GetUserById("+UserID+")/Groups",
type: "GET",
headers: { "Accept": "application/json; odata=verbose","X-...
4
If you need the Group Name, unfortunately there is no direct way to do that. But we can get the current user and get user collection for one group. Then you can check the user collection from one group to see whether it contains the current user.
https://stackoverflow.com/questions/6428300/get-current-users-group-using-the-sp-2010-javascript-client-side-...
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:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/e6981b2b-924b-4b0c-bcb8-4f9748119170/add-new-group-to-subsites-...
4
The code should look like this:
function getCurrentUser() {
this.clientContext = new SP.ClientContext.get_current();
this.oWeb = clientContext.get_web();
currentUser = this.oWeb.get_currentUser();
this.allGroups = currentUser.get_groups();
clientContext.load(allGroups);
this.clientContext....
4
Not sure why it could be empty - perhaps was deleted at some point (this has happened to me before). You can set the owner by visiting _layouts/permsetup.aspx of your site collection.
4
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 ...
4
The error you get with your code when used for a subsite is because you use Get-Site with a subsite Url.
Instead of Get-SPSite use Get-SPWeb as below:
Get-SPWeb http://server/sites/yoursite |
Select -ExpandProperty Groups |
Where {$_.Name -EQ "your group name here"} |
Select -ExpandProperty Users |
Select Name, Email
The code above will find the group only ...
4
$SiteCollection = "http://site/sitecollection"
$ADGroupName = "domain\adgroup"
$SPGroupName = "My Test Group A1"
$SPGroupDescription = "Test Group A1’s Description"
$SPGroupPermission = "Read"
#Start of script
$site = Get-SPWeb $SiteCollection
#Check if the group already exists
if ($site.SiteGroups[$SPGroupName] -eq $null)
{
#Ensure Group/User is part of ...
4
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 (i.e. ...
4
I tried your code and got an unknown error. So i tried removing each field in the LINQ query and I found the error is due to grup => grup.Owner. I have changed it to grup => grup.OwnerTitle and the code worked fine. Also for getting each property value of a group loop the group collection object and get its value as per below code.
GroupCollection ...
4
One of my favorite ways to automate repetitive tasks is to use PowerShell + CSOM.
The Client Object Model allows me to run my scripts on top of on-prem SharePoint or Office 365 using the exact same code, so I don't have to migrate it in order to make it run in one or the other.
Here is an example of how you use the client dll in a PowerShell script to ...
4
It doesn't matter where you create them, groups only exist in one place, the site collection root. Creating them anywhere makes them available everywhere in the collection.
4
The cons is obviously that you won't be able to add users to a group in SharePoint, and you have to manage AD-groups instead. If you already have 10'000 SharePoint groups in your environment, you may have to rethink how granular you're setting permissions.
But it's true that above 10'000 groups per site collection there are performance issues:
Above 10,000 ...
4
For adding user to group, instead of REST API I used JSOM, now I didn't get credentials pop up. :)
Adding users to a group with JSOM using following code::
addUserToSharePointGroup: function (loginName, success, failure) {
var _this = this;
var clientContext = new SP.ClientContext.get_current();
var siteGroups = clientContext.get_web().get_siteGroups(...
4
Try this code below :
GroupCollection groupColl = clientContext.Web.SiteGroups;
Group newgroup = groupColl.GetByName("InternalUsers");
clientContext.Load(newgroup);
clientContext.ExecuteQuery();
Only top voted, non community-wiki answers of a minimum length are eligible