Integrations

What we connect to, and what we read.

Dagron integrates with the tools your engineering organization already uses. We read the minimum metadata needed to produce capitalization reports — and nothing else. Below is the full list with explicit data scopes for each integration.

Tools available today
3
GitHub, Jira, Workday
Source code accessed
None
Metadata only
Data used for AI training
Never
Customer or model
GitHub
Source controlAvailable

Auto-discover projects from your pull requests, attribute work to contributors, and capture effort signals.

What we read
  • Pull request titles, descriptions, branch names
  • PR authors, reviewers, merge dates
  • Lines added/removed, files changed counts
  • Issue titles, labels, assignees
  • Repository names and basic metadata
What we don't read
  • Source code or file contents
  • PR diffs or commit content
  • Private repository code
  • Secrets or environment variables
Scopes / permissions requested
metadata: readcontents: readpull_requests: readissues: readmembers: read

Installed as a GitHub App, not a personal OAuth grant. You control which repositories we see at install time and can revoke anytime from your GitHub settings.

Jira Cloud
Project planningAvailable

Map Epics or Initiatives to capitalization projects. Pull issues, labels, and status into work-item tracking.

What we read
  • Epic and Initiative titles, descriptions, status
  • Issue titles, types, assignees, labels
  • Custom field values (where you've configured mapping)
  • Project metadata (key, name)
  • User profiles for matching to contributors
What we don't read
  • Issue attachments or comments (only counts, not content)
  • Private project workflows or admin settings
  • Other Atlassian product data (Confluence, Bitbucket)
Scopes / permissions requested
read:jira-workread:jira-userread:meoffline_access

OAuth 2.0 (3LO) with refresh tokens. Sync runs every 6 hours plus manual resync. Webhooks coming when we move to a Connect app.

Linear
Project planningRoadmap

Map Linear Projects or Initiatives to capitalization projects. Same data shape as Jira.

What we read
  • Initiative and Project titles, descriptions, status
  • Issue titles, labels, assignees
  • Cycle data for effort attribution
What we don't read
  • Issue comments content
  • Private workspace settings
Scopes / permissions requested
read

Available in our roadmap. Reach out if Linear is your primary planning tool.

Workday
HRISBeta

Pull contributor compensation, employment dates, and PTO so reports use accurate cost data.

What we read
  • Employee name, work email, employment type
  • Annual salary and currency (used for hourly-rate derivation)
  • Salary effective dates
  • Approved time-off ranges (for monthly availability)
What we don't read
  • Performance reviews or HR notes
  • Bank account / payroll details
  • Health, demographic, or compliance data
Scopes / permissions requested
Worker (Read)Compensation (Read)Time Off (Read)

Per-tenant configuration. Currently beta — contact us for setup. ADP, Gusto, BambooHR, Rippling are on the roadmap.

Okta / Azure AD
IdentityRoadmap

SAML SSO and SCIM provisioning for Enterprise customers.

What we read
  • User profile (name, email)
  • Group memberships (for role assignment)
What we don't read
  • Authentication credentials
  • MFA tokens
Scopes / permissions requested
openidprofileemail

Available on Enterprise plans. Roll-out target: Q3 2026.

Need an integration we don't list?

We prioritize roadmap based on real customer demand. Tell us what you use and how you'd use it.

Book a demo to discuss →