> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/easycla/v1-deprecated/project-managers/add-contributor-license-agreements.md).

# Add Contributor License Agreements

The CLA Management Console lets you select a template style to use for your Corporate CLA and Individual CLA.

In some circumstances, you need to change the legal text of the CLA agreement in major and minor revisions:

* A major revision (for example, a change to your charter) is one in which you are legally required to have all contributors re-sign the revised agreement.
* A minor revision is one that does not change a legal perspective and contributors do not need to re-sign the revised agreement.

In these cases, you simply add the updated CLA using the same procedure as for adding the initial CLA.

*Verify that the pop-up blocker is disabled on your browser before you begin this procedure.*

**To Add CLA:**

1\. [Sign in](/lfx/easycla/v1-deprecated/project-managers/sign-in-to-the-easycla-management-console.md) to the CLA management console.

2\. Click a **project** of interest.

3\. Go to the CLA group to which you want to add a CLA and click **SELECT TEMPLATE**.\
The Select a template page appears and lists available templates.

![CLA Select a template](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-831642e8a61bf1844038385cb6964df2caf436c3%2Fcla-select-a-template-page.png?alt=media\&token=fd7e1864-3fc0-49dd-9405-43bfa3dba6e2)

4\. Click the **button** on the template you want to use.

A template information form appears. The information you enter in this form will populate the corresponding fields in the resulting Corporate CLA and Individual CLA PDFs. The following form is an example; each form is specific to the project.

![CLA Select a template form](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-d2a71cefdbb7793b8d3d5e9088cfc75e4756d4e1%2Fcla-select-a-template-form.png?alt=media)

5\. Complete the form fields and click **GENERATE AND REVIEW PDFS**.\
The CLA appears.

6\. Click **VIEW CCLA** (Corporate CLA) or **VIEW ICLA** (Individual CLA) to view the respective PDF and scroll through the content to review it.

![CLA PDF content](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-10ac462893355efcf87c65799b4722551db77225%2Fcla-pdf-content.png?alt=media\&token=b72bd8a9-8c6c-40e9-be54-d8cd41430ce2)

7\. Click **DONE**. (BACK TO TEMPLATE INFORMATION returns you to the template form.)

The Projects page shows that you have successfully uploaded the Corporate CLA and Individual CLA templates under your CLA Group. Refresh the page if the templates do not appear.

## Next Step: <a href="#next-step" id="next-step"></a>

* (Optional) [View Current and Previous CLA PDFs](/lfx/easycla/v1-deprecated/project-managers/view-current-and-previous-cla-pdfs.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.linuxfoundation.org/lfx/easycla/v1-deprecated/project-managers/add-contributor-license-agreements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
