You are here:
Experience Builder Sites Search Best Practices and Considerations for Guest Users
When setting up your search pages and components for Experience Builder sites, keep these best practices and considerations in mind to keep data secure from guest users.
Search Page
- Review page access settings for the search page to ensure that you want the search page accessed by guest users.
- To limit access to the search page, consider creating a search page variation with a guest audience.
Global Search Results Component
The Global Search Results component is the main component on the Search page in any Experience Cloud site. The component allows admins to select the objects shown in search results.
- Guest users only see results on objects they have access to.
- Actual record access for the guest user isn’t limited to the objects the admin configures in the Global Search Results component. The guest user can have access to other objects based on org sharing configurations.
- Always check the org’s sharing model (including org-wide defaults and sharing rules) to ensure that the guest user doesn’t have access to your org’s sensitive data.
Search Box Component
- As with the Global Search Results component, the admin sets up which objects to show in searches. However, record access for the guest user isn’t limited to the objects the admin configures in the Global Search Box and Global Search for Peer-to-Peer Communities components. The guest user can have access to other objects based on org sharing configurations.
- Always check the org’s sharing model (including org-wide defaults and sharing rules) to ensure the guest user doesn’t have access to your org’s sensitive data.
Search for Experience Cloud Site Users from Your Org’s Global Search
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 , 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 insidesites. 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.
