Manage Teams & Permissions
You can add and remove members from your organization to share access to key management, usage stats, and billing setup.
Adding members to your organization
Section titled “Adding members to your organization”Visit the Members page in Runway Dev to invite members by email address, and pick the role they should have. Invitations default to Admin, so set the role before sending.
If they do not already have an account, they will be prompted to create one and join your organization.
If they already have an account, they will see a notification that they have been invited to join your organization. This appears under invitations on the top navigation bar.
Inviting someone who already has an invitation pending replaces it, and the role on the newest invitation applies.
Organization roles
Section titled “Organization roles”Every member holds one of three roles, which applies across the whole organization.
| Role | Access |
|---|---|
| Admin | Everything. |
| Billing admin | Credits, payment methods, autobilling, and members. Cannot create or disable API keys. |
| Developer | API keys. Cannot manage credits, payment methods, autobilling, or members. |
All three roles can use the Playground, build Model Routers, and read usage and request history. Linking a Runway web app workspace under Manage → Connections needs Admin or Billing admin.
The member who created the organization is listed as its owner. The owner has the same access as an Admin, and cannot be given another role, removed, or leave the organization.
Where your role does not allow an action, the control is greyed out with a note on who to ask.
Changing a member’s role
Section titled “Changing a member’s role”Admins and Billing admins can change a member’s role, including their own, from the Members page: open the menu on the member’s row and choose Edit role.
Removing members from your organization
Section titled “Removing members from your organization”Admins and Billing admins can remove members from the Members page, using the same menu. Any member can leave the organization themselves.
Removing a user from your organization does not revoke their API key access. Because keys are org-scoped (not user-scoped), you must disable keys separately to fully cut off access.