> 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/cla-signatories/review-and-sign-a-corporate-cla-by-request.md).

# Review and Sign a Corporate CLA by Request

As a CCLA signatory, you may receive email requests to review and sign a Corporate CLA.

**To sign a CCLA:**

1. Look in your email inbox for a CLA Sign Request email and open the email.
2. Click **REVIEW DOCUMENT** in the email.

   ​![DocuSign](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-72ed2578134d31f336f0f4a571de309b4b8b8928%2Fcla-docusign-email-review-document.png?alt=media\&token=8c2c9127-bbec-4a1f-ae7b-ca7d5454dfe2)​

   The Corporate CLA dialog opens.
3. Click **OPEN CLA** and then follow the instructions that DocuSign presents. Some fields are pre-populated such as the company name and email.

After the Corporate CLA is signed, the Company page shows the signed Corporate CLA under Signed Project CCLAs. You receive a CLA Signed Document email with an attached document PDF. Contributors to the company project simply need to confirm their association to the company, and then they can continue with their pull requests. Their subsequent contributions will not require association confirmations.

*A Corporate CLA that is signed by the CCLA signatory remains in effect even when that CCLA signatory is no longer employed at a company.*


---

# 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/cla-signatories/review-and-sign-a-corporate-cla-by-request.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.