Capabilities
| Feature | Description |
|---|---|
| Notification Delivery | Receive automated notifications about GitHub activity and documentation updates |
| Message Sync | Sync channel messages for AI context and searchability |
| Channel Management | View and select channels across your Teams workspace |
| AI Search | Search and analyze Teams conversations using natural language |
| OAuth Integration | Secure authentication via Microsoft identity platform |
Connecting Microsoft Teams
Kasava supports two connection methods for Microsoft Teams: OAuth for full workspace access, and Webhooks for simple notifications.OAuth Connection (Recommended)
OAuth provides full access to channels, messages, and AI features.Start Connection
Click the Microsoft Teams card to open the connection page, then click Connect Teams Workspace

Sign in to Microsoft
You’ll be redirected to Microsoft’s sign-in page. Enter your Microsoft 365 credentials

Kasava uses Microsoft’s OAuth 2.0 authentication. Your Microsoft credentials are never stored—only an access token for API calls.
Webhook Connection
Webhooks are useful for simple notification delivery without full workspace access.Configure Webhook
- Give the webhook a name (e.g., “Kasava Notifications”)
- Optionally upload an image
- Click Create
Managing Your Connection
After connecting via OAuth, click Manage on the Microsoft Teams integration card to access configuration options.Connection Status
View your workspace details:- Connection Status - Whether the integration is active
- Organization - Your Microsoft 365 organization name
- Last Sync - When data was last synchronized
Sync Settings
Configure how Kasava syncs your Teams data:| Setting | Description |
|---|---|
| Historical Data | Number of days to sync (1-90 days, default: 30) |
| Sync Messages | Import channel messages for AI context and search |
| Team Selection | Choose specific teams to sync |
| Channel Selection | Choose specific channels within teams |
Token Management
If you experience connection issues, click Refresh Token to renew your OAuth credentials.Viewing Channels
After connecting via OAuth, you can view all accessible channels:
Channels are organized by team:
- Team Name - The parent team
- Channel Name - Individual channels within the team
- Membership Type - Standard, Private, or Shared
Notification Channels
Set up Microsoft Teams as a notification destination to receive automated updates from Kasava.Creating a Notification Channel
Configure Channel
- Channel Name - A friendly name (e.g., “Engineering Updates”)
- Teams Webhook URL - Paste your webhook URL from Teams
Available Notifications
Configure which events send notifications to Teams:- Documentation Updates - When auto-generated documentation is ready
- Repository Activity - New commits, PRs, and issues
- Product Updates - Roadmap item status changes
- AI Digests - Scheduled summary reports
Using Teams in AI Chat
Once connected via OAuth, you can search and interact with Teams using natural language in Kasava’s AI chat:Example Commands
- “Find Teams messages about the Q4 roadmap”
- “Search Teams for discussions about the API migration”
- “Show me recent messages in the Engineering channel”
- “Send a message to the Product Updates channel”
AI Features
Conversation Search
Kasava indexes synced Teams messages to enable semantic search:- Natural language queries - Ask questions in plain English
- Cross-channel search - Find messages across all synced channels
- Team filtering - Narrow results to specific teams
Context Building
Synced Teams messages provide context for AI features:- Include team discussions when generating documentation
- Reference past decisions in planning documents
- Build comprehensive project timelines from conversations
Permissions
Kasava requests the following Microsoft Graph permissions during OAuth:| Permission | Purpose |
|---|---|
Team.ReadBasic.All | List teams you’re a member of |
Channel.ReadBasic.All | List channels in your teams |
ChannelMessage.Read.All | Read messages from channels |
User.Read | Access your basic profile information |
ChannelMessage.Send | Send messages on your behalf |
Kasava only accesses teams and channels where you are a member. Admin consent may be required by your organization’s Microsoft 365 administrator.
Admin Consent
Some organizations require admin consent for third-party applications. If you see an “Admin approval required” message:- Contact your Microsoft 365 administrator
- Share the Kasava application ID for review
- Once approved, return to Kasava and try connecting again
Disconnecting Microsoft Teams
To disconnect your Teams workspace:- Go to Settings → Integrations
- Click on the Microsoft Teams integration
- Click Manage
- Click Disconnect in the settings
- Confirm the disconnection
Troubleshooting
OAuth authorization requires admin approval
OAuth authorization requires admin approval
Messages not syncing
Messages not syncing
Verify that message syncing is enabled in your integration settings. Click Sync Now to trigger a manual sync. Note that syncing large workspaces may take several minutes.
Webhook notifications not being delivered
Webhook notifications not being delivered
Check that your webhook URL is correct and hasn’t expired. Teams webhooks can be disabled by workspace administrators. Try creating a new webhook if the current one isn’t working.
Can't see certain teams or channels
Can't see certain teams or channels
Kasava can only access teams and channels where you are a member. For private channels, ensure you’ve been added as a member.
Connection shows 'Needs Re-auth'
Connection shows 'Needs Re-auth'
Microsoft OAuth tokens expire periodically. Click the integration card and click Refresh Token to renew your connection. If that fails, disconnect and reconnect the integration.
Error: Insufficient privileges
Error: Insufficient privileges
This typically means the required Microsoft Graph permissions weren’t granted during OAuth. Try disconnecting and reconnecting, ensuring you accept all requested permissions.
Security
- All OAuth tokens are encrypted at rest
- Webhook URLs are stored securely and never exposed in logs
- You can revoke Kasava’s access anytime from your Microsoft account settings
- Kasava uses Microsoft’s OAuth 2.0 with PKCE for enhanced security
- Data is transmitted over HTTPS only