> 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-a-cla-group.md).

# Add a CLA Group

A CLA group defines:

* What CLA types your project requires for pull requests or push submissions—the agreement types are for corporate or individual CLAs
* What CLAs and their versions are used for the contributors
* What GitHub repositories, Gerrit instances, or both enforce CLA monitoring

A CLA group gives you the flexibility to handle different CLA requirements for various GitHub repositories and Gerrit instances.

**To Add a CLA Group**:

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.\
The project page appears. A message informs you that your project needs a CLA group. A CLA group defines one or more CLA types that contributors must sign before they can contribute to a project.

3\. Click **ADD CLA GROUP**.

4\. Complete the dialog options:

![CLA CLA Group](/files/-M6ckdP-WdRu_IESJ6gL)

5\. Enter a **CLA Group Name**.\
The CLA Group Name indicates that a project has one or more CLAs (Individual CLA, Corporate CLA, or both). Consider matching the CLA group name to the project name for easy identification.

6\. Select the CLA types that you want applied to contributions to the project:

1. **Corporate CLA: to be signed by a company** - This Corporate CLA must be signed by the CCLA signatory for your company. This person has authority to enter into legal contracts on behalf of the corporation.
2. **Individual CLA: to be signed as an individual contributing** - A developer who is not contributing on behalf of any company signs this Individual CLA. This individual is contributing to a project on their own behalf. Selecting this type automatically enables the "Contributors under Corporate CLA must also sign Individual" CLA type.
3. **Contributors under Corporate CLA must also sign Individual CLA** - Employees (developers) of a company use this agreement. A Corporate CLA may not remove the need for every employee to sign their own Individual CLA as an individual. This option covers both owned contributions and not-owned contributions by the corporation signing the Corporate CLA.

7\. Click **SAVE**.

The CLA group that you added and the CLA types that you specified appear under CLA Groups.

### Next Steps:

* [Add Contributor License Agreements](/lfx/easycla/v1-deprecated/project-managers/add-contributor-license-agreements.md)
* [Add GitHub Repositories to CLA Monitoring or Remove Them From CLA Monitoring](/lfx/easycla/v1-deprecated/project-managers/add-github-repositories-to-cla-monitoring-or-remove-them-from-cla-monitoring.md)

  or
* [Add Gerrit Instances to CLA Monitoring or Delete Them From CLA Monitoring](/lfx/easycla/v1-deprecated/project-managers/add-gerrit-instances-to-cla-monitoring-or-delete-them-from-cla-monitoring.md)
* (Optional) [Manage CLA Group Details](/lfx/easycla/v1-deprecated/project-managers/manage-cla-group-details.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.linuxfoundation.org/lfx/easycla/v1-deprecated/project-managers/add-a-cla-group.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.