# Look Ahead Sections ### Overview Instead of navigating between multiple modules or applications to access relevant data, employees can conveniently find what they need directly within the company's intranet environment via predictive search. Predictive search software streamlines workflow by reducing the time and effort required for information retrieval and can even pull from third-party integrations such as Freshdesk, Gitbook, and more. Predictive look ahead can surface relevant documentation or support resources, saving valuable time and minimizing disruptions to productivity.
{% hint style="info" %} If no pertinent matches are found within the internal data sources, the section will be omitted from the Predictive Look Ahead box. {% endhint %} *** ### Predictive Look Ahead Views Admins can configure the lookahead experience from the Admin Portal following **Admin Portal → Search → Look Ahead → Predictive Look Ahead View**. Two display styles are available: **Categorized** and **Simplified**. The **Categorized** view is ideal for users who prefer structured results and want to browse content by type. The **Simplified** view is better suited for fast discovery when users care more about relevance than content classification. By selecting the appropriate Predictive Look Ahead view, administrators can tailor the search experience to better match how users find and access information in their organization. *** #### Categorized View ( Default) The Categorized view organizes predictive search results by content type. As users type a keyword, results are displayed under labeled sections such as Users, Teams, Files, Pages, Wikis, Trackers, and other supported content types. Within each section, results are ordered by best match.
Each category displays a limited number of top results, and categories appear in a predefined order. For example, when a user searches for a term like “team,” all matching Teams may appear first under the Pages section, followed by matching People, Files, Libraries, etc. in their respective sections. This approach makes it easy for users to scan results by content type and focus on a specific category. {% hint style="info" %} Federated Search items will always appear beneath module sections. {% endhint %} If necessary, administrators have the option to reset the Predictive Look Ahead settings to the recommended system defaults for convenience and ease of management. *** #### Simplified View (Uncategorized) The Simplified view displays predictive search results purely based on relevance, without grouping them by content type. All matching results are shown together in a single list, regardless of whether they are Files, Pages, Teams, Events, Trackers, or other resources.
Results are ranked according to how closely they match the search keyword across all content types. For example, if a keyword matches a Team, a Wiki, a Tracker, and a File, all of these items may appear together in the top results. The order reflects overall relevance rather than content type, allowing the closest matches to surface first. This view provides a streamlined, relevance-first search experience and is especially useful when users want to quickly access the best match without scanning through categorized sections. *** ### Federated Search Sections Federated Search sections will appear once an [external data repository](https://guides.mangoapps.com/admin-guide/search/data-sources) is added to the domain. Some connections require only API authorization, which admins must retrieve from the third-party site. For example, to display Freshdesk results in MangoApps, an admin must first connect Freshdesk. This can be done by clicking the authorization link in the search dropdown menu.
A pop-up window will appear where the Freshdesk API key can be entered.
After completing this setup, the search results will include additional sections with matching results. Clicking on a search result from a federated data source will open the corresponding article or page in a new tab, allowing the user to access the full content. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guides.mangoapps.com/admin-guide/search/look-ahead-sections.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.