Teams
A team is the organizational unit in deploybase. All resources (projects, deployments, domains, API keys) belong to a team, and every API request is scoped to the authenticated user’s team.
How Teams Work
Section titled “How Teams Work”- Every user belongs to exactly one team (created automatically on first login)
- All data is isolated per team — users in one team cannot see or access another team’s resources
- Team membership is tracked internally with role-based access control
- Billing plans and usage limits apply at the team level
deploybase has four roles, ordered from most to least privileged:
| Role | Description |
|---|---|
| Owner | Full control over the team, including billing, member management, and ownership transfer. Every team has exactly one owner. |
| Admin | Can manage projects, domains, API keys, invitations, and remove members. Cannot change billing or transfer ownership. |
| Member | Can create projects, trigger deployments, and manage environment variables. Cannot delete projects or manage team settings. |
| Viewer | Read-only access to projects, deployments, and billing info. Cannot create or modify any resources. |
Roles are hierarchical — each role inherits all permissions of the roles below it. An admin can do everything a member can, and so on.
Permissions Matrix
Section titled “Permissions Matrix”| Action | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| Projects | ||||
| View projects & deployments | ✓ | ✓ | ✓ | ✓ |
| Create / update projects | ✓ | ✓ | ✓ | |
| Delete projects | ✓ | ✓ | ||
| Deployments | ||||
| Trigger / cancel deployments | ✓ | ✓ | ✓ | |
| Promote to production (rollback) | ✓ | ✓ | ✓ | |
| Delete deployments | ✓ | ✓ | ||
| Domains | ||||
| View domains & DNS status | ✓ | ✓ | ✓ | ✓ |
| Add / verify / remove domains | ✓ | ✓ | ||
| Environment Variables | ||||
| View env vars | ✓ | ✓ | ✓ | ✓ |
| Set / delete env vars | ✓ | ✓ | ✓ | |
| Share Links | ||||
| Create / revoke share links | ✓ | ✓ | ✓ | |
| API Keys | ||||
| List API keys | ✓ | ✓ | ✓ | |
| Create / revoke API keys | ✓ | ✓ | ||
| Team Members | ||||
| View members | ✓ | ✓ | ✓ | ✓ |
| Invite / revoke invitations | ✓ | ✓ | ||
| Remove members | ✓ | ✓ | ||
| Change member roles | ✓ | |||
| Transfer ownership | ✓ | |||
| Billing | ||||
| View plan & invoices | ✓ | ✓ | ✓ | ✓ |
| Change plan / manage billing | ✓ | |||
| Notifications | ||||
| View preferences | ✓ | ✓ | ✓ | ✓ |
| Update preferences | ✓ | ✓ | ✓ | |
| Change notification email | ✓ | ✓ |
Invitations
Section titled “Invitations”Team admins and owners can invite new members by email:
- Admin sends an invitation with a role assignment (admin, member, or viewer)
- An email is sent with a link to
https://app.deploybase.eu/join/{token} - The invitee signs in (or creates an account) and accepts the invitation
- A team membership is created with the assigned role
Invitations expire after 7 days. Admins can resend (up to 3 times per 24 hours) or revoke pending invitations from the team settings page.
Expired, unaccepted invitations are automatically cleaned up 7 days after expiry. Accepted invitations are kept as an audit trail.
Ownership Transfer
Section titled “Ownership Transfer”The team owner can transfer ownership to any other member. This is a single atomic operation:
- The target member becomes the new owner
- The previous owner is demoted to admin
A team must always have exactly one owner. The owner cannot leave the team without first transferring ownership.
Managing Your Team
Section titled “Managing Your Team”- Dashboard: Navigate to Settings → Team to view members, send invitations, and manage roles
- API: Use the
/api/v1/team/membersand/api/v1/team/invitationsendpoints - MCP: Use
list_team_membersandlist_team_invitationstools