Supported integrations
Last updated: October 12, 2026
Span connects to the tools your engineering team already uses, so you can see delivery, time allocation, and AI impact in one place.
Why it matters
Span builds its metrics from the systems your team already works in. Nothing new needs to be logged. More connections give a more complete picture. For example, adding your calendar lets Span show focus time next to cycle time.
How it works
Category | Integrations | What Span uses it for |
|---|---|---|
Version control | GitHub, GitHub Enterprise (Server, or Cloud with data residency), GitLab (Cloud or self-hosted), Azure DevOps | Pull requests, commits, and repository activity for code review, cycle time, and productivity metrics |
Project management | Jira, Linear, GitHub Issues, Azure DevOps Boards | Issues, sprints, and cycles for planning, delivery, and ticket cycle time |
Incident management | incident.io, Rootly | On-call load, incident frequency, and mean time to resolution |
Calendar | Google Calendar, Microsoft Outlook (Microsoft 365) | Meeting load and focus time |
Communication | Slack | Survey delivery, notifications, and running Src and Playbooks in Slack |
HRIS and directory | BambooHR, HiBob, Workday, ADP Workforce Now, Rippling, Dayforce, Deel, Leapsome, Personio, UKG Pro, Okta, Google Workspace, Microsoft Entra ID, SFTP file drop | Teams, managers, and org structure. Most HRIS connections also bring in time off, so metrics account for absences. |
AI coding tools such as Cursor, Claude Code, and GitHub Copilot are covered in Supported AI coding tools.
Single sign-on and user provisioning
Span supports SSO over SAML and SCIM user provisioning with identity providers including Okta, Microsoft Entra ID, and Google Workspace.
SSO lets your team sign in to Span with your company identity provider. Once it is on, email and password sign-in is turned off.
SCIM grants and removes Span access automatically as people are added to or removed from your identity provider.
SSO and SCIM control who can sign in. Team and manager structure still comes from your HRIS or directory connection above.
Setup
An admin connects each integration from Span's settings. Your Span team walks through setup during onboarding, and the first data sync can take a few hours.
Things to know
One version control system is enough to start. Project management, HRIS, and calendar connections add depth but are not required on day one.
GitHub Copilot connects through GitHub. It is turned on inside your GitHub connection, not as a separate integration.
Don't see your tool? Contact us. We add integrations based on customer demand.
Related articles
Supported AI coding tools
Span products and use cases
More in Span customer library
Customers and teams running POC get the full library of 130+ articles including:
Productivity Metrics: definitions for every metric
AI Transformation: AI tool setup, deployment and guides
Getting Started: SSO, SCIM, roles, roster, and implementation setuo
DORA, Allocation, Cost Capitalization, and Survey guides
Already a customer? Log in (top right corner). Evaluating Span? Talk to us about POC access.
Need help?
Reach out to your Span team or email support@span.app.