> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/identity-access-and-administration/sso-social-sign-in-and-account-identity.md).

# SSO, Social Sign-In, and Account Identity

StackAI sign-in identifies your account. Organization SSO and social sign-in are different access methods, even when they use the same email domain.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2Fjmyie5wYJK9GN3Bzo7Xp%2Fsso-social-sign-in-and-account-identity.mp4?alt=media&token=a9cbc41f-af89-4733-8162-3b03c047560e>" %}
Review SSO configuration and the effect of the account’s sign-in method on password controls.
{% endembed %}

## Before you begin

The sign-in method required by your organization.

## Sign-in methods

| Term           | Definition                                                                                                                                                                      |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | Verification of the account or credential making a request. It identifies the caller but does not grant every resource permission.                                              |
| SSO            | Single sign-on through the identity provider configured by the organization. Provider assignment and organization setup can affect sign-in availability.                        |
| Social sign-in | Authentication through an external identity provider’s standard sign-in option. It is not automatically the same configuration or account-linking behavior as organization SSO. |
| User identity  | The authenticated person or application acting on a resource. It determines access; a display name or conversation ID does not authenticate a caller.                           |
| Membership     | The account’s association with an organization and assigned access. An invitation alone is not proof of accepted membership.                                                    |

## Configure member sign-in

1. Use the organization’s supported sign-in option.
2. Complete any identity-provider requirements.
3. Confirm the account and selected organization before opening resources.

You enter the intended account and organization.

## Behavior and limitations

A matching email address does not guarantee automatic account linking across every sign-in method. SSO access can depend on identity-provider assignment and organization configuration. If an expected organization is missing, check the account and membership before creating another account.

## Related resources

[Organization Roles and Permissions](https://docs.stackai.com/technical-reference/identity-access-and-administration/organization-roles-and-permissions.md)


---

# 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.stackai.com/technical-reference/identity-access-and-administration/sso-social-sign-in-and-account-identity.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.
