Skip to main content
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

RolePermissions
OwnerFull access. Manage billing, delete team, transfer ownership. One per team.
AdminManage projects, integrations, members, and settings. Cannot manage billing or delete team.
MemberView 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.

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.

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.

Data privacy

Bugzy is GDPR compliant with EU-only data processing:
AspectDetail
Data processingEU-only — all data stored and processed in European data centers
DPAData Processing Agreement available on request (contact privacy@bugzy.ai)
Data exportRequest a full export of your data via privacy@bugzy.ai
Data retentionActive data retained while account is active. Deleted after 30-day grace period on account deletion.
AuthenticationGitHub OAuth via Supabase Auth — Bugzy does not store passwords
EncryptionTLS in transit, Cloud KMS encryption at rest for credentials and task payloads
IsolationEach task execution runs in an ephemeral container — no shared state between projects or teams
For security-specific details, see the Security page.