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

# Login and Access Issues

> Fixes for invitation, password, and single sign-on problems that keep someone from logging in to Exec.

If someone can't log in to Exec, the cause is almost always one of a few things: the email address on their account has a typo, their invitation or reset email landed in junk, they need to reset a password, or their workspace uses single sign-on (SSO). Work through the sections below in order.

<Info>
  Most access problems are resolved by a workspace admin from **Settings > Users**. End users who are stuck should contact their own admin first, then [hello@exec.com](mailto:hello@exec.com) if that doesn't resolve it.
</Info>

***

## Start Here: Confirm the Account Email Is Correct

The single most common cause of "I can't log in" is a small typo in the email address entered when the account was created, for example an extra letter or the wrong domain. If the address is wrong, the invitation and every login or reset email go to an address the user can't reach, so they never get in.

<Steps>
  <Step title="Open the Users page">
    A workspace admin goes to **Settings > Users** and finds the person's account.
  </Step>

  <Step title="Check the email character by character">
    Compare it against the address the user actually checks. Watch for extra letters, swapped characters, and the wrong domain.
  </Step>

  <Step title="Correct it and re-invite">
    Fix the address and re-send the invitation. See [Add a New User](/platform/add-user) for the invite flow.
  </Step>
</Steps>

<Note>
  Admins can correct a typo themselves. If the account's email needs to be changed to an entirely different address (not just a typo fix), contact [hello@exec.com](mailto:hello@exec.com) and we'll update it.
</Note>

***

## "I Never Received My Invitation Email"

When an organization adds someone to Exec, that person gets an email with the subject **"\[Your Organization] has invited you to join them on Exec"**. If it never arrives:

<Steps>
  <Step title="Check spam and junk">
    The invitation often lands in a spam, junk, or "Other" folder. Search the mailbox for "Exec" before anything else.
  </Step>

  <Step title="Confirm the email address is right">
    Have an admin verify the address on the Users page (see the section above). A typo is the most common reason the email never arrives.
  </Step>

  <Step title="Ask IT to allow Exec's email sender">
    Corporate email security gateways sometimes quarantine the invite. Exec sends from **`mg.exec.com`**. Ask your IT or messaging team to allow that sender. See [Network and Email Whitelist Requirements](/platform/whitelist-requirements).
  </Step>

  <Step title="Re-send the invitation">
    Once the address is confirmed and the sender is allowed, an admin re-sends the invite from **Settings > Users**.
  </Step>
</Steps>

See [Create Your Exec Account](/platform/create-account) for what the user does once the invitation arrives.

***

## "Email or Password Isn't Being Accepted"

If you see **"The e-mail address and/or password you specified are not correct"**, the email is recognized but the password doesn't match. Reset it.

### Reset Your Password

<Steps>
  <Step title="Go to the login page">
    Open **Login to Exec** and enter your email, then click **Continue**.
  </Step>

  <Step title="Click Forgot your password?">
    Once the password field appears, select the **Forgot your password?** link.
  </Step>

  <Step title="Enter your email and reset">
    On the **Reset Your Password** page, enter your email and click **Reset Password**. You'll see "Check your email to complete the password reset process."
  </Step>

  <Step title="Open the reset email">
    Follow the link in the email to set a new password, then log in. If the reset email doesn't arrive, check junk and confirm IT allows the **`mg.exec.com`** sender (see above).
  </Step>
</Steps>

<Tip>
  If you enter your email on the reset page and get redirected to your company's sign-on screen instead, your workspace uses SSO and there's no Exec password to reset. See the next section.
</Tip>

***

## Your Organization Uses Single Sign-On (SSO)

If your workspace has SSO enabled, you don't use an Exec password at all. After you enter your email and click **Continue**, Exec sends you to your company's identity provider (Okta, Microsoft Entra ID, Google Workspace, etc.) to sign in. Once SSO is enabled for a workspace, it is the only way to log in.

If SSO login fails:

* **You reach your identity provider but can't sign in there.** This is an account issue on your organization's side. Contact your internal IT or identity team, not Exec.
* **You're not sent to SSO at all, or get an error before the provider loads.** Confirm you're using your corporate email address. If it still fails, contact [hello@exec.com](mailto:hello@exec.com).

<Note>
  SSO alone does not create accounts. A user must be both allowed in your identity provider and present in the Exec workspace. For automatic provisioning, see [Single Sign-On and Directory Sync](/sso-directory-sync).
</Note>

***

## "Your Account Is Not Associated With Any Workspace"

This message means the login succeeded but the account isn't attached to a workspace, usually because the person hasn't been invited yet or was removed. A workspace admin should confirm the user exists under **Settings > Users** and re-invite if needed. If the user should have access and doesn't, contact [hello@exec.com](mailto:hello@exec.com).

***

## "Too Many Attempts" or a Temporary Lock

After several failed login attempts, Exec temporarily blocks further tries to protect the account. Wait a few minutes and try again, and use **Forgot your password?** rather than guessing, so you're not locked out repeatedly.

***

## Still Can't Log In?

If you've confirmed the email is correct, reset the password (or used SSO), and the user still can't get in:

<Steps>
  <Step title="Test from the admin side">
    A workspace admin confirms the account exists and is set up under **Settings > Users**.
  </Step>

  <Step title="Rule out the device or network">
    Have the user try a different browser (Chrome is most reliable) or an incognito window. A corporate firewall can also block Exec. See [Network and Email Whitelist Requirements](/platform/whitelist-requirements) for the domains IT needs to allow.
  </Step>

  <Step title="Escalate">
    If access still fails, contact [hello@exec.com](mailto:hello@exec.com) with the user's email and what they've already tried.
  </Step>
</Steps>

***

## Getting Help

**Need help?** Contact us at [hello@exec.com](mailto:hello@exec.com) for assistance with login, invitations, or workspace access.