---
sourceDocument: Australia ServiceNow AI Platform user interface
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-user-interface

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform user interface

ft:clusterId :

    - platux

bundleId :

    - platux

workflow :

    - Platform


---

# Global search in Content Management

# Global search in Content Management {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

When you add global search to a CMS site, two different search result blocks can
display, depending on the user role: global or no global.
Roles are defined at System PropertiesGlobal Text Search.

* Search Results (Global): For users with permission to use the global search within the normal frame set. The normal frame set is defined as the default, non-CMS user interface with the set of frames.
* Search Results (No Global): For users without permission to use the global search. Searches only the knowledge base and the catalog.

The header search bar and the Search dynamic block in the base system both
automatically handle the permissions and direct the user to the appropriate search results.
In the base system, the search result blocks are deployed on the same Search Results content
page.

In order for the global search to work properly, it is important to ensure that
the DEFAULT directs users to a working content page. If not, the results from the global
search link back to the frame set, not to pages within the CMS site.  
Note:  
The global search is similar to the normal frame set user interface and ties to the same roles ([Set global text search properties](https://www.servicenow.com/docs/access?context=set-global-text-search-properties&version=australia&pubname=australia-platform-administration&ft:locale=en-US)).

## Search Results (Global)

Before you use the Search Results (Global) dynamic block, define
Configure content types to control the behavior a search result is clicked. If no content
type is defined for a table, selecting a link on that table renders the results according to
the DEFAULT content type. It is good practice to point the
DEFAULT content type to a page with a normal "Current Document"
detailed block. Set the content type detail (Detail Template field)
to have just an iFrame.

The Search Results (No Global) dynamic block does not require any
additional configuration.
**Related concepts**   

* [Content Management design](https://servicenow-prod.fluidtopics.net/Ws93gAFxFX~QLi37LUz1gQ "Before building a website in the CMS, it is important to have a good understanding of what to build and who the audience is.")
* [Domain separation and the Content Management System](https://servicenow-prod.fluidtopics.net/a_Gv7P3Ndq9mfi59_67OFg "Domain separation is supported in the Content Management System. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.")
* [Content Management integration points](https://servicenow-prod.fluidtopics.net/ESC~I~XD~9DB0EG_V_G5jw "Integration points use content blocks in CMS to link different applications together using static and dynamic methods.")
* [Content Management testing](https://servicenow-prod.fluidtopics.net/DtrjyInKioIdFu3GdRKlrA "Test your site to ensure that all pages display correctly, links go to the specified address, and images are not broken. It is important to test the site as you build it. Do not wait until just before launch to begin testing.")
* [CMS translation](https://servicenow-prod.fluidtopics.net/hJFQZFrhYHGhRo4pEa9gfg#c_CMSTranslation "You can translate CMS sites by activating internationalization plugins and manually translating custom interface strings.")  
**Related tasks**   

* [Configure Content Management sites](https://servicenow-prod.fluidtopics.net/jGjhGBFsikRvbCuUD8usMw "Planning a CMS site involves obtaining resources, communicating with others about design, and gathering content.")

*[\>]: and then