> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/access-and-sharing/authentication-and-sso/troubleshoot-sign-in.md).

# Troubleshoot sign-in

Separate authentication failures from permission and publishing problems before changing settings.

## Check the symptom

| Symptom                                  | Check first                                                                                      |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------ |
| Invitation cannot be found               | Recipient email, spam or quarantine, and the intended app.                                       |
| Login returns to the sign-in screen      | Provider configuration, current callback or redirect values, and provider-side error details.    |
| Sign-in works but the app is unavailable | Membership, team assignment, app environment, and published version.                             |
| The wrong pages or records appear        | [App and data permissions](/access-and-sharing/app-and-data-permissions.md) and user properties. |
| Builder and user see different versions  | Whether the intended app changes are published.                                                  |

## Collect a useful reproduction

1. Record the app, environment, sign-in method, time, and visible error.
2. Reproduce with a separate intended test account.
3. Open **More → System logs** and filter around that time.
4. Compare the app's authentication settings with the provider configuration.
5. Retest the same account after one configuration change at a time.

[System logs](/access-and-sharing/audit-logs-privacy-and-security/investigate-system-logs.md) may help explain authentication and integration errors. An empty result does not establish that sign-in succeeded or that no error occurred.

Keep passwords, tokens, cookies, and client secrets out of screenshots and shared error reports. Include the symptom and relevant redacted details instead.

Before disabling an existing method, verify that another administrator sign-in path works.


---

# 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.jetadmin.io/access-and-sharing/authentication-and-sso/troubleshoot-sign-in.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.