# GitHub App permissions

TestVibe uses a GitHub App installation to connect your workspace to a repository. That installation controls which repositories TestVibe can see and which GitHub features it can use.

## Why Permissions Matter

TestVibe may need to:

* read repository files so it can show feature files and generated tests
* create or update generated Playwright test files
* dispatch GitHub Actions workflows for generation and runs
* read workflow status so TestVibe can show live progress
* read artifacts such as screenshots, videos, traces, and reports
* manage repository secrets or variables when you add them through settings

The exact permissions are managed in GitHub by the organization or repository owner.

## Permission Symptoms

| Symptom                        | Likely permission area                       |
| ------------------------------ | -------------------------------------------- |
| Repository is missing          | App installation or repository access.       |
| Generation cannot write output | Contents or pull request access.             |
| Run cannot start               | Actions workflow dispatch access.            |
| Live status does not update    | Workflow read access or callback setup.      |
| Secrets cannot be saved        | Repository secrets or administration access. |
| Artifacts are unavailable      | Actions artifact read access.                |

## Update Access

1. Open the TestVibe GitHub App installation settings in GitHub.
2. Confirm the installation includes the repository you want to use.
3. If the installation is limited to selected repositories, add the missing repository.
4. Confirm organization policies allow the app to use Actions and repository contents.
5. Return to TestVibe and refresh the workspace or repository picker.

If you are not an organization owner, ask an owner to make these changes.

## Good Admin Request

Send a short request like this:

> Please check the TestVibe GitHub App installation for `<repository>`. I need it available in TestVibe so I can create tests, run GitHub Actions workflows, and review run artifacts.

For a broader summary, see [GitHub permissions overview](/reference/github-permissions-overview.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/github-app-permissions.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.