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

# Collaboration

**Collaboration** lets you **share a scope** with other BugRecon users. They get access to the same scope-to view results and, if you give them writer access, to run scans-without you giving away ownership. Useful for working with a teammate, getting a second opinion, or triaging targets together.

![Collaboration](https://1075470145-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2n4UTcrS4SHhY2NTi0v%2Fuploads%2Fgit-blob-dd02bea09dc26a1a2c2c6b5c2c1302a808f92d1a%2Fcollab.png?alt=media)

## Who can use it

* **Premium** and **Enterprise** only. Free and Basic users cannot share scopes or be invited.
* **Both you and the person you invite** must be on Premium or Enterprise. If you invite someone on Free or Basic, they will not get access.

## Two roles

When you invite someone, you choose their **role**:

| Role          | Can view the scope and results | Can run or stop scans |
| ------------- | ------------------------------ | --------------------- |
| **Read-only** | Yes                            | No                    |
| **Writer**    | Yes                            | Yes                   |

* **Read-only** - They can open the scope, see all results (subdomains, HTTP, vulnerabilities, AI results, etc.), and use things like export and search. They cannot start, stop, or cancel any scan.
* **Writer** - They can do everything you can on that scope: run any scan type, cancel runs, see all data. They cannot delete the scope or manage collaborators; only the owner can do that.

## How to invite someone

1. Open the **scope** (scope detail page).
2. Open the **Collaborators** (or Share) section.
3. Enter the **email** of the person you want to invite. They must already have a BugRecon account with that email.
4. Choose **Read-only** or **Writer**.
5. Send the invitation.

If they are on Premium or Enterprise, they receive an **email** with a link to accept. The email explains that they need a Premium or Enterprise account to access shared scopes.

## How to accept an invitation

1. The invited person receives the email and clicks the **link** in it.
2. They must be **logged in** and on a **Premium or Enterprise** plan. If not, they will see an error.
3. After accepting, the scope appears for them and they can open it from the link or from their scope list, with the permissions you gave (read-only or writer).

## Managing collaborators (owner only)

* **See who has access** - In the Collaborators section you see everyone you invited: their email, role, and status (e.g. pending invitation, or active).
* **Remove access** - You can **revoke** a collaborator at any time. They lose access immediately. You can invite them again later if you want; they will receive a new invitation and must accept again.

Only the **owner** can invite people, change roles (by re-inviting with a different role), and revoke access. Writers on the scope cannot add or remove collaborators.

## What collaborators see

* They only see the **scopes you shared** with them. They do not see your other scopes, projects, API keys, or account settings.
* Notifications for the scope (e.g. Discord) still follow **your** notification settings; collaboration does not change who gets alerts.

## Privacy

* Collaborators have no access to your account beyond the specific scope(s) you shared.


---

# 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://bugrecon.gitbook.io/docs/features-list/collaboration.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.