> 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/sso/sign-in/sign-in-with-linkedin.md).
# Sign in with LinkedIn
You can use your LinkedIn login credentials to sign in to the protected Linux Foundation service instead of creating an LF account. The first time you sign in, you will enter your LinkedIn credentials to authenticate your LinkedIn account. Subsequent logins will not require you to enter the credentialsâ¤you will simply click the **LinkedIn** icon to sign in. This one-click approach simplifies your login process.
## To Sign in with LinkedIn:
1\. On the **SSO login page**, click on the LinkedIn icon to sign in with your LinkedIn account.
2\. Enter your LinkedIn login credentials, and click on **Sign in** CTA icon.
4\. If you have an existing LF account, the Linux Foundation will map it to you LinkedIn login. If you don't have an LF Account associated with the email address you're using, you will be navigated to **Create your LF Account** page.
5\. Enter username, and click on **Create Account** CTA button. You will be redirected to the Linux Foundation service page that you are trying to access.
{% hint style="info" %}
This username will be your new LF Account username, and will be synced with your email address.
{% 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/sso/sign-in/sign-in-with-linkedin.md?ask=&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.