Maximum Number of Users to Display in SharePoint Hierarchy (SPUSERCAP)
By default, up to 45 SharePoint Users can display beneath a site in the SharePoint Hierarchy
(Note that the Users folder contains only SharePoint users who have been granted direct permissions for a site.)
ControlPoint Application Administrators can, however, modify this number by changing the Maximum Number of Users to Display in SharePoint Hierarchy Value.
If the number of SharePoint users is greater than the specified parameter value, the list will be truncated. For example, if you set the Maximum Number of Users to Display in SharePoint Hierarchy Value to 10, and 12 users have direct permissions to a site, the first 10 users (in alphabetical order) will display in the Users folder. (Remember, however, that the total number of users with direct permissions for the site displays in parentheses to the right of the user folder.
Maximum Number of SharePoint Groups to Display in SharePoint Hierarchy (SPGROUPCAP)
By default, up to 45 SharePoint Groups can display beneath a site in the SharePoint Hierarchy.
ControlPoint Application Administrators can, however, modify this number by changing the Maximum Number of SharePoint Groups to Display in SharePoint Hierarchy Value.
If the number of SharePoint groups with permissions to a site is greater than the specified parameter value, the list will be truncated. For example, if you set the Maximum Number of SharePoint Groups to Display in SharePoint Hierarchy Value to 10, and 12 groups have permissions to a site, the first 10 groups (in alphabetical order) will display in the Groups folder. (Remember, however, that the total number of groups with permissions for the site displays in parentheses to the right of the Group folder.)
Maximum Number of Users to Act On (MAXUSERSFORACTION)
By default, when you want to run a ControlPoint action that operates on SharePoint users, up to two thousand (2000) users may be included in the operation, as determined by the People Picker entry. Before running the action, ControlPoint evaluates the number of users included in the People Picker entry, and if it exceeds the maximum number allowed, the action is not carried out and the following message is recorded in the ControlPoint Task Audit:
The number of users ([numusers]) has exceeded the allowable threshold of [maxusers].
This setting is especially useful as a "safety net" when an operation allows wildcards to be used in the People Picker and could potentially act on more users than intended.
ControlPoint Application Administrators can, however, specify a different limit by changing the Value of the ControlPoint Configuration Setting Maximum Number of Users to Act on.
NOTE: This is an Advanced Setting.
NOTE: This setting does not apply to users within the scope of a SharePoint User Profile property selection, for which no maximum is enforced.
Load The Hierarchy from Database (LOADHIERARCHYFROMDATABASE)
By default, the SharePoint Hierarchy is populated with cached data from the ControlPoint Services (xcadmin) database, which means it is current as of the last Discovery run. Using cached data decreases the amount of time it takes for the hierarchy to load (for large tenants it can decrease loading time by several minutes over using real-time data).
ControlPoint Application Administrators can, however, override this behavior and have the hierarchy load in real time by changing the Value of the ControlPoint Configuration Setting Load the Hierarchy from Database from True to False.
