Search Connectors
Overview
A table of built-in content connectors that power the search capability of Moveworks AI Assistant. There are two types of built-in content connectors:
- Max Capacity connectors: The newest connectors, available for select content systems. They support up to 100M documents per connector, out-of-the-box permission ingestion, and improved freshness SLAs. Available as an upgrade — contact your account team to learn more. See Max Capacity Setup for setup details.
- Classic connectors: The long-standing connectors, available as part of your Moveworks subscription. Support up to 100K documents per connector. Some connectors support permission ingestion.
Please see the tables below for the specific content types supported.
Choosing Your Journey
Both journeys live under Configure Search in Moveworks Setup, and whichever you use, the results end up in the same place. The Enterprise Search Application and the Enterprise Search Plugin search across all ingested content, regardless of which journey it came through. Choosing a journey is a per-system setup decision, not a fork in your search experience.
Walk through these questions in order:
- Is your content system on the Max Capacity list? (See the tables below.) If not, use Classic Ingestion — it remains fully supported, and its content is served through the same search surfaces.
- How much content do you have? If a single system holds more than 100K documents, Classic Ingestion cannot index all of it.
- Do you need permission-aware search? Max Capacity provides permission ingestion out of the box on every indexed connector. On Classic, permission ingestion exists only for a handful of systems.
- Does your current setup depend on filters Max Capacity doesn’t have yet? If you rely on library- or folder-level scoping, custom query filters, or article-type exclusions, review what carries over from Classic before committing.
- Do you need live search or personal-content search? These are available only through Max Capacity, and they require that your employees authenticate through the Enterprise Search Application.
There is no in-place conversion between the journeys: an existing Classic connector or configuration cannot be edited into a Max Capacity one. To move an existing Classic Ingestion configuration to Max Capacity, contact your Moveworks account team to plan the transition. If you are unsure which journey fits a system, your account team can review your content volumes and filtering needs and recommend a path.
FAQ
What are the different Content Types?
- Permissioned content ensures that employees only see the content authorized to them within the AI Assistant search experience.
- Public content will be shown to all employees within the AI Assistant search experience.
- Personal content is from private repositories, e.g. personal direct messages, personal calendar, etc, and is only accessible through user-granted authentication within the AI Assistant search experience.
What are the limits?
- Limits are applied within indexed search, which constrains the # of content items that can be searched.
- However, the limit is unlimited for live API search, which means the limit is set by the system’s retrieval setup, e.g. Notion Search API.
What are the various implementation approaches?
- Indexed: Refers to mirroring content and permissions to build an index for search.
- Live API: Refers to using the connectors own search api to retrieve content via user impersonated search.
What does Availability mean?
- Generally Available: Available now within the Moveworks AI Assistant experience.
- Limited Preview: Available if participating in the Limited Preview program (terms and conditions may apply). Please fill out the self-nomination form in Community and the Moveworks Product team will reach out to you with the next steps.
- Roadmap: Planned for the upcoming release but exact release quarter is to be determined. To learn more, join the Community to ask questions.
What if the content connector is not listed?
If the content connector is not listed, then Moveworks does not have a native content connector. There are two ways forward:
- To submit a request for a native connector, we recommend to submit the request the Ideas Portal.
- If you have developers who can build the integration, we recommend implementing a Content Gateway connector.
Is “Max Capacity” the same thing as “Next Gen”?
Yes — they are the same connectors. The connectors used by the Max Capacity journey formerly showed a (Next Gen) suffix in the Connectors page and have been renamed to Max Capacity. You may still see the old label in older screenshots, documentation, and training materials; treat “Next Gen” and “Max Capacity” as one and the same.
Is “Enterprise Search” the same as “Max Capacity”?
No. Enterprise Search is the product — the Enterprise Search Plugin (conversational search inside the AI Assistant) and the Enterprise Search Application (a dedicated search surface in My Moveworks). Max Capacity is one of two setup journeys for connecting content systems. Content ingested through either journey is served by both surfaces. See Choosing Your Journey for the full picture.
Why do I see two connectors for the same system (for example, “Confluence” and “Confluence (Max Capacity)”)? Which one do I pick?
For most systems that support both journeys, there are two distinct connectors: the Classic connector (used by Classic Ingestion) and the Max Capacity connector. Pick the connector that matches the journey you are setting up. ServiceNow and Zendesk are exceptions: those connectors are consolidated, so a single connector serves both journeys — note that a single consolidated connector cannot back a Classic configuration and a Max Capacity configuration at the same time.
Can I keep using Classic Ingestion? Will Classic connectors be deprecated?
Yes, you can keep using Classic Ingestion — it remains generally available and fully supported, and for many systems it is the only option. No deprecation date or migration deadline for Classic connectors has been announced.
My content system isn’t in the Max Capacity list — what should I do?
Use the Classic connector for that system; Classic Ingestion remains the correct and supported path, and the content it ingests is served in the Enterprise Search Plugin and Application just like Max Capacity content. If your system has no native connector at all, request one through the Ideas Portal or build your own integration with Content Gateway.
Is Confluence Data Center or Confluence Server supported on Max Capacity?
No. Max Capacity supports Confluence Cloud only. Confluence Data Center and Server deployments are not supported on Max Capacity — including Data Center instances placed behind a proxy. For Data Center or Server, use the Classic Confluence connector.
Why don’t I see the Max Capacity page in Moveworks Setup?
The Max Capacity journey is enabled for all organizations. You’ll find it in Moveworks Setup under Configure Search → Max Capacity. If you don’t see it there, contact your Moveworks account team.
I configured a Max Capacity connector, but employees don’t see the content in search. Why?
The three most common causes are: (1) the configuration’s Target Audience does not include those employees — for example, it is still “No users” or a small pilot group, (2) the first ingestion has not completed, so the content is not in the index yet, or (3) for live-search and personal-content connectors, employees have not authenticated through the Enterprise Search Application, or your organization does not have it enabled. Check the audience setting and ingestion status first; for live-search issues, confirm Enterprise Search Application access with your account team.