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
| Check | Question to resolve |
|---|---|
| Requester | How is a messaging identity associated with an enterprise account? |
| Conversation scope | Which content is allowed in direct and group chats? |
| Application identity | Does the service have more data access than the task requires? |
| Citations and files | Is access checked again when the link opens? |
| Lifecycle | How are departures, role changes and revocation of application access handled? |
Test an entire workflow with synthetic data
- Confirm the entry point's authorizations and required features, then configure the minimum permissions.
- Have two test identities with different permissions ask the same question and compare their results.
- Show only a summary every group member may read, and verify the link back to its source.
- 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.
