> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://help.moveworks.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.moveworks.com/_mcp/server.

# Configure Enterprise Search

Ingest your ServiceNow knowledge base articles into Moveworks Enterprise Search so the AI Assistant can answer questions from your content, respecting the article permissions defined in ServiceNow.

**For administrators.** This page covers the minimum configuration to get knowledge answers working. For deeper options, see the [Enterprise Search documentation](/ai-assistant/enterprise-search/overview).

## Before You Begin

* [Connect ServiceNow](/ai-assistant/getting-started/implement-on-servicenow/connect-servicenow) is complete: connector tested, update sets installed (the `moveworks.acl` update set powers permission mirroring), and the integration account holds the `moveworks_user` role.
* Your ServiceNow instance has published knowledge base articles.
* **Plan for the initial ingestion window:** the first content-and-permissions ingestion takes approximately 12 hours. After that, incremental syncs run every 15 to 30 minutes.

## Procedure

### 1. Create the Search Configuration

1. In **Moveworks Setup**, go to **Search > Configure Search > Max Capacity** and click **Get Started**.

   ![Max Capacity entry point under Search > Configure Search in Moveworks Setup](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/moveworks.docs.buildwithfern.com/e1d702bea5d52a47b0df39eafedb3ec8cf7978c15070e98507ce3f744de84f2a/docs/assets/images/setup-labs/lab3_search_enterprise_search_max_capacity.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260826%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260826T070015Z&X-Amz-Expires=604800&X-Amz-Signature=69ca00868a1614a4b1872c38621ab21aaae955c01ab99a2f7480be577cbc705e&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

2. Select **ServiceNow** as the source system, then choose **your connector** from the **Select connector** dropdown.

3. Under **Select and combine one or more required method(s)**, check **Add Knowledge Bases**, then click **Start Validation**. Moveworks verifies the instance is ready for ingestion.

   ![Start Validation step with the Add Knowledge Bases method checked](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/moveworks.docs.buildwithfern.com/11ead60c08db70eec9d3947575e67dcc41d2e30f07022d5c4dbae5e2d263862a/docs/assets/images/setup-labs/lab3_start_validation.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260826%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260826T070015Z&X-Amz-Expires=604800&X-Amz-Signature=e2aee93f4a7bd8e9df8ba52809a1c63d1f0e009add6b4f4d7e4196b56aeb3dc4&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

4. Confirm that **Credentials**, **Content**, **User**, and **Permission** all return successful, then click **Close** and **Save**.

**If validation fails:** confirm you can reach the instance from the Moveworks Setup **API Playground**, and confirm the Moveworks update sets appear on your instance's **Retrieved Update Sets** page. A failing **Permission** check usually means the `moveworks.acl` update set is missing or the integration account lacks the `moveworks_user` role.

### 2. Select Content and Audience

1. On the **Content Selection** step, choose which knowledge bases to ingest - all of them, or a specific subset - and click **Save**.

   ![Content Selection step showing knowledge base selection](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/moveworks.docs.buildwithfern.com/9d082befd801168b8a42051ed081d4fb56c1a86b6ca0119e2ea3010fa0d7043c/docs/assets/images/setup-labs/lab3_c797053c-5f79-44c3-9f86-9f999cdc409e_es_select_knowledge_bases.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260826%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260826T070015Z&X-Amz-Expires=604800&X-Amz-Signature=d93be4b893531d9ffb52aa8b8406307977d82a9e711cb0a983a12f2fcf6f6af3&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

2. On the **Audience** step, choose who can search this content (for example, **All Users**) and click **Save**. Initial ingestion begins after you save.

### 3. Confirm Permissions Are Mirrored

Moveworks enforces your ServiceNow article permissions using Relationship-Based Access Control (ReBAC): users only see articles their ServiceNow user criteria allow.

1. On the **Resource Permissions > Mirror Permissions** page, confirm your connector is selected and knowledge access controls are being fetched. This page is powered by the `moveworks.acl` update set.
2. Review the **Permission Rules** page. Mirroring is ServiceNow-specific; permission rules apply across all integrated systems.

### 4. Enable the Plugin

Go to **AI Assistant > Plugin Management** and set the **Enterprise Search** plugin to **TRUE**. Leave the DSL rule empty to grant access to all users, or scope it later.

![Plugin Management page with the Enterprise Search plugin enabled](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/moveworks.docs.buildwithfern.com/9827a7a39f0b6f3914f33aac5864f1b662ff4532d947034489859e659ee220dc/docs/assets/images/setup-labs/lab3_83e8b29b-118e-4c49-b1a8-392b857eff21_es_true.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260826%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260826T070015Z&X-Amz-Expires=604800&X-Amz-Signature=7601e9acac0eebcecaed1acdfc9503fcab92382a299df9de8369250c39119163&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

## Result

After the initial ingestion completes (approximately 12 hours), your articles appear with status **Serving** on the **Indexed Content > Internal Knowledge** page, and asking the AI Assistant a question covered by an ingested article returns an answer with a citation.

![Indexed Content > Internal Knowledge page listing ingested articles](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/moveworks.docs.buildwithfern.com/4dc27863a4b7821fdb38cbd7d92770ded68929c4d569a2ecfb64b0b745b0e2b5/docs/assets/images/setup-labs/lab3_search_indexed_content_internal_knowledge.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260826%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260826T070015Z&X-Amz-Expires=604800&X-Amz-Signature=11678e9a8165b75865c65d2ea2fd5dcd2dbc17ab2bb1b6010683e8df3b0783ef&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

## What to Do Next

* [Configure Forms](/ai-assistant/getting-started/implement-on-servicenow/configure-forms) so users can find and fill catalog items in chat.
* If an ingested article is not surfacing for a user, check its status is **Serving** on Indexed Content, then verify that user's access on the article's resource permission - Moveworks follows your ServiceNow user criteria.