Can't See a Project
Find a project that does not appear in TestVibe by checking the active workspace and your membership.
Last updated
Was this helpful?
⌘Ctrlk
Find a project that does not appear in TestVibe by checking the active workspace and your membership.
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.
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.
Switch to the workspace that owns the project.
If you are not a member of that workspace, ask an owner or admin to invite you from Settings → Members.
Refresh the project list after switching or accepting an invite.
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.
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.
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.
Last updated
Was this helpful?
Was this helpful?