Browse the documentation
AI-Soda Brain

Prepare an integration with Feishu or another collaboration platform

Carry the user's identity and viewing scope into the collaboration tool where questions are asked. What a chat group can see, what an application can access and what an individual may read are three separate conditions to verify.

Technical guide · November 20263 min read

Choose an entry point and use case

Decide whether users ask questions in a direct chat, group chat, message card or business portal. Check which entry points and versions your deployment supports. Consider the audience before placing detailed business records in a message.

Start with read-only summaries and citations that return to an access-controlled page. Before showing detailed records, check whether all conversation members have the required authorization. If necessary, direct the user to a page that enforces individual access.

Map identity to scope

CheckQuestion to resolve
RequesterHow is a messaging identity associated with an enterprise account?
Conversation scopeWhich content is allowed in direct and group chats?
Application identityDoes the service have more data access than the task requires?
Citations and filesIs access checked again when the link opens?
LifecycleHow are departures, role changes and revocation of application access handled?

Test an entire workflow with synthetic data

  1. Confirm the entry point's authorizations and required features, then configure the minimum permissions.
  2. Have two test identities with different permissions ask the same question and compare their results.
  3. Show only a summary every group member may read, and verify the link back to its source.
  4. Test duplicate messages, timeouts, access revocation and conversation changes. Check that users can understand errors and retries.

Tie notifications to a specific task

Let users choose subscription scope and frequency and make stopping a subscription straightforward. Send the necessary summary and a controlled link, so complete sensitive results do not remain in chat history.

This guide covers collaboration entry-point design and validation. For application configuration, authorization scopes, event subscriptions and identity binding, use the official instructions for the connector and deployment version in use.

Try “permissions,” “data source,” “manufacturing” or “API.”