> ## Documentation Index
> Fetch the complete documentation index at: https://www.bugzy.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Team management

> Team creation, invitations, roles, billing, account settings, and data privacy in Bugzy Cloud.

Bugzy organizes users into teams. Every project belongs to a team, and team members share access to all projects within their team.

## Team creation

A team is created automatically during signup. The user who creates the team becomes the **owner**. You can rename the team and configure preferences from the team settings page.

## Invitations

Invite team members by email from the dashboard:

1. Go to **Settings** > **Team Members**
2. Click **Invite Member**
3. Enter the invitee's email address
4. Select a role (member or admin)
5. The invitee receives an email with a signup/login link

Invitees who already have a Bugzy account are added immediately. New users are prompted to sign up with GitHub OAuth.

## Roles

| Role       | Permissions                                                                                       |
| ---------- | ------------------------------------------------------------------------------------------------- |
| **Owner**  | Full access. Manage billing, delete team, transfer ownership. One per team.                       |
| **Admin**  | Manage projects, integrations, members, and settings. Cannot manage billing or delete team.       |
| **Member** | View and run tests, view results, access dashboards. Cannot manage integrations or team settings. |

All roles can trigger test runs and view results. The difference is in configuration and administrative access.

## Removing members

Team owners and admins can remove members from the team:

1. Go to **Settings** > **Team Members**
2. Click the **remove** button next to the member you want to remove
3. Confirm the removal in the dialog

### Permissions

* **Owners** can remove admins and members
* **Admins** can remove members (but not other admins)
* No one can remove the team owner
* You cannot remove yourself

Removing a member revokes their access to all team projects immediately. The removed user receives an email notification informing them of the removal. If the removed member had a pending ownership transfer, it is automatically cancelled.

## Ownership transfer

The team owner can transfer ownership to any other team member.

### How it works

1. Go to **Settings** > **Team Members**
2. Click **Transfer Ownership** next to the target member
3. The target member receives a notification and must **accept** the transfer
4. Once accepted, the target becomes the new owner and the previous owner is moved to the admin role

### Key details

* **Acceptance required** — the target member must explicitly accept the transfer. It does not happen automatically.
* **Billing transfers with ownership** — the new owner assumes billing responsibility for the team. The Stripe billing email is updated to the new owner's email upon acceptance.
* **7-day expiration** — pending transfers expire after 7 days if not accepted or declined.
* **Cancel anytime** — the current owner can cancel a pending transfer before it is accepted.
* **One at a time** — only one ownership transfer can be pending per team.

## Billing

Bugzy uses outcome-based pricing — you pay for test runs, not per seat. There is no per-user cost.

### Subscription management

* Go to **Settings** > **Billing** to view your current plan, usage, and invoices
* Bugzy uses Stripe for payment processing
* Click **Manage Subscription** to open the Stripe Customer Portal where you can update payment methods, view invoices, and change plans

### What counts as a test run

A test run is a single execution of the `run-tests` task. Other tasks like `generate-test-plan` and `generate-test-cases` are included in your plan and do not count as additional test runs.

### Spending controls

Cap your monthly **overage** spend so a regression or runaway loop cannot produce a surprise invoice. Base-plan usage is never counted against the budget — only extra usage beyond your included allotment.

* Go to **Settings** > **Billing** > **Spending controls** to set a monthly overage budget in EUR.
* Only **owner** and **admin** roles can change the budget.
* Warning emails are sent to your billing email at **50%**, **75%**, and **100%** of the budget.
* At **100%**, new agent task executions are temporarily blocked. You can lift the block at any time by raising the budget; the block lifts automatically when your billing period renews.
* Setting the budget to **No budget** leaves overage uncapped (the default behavior).
* Setting the budget to **0** blocks any overage immediately — useful if you want to be notified before accepting any extra charge.

## Communication channels

Configure where Bugzy sends notifications for your team. The channels page is accessible from the **Channels** item in the team sidebar navigation.

Supported channel types:

* **Slack** — Connect via OAuth and select a channel for notifications
* **Microsoft Teams** — Connect via Azure Bot integration
* **Email** — Add email addresses for notification delivery

Each team can have multiple channels configured. Set a **primary channel** to control where the most important notifications are delivered.

To manage channels:

1. Click **Channels** in the team sidebar
2. Click **Add Channel** to connect a new notification channel
3. Use the channel list to remove or set a primary channel

## Team settings

Available in **Settings** > **Team**:

* **Team name:** Display name shown in the dashboard
* **Default project settings:** Base configuration applied to new projects

## Account deletion

Account deletion follows a 30-day soft delete process:

1. Request deletion from **Settings** > **Account**
2. Your account is deactivated immediately — you cannot log in
3. Data is retained for 30 days in case you change your mind
4. After 30 days, all data is permanently deleted

To cancel a deletion request within the 30-day window, contact [support@bugzy.ai](mailto:support@bugzy.ai).

## Data privacy

Bugzy is GDPR compliant with EU-only data processing:

| Aspect              | Detail                                                                                               |
| ------------------- | ---------------------------------------------------------------------------------------------------- |
| **Data processing** | EU-only — all data stored and processed in European data centers                                     |
| **DPA**             | Data Processing Agreement available on request (contact [privacy@bugzy.ai](mailto:privacy@bugzy.ai)) |
| **Data export**     | Request a full export of your data via [privacy@bugzy.ai](mailto:privacy@bugzy.ai)                   |
| **Data retention**  | Active data retained while account is active. Deleted after 30-day grace period on account deletion. |
| **Authentication**  | GitHub OAuth via Supabase Auth — Bugzy does not store passwords                                      |
| **Encryption**      | TLS in transit, Cloud KMS encryption at rest for credentials and task payloads                       |
| **Isolation**       | Each task execution runs in an ephemeral container — no shared state between projects or teams       |

For security-specific details, see the [Security](/docs/security) page.