> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.moveworks.com/llms.txt.
> For full documentation content, see https://docs.moveworks.com/llms-full.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server.
# Max Capacity Setup
The **Max Capacity Connectors** journey is currently in **Limited Preview** and is not yet available to all customers. The Enterprise Search Application and Plugin themselves are generally available — access depends on entitlement. Contact your Moveworks account team to learn more.
For an overview of what Enterprise Search is and how it works, see [Enterprise Search Overview](/ai-assistant/enterprise-search/overview). For the inventory of supported connectors and their capabilities, see [Search Connectors](/ai-assistant/enterprise-search/search-connectors).
## 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](/ai-assistant/enterprise-search/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
This step applies to **indexed connectors only**. Live Search connectors (such as Outlook, Slack, and Jira) query the source system in real time and do not require an 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:
| Option | Description |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| All users | Allows all users in your organization to search this content. Source permissions from the connected system are still strictly enforced. |
| Selected users by email ID | Grants access only to specific individuals by entering their email addresses. Up to 100 users can be added. Use the search field to find and add users. |
| No users | Temporarily disables this content from appearing in anyone's search results. |
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.