LFX Documentation Sign in

My CLAs

View your signed Individual and Employee CLAs in LFX Self Serve, and understand why an agreement might not appear.

Last updated

These steps apply to any signed-in user on LFX Self Serve.

My CLAs is a read-only Profile tab that lists the Contributor License Agreements (CLAs) EasyCLA has on file for you. A CLA is the agreement that covers your contributions to a Linux Foundation project that requires one. My CLAs answers: which agreements have I signed, and under which projects am I covered?

You cannot sign a CLA from this page. Signing happens outside My CLAs, and the signing process may evolve; this page only shows agreements already on file.

For broader EasyCLA concepts (what a CLA is, project and corporate consoles, troubleshooting), see the EasyCLA documentation.

Where do I find My CLAs?

  1. Sign in to app.lfx.dev.
  2. Select Profile from the left navigation sidebar.
  3. Open the My CLAs tab, or go directly to /profile/clas.

Agreements are matched from your signed-in session and your linked Email and GitHub identities. You never search or type a project name here.

What is the difference between ICLA and ECLA?

Type What it means On My CLAs Document
ICLA (Individual CLA) You signed as yourself for a project Listed Download PDF when EasyCLA has the signed file (otherwise PDF unavailable)
ECLA (Employee CLA) You are covered because your employer holds a Corporate CLA (CCLA) and you are on that company's Approved List Listed (shows the employer name) No individual PDF — shown as Covered by Corporate CLA (CCLA)
CCLA (Corporate CLA) Signed by a company CLA manager; covers employees via the company's Approved List Not listed as its own row — it is the parent agreement an ECLA hangs off Managed in the corporate EasyCLA flow, not on this tab

In short: an ICLA is your paperwork; an ECLA means you are covered under your company's CCLA.

What does the My CLAs list show?

When agreements are found, My CLAs shows a table with four columns:

Column Contents
Project Project logo (or a placeholder), project name, and — when it differs — the CLA group name as secondary text
Type ICLA, or ECLA · <company name>
Signed The date the agreement was signed
Document Download PDF for an ICLA when available (else PDF unavailable); Covered by Corporate CLA (CCLA) for an ECLA

Only currently valid agreements appear on this list.

Why does My CLAs say I have no CLAs?

If nothing matches your linked identities, you see:

  • No CLAs on file yet
  • We haven't found any signed ICLAs or ECLAs for your linked identities.

That does not always mean you never signed — see the next section.

Why don't my signed CLAs show up?

My CLAs only finds agreements that match an identity linked to your LFX account. Matching today uses your LF username, verified emails, and linked GitHub accounts. A CLA can be missing from the list when:

  • The email or GitHub account you used when signing is not linked to this LFX profile
  • You signed under a work or secondary email that is not among your verified / linked emails
  • You signed with a GitHub username that is not connected under Identities

What to do:

  1. Open Identities.
  2. Link the Email or GitHub accounts you used when signing.
  3. Return to My CLAs — newly linked Email/GitHub identities are included on the next load.

If an agreement is still missing after that, see EasyCLA troubleshooting.

The info banner on the My CLAs tab also points to the Identities flow (Link your Email, GitHub, or GitLab accounts →). Linking Email or GitHub is what recovers missing CLA matches today.

Can I download my signed CLA PDF?

Yes for an ICLA, when EasyCLA has the signed file — use Download PDF in the Document column. If the file is missing, the row shows PDF unavailable.

No for an ECLA. Employee coverage is under your company's Corporate CLA (CCLA), so there is no individual PDF to download. The Document column shows Covered by Corporate CLA (CCLA).

Can I sign a CLA from My CLAs?

No. My CLAs is read-only. Signing happens outside this tab, and the process may evolve. See the EasyCLA documentation for current guidance.

Related