# Your team (/docs/teams-and-billing)



A BerryBox team owns its GitHub organization connection, runner settings, job history, prepaid wallet and API keys. Choose the correct team in the dashboard before making changes.

| Role    | Intended access                                     |
| ------- | --------------------------------------------------- |
| Owner   | Team ownership, members, settings and billing       |
| Admin   | Team administration, runner settings and billing    |
| Member  | CI visibility and permitted developer tools         |
| Billing | Financial information and permitted billing actions |

The server checks the current role on every protected action. Giving a key a scope does not grant a permission its creator lacks. Only an owner can transfer team ownership.

<Cards>
  <Card title="Connect GitHub" description="Install the App and select private repositories." href="/docs/teams-and-billing/github" />

  <Card title="Manage billing" description="Top-ups, runtime holds, plans and budgets." href="/docs/teams-and-billing/billing" />

  <Card title="Create agent keys" description="Short-lived scopes and safe credentials." href="/docs/teams-and-billing/management-keys" />

  <Card title="Invite your team" description="Email invitations and account access." href="/docs/teams-and-billing/invitations" />
</Cards>

The CLI and MCP expose team operations as well as CI tools. Check `berrybox help` for supported commands. Invitations and other mutations still require the correct role, scope and explicit write access.