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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Configure semantic indexing settings for an indexed source

# Configure semantic indexing settings for an indexed source {#ariaid-title1}

Release version: Australia  
Updated July 24, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Specify the semantic indexing configuration settings you want to apply when AI Search indexes records from your indexed sources.

## Before you begin

The AI Search Semantic Controller plugin (com.glide.ais.semantic_search) must be active on your instance. This plugin is automatically activated when any [ServiceNow Otto® application](https://www.servicenow.com/docs/access?context=platform-now-assist-landing&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) is installed on your instance.{#configure-semantic-indexing-ais__ais-semantic-controller-plugin-id-ph}

Role required: ais_admin

## About this task

As an AI Search admin, you can perform this task to choose the fields from and indexed source's table that you want the system to index for semantic vector search. You can also choose the embedding models and
content chunking strategy to use for semantically indexed content from the source table.

## Procedure

1. Navigate to AllAI SearchAI Search IndexIndexed Sources.
2. Select the indexed source that you want to configure semantic indexing settings for.  
   The selected indexed source opens in Indexed Source form view.
3. In the Semantic Index Configuration related list, select New.  
   Note:  
   If you don't see the Semantic Index Configuration related list on the Indexed Source form, check with your administrator to make sure that your instance has at least one [ServiceNow Otto application](https://www.servicenow.com/docs/access?context=platform-now-assist-landing&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US) installed. Installing any ServiceNow Otto application activates the AI Search Semantic Controller plugin (com.glide.ais.semantic_search), which is required for semantic index configuration.
4. On the Semantic Index Configuration form, fill in the fields.  
   For a description of the field values, see [Semantic Index Configuration form](https://servicenow-prod.fluidtopics.net/BhjiBfirPIjoYXrFfrMjNg "The Semantic Index Configuration form enables you to define semantic indexing settings for an AI Search indexed source.").
5. Select Submit.  
   If you're updating an existing semantic index configuration, select Update instead.  
   The Semantic Index Configuration form reloads and displays your selected field values and the Semantic Index Fields related list.
6. In the Semantic Index Fields related list, create a record for each field with content that you want to include in the semantic index for the specified indexed source.
   1. Select New.
   2. On the Semantic Index Field form, fill in the fields.  
      For a description of the field values, see [Semantic Index Field form](https://servicenow-prod.fluidtopics.net/XY4cxVFECUnD0Gh3DpsWTQ "The Semantic Index Field form enables you to define a semantic index field for use in an AI Search semantic index configuration.").
   3. Select Submit.  
      The new semantic index field record appears in the Semantic Index Fields related list.
   {#configure-semantic-indexing-ais__substeps_sh2_hk3_xcc}

## What to do next

After changing the semantic index configuration settings for an indexed source, you must reindex content from that indexed source. For reindexing steps, see [Perform a full table index or reindex for a single AI Search indexed source](https://servicenow-prod.fluidtopics.net/bwrBDfHjTH51BUWqtnLaOg "Make content from an internal indexed source searchable by performing a full table index. This procedure indexes existing records from the source table and any child tables configured for indexing. You can manually reindex content from an internal indexed source by repeating this procedure.").  
Note:  
Indexing content for semantic vector search is typically slower than indexing for keyword search. Your indexed source may take more time to reindex once you have defined a semantic index configuration for it.

*[\>]: and then