> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plerion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub single sign-on

> Sign in to Plerion using your GitHub account with OAuth-based single sign-on

With **\[GitHub single sign-on (SSO)]**, your team can sign in to Plerion using their existing GitHub accounts.

<Note>
  You must be a member of an existing Plerion organization to sign in with GitHub SSO.
</Note>

***

## Steps to sign in with GitHub SSO

<Steps>
  <Step title="On the Plerion login page, click the GitHub SSO button">
    <Frame>
      <img src="https://mintcdn.com/pleriondocs/EYT7sD0Nxx4twMkd/images/onboarding/sso/github-sso/github-sso-login-button.png?fit=max&auto=format&n=EYT7sD0Nxx4twMkd&q=85&s=fef9cab57f745739cb3737428e930319" alt="Plerion login page with GitHub SSO button" width="2880" height="1800" data-path="images/onboarding/sso/github-sso/github-sso-login-button.png" />
    </Frame>
  </Step>

  <Step title="Authorize the Plerion OAuth app">
    GitHub displays an authorization page for **Plerion authentication**. This page shows the permissions Plerion requests:

    * **Organizations and teams**: Read-only access to your organization and team membership.
    * \**Personal user data*: Read-only access to your email addresses and profile information.

    Click `Authorize` to continue.

    <Frame>
      <img src="https://mintcdn.com/pleriondocs/EYT7sD0Nxx4twMkd/images/onboarding/sso/github-sso/github-sso-authorize.png?fit=max&auto=format&n=EYT7sD0Nxx4twMkd&q=85&s=17919bff76c2145ece713eb2723a9b3b" alt="GitHub OAuth authorization page showing Plerion authentication permissions and organization access" width="2880" height="1800" data-path="images/onboarding/sso/github-sso/github-sso-authorize.png" />
    </Frame>
  </Step>

  <Step title="Complete sign-in">
    After authorization, GitHub redirects you back to Plerion and you are signed in. On subsequent logins, you will not need to re-authorize unless the app's permissions change.
  </Step>
</Steps>
