> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/other/reference-documentation/log-in-to-your-impactcom-account.md).

# Log In to Your impact.com Account

Learn how to log in to your impact.com account in different scenarios and how to log in securely using two-factor authentication.

## Login scenarios

How you log in to your impact.com account depends on how you originally signed up. For more information see our [Log In to impact.com FAQ](/other/reference-documentation/log-in-to-impactcom-faq.md).

<details>

<summary>You signed up via email</summary>

If you signed up with a single email address, and not via SSO, then you can log in with your email address and password.

</details>

<details>

<summary>You signed up via SSO</summary>

If you signed up using one of the SSO options provided, select it when logging in and follow the prompts.

* Alternatively, you can enter your email address which will prompt you to log in via the SSO option you signed up with.

</details>

<details>

<summary>You signed up for multiple accounts via the same email address</summary>

If you use 1 email address for multiple accounts, the next screen asks for your username and password. Enter the username for the account you want to access, not your email address. Your username is case- and space-sensitive.

If you entered the wrong email address, select **Switch Account**. Then, enter a different email address.

<div data-with-frame="true"><figure><img src="https://3964917321-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhRN1rcrim887TwHLBjac%2Fuploads%2FaALdguinPmtQRHYOZPDP%2FScreenshot%202026-06-04%20at%2008.52.31.png?alt=media&amp;token=7ff7513e-ee72-44c2-a5d0-466efd56cf81" alt="" width="331"><figcaption></figcaption></figure></div>

</details>

## Troubleshoot sign-in problems / account lockouts

Use the message on the sign-in page to identify the problem. An account lockout differs from SSO, browser, and suspension issues.

<details>

<summary>My account is locked after failed sign-in attempts</summary>

impact.com disables access after 6 incorrect login attempts. A message such as “too many failed attempts” or “account locked” indicates a credential lockout.

Stop retrying. Confirm that you selected the correct sign-in method and entered the account's correct identifier. Use password or username recovery when appropriate. If the account remains locked, preserve the error message and [contact support](https://app.impact.com/support/portal.ihtml) for restoration. If troubleshooting does not resolve the issue, provide a screen recording of the sign-in steps and error.

</details>

<details>

<summary>I use single sign-on (SSO)</summary>

Select your organization's configured SSO option. Resolve password and identity-provider issues with your SSO administrator or provider. Do not reset an impact.com password for an SSO account.

</details>

<details>

<summary>The sign-in page loops, fails to load, or behaves unexpectedly</summary>

Clear the relevant cache and cookies. Disable your VPN, ad blocker, and interfering security tools. Then, retry in an incognito or private window, or use another supported browser.

</details>

<details>

<summary>My account is suspended</summary>

An account-suspension message is not a credential lockout. Do not keep retrying passwords or verification codes. Preserve the message and [contact support](https://app.impact.com/support/portal.ihtml). If troubleshooting does not resolve the issue, provide a screen recording of the sign-in steps and message.

</details>

## Log in with two-factor authentication

You can log in to your impact.com account securely by using two-factor authentication (2FA). You'll first have to enable 2FA in your security settings.

You'll be prompted to verify your identity via 1 of 3 methods, depending on which 2FA method you enabled for your account. If you enabled multiple verification methods, you can bypass the default method by selecting **Verify with other options**.

{% tabs %}
{% tab title="Verify using the authenticator app" %}
When logging in with this method, you will see the following:

1. Open the authenticator app you used [when setting up 2FA](/other/reference-documentation/enable-user-level-two-factor-authentication.md) for your account.
   * The app will generate a Time-based One-Time Password (TOTP) for you.
2. Enter the TOTP as your verification code.
3. Optionally, select ![](https://3964917321-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhRN1rcrim887TwHLBjac%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[Unchecked box]** **Remember this device** to remember this device and bypass authentication for the next 30 days. If you log in from a different country, we'll ask you to verify again.

{% hint style="success" %}
**Note:** Your authenticator app shows a new 6-digit code about every 30 seconds. Enter the one showing now.
{% endhint %}
{% endtab %}

{% tab title="Mobile ending in \[last digits]" %}
When logging in with this method, you will see the following:

1. Check the mobile number you used [when setting up 2FA](/other/reference-documentation/enable-user-level-two-factor-authentication.md) for your account.
   * You will receive a text message via SMS with a unique verification code.
2. Enter the verification code.
3. Optionally, select ![](https://3964917321-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhRN1rcrim887TwHLBjac%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[Unchecked box]** **Remember this device** to remember this device and bypass authentication on future logins from the device you're using.
4. Select **Verify**.

{% hint style="success" %}
**Note:** Each verification code is valid for 10 minutes, and any code received during this window can be used. If your code doesn't arrive immediately, please wait for the 30-second timer to expire before trying again.
{% endhint %}
{% endtab %}

{% tab title="Your email address" %}
When logging in with this method, you will see the following:

1. Check the email address you used [when setting up 2FA](/other/reference-documentation/enable-user-level-two-factor-authentication.md) for your account.
   * You will receive an email with your unique verification code.
2. **Enter** the verification code.
3. Optionally, select ![](https://3964917321-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhRN1rcrim887TwHLBjac%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[Unchecked box]** **Remember this device** to remember this device and bypass authentication on future logins from the device you are using.
4. Select **Verify**.

{% hint style="success" %}
**Note:** Each verification code is valid for 10 minutes, and any code received during this window can be used. If your code doesn't arrive immediately, please wait for the 30-second timer to expire before trying again.
{% endhint %}
{% endtab %}
{% endtabs %}


---

# 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://help.impact.com/other/reference-documentation/log-in-to-your-impactcom-account.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.
