# Sign-in problems

TestVibe uses GitHub sign-in so it can show the installations, teams, and repositories you are allowed to use. If sign-in does not finish, the issue is usually browser state, GitHub authorization, or a mismatch between the GitHub account you used and the account that has access to the repository.

## Quick Checks

1. Make sure popups and redirects are allowed for TestVibe.
2. Confirm you are signing in with the GitHub account that has repository access.
3. If your browser opens GitHub in a different profile, sign out of GitHub there and try again.
4. Return to the same TestVibe tab after approving GitHub authorization.
5. Refresh TestVibe after sign-in completes.

## Common Symptoms

| Symptom                                        | What to try                                                                                                                        |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| GitHub opens but returns to the sign-in screen | Refresh TestVibe, then sign in again and complete the full GitHub authorization prompt.                                            |
| Nothing happens when you click sign in         | Allow popups and redirects, then try again.                                                                                        |
| You signed in but no repositories appear       | Check the GitHub App installation and selected organization. See [Missing repositories](/troubleshooting/missing-repositories.md). |
| The wrong GitHub account is used               | Sign out of GitHub in the browser profile, then sign in with the correct account.                                                  |
| Organization access is blocked                 | Ask an organization owner to approve OAuth or GitHub App access for TestVibe.                                                      |

## After Sign-In

After GitHub accepts the sign-in, TestVibe loads the GitHub App installations available to your account. If you are asked to choose an installation, team, or repository, select the one that owns the tests you want to create or run.

If the expected organization or repository is missing, sign-in probably worked but access still needs to be adjusted. Continue with [Missing repositories](/troubleshooting/missing-repositories.md) or [GitHub App permissions](/troubleshooting/github-app-permissions.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/troubleshooting/sign-in-problems.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.