Team members and permissions

Invite team members to your Runtype organization and manage their access levels.

Team member limits

Team members are unlimited on the Build (free) plan and all paid plans.

Inviting team members

1. Go to Settings → Team
2. Click Invite Team Member
3. Enter email address
4. Select role:
   • Admin: Full access to everything
   • Member: Standard access
5. Click Send Invite

They will receive an email invitation to join your organization.

Roles and permissions

Admin

Full control over the organization:

• All member permissions
• Manage billing and subscription
• Invite, promote, demote, and remove team members
• View and manage pending invitations
• Configure integrations and API keys

Member

Standard access to the organization:

• Create and edit Flows, Agents, Products
• Manage Records and tools
• Run Evals and view logs
• Cannot: Change billing, invite or remove users, or manage organization settings

What members see (read-only view)

Members can open Settings → Team and see the full list of organization members and their roles. The page shows a banner explaining that the view is read-only and that team management actions require an admin role.

The invite button, the per-member actions menu (promote, demote, remove), and the pending-invitations section are not shown to Members. Only Admins see these controls.

This read-only view applies automatically based on your organization role. No configuration is required — Members get the read-only experience, and Admins get the full management controls.

Changing roles

1. Go to Settings → Team
2. Find the team member
3. Use the actions menu to promote to Admin or demote to Member

Changes take effect immediately.

Removing team members

1. Go to Settings → Team
2. Find the member
3. Click Remove
4. Confirm

They immediately lose access to the organization.

Organizations vs personal accounts

Each user can:

• Have a personal account (free)
• Belong to multiple organizations
• Switch between organizations via the account menu

Resources (Flows, Products, etc.) belong to organizations, not individual users.

Use organizations to separate client work, personal projects, and team projects. Switch between them via the organization dropdown in the top navigation.

Best practices

• Principle of least privilege: Start with Member, upgrade as needed
• Limit admins: Only 2-3 admins per organization
• Use descriptive emails: Invite with work emails for accountability
• Review regularly: Remove members who’ve left the team

Next steps

• Billing and plans — Manage your subscription
• Managing API keys — Programmatic access
• Appearance and preferences — Personal settings