# Manage teams and members

Teams help TestVibe show the repositories and members connected to an organization workspace.

If your repository belongs to an organization, TestVibe may ask you to choose a team before selecting a repository.

## What Teams Control

| Area                  | What it means                                                           |
| --------------------- | ----------------------------------------------------------------------- |
| Repository list       | The team context can determine which repositories appear in TestVibe.   |
| Member access         | Team membership affects who can work in the same project context.       |
| Setup permissions     | Some actions may require team, repository, or organization permissions. |
| Organization settings | Admins may control GitHub App access, runners, and secrets.             |

TestVibe reflects what GitHub allows your account to see and manage.

## Select A Team

1. Sign in with GitHub.
2. Select the GitHub App installation for the organization.
3. Choose the team that owns or has access to the testing repository.
4. Select the repository.

If you only have access to one team, TestVibe may select it automatically or skip the team screen.

## Manage Members

Depending on your permissions, you may be able to:

| Action            | When to use it                                               |
| ----------------- | ------------------------------------------------------------ |
| View members      | Confirm who can participate in the workspace.                |
| Add a member      | Give a teammate access to the team context used by TestVibe. |
| Remove a member   | Remove access when someone no longer needs the workspace.    |
| Edit team details | Keep the team name and description understandable.           |

Some member changes happen in GitHub. If TestVibe opens a GitHub team page, complete the change there and refresh TestVibe afterward.

## Common Access Questions

| Question                                        | Answer                                                                                                    |
| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Why do I not see a team?                        | Your GitHub account may not belong to the organization team, or the organization may restrict visibility. |
| Why do I not see a repository?                  | The repository may not be connected to the team or GitHub App installation.                               |
| Why can I view but not edit settings?           | Your repository role may allow read access but not administrative changes.                                |
| Why can another teammate see different options? | GitHub permissions can differ by user, team, repository, and organization role.                           |

## Team Setup Checklist

Before a team starts using TestVibe together, confirm:

* the TestVibe GitHub App is installed for the organization
* the repository is selected in the GitHub App installation
* the right team can access the repository
* team members can sign in with GitHub
* required secrets, variables, and runner access are available

For repository setup, see [Choose a repository](/workspace/choose-repository.md) and [Configure site URL and repository settings](/workspace/configure-site-url-and-repository.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/workspace/manage-teams-and-members.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.