Planning .NET Search Hubs and Search Interfaces

The Coveo Platform comes with a set of feature-rich out-of-the-box .NET search interfaces that you can use immediately.

Coveo .NET Front-End makes search interfaces available through search hubs that contain one or more .NET search interfaces (see About .NET Search Hubs and Search Interfaces). Each .NET search interface has its own search scope and presents appropriate content.

Examples: While the All Content .NET search interface searches all indexed repositories, the Intranet .NET search interface returns result from your SharePoint farm, and the People .NET search interface consolidates people information from Microsoft Active Directory and Microsoft Outlook contacts.

When different groups of people have different search needs, you can create different search hubs that include appropriate search interfaces for each group, and control the access to each .NET search hub (see Creating a Search Hub With the .NET Interface Editor).

Example: When you want that only people from the marketing, sales, and management departments have access to the CRM search interface, you can include this interface only in a search hub to which only these people have access. If this is the only exclusive search interface, you only need one other search hub for everybody else.

CES integrates and indexes document-level permissions of each repository. This means that for each repository, only documents to which a user has access are returned in the search results. Consequently, you do not need to create different search hubs for one shared repository (see Security).

Example: On a shared network file server, if a HR folder access is restricted to people from the human resources department, the connector that crawls the whole file server indexes the access restriction together with the documents. When searching the network file server content, only human resources employees will see search results from the HR folder.

To plan search hubs and interface

1. List all the repositories that you want to index (see Planning Repositories to Index).

2. Review the out-of-the-box .NET search interfaces that you can use to search all or specific repositories (see About .NET Search Hubs and Search Interfaces).

3. When the access to one or more .NET search interface must be restricted:

   1. Identify the .NET search interfaces to which you want to restrict the access.

   2. Create a list of search hubs, their .NET search interfaces, and the access restriction to each hub.

4. Note the information in a table similar to the following example and contact the Coveo Support to help you plan your Coveo Platform installation.

   Search hub	Search interfaces	Access restriction
   Sales &marketing	My Emails My Files People Intranet CRM File Share Extranet Knowledge Base All Content	Marketing, Sales, Management
   General	My Emails My Files People Intranet File Share Knowledge Base All Content	All employees
   Website	Website	All web users