# Troubleshooting Privacy Center Login and Identity Verification (/docs/privacy-center/troubleshooting/troubleshooting-privacy-center-login)

Admin Dashboard pages: /privacy-center/authentication-methods, /privacy-requests/settings/data-subjects

Find the cause when a data subject cannot log in to your Privacy Center or verify their email. Ask the data subject for the message on screen, then find it below. To set up a login method, see [Set Up Privacy Center Login](../configuration-and-publishing/set-up-privacy-center-login.mdx).

## The login link does not work [#the-login-link-does-not-work]

| Message starts with                      | Cause                                                                                           | What to do                                         |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| **This login link has expired.**         | The link in a login email works for 45 minutes after Transcend creates it.                      | Ask the data subject to request a new login email. |
| **This link is invalid or has expired.** | Transcend found no active access link for the token, or the access link passed its expiry time. | Give the data subject a new access link.           |

The login email also has a link to report a wrong recipient. After someone selects it, the Privacy Center shows **Thanks for letting us know! We have invalidated the login attempt.** The login link in that email stops working.

## The login email does not send [#the-login-email-does-not-send]

When the Privacy Center cannot send the login email, the form shows the error. It also shows a note that browser extensions that block content or network requests can cause errors.

- Ask the data subject to turn off those extensions for the Privacy Center, then select **Send Email** again.
- Transcend sends at most two login emails per minute to one email address.
- A data subject type that signs in with OAuth or JWT cannot log in by email.

## OAuth or JWT login fails [#oauth-or-jwt-login-fails]

| Message starts with                                           | Cause                                                                                                                               | What to do                                                                                                                              |
| ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **We could not verify that the login attempt was initiated**  | The OAuth provider returned no state value, a state value that differs from the one saved in the browser, or no authorization code. | Start the login again from the Privacy Center, in the same browser.                                                                     |
| **Something went wrong. Please try again later**              | The `/login` page did not finish the redirect within 5 seconds.                                                                     | Open the Privacy Center and log in again.                                                                                               |
| **An unexpected error occurred while creating your session.** | The login request failed. For JWT login, Sombra rejects a token that fails verification against your public key.                    | Check the settings under [**Privacy Center → Authentication Methods**](https://app.transcend.io/privacy-center/authentication-methods). |

## The request type is not available [#the-request-type-is-not-available]

| Message starts with                                              | Cause                                                                                                   | What to do                                                                                                                                         |
| ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **This request type is not yet available on the Privacy Center** | Your organization has published workflows, and none matches the data subject type and the request type. | Publish a workflow for that data subject type and request type.                                                                                    |
| **Token returned was valid, but the data subject type**          | The login link is for a data subject type that the Privacy Center no longer lists.                      | Check the data subject type under [**Workspace Configuration → Data Subjects**](https://app.transcend.io/privacy-requests/settings/data-subjects). |

## Sign-in is off for a data subject type [#sign-in-is-off-for-a-data-subject-type]

When **Privacy Center Sign-in** is off for a data subject type, data subjects of that type see the **Sign-in Unavailable Message** instead of the login.

1. Go to **Workspace Configuration → Data Subjects**.
2. Click the pencil icon next to the data subject.
3. Turn on **Privacy Center Sign-in** and set **Sign-in Method**.

If OAuth or JWT is unavailable in **Sign-in Method**, configure it first under **Privacy Center → Authentication Methods**.

## The session ended [#the-session-ended]

The **Your session has ended** message appears when the data subject ends their session in another browser tab. The data subject selects **Reload page** and logs in again.

## The request email does not verify [#the-request-email-does-not-verify]

The message **Uh-oh! Something went wrong while verifying your email.** appears when the Privacy Center cannot verify the email for a request.
