Max Capacity Setup

For an overview of what Enterprise Search is and how it works, see Enterprise Search Overview. For the inventory of supported connectors and their capabilities, see Search Connectors. New to the two setup journeys or the naming? Start with Choosing Your Journey.

Configuring a Max Capacity connector

Max Capacity connectors are configured through a four-step process. This streamlined approach simplifies setup and ensures organizations can quickly connect their content systems to provide a unified search experience.

Step 1: Prepare and Configure Content Systems

• Collaborate with your system admin to assess the integration requirements for your chosen connector
• Follow the detailed configuration guide for your content system (see Search Connectors for links)
• Create and configure connectors for the content systems in Moveworks Setup
• Grant the appropriate scopes as specified in the configuration documentation

Step 2: Select Connector

• Choose authentication strategy: Review recommended options in the right-hand pane (e.g., Service Account, OAuth 2.0) and select the appropriate method for your system
  Note: Authentication strategies vary by content systems

• Select your connector: From the dropdown, choose the preconfigured connector with correct credentials
• Connector Validation: Selecting a connector triggers automatic validation of authentication, content access, permissions, users and groups — click on ‘View Details’ to review all validation results
  Note: Validation checks vary by content systems

• Review validation results:
  • ✅ Green = all checks passed, ready to save
  • ❌ Red = issues that must be fixed before proceeding (e.g., invalid credentials, missing scopes) — Use troubleshooting guides provided in the validation popup to resolve these
  • ⚠️ Yellow = non-critical issues (e.g., server errors) — Retrying usually resolves these errors
    Note: All validations must pass before you can save the connector

Step 3: Select Content Ingestion Strategy

• Choose content scope: Select your preferred ingestion strategy - ‘Only selected sources’, ‘All except selected’, or ‘All available sources’
• Specify content sources: Enter the specific content repositories, folders, or collections you want to include or exclude using the appropriate identifiers for your system
• Review ingestion limits: Review the system-specific ingestion limits and refer to the right-hand pane to optimize your content selection strategy to stay within those constraints
• Configure additional filters: Use the additional filters section to narrow your content scope - only records matching all specified criteria will be included in the ingestion
• Save and proceed: Click ‘Save’ to save your content selection strategy, or ‘Save and Start Ingestion’ to start ingesting content immediately
  Note: Content selection strategies vary by content systems

Step 4: Define Target Audience

After configuring your connector and content ingestion, define who can access search results from this connector by setting up a Target Audience.

1. From your connector’s home page, click Select Audience (or navigate to the Target audience tab).
2. Choose one of the following options:

3. Click Save to apply your selection.

Important notes

• New connectors do not serve content until an audience is configured. After setting up a new connector, you must select a target audience and save before any content from this connector appears in search results.
• Changes take effect immediately. Audience filtering is applied at query time — no re-ingestion or re-indexing is required when you change the audience setting.
• Source permissions are always enforced. The target audience setting works on top of the source system’s native permissions. Even if a user is in the audience, they can only see content they are authorized to access in the source system.

Recommended workflow

1. Start with Selected users by email ID to test search results with a small pilot group.
2. Once validated, switch to All users to roll out content to your entire organization.
3. If you need to temporarily pause serving content from a connector, switch to No users — ingested content is preserved and can be re-enabled at any time.

User identity prerequisite

Max Capacity generates the user identity and resource permission configurations for you when two things are true:

1. Your organization already has an identity configuration. The journey adds the new system to your existing identity configuration; it does not create one from scratch.
2. Your joining key resolves to an email address. Either your organization’s joining key is the email address itself, or a non-email joining key (for example, an employee ID) is mapped to the email field of your primary identity source.

If either check fails, configure user identity first: set the correct joining key for the system you are configuring, following Configure User Identity. Permission validation depends on identity being in place.

Filtering: what carries over from Classic Ingestion (and what doesn’t yet)

If you have an existing Classic Ingestion configuration with carefully tuned filters, review this section before setting up the same system on Max Capacity.

What Max Capacity supports today: self-serve selection of content sources — sites, spaces, knowledge bases, drives, folders, or categories, depending on the system — using “Only selected”, “All except selected”, or “All available”, plus created-date and modified-date filters.

What does not carry over from Classic yet:

• Library- and folder-level scoping (SharePoint Online) — Max Capacity scopes at the site level today; scoping to individual document libraries or folders within a site is planned.
• Custom query filters — Confluence CQL filters and ServiceNow query-string filters (including article-type exclusions) have no Max Capacity equivalent today; equivalents are planned.
• Custom attribute rules and file name/type rules — rule-based inclusion/exclusion by content attributes is planned.

If your Classic setup depends on these filters, moving that system to Max Capacity today means changing your content scope — typically ingesting more broadly and relying on permission ingestion and the Target Audience setting to control who sees what. For some setups that is acceptable (source permissions are always enforced); for others it isn’t, and staying on Classic until the corresponding filters ship is the right call. Discuss your specific filter requirements with your account team before moving an existing configuration.

Moving from Classic Ingestion

There is no in-place conversion between journeys — an existing Classic Ingestion 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.

What to expect after you save

Ingestion does not begin immediately: it starts roughly 12 hours after you save the configuration, and the initial run then takes additional time depending on your content volume. Plan to wait at least 18 to 24 hours after saving before you test search results.

Known limitations across the journey

Each connector’s setup guide lists its own known limitations. Two apply across the journey:

• Validation error specificity. Some validation failures currently report a generic error rather than the specific failing check. If a red check doesn’t match an obvious cause (credentials, scopes, grants), contact Moveworks support rather than re-working your configuration — improved per-check errors are in progress.
• Very large deployments. Deployments with very large content volumes are staged in coordination with Moveworks. Engage your account team early for sizing and planning.