New answers tagged

0

You'd need to setup the token timeout expiration. Via PowerShell script it would look like: $sts = Get-SPSecurityTokenServiceConfig $sts.FormsTokenLifetime = (New-TimeSpan -minutes 10) $sts.WindowsTokenLifetime = (New-TimeSpan -minutes 10) $sts.LogonTokenCacheExpirationWindow = (New-TimeSpan -minutes 1) $sts.Update() iisreset Explanation ...


1

Does this answer you question: http://www.nothingbutsharepoint.com/2011/05/20/active-directory-groups-vs-sharepoint-groups-for-user-management-a-dilemma-aspx/ There are some differences in using ad groups vs sharepoint groups. One of the differences is that you can't view the members of an ad group in SharePoint. So a people picker with the limitation on ...


0

You probably need to grant them read access on the top level of the site to have access to the site aspx pages. You could even restrict that access to only the site assets and site pages library if needed. Making them a group owner in no way gives them rights anywhere else.


0

try this one using (var ctx = new ClientContext(webUri)) { ctx.Credentials = credentials; var groupCreationInfo = new GroupCreationInformation { Title = groupName, Description = groupDesc }; var groupOwner = ctx.Web.SiteGroups.GetByName("Tech Support"); //get an existing group var group = ...


1

There is a known limitation related to send SPD workflow e-mails to AD groups. Basically AD groups are seen by SPD as a regular user... let's remember that AD groups have properties like e-mail, name, login and everything else. So, the SPD can't understand that you are trying to send e-mails to everyone inside that group. What you can do is create something ...


2

You can create the group in SharePoint and send de email to the SharePoint Group. Let me explain. Understanding that you can not configure Exchange, I think there is no solution using AD groups. The alternative I propose is: create native sharepoint groups and associate users directly to SharePoint groups. I know that probably you prefer to manage AD ...


0

Can you try to execute this powershell and check "IsHiddenInUI" tag ? $web = get-spweb "siteurl" $group =$web.SiteGroups["groupname"] $group


0

Can you try to get all groups and check if corrupt group is found. Also try to delete group through group ID.


4

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 ...


1

SPGroup.ContainsCurrentUser() is also an option. You can get the HR group as usual and check if the HR group contains the current user. Then, it's just about hide/disable that button.


1

You can do it by code also: if (SPContext.Current.Web.CurrentUser.Groups.Cast<SPGroup>().Any(g => g.Name == "hr Group")) { show button } else { hide button }


0

A way to do this without code, using just InfoPath and the browser user interface: create a new SharePoint list "AuthorisedStaff". Add a Person field and a text field called Account to that list. Use InfoPath to customise the list form and create a rule to write the selected person's Account into the Account field. Add all people who should see the ...


0

There are two types of task actions in SharePoint Designer: 'Assign a task' and 'Start a task process'. The former is only meant to assign a task to a single person. The latter is meant to assign a task to multiple people and therefore has the ability to expand SharePoint groups. In your case you want to "Start a task process" and then assign it to a ...


1

Just add the group A as the owners of group B. It's in the group settings. Go to the group like you would to add someone, then Settings -> Group Settings



Top 50 recent answers are included