> 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/workspace/manage-teams-and-members.md).

# Manage Members

Every TestVibe user gets a personal workspace automatically. You can also create or join team workspaces and switch the active workspace from the workspace switcher in the header — projects belong to the workspace that created them.

## Workspaces

| Type               | What it is                                                                                                  |
| ------------------ | ----------------------------------------------------------------------------------------------------------- |
| Personal workspace | Created for you at sign-up; your own projects live here. Personal workspaces never have additional members. |
| Team workspace     | Shared workspace for a team; members join by invite, invite link, or an approved access request.            |

## Create a Team Workspace

Choose **"+ New workspace"** from the workspace switcher in the header. The form creates the workspace **and its first project in one action** — enter the workspace name and, right below it, the same minimal project fields (name, base URL, optional framework) used elsewhere in TestVibe. Creating is instant and free; you land in the new project on the Test Suite, ready to describe your first test.

If you genuinely want an empty workspace with no project yet, use the quiet **"Skip for now — create the workspace only"** link below the form. Either way, a new workspace starts as a **0-credit shell** — there's no forced checkout — and you pick a plan later from **Settings → Billing** whenever you're ready.

## Roles

| Role   | What it allows                                                                                 |
| ------ | ---------------------------------------------------------------------------------------------- |
| Owner  | Full control of the workspace, including roles, ownership transfer, and billing.               |
| Admin  | Invite and remove members, approve access requests, manage projects and settings.              |
| Member | Day-to-day testing work in the workspace's projects — edit, run, and generate.                 |
| Viewer | Read-only — can view projects, tests, and results but cannot spend credits or change settings. |

## Invite Members

1. Open **Settings → Members** in the workspace.
2. Enter the teammate's email address and choose a role. Only an owner can invite another **Owner**.
3. Send the invite.

Once sent, the invited teammate sees a dedicated **"You've been invited to `<workspace>`"** screen the moment they open TestVibe or the invite link — naming who invited them, so the invitation is the first thing they see rather than a generic sign-in or a "create your first project" screen. If they're creating a new account, signing up with the exact invited email skips the usual email-verification step. Once accepted, the workspace appears in the teammate's workspace switcher. See [Sign in](/quickstart/sign-in-with-github.md#if-you-followed-an-invite-link).

You can also copy an **invite link** from the same panel and share it directly — anyone who opens it and signs in joins with the role the link carries.

## Access Requests

When someone opens a link to a project outside their workspaces, TestVibe shows an access-request dialog. Owners and admins can approve the request to add the person to the workspace. See [Join an existing project](/workspace/connect-existing-project.md).

## Common Access Questions

| Question                                              | Answer                                                                                                                                          |
| ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Why do I not see a project?                           | Check the active workspace in the workspace switcher — projects are listed per workspace.                                                       |
| Why can I view but not edit settings?                 | Some settings require the Admin or Owner role.                                                                                                  |
| Why can a teammate see different options?             | Roles differ per workspace; the same person can be an Owner in one and a Member in another.                                                     |
| Why did a teammate join without me sending an invite? | They likely used a shared **invite link**, or an owner/admin approved their access request. TestVibe does not auto-join anyone by email domain. |

## Related Help

* [Join an existing project](/workspace/connect-existing-project.md)
* [Team settings](/account-settings/team-settings.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/workspace/manage-teams-and-members.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.