CLA Automation
Automated CLA collection that runs inside every PR
From the moment a new contributor opens a pull request, Cohorto detects, requests, and confirms their CLA signature — without any manual intervention from your team.
How CLA collection works in your PR flow
PR opened
New contributor
CLA check runs
Status check via webhook
Signature requested
In-thread PR comment
Contributor signs
Hosted signing portal
Status: cleared
Merge unblocked
What the automation covers — and what it doesn't do for you
PR status checks
Cohorto integrates directly as a required status check. PRs with unsigned CLAs block until all contributors are cleared.
Custom CLA templates
Upload your legal team's exact CLA language. Version-control your template — Cohorto tracks which version each contributor signed.
Re-sign management
Update your CLA text and Cohorto automatically surfaces contributors who need to re-sign under the new version.
Corporate CLA support
Issue both Individual and Corporate CLAs. Corporate agreements map all employees under a single authorized signing authority.
Contributor identity
Tie each signature to a verified GitHub, GitLab, or Bitbucket identity. Prevent signing from ephemeral throwaway accounts.
Slack notifications
Get notified in your OSPO Slack channel when a new CLA is pending, signed, or expired. No more polling the dashboard.