Templates on the Agreements page (/app/governance/templates) store the CLA legal text your organization enforces. Each saved version is immutable for audit purposes; updates create new versions.

What you can do

• List organization-wide CLA templates
• Create a template with Markdown body content
• Import Dropbox Sign templates for e-signature-based signing
• Open /app/governance/templates/[templateId] to edit and review versions

Versioning

Every template version has a content hash. Signatures and corporate agreements bind to that hash:

• Contributors must sign again when you activate a new version on a repository
• Historical signatures remain tied to older hashes for compliance records

Communicate version bumps to contributors before switching the active version on busy repositories.

Assigning templates to repositories

Templates are not global enforcement by themselves—you assign a template version on each repository detail page where Open CLA is installed.

Best practices

• Use clear template titles (e.g. “Standard CLA v2”)
• Review language with counsel before production use
• Use Dropbox Sign when you need a hosted e-signature audit trail
• Keep one active version per repo unless you intentionally run parallel policies

Next steps

• Integrations
• How CLA checks work
• Contributors