# Glossary

## Approved List

Approved Lists are lists of approval-list entries that authorize contributors under a signed CCLA. These entries can include email address domains, contributor email addresses, GitHub organization names, GitHub usernames, GitLab group URLs, or GitLab usernames. [CLA Managers](#cla-manager) create and manage the approved list.

## Approval Criteria

Approval Criteria is the category under which a contributor is added to the approved list. There are six approval criteria currently available in EasyCLA: Email Address Domain, Contributor’s Email, GitHub Organization, GitHub Username, GitLab Group URL, and GitLab Username.

## **CLA**

A Contributor License Agreement (CLA) defines the terms under which content is contributed to a project. Typically, the content is software which the project makes available under an open source license.

A project's intellectual property policy will define whether or not it uses a CLA. Frequently, if a project does use a CLA, it will have different templates to be signed by a company (CCLA) or by an individual (ICLA).

## **CCLA**

A Corporate Contributor License Agreement (CCLA) defines terms and conditions under which employees contribute code on behalf of the company.

## **CLA Template**

A CLA template is a form of CCLA or ICLA used by a Project Manager to configure the CLA Group for a project.

## **CLA Group**

A CLA group defines CLA details, such as which CLA types (ICLA and/or CCLA) a project requires for pull requests or push submissions, which GitHub repositories, GitLab groups/projects, and/or Gerrit instances are checked against those CLAs, and which projects are linked to those CLAs. One CLA group is used under a unique [CLA template](https://docs.linuxfoundation.org/lfx/easycla/v2-current/project-managers/create-new-cla-group#select-cla-template).

## **ICLA**

An Individual Contributor License Agreement (ICLA) defines terms and conditions under which individuals contribute code on their own behalf.

## **CLA Manager**

CLA Managers are authorized by their company to manage the list of approved contributors under the company’s CCLA for a project. They use the EasyCLA Corporate Console to add and manage contributors and other CLA Managers.

Before a CCLA is signed, there is not an official CLA Manager. The person who will become the initial CLA Manager is responsible for [coordinating the CCLA signing process](/lfx/easycla/v2-current/corporate-cla-managers/coordinate-signing-cla-and-become-initial-cla-manager.md). This may involve them signing the CCLA themselves if they are authorized by their company to do so, or designating someone else as the CLA Signatory if they are not authorized. After the CCLA is signed, they become the initial CLA Manager under that CCLA.

## **CLA Signatory**

A CLA Signatory signs a CCLA on behalf of the company. CLA Signatories can be any person who is authorized by their company to sign the CCLA on its behalf.

## **EasyCLA Corporate Console**

Corporate employees and CLA Managers use the [EasyCLA Corporate Console](https://organization.lfx.linuxfoundation.org/company/dashboard) to view and (in the case of CLA Managers) manage their company’s CCLA information.

## **Contributor Console**

After creating a PR and being flagged by the EasyCLA check, corporate and individual contributors navigate to the contributor console to become authorized under a signed CLA before their contribution is accepted.

## **Individual Contributor**

Individual contributors contribute code on their own behalf (not on behalf of an employer). Their CLA status is verified after creating a PR, and they must sign an ICLA via the Contributor Console before they can contribute to the project.

## **Project Console**

Also known as Project Control Center. Project managers use the [project console](https://projectadmin.lfx.linuxfoundation.org) to create CLA groups, add and manage projects, repositories, and so on for the CLA group.

## Project Manager

Project managers are authorized by The Linux Foundation to configure the EasyCLA settings for a project. They use the [LFX Project Control Center (PCC)](https://projectadmin.lfx.linuxfoundation.org), also known as Project Console, where they have access to specific projects as per the permission provided by The Linux Foundation. They add and manage projects and repositories on PCC.


---

# Agent Instructions: 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:

```
GET https://docs.linuxfoundation.org/lfx/easycla/v2-current/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
