Skip to main content
Known Participant
July 6, 2026
Solved

Confluence Data Center/Server for Enterprise Search

  • July 6, 2026
  • 3 replies
  • 169 views

Hello, 

I am looking to set up Confluence DC/Server for Enterprise search. We were told that it is doable now but any documentation we find is specific to Confluence Cloud. Is there any other documentation on setting this up?

Best answer by rgeroulo

@Joel.Matias I see.

To be clear, both the Classic connectors and the new Max Capacity connectors are leveraged for Enterprise Search. The difference is more so in the load that the connector can handle and the setup experience. You can still set up content to be used by the Enterprise Search plugin in-bot and within the Enterprise Search web UI using the Classic connectors.

In your case, there is currently a specific set of systems that have had this new Max Capacity journey built out for. Those systems are: Box, Confluence Cloud, Google Drive, Outlook, ServiceNow, SharePoint Online & OneDrive, Slack, Unily, and Zendesk. If your system is not in this list, then you will use the classic connector to configure ingestion. The experience will be the same in-bot as this is more of an admin experience/setup change.

Below is a general outline of the differences between the two connectors. This doc has more guidance as well if you wanted to take a look.

  •  Classic connectors: The long-standing connectors, available as part of your Moveworks subscription. They cover 35+ content systems and support up to 100K documents per connector. Some connectors support permission ingestion.
  • Max Capacity connectors: The connectors used by the Max Capacity journey, available for nine content systems. They support up to 100M documents per connector, out-of-the-box permission ingestion, and improved freshness. In the Connectors page these connectors are labeled (Next Gen). Available to all organizations.

Let me know if that helps to clear things up.

Best,

Ryan

3 replies

rgeroulo
Community Manager
July 15, 2026

Hi ​@Joel.Matias!

The following documents would be your starting point to set up Confluence DC/server:

  1. Confluence Server / Data Center Access Requirements
  2. How to Configure Confluence Server / Data Center Knowledge Ingestion

Best,

Ryan

Known Participant
July 23, 2026

Hi ​@Joel.Matias!

The following documents would be your starting point to set up Confluence DC/server:

  1. Confluence Server / Data Center Access Requirements
  2. How to Configure Confluence Server / Data Center Knowledge Ingestion

Best,

Ryan

This seems to be specific to the classic ingestion or does this apply to Enterprise Search. When trying to set up Confluence for ES the connector only seems to accept the Confluence Next Gen connector settings. 

rgeroulo
rgerouloAnswer
Community Manager
July 23, 2026

@Joel.Matias I see.

To be clear, both the Classic connectors and the new Max Capacity connectors are leveraged for Enterprise Search. The difference is more so in the load that the connector can handle and the setup experience. You can still set up content to be used by the Enterprise Search plugin in-bot and within the Enterprise Search web UI using the Classic connectors.

In your case, there is currently a specific set of systems that have had this new Max Capacity journey built out for. Those systems are: Box, Confluence Cloud, Google Drive, Outlook, ServiceNow, SharePoint Online & OneDrive, Slack, Unily, and Zendesk. If your system is not in this list, then you will use the classic connector to configure ingestion. The experience will be the same in-bot as this is more of an admin experience/setup change.

Below is a general outline of the differences between the two connectors. This doc has more guidance as well if you wanted to take a look.

  •  Classic connectors: The long-standing connectors, available as part of your Moveworks subscription. They cover 35+ content systems and support up to 100K documents per connector. Some connectors support permission ingestion.
  • Max Capacity connectors: The connectors used by the Max Capacity journey, available for nine content systems. They support up to 100M documents per connector, out-of-the-box permission ingestion, and improved freshness. In the Connectors page these connectors are labeled (Next Gen). Available to all organizations.

Let me know if that helps to clear things up.

Best,

Ryan