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

# Knowledge Connectors

> Connect Feishu, DingTalk, IMA, Yuque, and other external knowledge bases to give Expert access to your team knowledge

Profy's knowledge capability is an external knowledge base **connector**. In the default mode, your documents stay on their original platforms, and Expert accesses them directly via API — no importing, no vectorization required.

If you need higher search precision, you can enable **RAG Indexing** for any connection — the system will periodically sync documents locally, chunk them into vector-indexed segments, and use hybrid retrieval instead of native platform search. See [Knowledge RAG Pipeline](/en/documentation/how-it-works/knowledge-rag) for details.

<Warning>
  Before use, you must bind your knowledge platform credentials in **Settings → Connectors**. Expert cannot access platforms that haven't been connected.
</Warning>

## Supported Platforms

<CardGroup cols={2}>
  <Card title="Feishu / Lark" icon="feather">
    Connect to Feishu cloud documents and knowledge bases. Supports automatic token refresh — credentials are renewed automatically when they expire.
  </Card>

  <Card title="DingTalk" icon="link">
    Connect to DingTalk documents. Also supports automatic token refresh with no manual credential maintenance needed.
  </Card>

  <Card title="IMA" icon="database">
    Connect to the IMA knowledge base platform. Uses Client ID + API Key authentication with no expiration concerns.
  </Card>

  <Card title="Yuque" icon="book">
    Connect to Yuque knowledge spaces. Uses a Personal Access Token for authentication.
  </Card>
</CardGroup>

## Three Steps to Get Started

<Steps>
  <Step title="Bind a Connector">
    Go to **Settings → Connectors**, select the target platform, and fill in the required credentials:

    | Platform      | Required Credentials  | Auth Mode          |
    | ------------- | --------------------- | ------------------ |
    | Feishu / Lark | App ID + App Secret   | Auto token refresh |
    | DingTalk      | App Key + App Secret  | Auto token refresh |
    | IMA           | Client ID + API Key   | Static key         |
    | Yuque         | Personal Access Token | Static token       |

    Credentials are stored encrypted and are never exposed in any API response.
  </Step>

  <Step title="Enable the Knowledge Plugin">
    Knowledge is a **manually enabled** plugin. In the chat interface, click the "+" menu and check the **Knowledge** plugin. Without enabling the plugin, Expert cannot access knowledge bases even if connections exist.
  </Step>

  <Step title="Start a Conversation">
    Once enabled, simply ask Expert questions in the conversation. You can specify a platform ("Search for OKR-related content in Feishu docs"), or leave it unspecified — Expert will search across all connected platforms.
  </Step>
</Steps>

## What Expert Can Do

Once connections are established, Expert can perform five types of operations in conversations:

<AccordionGroup>
  <Accordion title="Search Knowledge">
    Search for relevant documents across connected platforms based on your questions. When no platform is specified, it searches all platforms.
  </Accordion>

  <Accordion title="Browse Directories">
    List the document directory structure of a knowledge base to help you locate content.
  </Accordion>

  <Accordion title="Read Documents">
    Read specific document content and reference or analyze it in the conversation.
  </Accordion>

  <Accordion title="Create Documents">
    Create new documents in the knowledge base. For example: "Organize our discussion into a Feishu document."
  </Accordion>

  <Accordion title="Append Content">
    Append new content to existing documents — ideal for continuously updated documents such as meeting notes or project logs.
  </Accordion>
</AccordionGroup>

<Note>
  Whether write operations (create, append) are available depends on the specific platform's API support and the permissions of the credentials you provided. Read-only credentials can only search and read.
</Note>

## Use Cases

<CardGroup cols={2}>
  <Card title="Enterprise Knowledge Q&A" icon="comments">
    New employee wants to learn about company policies? Have Expert search the internal knowledge base and answer in natural language.
  </Card>

  <Card title="Cross-Platform Knowledge Integration" icon="layer-group">
    Team has documents on both Feishu and Yuque? Expert searches multiple platforms simultaneously and provides a consolidated answer.
  </Card>

  <Card title="Knowledge Capture" icon="floppy-disk">
    After finishing a discussion, have Expert write the conclusions directly to Feishu or Yuque — avoid letting information get lost in chat history.
  </Card>

  <Card title="Document Generation" icon="file-lines">
    Generate summary reports, comparative analyses, or FAQ compilations based on existing content in your knowledge bases.
  </Card>
</CardGroup>

## Obtaining Platform Credentials

<AccordionGroup>
  <Accordion title="Feishu / Lark">
    1. Visit the [Feishu Open Platform](https://open.feishu.cn) and create a custom app
    2. Request document-related API permissions
    3. Obtain the App ID and App Secret, then enter them in the Profy connector
  </Accordion>

  <Accordion title="DingTalk">
    1. Visit the [DingTalk Open Platform](https://open.dingtalk.com) and create an internal enterprise app
    2. Authorize knowledge base-related API permissions
    3. Obtain the App Key and App Secret, then enter them in the Profy connector
  </Accordion>

  <Accordion title="IMA">
    1. Create API credentials in the IMA platform's developer settings
    2. Obtain the Client ID and API Key, then enter them in the Profy connector
  </Accordion>

  <Accordion title="Yuque">
    1. Log in to Yuque and go to Personal Settings → Token Management
    2. Create a Personal Access Token, then enter it in the Profy connector
  </Accordion>
</AccordionGroup>

<Warning>
  * Use credentials with **appropriately scoped permissions** — avoid using full-access administrator credentials
  * If credentials expire or are revoked on the platform side, you'll need to update them in Settings
  * API calls to each platform are subject to the platform's own rate limits
</Warning>

## Billing

Knowledge Connectors themselves are free. Credit consumption when using knowledge base content in conversations comes from model token usage — the content Expert reads and analyzes from documents counts toward conversation tokens. Actual consumption is displayed in real time within the product.