Team Management
Control who can access your project and what actions they can perform. Assign roles based on responsibilities to maintain security and accountability.
Team management is coming soon. Currently, each project has a single Owner. Role-based access control (RBAC) will be available in a future release.
Roles and Permissions
| Permission | Owner | Admin | Billing | Developer |
|---|---|---|---|---|
| Transfer project ownership | Yes | No | No | No |
| Add or remove admins | Yes | Yes | No | No |
| Add or remove team members | Yes | Yes | No | No |
| Manage sponsorship rules | Yes | Yes | No | Yes |
| Configure scaling settings | Yes | Yes | No | Yes |
| Manage billing and payments | Yes | Yes | Yes | No |
| View analytics dashboard | Yes | Yes | No | No |
| Delete project | Yes | No | No | No |
When to Use Each Role
Owner
Assign to the person ultimately responsible for the project. Owners have full control, including the ability to delete the project or transfer ownership. Limit this to one or two trusted individuals.
Admin
Assign to technical leads who need to manage team composition and project settings. Admins can do everything except delete the project or change ownership. Use this for senior engineers or managers.
Billing
Assign to finance team members who manage payments but should not access technical settings. Billing users can view invoices, update payment methods, and manage subscriptions without seeing sensitive project data.
Developer
Assign to engineers who build and maintain integrations. Developers can configure sponsorship rules and scaling settings but cannot access billing or team management. This is the most common role for day-to-day development work.
Best practice: Follow the principle of least privilege. Assign the minimum role needed for each team member to do their job.