> 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/account-settings/team-settings.md).

# Members

TestVibe uses workspaces and roles to decide what each user can see and manage. Every user has a personal workspace; team workspaces are shared, and each member has a role — owner, admin, member, or viewer.

Membership is managed inside TestVibe from **Settings → Members** — it does not depend on GitHub teams or repository permissions.

## Where workspace context appears

| Place                       | What it means                                                         |
| --------------------------- | --------------------------------------------------------------------- |
| Workspace switcher (header) | Sets the active workspace; projects are listed per workspace.         |
| Settings > Members          | Shows who belongs to the workspace, their roles, and pending invites. |
| Settings > Profile          | Confirms which workspace you are configuring.                         |

## Joining a Team Workspace

TestVibe does not auto-join anyone by email domain. Owners and admins of a **team** workspace add people from the Members panel by sending an **invite** (email + role) or sharing an **invite link** — anyone who opens the link and signs in joins with the role the link carries. See [Invite Members](/workspace/manage-teams-and-members.md#invite-members).

## What roles control

| Role   | How it affects TestVibe                                                                        |
| ------ | ---------------------------------------------------------------------------------------------- |
| Owner  | Full control of the workspace, including members, roles, billing, and deleting the workspace.  |
| Admin  | Manage projects, settings, and members.                                                        |
| Member | Day-to-day testing work in the workspace's projects.                                           |
| Viewer | Read-only — can view projects, tests, and results but cannot spend credits or change settings. |

## Change workspace or project

1. Open the workspace switcher in the header.
2. Select the workspace.
3. Select the project.

## If a teammate cannot see a project

| Check                            | Why                                                           |
| -------------------------------- | ------------------------------------------------------------- |
| Workspace membership             | The user must belong to the workspace that owns the project.  |
| Active workspace                 | They may be looking at a different workspace in the switcher. |
| Pending invite or access request | Invites must be accepted and access requests approved first.  |
| Role                             | Some settings require the admin or owner role.                |

After a membership change, refresh TestVibe or sign in again so the workspace reloads current permissions.

For invites and roles, see [Manage workspaces and members](/workspace/manage-teams-and-members.md). For joining via a project link, see [Join an existing project](/workspace/connect-existing-project.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/account-settings/team-settings.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.