Connected work tools link the systems where work already happens to 15Five AI, so Agents can ground their insights in real work activity instead of self-reported updates alone.
This article explains what connected work tools are and where to set them up. For HRIS, SSO, or SCIM integrations, see Integrations & Identity: Overview.
In this article
- What connected work tools do
- How access and privacy work
- How connected work tools relate to AI-Assisted Reviews
- Where to connect and manage them
Access and Availability
- Company Admins, HR Admins, and IT Admins can connect or assign a work tool
- Requires access to Agents Hub
- Available in the Perform and Total Platform pricing packages
Availability varies by integration. The Integrations tab in Agents Hub shows the current status of each one, including any that are still coming soon.
Feature Structure
Connected work tools are managed from Agents Hub > Integrations, where they are grouped by category. Each integration has its own detail drawer covering what it enables, what data is used, the permissions it requests, and any plan requirements.
Connected work tools are separate from platform integrations such as HRIS, SSO, and SCIM, which are configured elsewhere and cover identity and provisioning rather than work activity.
Supported integrations
The following integrations are available. Availability and setup requirements vary by integration, so check the Integrations tab in Agents Hub for the current status of each one. Each article covers that integration's own permissions, synced data, and backfill window.
- Slack
- Microsoft Teams
- Granola
- Google Calendar
- Microsoft Outlook
- Jira
- Asana
- Linear
- GitHub
- Google Drive
- Microsoft OneDrive
- Notion
- Salesforce
- HubSpot
- Zendesk
- Claude.ai
- Cursor
- OpenAI Codex
How access works
Each integration reads only what the connected account, API key, or approved source permissions allow. Insights stay permission-aware, so people only see insights drawn from information they already have access to in the source tool. Data from private channels, spaces, or restricted projects is not surfaced to someone who is not already part of them.
How connected work tools relate to AI-Assisted Reviews
AI-Assisted Reviews can use evidence from supported connected work tools to help review writers bring relevant work into a review. That evidence can appear as Moments, which are examples of work a writer can inspect and decide whether to use.
The supported sources are Slack, Microsoft Teams, Jira, Asana, Zendesk, Linear, GitHub, Google Drive, OneDrive, Notion, Google Calendar, and Kona Meeting Assistant. Other integrations in the list above support different 15Five AI capabilities, so check an integration's own article for what it does.
Four things are worth understanding before you connect a source for this purpose:
- These connected sources are optional. A customer can still use AI-Assisted Reviews without them, drawing on relevant context already in 15Five along with Company Context, Prompt Instructions, and information a review writer adds.
- Only activity inside the cycle's performance period is eligible. The performance period is set on the review cycle and is separate from the cycle's own open and close dates. Work outside that range does not become a Moment for that cycle.
- Relevant does not mean guaranteed. Even activity from a supported source during the performance period may not become a Moment. Moments are a curated set of meaningful evidence rather than a complete log of activity.
- Connecting a source does not recreate the whole period. Available history varies by integration, so a recently connected source commonly has less history than the performance period covers.
Existing permissions continue to apply, so two writers at the same company can have different evidence available even when the same sources are connected.
For what a Moment is and what does not become one, see Understand Moments in AI-Assisted Reviews. If a writer sees less evidence than expected, see Troubleshoot: A review has fewer Moments than expected.
What You Can Do
Set Up
Manage
Understand the context layer
Common Issues
Key Rules
- Setup requirements, plan requirements, and available data differ by integration. Review the integration's detail drawer before connecting.
- Backfill depth and sync cadence are set per integration, not platform-wide. See the integration's own article for the window that applies to it, and note that actual depth still depends on retention settings and permissions in the source system.
- Connected data is processed to generate insights, patterns, and trends rather than kept as a raw log. The underlying raw content is not retained after 30 days.
- Each integration is read through the permissions granted to the connected identity or API key, and can be revoked from the source tool at any time.
- Insights follow source permissions. Restricted content is never surfaced to people who do not already have access to it.
- Integration availability changes over time. Agents Hub is the source of truth for what is connectable today.
- Connected sources are optional for AI-Assisted Reviews, and only activity inside a cycle's performance period is eligible to become a Moment.