> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/team-and-account/single-sign-on.md).

# Single sign-on (SSO)

Let your team log in to Pipefile through your company's identity provider, and optionally sync users and groups from your directory.

{% hint style="info" %}
Available on the **Enterprise** plan.
{% endhint %}

With single sign-on, your team logs in to Pipefile with their company account instead of a Pipefile password. Pipefile matches people to your SSO connection by their email domain (for example, everyone with an `@yourcompany.com` address).

## Set up SSO

SSO is set up together with the Pipefile team. Email <support@pipefile.com> with:

* the email domain or domains your team uses, and
* whether everyone on those domains must log in with SSO, or may still use a password.

We'll connect your identity provider and send your IT admin what they need to finish the setup on their side.

## Log in with SSO

{% stepper %}
{% step %}

### Choose SSO on the login page

On the [login page](https://pipefile.com/login), click **Log in with SSO** under **Using SSO?**.
{% endstep %}

{% step %}

### Enter your work email

Type **Your corporate email address** and click **Continue**.
{% endstep %}

{% step %}

### Sign in with your identity provider

You're sent to your company's sign-in page. After you sign in, you land on your Pipefile dashboard.
{% endstep %}
{% endstepper %}

When your team requires SSO, entering a password for an address on your domain takes you to the SSO form automatically.

## Adding people

* **Invitations:** a new teammate without a Pipefile account needs an invitation from a team admin. They open the invitation and sign in with SSO; their account is created and added to the team. See [Team members and admins](/team-and-account/team-members-and-admins.md#invite-members).
* **Directory sync:** if your identity provider supports it, Pipefile can add users when they are created in your directory, deactivate them when they are removed, and keep [user groups](/team-and-account/user-groups.md) in step with your directory groups. Ask support to turn it on when you set up SSO.

Someone who logs in with SSO but has no Pipefile account and no invitation is refused.

## SSO and two-factor authentication

Logging in through SSO doesn't trigger Pipefile's two-factor prompt or new-device email: your identity provider handles that step. On the Team page, members who log in with SSO are marked **SSO** instead of **2FA**, and they're left out of the team's two-factor requirement. See [Two-factor authentication and device verification](/team-and-account/two-factor-and-device-verification.md).

## Related

* [User groups](/team-and-account/user-groups.md)
* [Login issues](/troubleshooting/login-issues.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://support.pipefile.com/team-and-account/single-sign-on.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.