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

# Review and sign a Corporate CLA by Request

Note: The CLA Signatory does not need to have a Linux Foundation Single Sign-On (SSO) account to sign a corporate CLA.

{% hint style="info" %}
**Note:** The CLA Signatory does *not* need to have a Linux Foundation Single Sign-On (SSO) account to sign a corporate CLA.
{% endhint %}

To sign the CCLA, after someone else has coordinated the CCLA signing process and designated you to sign:

1. Look in your email inbox for a CLA Sign Request email and open the email.
2. Click **the link** in the email to review and sign CLA.​\
   The "Preparing CCLA" dialog opens.

![Preparing CCLA](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-d494f747f03eb9a64abf15cefb6222029c7de506%2Fpreparing%20ccla.png?alt=media\&token=4c0e669f-6585-4ed6-9cb1-6b17e9bbc941)

3\. After the CCLA preparation is complete, click **Sign CCLA**.

![CCLA ready for Signature](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-1b4c75d2a3a25fb3fdf4bd687cf7515c0be503c5%2Fccla%20ready%20for%20signature.png?alt=media\&token=3893cd22-dc38-4594-abff-bf2f849f2529)

{% hint style="warning" %}
EasyCLA [automatically screens organizations](/lfx/easycla/v2-current/automated-sanctions-screening.md) against government sanctions lists when the CCLA is prepared. If your organization is flagged by the screening, the dialog shows **Unable to Prepare CCLA** with a message that the CCLA cannot be completed at this time, and the **Sign CCLA** button remains disabled. If you believe this is an error, or the matter has since been resolved, try again after a few minutes, or contact EasyCLA support via the chat widget.
{% endhint %}

**Result:** You will be redirected to complete the DocuSign process.

4\. Select the check box to agree to use electronic signatures and click **Continue**.

5. Follow the instructions in the DocuSign document to fill in the required fields, sign the CCLA, and click **Finish**.

![](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-2b00dc6be9039a0f427e8473b7971d8244f37757%2Fdocusign%20icla%20flow.png?alt=media\&token=b134858d-5596-4d84-9126-01d0f9a55481)

{% hint style="info" %}

* After signing the CCLA, you will receive an email from The Linux Foundation confirming that it was signed.
* You can download the signed PDF document by clicking the link from that email, where you will be redirected to The Linux Foundation's website. If the download doesn't start automatically, click **Proceed to Download**. ![](https://3411187760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2DCN9UgoRgMEkgnLyP-887967055%2Fuploads%2Fgit-blob-5cda3db11670e4d443bec2359ebb0e3f2a7893da%2Fproceed%20to%20download%20ccla.png?alt=media\&token=6cb6bcfd-c181-44d0-81b1-941f1ef383d5)
  {% endhint %}


---

# 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/v2-current/ccla-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.