> ## 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.

# Aha! Connector

<Badge icon="arrow-left" color="gray">[Back to Search AI connectors list](/ai-for-service/searchai/content-sources#supported-connectors)</Badge>

The Aha! connector integrates with the Aha! REST API to ingest Ideas and Features into Search AI, making them searchable across your knowledge base.

| Specification | Details |
| - | - |
| Repository type | Cloud |
| Supported content | Ideas, Features |
| RACL support | Yes |
| Content filtering | No |
| Auto permission resolution | Yes |

## Authorization Support

The Aha! connector supports two authentication methods:

1. API Key
2. OAuth 2.0 (Authorization Code grant)

## Generate an API Key

1. Sign in to Aha!.
2. Click the **Settings** icon (top right) and select **Personal**.
3. Go to the **Developer** page.
4. On the **API Key** tab, click **Generate API Key** and provide a name for the key.
5. Save the generated key — you will need it to configure the connector in Search AI.

## Generate OAuth Credentials

1. Sign in to Aha!.
2. Click the **Settings** icon (top right) and select **Personal**.
3. Go to the **Developer** page.
4. On the **OAuth Applications** tab, click **Register OAuth application**.
5. Enter a name and set the Redirect URI based on your region or deployment:
   * JP Region: `https://jp-bots-idp.kore.ai/workflows/callback`
   * DE Region: `https://de-bots-idp.kore.ai/workflows/callback`
   * Production: `https://idp.kore.com/workflows/callback`
6. Save the generated client ID and client secret.

## Configure the Aha! Connector in Search AI

On the **Authorization** page of the Aha! connector, provide the following fields and click **Connect**.

| Field | Description |
| - | - |
| **Name** | Unique name for the connector |
| **Authorization Type** | Select API Key or OAuth 2.0 |
| **API Key** | (If API Key selected) The key generated in Aha! |
| **Grant Type** | (If OAuth selected) Set to Authorization Code |
| **Client ID / Client Secret** | (If OAuth selected) Credentials from the Aha! OAuth application |

## Content Ingestion

After authorization, sync content from the **Configuration** tab.

1. Go to the **Configuration** tab.
2. Click **Sync Now** for an immediate sync, or configure a **Schedule Sync** for future runs.

Search AI ingests **Ideas** and **Features** from your Aha! application. The `type` field in each ingested record indicates whether the content is an idea or a feature.

## RACL Support

**Features**

Features are accessible to all workspace and project users. When ingested, the `sys_racl` field is set to the **Project ID** of the project the feature belongs to. Search AI automatically resolves permission entities — it identifies users with project access and maps them to the corresponding Project ID permission entity.

**Ideas**

Idea access depends on the **Visibility for Ideas in Portal** setting:

| Visibility Setting | Access Control |
| - | - |
| Not visible | Visible to project users only. `sys_racl` = Project ID |
| Visible to creator | Visible to the creator in the portal and all workspace members. `sys_racl` = Project ID + creator email |
| Visible to all | Visible to everyone. `sys_racl` = `*` |
| Visible to employees | Accessible to project users and idea portal users. `sys_racl` = Project ID + idea portal ID |
| Private idea portal | Visible to workspace members and users added to the portal. `sys_racl` = Project ID + idea portal ID |


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