> For the complete documentation index, see [llms.txt](https://docs.debricked.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.debricked.com/tools-and-integrations/single-sign-on-sso/single-sign-on-sso-through-github.md).
# Single Sign-On (SSO) through Github (OIDC)
Learn how to set up Single Sign-On (SSO) with Fortify SCA through GitHub.
As the company administrator, you can choose to enable single sign-on for the users to log in via GitHub.
### Enable Single Sign on via GitHub
1. Go to **Admin tools** on the left side menu.
2. Type your password to enter the administrative mode.
3. In the **User permissions** tab, toggle the **SSO with GitHub** to enable the feature.
4. Click **+Add organizations** to add your organization. Everyone who is part of the organization will be able to create their account or log in via the GitHub SSO.
### **Whitelist email domains**
As the company administrator, you are able to filter which users in your organization can use SSO by whitelisting email domains.
To whitelist a new email domain:
1. Go to **Admin tools** on the left side menu.
2. Type your password to enter the administrative mode.
3. In the **User permissions** tab, under **Whitelist** user domains, enter all domains (starting with “@”, for example, “@debricked.com”) and click **Save**. From now on, only users with those email domains will have access to SSO.
### **User management using SSO**
Keep in mind that all the users who are part of the organization on GitHub are able to join your company account on Fortify SCA. If a user has a different email address on GitHub than the Fortify SCA account, a new account will be created when the user logs in to Fortify SCA for the first time. If the user wants to use SSO, the company admin may remove their other account.
### **Access control**
It is currently not possible to prevent a user from logging in using a specific method if they signed up through an invite email and the SSO is enabled.
However, since accounts with email login can only be created via invites from an admin, if the admin does not invite users and instead enables SSO, then only SSO may be used.
---
# 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.debricked.com/tools-and-integrations/single-sign-on-sso/single-sign-on-sso-through-github.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.