> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/troubleshooting/missing-repositories.md).

# Can't See a Project

Projects belong to a workspace. If a project does not appear, you are most likely looking at the wrong workspace, or you are not a member of the workspace that owns it.

## First Checks

1. Open the workspace switcher in the header and check which workspace is active. Every user has a personal workspace plus any team workspaces they joined.
2. Switch to the workspace that owns the project.
3. If you are not a member of that workspace, ask an owner or admin to invite you from **Settings → Members**.
4. Refresh the project list after switching or accepting an invite.

## Why A Project Can Be Missing

| Cause                                                    | What to do                                                                   |
| -------------------------------------------------------- | ---------------------------------------------------------------------------- |
| Wrong active workspace                                   | Switch workspaces from the header.                                           |
| You are not a member of the owning workspace             | Ask an owner or admin to send you an invite.                                 |
| The invite was sent but not accepted                     | Open the invite email or notification and accept it.                         |
| You followed a link to a project outside your workspaces | Use the access-request dialog that appears and wait for an owner to approve. |
| The project was deleted                                  | Ask a workspace owner whether it still exists.                               |

## Opening A Shared Link

If someone shares a direct link to a project you cannot access, TestVibe shows an access-request dialog instead of the project. Send the request — an owner or admin of that workspace can approve it and the project then appears in your workspace. Alternatively, an owner or admin can send you an invite or share an **invite link** — opening it and signing in adds you to the workspace directly, with no approval step. TestVibe does not auto-join anyone by email domain.

## App Repository Picker Is Empty

This page is about projects, which never require a repository. Separately, when you connect an optional source repository in **Settings → App Repository** (so the assistant and coverage can read your code) or enable **Test Files Sync**, the repository picker only lists repositories your connection can access. If it is empty, grant the connection access to the repository — see [GitHub connection issues](/troubleshooting/github-app-permissions.md).

## Related Help

* [Sign-in problems](/troubleshooting/sign-in-problems.md)
* [GitHub connection issues](/troubleshooting/github-app-permissions.md)


---

# 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 dynamically by asking a question.

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

```
GET https://docs.testvibe.com/troubleshooting/missing-repositories.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.