# Team settings

TestVibe uses GitHub installations, organizations, teams, and repository permissions to decide what each user can see and manage.

Most team membership and repository access changes are managed in GitHub. TestVibe reflects the access GitHub gives to your signed-in account.

## Where team context appears

You may choose or see team context when:

| Place                       | What it means                                                                   |
| --------------------------- | ------------------------------------------------------------------------------- |
| Sign-in workspace selection | Organization users may choose an installation, team, and repository.            |
| Repository settings         | Organization projects may show the active team as read-only context.            |
| Repository list             | The selected team can affect which repositories appear.                         |
| Account settings            | The active account or installation context helps confirm where you are working. |

## What teams control

| Area                  | How it affects TestVibe                                                            |
| --------------------- | ---------------------------------------------------------------------------------- |
| Repository access     | Determines which repositories you can open or configure.                           |
| Settings permissions  | Determines whether you can edit secrets, variables, runners, and project settings. |
| Runner access         | Organization runner groups may limit which repositories can use a runner.          |
| Secrets and variables | Organization values may be restricted to approved repositories.                    |
| Member visibility     | Users may see different options depending on their GitHub role.                    |

## Change team or repository

To switch context:

1. Use the workspace selector.
2. Choose the correct GitHub App installation.
3. Select the organization team when prompted.
4. Select the repository.

If only one team or repository is available, TestVibe may skip part of this flow.

## Manage team members

If a teammate cannot see a repository or setting, check GitHub first:

| Check                          | Why                                                                      |
| ------------------------------ | ------------------------------------------------------------------------ |
| GitHub organization membership | The user must belong to the right organization.                          |
| GitHub team membership         | The team may control repository visibility in TestVibe.                  |
| Repository role                | Some settings require write or admin permissions.                        |
| GitHub App installation        | The repository must be included in the TestVibe GitHub App installation. |
| Runner group access            | Organization runner groups may only allow selected repositories.         |

After changing GitHub access, refresh TestVibe or sign in again so the workspace can reload the current permissions.

For setup details, see [Manage teams and members](/workspace/manage-teams-and-members.md). For missing repositories, see [Missing repositories](/troubleshooting/missing-repositories.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/account-settings/team-settings.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.