The people picker, allows users to assign tasks to users in AD. This is a useful, but what do you do if you have multiple clients or user groups who shouldn't see each other.
Enter the Filtering People Picker for the entire collection.
People Picker Filters: http://technet.microsoft.com/en-us/library/gg602075.aspx
People Picker is configured at the zone level for a farm by using the Stsadm setproperty operation. By configuring the settings for the control, you can filter and restrict the results that are displayed when a user searches for a user, group, or claim. Those settings will apply to every site within the site collection.
Restrict users to pick from a specific OU: stsadm -o setsiteuseraccountdirectorypath -path<Valid OU name>–url<Web application URL>
Restrict users to pick from only users within the collection: stsadm -o setproperty –pn peoplepicker-onlysearchwithinsitecollection –pv yes –url<Web application URL>
** this is ideal either you have access to the collection our you don't.
To meet the requirement of limiting users to only co workers would need be its one collection. While this approach introduces many collections (one for each client/ instance) it's not an untenable situation nor will it reach any limits.
SharePoint Boundaries: http://sdrv.ms/S9ive2
| Web site |
250,000 per site collection |
Supported |
You can create a very large total number of Web sites by nesting the subsites, For example: a shallow hierarchy with 100 sites, each with 1,000 subsites, is a total 100,000 Web sites, or a deep hierarchy with 100 sites, each 10 levels deep also containing a total of 100,000 Web sites. The maximum recommended number of sites and subsites is 250,000 sites. Note that Web deletion can have significant impact on the Site's availability, access to the site and subsites will be limited during the time of Web deletion. Also high concurrency of subsite creation might fail beyond a certain pace |
| Site Collection Size |
100 GB per site collection |
Supported |
A site collection should not exceed 100 GB unless it is the only site collection in the database. Certain site collection actions, such as site collection backup/restore or Move-SPSite, cause large Microsoft SQL Server® operations which can have performance impact or fail if other Site collections are active in the same database. |
| Content database |
300 per Web application |
Supported |
With 300 content databases per Web application, end user operations such as navigating to the site or site collections are not affected. But admin operations such as creating a new site collection will experience performance degradation. It is also suggested to user PowerShell to manage the Web application when a significant number of Content databases is present |