> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/collaboration/inviting-team-members.md).

# Inviting team members

Learn how to invite team members and enhance your team collaboration with BugBug. You can work together on test cases, share links to test results, empower developers and many more.

## Why invite collaborators?

Working in a team on test automation is easier if all of your team members have access to BugBug.

* Work together on test cases
* Share direct links to test results
* Empower developers to [run tests locally](/running-tests/test-in-your-browser.md)
* Let developers see test results by clicking a link in [build pipelines](/integrations/cli.md)
* Get all-team [notifications](/collaboration/alerts.md) for scheduled cloud runs

{% hint style="info" %}
**Hint!** If you're a software agency, you don't need to invite your clients to send them email notifications. You can add them as "additional email addresses" in [project notification settings](/collaboration/alerts.md).
{% endhint %}

## How many users can I invite?

The number of users depends on your plan:

* **Free** - 1 user
* **Core** - 3 users
* **Pro** and **Business** - unlimited users

[Billing managers](#billing-manager) don't count towards this limit. If you reach your user limit, you can still invite a billing manager, for example someone from your finance team who will upgrade the plan.

## How to invite collaborators?

Go to "Organization settings" and switch to the "User" tab. Here you can see who has access and their role.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FMda2chT6UDJoss7OcoRM%2FScreenshot%202022-04-11%20at%2012.39.37.png?alt=media\&token=d0e9c5ca-2e61-4c0a-81d6-9aa257385ab9)

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FOgkUiFzHswCLzza2jw4o%2FScreenshot%202022-04-11%20at%2012.40.07.png?alt=media\&token=ff5f5ff2-306b-4457-9e5c-7b67eb5df861)

## User roles

| Role            | Can                                                                                                                           |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Editor          | Access & Edit assigned projects                                                                                               |
| Admin           | <p>Access & Edit all projects<br>Invite users<br>Manage Billing<br>Update credit card information<br>Change subscriptions</p> |
| Billing manager | <p>Manage Billing<br>Update credit card information<br>Change subscriptions<br>Download invoices</p>                          |

### Billing manager

The billing manager role is for people who pay for BugBug but don't work on tests, for example an accountant or someone from your finance team.

A billing manager:

* can access only the billing address, subscription, credit card and invoices tabs in the organization settings
* can't access, create or import projects
* can't invite other users
* doesn't count towards your plan's user limit

Only an Admin can invite a billing manager. An organization can have up to 10 billing managers, including pending invitations.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugbug.io/collaboration/inviting-team-members.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
