> ## Documentation Index
> Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt
> Use this file to discover all available pages before exploring further.
# LumApps Connector
[Back to Search AI connectors list](/ai-for-service/searchai/content-sources#supported-connectors)
**LumApps** is a digital workplace platform that centralizes internal communication, collaboration, and employee engagement. It serves as a hub where employees can access company news, documents, and tools, and collaborate through communities.
LumApps organizes content into pages, news, custom objects, and community posts. The LumApps connector lets Search AI ingest and index all these content types for intelligent search and retrieval.
## Connector Specifications
| Specification | Details |
| ------------------------------- | ------------------------------------------------------------- |
| Repository type | Cloud |
| Supported content | Content Objects, Pages, News, Custom Objects, Community Posts |
| RACL support | Yes |
| Content filtering | Yes |
| Automatic permission resolution | Yes |
## Connector Configuration
Search AI interacts with LumApps through its APIs using OAuth. You need to create an OAuth application in LumApps and generate client credentials before configuring the connector.
### Create an OAuth Application in LumApps
1. In the LumApps back office, go to **Extensions** > **Installed extensions**.
2. Select **OAuth Application Manager** > **Details**.
3. Go to the **Settings** tab.
4. Click **Add an OAuth application**.
5. Enter a name in the **Application name** field.
6. In the **Scopes** field, select **All.read**.
7. Leave the **Authorized User ID** field blank.
8. Click **Save**.
9. Copy the **Application ID** and **Application secret**.
### Configure the Connector in Search AI
On the **Authorization** tab of the connector, provide the following details:
| Field | Description |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name** | Unique name for the connector |
| **Authorization Type** | Select **Token** |
| **Grant Type** | Select **Client Credentials** |
| **Client ID** | Application ID from LumApps |
| **Client Secret** | Application Secret from LumApps |
| **Organization ID** | Unique identifier for your organization's platform. Found in your platform URL after `org-` (e.g., in `https://org-3731839993107899.app.lumapps.com/`, the Organization ID is `3731839993107899`). Also available in the debug dialog (press **Ctrl+Shift+?**) |
| **User ID** | User ID used to access LumApps content. This user is impersonated to fetch content. Find in the debug dialog |
| **Host URL** | URL of the LumApps API host (also called the **Haussmann cell**). Varies by LumApps environment. Find in the debug dialog |
| **Content-Type** | Type of content to ingest — all content, Pages, or Community Posts |
Click **Connect** to authenticate and establish the connection.
## Content Ingestion
Search AI ingests **Pages, News, and Custom Content Objects** from LumApps, as well as **posts from LumApps communities**. Each page, post, news item, or custom content item is ingested as a separate document.
Key fields in ingested content:
* `resource_type` — identifies whether the record is a content object or a community post
* `doc_source_type` — specifies the type of content object (page, news, or custom)
* `content` — textual content from the ingested record
* `title`, `url`, creation date, and update date are captured in their respective fields
### Attachments
Attachments to content objects or community posts are ingested as **separate records** in Search AI.
For the **parent record**, an `attachment` field lists all associated attachments with their name and URL.
For each **attachment record**:
* `doc_source_type` is set to `attachment`
* `resource_type` is inherited from the parent content object
* The record includes parent metadata: `parent_name`, `parent_url`, and `parent_id`
Supported attachment types: `.doc`, `.docx`, `.ppt`, `.pptx`, `.pdf`, `.txt`, `.html`
### Content Filtering
Use content filtering to control which content is ingested from LumApps.
1. Go to the **Manage Content** page and use the **Object Type** selector to specify the type of content to ingest (Page, News, Custom Object, or Community Post).
2. Select **Ingest Filtered Content** and click **Configure** to apply field-based rules.
3. Define **field-based rules** to refine ingestion further. For example, ingest only news items from the past week.
Choose from available fields for the selected object type in the dropdown and provide operators and values. Field names must match the field names for the selected object in your LumApps account. Use **logical operators** to combine multiple conditions in a single rule.
## Access Control
### Content Objects (Pages, News, Custom Content)
* LumApps controls content visibility through the **Visible By** field in the UI.
* The `sys_racl` field stores the Group ID of the user group that has access to the content. Search AI automatically resolves permission entities, associating users with the correct Group ID.
### Community Posts
* The `sys_racl` field stores the Community ID, ensuring posts are visible only to authorized community members.
* Search AI automatically resolves permission entities by identifying eligible members and associating them with the correct Community ID.