---
schema_version: "1"
id: d3ceefae5bbfd8f0605caa9ae57b8c75d6cc8236f0e5af159d02ce08dd7110a9
title: Global Search Box
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/experience/264-0-0/rss_search_global_no_publisher.md
canonical_url: https://help.salesforce.com/s/articleView?id=experience.rss_search_global_no_publisher.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b0dce950cedc65cfb0bec522c4401df8dd64a90c6bff08d0e31aa8963d0e8317
description: The Global Search Box component lets you expose global search in your Experience Builder site. Let your users search for any object available to them.
products:
  - Experiences
release: "264"
---
# Global Search Box

The Global Search Box component lets you expose global search in your Experience Builder site. Let your users search for any object available to them.

Autocomplete search results are based on the most recently used objects and records by the user, the same as global search in your org. The search accounts for partially matching terms and non-adjacent terms.

1. Select the **Global Search Box** component in the page you’re configuring.
    
    In the Partner Central template, for example, this box is on the Home page.
2. In the property editor, configure the properties for the component.
    
     
    | Property | Details |
    | --- | --- |
    | Placeholder Text for Search Field | Specify the text that appears in the search box. The default text is Search... |
    | Objects in Autocomplete Results | Click **Add** to add searchable Salesforce objects to your site’s autocomplete results. To edit an object, click the object name. In the edit window, you can change to another type of object and you can mark the object as **Publicly available**. To select a different object type, click the object name and select from the list. To make results of that object type available to guest users, select **Publicly available**. |
    | Maximum Autocomplete Results | Enter the maximum number of autocomplete results displayed to the user during a search. The default is 5. |

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_example.png)

Example Sample Global Search Box component in Partner Central:

![Global Search Box component in Partner Central](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/communities/images/global_search_no_publisher.png)

With global search from your internal org, you can get uneven results when searching for a site User record. Here’s why and what you can do about it. Each site has a unique network ID. When you create a site user through **Contact record** | **Create External User**, the new User record is assigned to a site's network ID.

Global search looks for records in the internal org, which has a different network ID than the site. A global search doesn't search inside sites. Since the User record is associated with a site network ID, global search doesn't return results for that record.

The workaround is to create User records in the internal org, and then associate the records to a site. You can associate an internal User record to a site by linking the internal record to a Contact record. After you forge the link, you can find the User record through global search. The User record's network ID is now associated with the internal org.

#### See Also

- [Which Components Can I Use with Each Aura Template?](https://help.salesforce.com/s/articleView?id=experience.rss_component_reference_table.htm&release=264.0.0&type=5 "Aura site templates, such as Customer Service and Partner Central, are each composed of pages, which in turn are made up of customizable components. Consult this table to find out which Aura template each component can be used in, and when the component became available.")
- [Enable Search Autocomplete for Guest Users](https://help.salesforce.com/s/articleView?id=experience.networks_search_autocomplete_guest.htm&release=264.0.0&type=5 "Sometimes you want your Experience Cloud site’s guest users to benefit from the suggestions that come from autocomplete on their search terms. To make it happen, you must explicitly make result types publicly available. For example, when you want guest users to see suggestions for Knowledge articles, you can set up your search component so that Knowledge results are public. After you set up autocomplete, search shows any Knowledge articles that match a guest user’s search terms in autocomplete suggestions.")