Members & Roles
Roles
An organization has four membership roles, ordered from least to most privileged: viewer → member → admin → super_admin.
| Role | Use deployments | Manage deployments | Manage org & members | Billing |
|---|---|---|---|---|
super_admin |
✅ | ✅ | ✅ | ✅ |
admin |
✅ | ✅ | ✅ | — |
member |
✅ | — | — | — |
viewer |
— | — | — | — |
super_admin
The highest privilege, held by the organization creator. Includes everything an admin can do, plus billing permission (billing actions require super_admin).
admin
Can manage the organization and its members (update the organization, invite members) and manage deployments. Does not have billing permission.
member
Can use resources — create and use deployments — but cannot manage the organization, its members, or billing.
viewer
Read-only access.
Viewing Members
List the organization's members via GET /v1/organization/members (see the Organizations API). Each member record includes id, user_id, email, name, role, and joined_at.
Assigning Roles
Roles are assigned when you invite a member. Invitations may grant admin, member, or viewer (the default is member). The super_admin role belongs to the organization creator and is not an invitable role. Inviting members requires admin or super_admin. See Invitations.