Templates (/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 global CLA templates shared across repositories
• Create a new template with Markdown body content
• Import Dropbox Sign templates for e-signature based CLA signing
• Open a template detail page (/app/governance/templates/[templateId]) to edit and review versions

Versioning

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

• Contributors must sign again when you roll out new CLA text
• Historical signatures remain tied to older hashes for compliance records

Best practices

• Use clear template titles (e.g. “Standard CLA v2”)
• Communicate version changes to contributors before switching active versions on repos
• Review template language with counsel before production use
• Use Dropbox Sign templates when the signing process needs a hosted e-signature audit trail

Next steps

• Integrations
• Repositories
• How CLA checks work