> ## Documentation Index
> Fetch the complete documentation index at: https://koreai.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Invision Community Connector

[Back to Search AI connectors list](https://koreai.mintlify.site/ai-for-service/searchai/content-sources.md#supported-connectors)

Invision Community is a community platform used by organizations to host online forums, discussion boards, and member communities. You can configure Search AI to connect to your Invision Community instance to enable users to fetch query results using forum topics and posts from your community.

| Specification | Details |
| - | - |
| Repository type | Cloud / On-premises |
| Supported content | Forum Topics (Threads) and Posts, Custom Databases and Downloads |
| Content filtering | Yes (forum selection and sync scope filters) |
| RACL support | Yes |

## Authorization Support

Search AI supports **API Key-based** authentication for communicating with Invision Community. Authentication requires a **Base URL** pointing to your community instance and an **API Key** generated from your Invision Community admin panel.

## Integration Steps

To configure Invision Community as a content source, complete the following steps.

* Configure the Invision Community connector in Search AI
* Set up Permissions
* Configure Content Scope
* Schedule Sync

## Step 1: Configure the Invision Community Connector in Search AI

### Prerequisites - Obtaining an API Key

Before configuring the connector, generate an API key from your Invision Community admin panel:

1. Log in to your Invision Community admin panel.
2. Navigate to **System > REST & OAuth > API Keys**.
3. Create a new API key with read access to forums, topics, and posts.
4. Copy the generated API key for use in the connector configuration.

### Configuring the Connector

Go to **Connectors** under the Sources page and select **Invision Community**. On the **Authentication** tab, enter the following details and click **Connect**.

| Field | Description |
| - | - |
| Name | A unique name for this connector instance. |
| Base URL | The root URL of your Invision Community instance (for example: `https://community.example.com`). |
| API Key | The API key generated from your Invision Community admin panel. |

Once successfully authenticated, the status shows as **Connected**.

## Step 2: Set Up Permissions

Go to the **Permissions** tab to configure access control for the ingested content. The following options are available.

* **Same users as in the source system (Restricted Access)** - Applies RACL-based access control. Permissions are enforced using platform/RACL configuration. The permissions aren't continuously synced from Invision Community; you must manually update any permission changes in the source system using RACL configuration.
* **Everyone (Public Access)** - All users get full access to the ingested content, overriding any previous restrictions in the connector.

> [!NOTE]
>
> Automatic permission sync isn't supported for the Invision Community connector. File attachments within topics or posts aren't ingested as part of the connector flow.

## Step 3: Configure Content Scope

Go to the **Content Scope** tab under Connector Setup to define which forums and content are ingested.

| Option | Behavior |
| - | - |
| **All Content** (default) | Syncs content from all available content types in your community. |
| **Filtered Content** | Allows you to choose individual content types to sync. |

You can set up standard or advanced filters to sync specific content.

**Standard Filter**: Lists all forums available forums. Select one or more forums to ingest the content from the selected forums. \*\*
Advanced Filters:\*\* Define rules to sync content using the content type and their parameters like id or clubs. You can add any number of rules to set up filtering. Within each rule, you can add multiple conditions using logical AND or OR operators.

> [!NOTE]
>
> Only content available via the configured API key is ingested. Private or member-restricted forums are synced only if the service account has the appropriate access permissions.

## Step 4: Sync Content

After configuring the connector, go to **Schedule Sync** to initiate and manage content synchronization.

* Use the **Sync** option for an immediate, on-demand sync.
* Enable **Schedule Sync** to set up automated, recurring syncs.

The Schedule Sync table displays a log of all sync activity with the following details.

| Field | Description |
| - | - |
| Sync Scope | The scope of the sync (for example, Full Sync). |
| Sync Type | Indicates whether the sync was On-Demand or Scheduled. |
| Sync Status | The result of the sync (for example, Successful). |
| Triggered By | The user who initiated the sync. |
| Started On | The date and time the sync started. |
| Completed On | The date and time the sync completed. |

## Content Ingestion

Once the sync is complete, go to the **Content** tab to review the ingested content. The tab displays the count of files that are Successful, Failed, and Skipped, along with the total number of Accessible Files.

Search AI ingests two content types from Invision Community.

### Forum Topics (Threads)

The following key fields are extracted and indexed for each forum topic.

* `title` - The title of the forum topic or thread.
* `content` - The body text of the opening post in the thread, made available for search operations.
* `doc_id` - A unique identifier for the ingested topic, derived from the topic ID in Invision Community.
* `doc_source_type` - Identifies the content type as a forum topic.
* `doc_created_on` or `doc_updated_on` - Timestamps capturing when the topic was created and last updated.
* `url` - The URL pointing to the topic in your Invision Community instance.
* `forum` - The name of the forum the topic belongs to.
* `author` - The username of the member who created the topic.

### Posts (Replies)

The following key fields are extracted and indexed for each post within a topic.

* `title` - Derived from the parent topic title for context.
* `content` - The body text of the individual post or reply.
* `doc_id` - A unique identifier for the ingested post, derived from the post ID in Invision Community.
* `doc_source_type` - Identifies the content type as a forum post.
* `doc_created_on` or `doc_updated_on` - Timestamps capturing when the post was created and last updated.
* `url` - The URL pointing to the specific post within its topic thread.
* `author` - The username of the member who authored the post.

> [!NOTE]
>
> File attachments within topics or posts are not ingested as separate documents in the connector flow.

## RACL Support

Search AI provides access control support for forums and posts ingested from Invision Community. The `sys_racl` field is used to enforce access control by associating the appropriate permission identifiers with the ingested content, ensuring that users can only access forums and posts they are authorized to view.

| Feature | Status |
| - | - |
| RACL Support | Available (can be enabled) |
| RACL Sync | Not applicable (manual configuration required) |

* When RACL is disabled (default), all ingested content is publicly accessible (`sys_racl` is set to `*`).
* When RACL is enabled:
  * Forums and posts entries include the appropriate permission entity identifiers in the `sys_racl` field. Public forums and posts have sys\_racl set to \*.
  * Other content types (such as downloads, custom databases) are always treated as publicly accessible and have `sys_racl` set to `*`.
  * Since automatic permission synchronization is not supported, use the [Permission Entity APIs](https://koreai.mintlify.site/ai-for-service/apis/searchai/permission-entity-apis) to manually associate users with the appropriate permission entities after ingestion.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.