For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform Keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily Executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a Product
    • Setting up a Chat Surface
    • Setting up an API Surface
    • Setting up an MCP Surface
    • Setting up an A2A Surface
    • Setting up a Slack Surface
    • MCP authentication
    • Authenticating with product API keys
    • Embedding the chat widget (script tag)
    • Embedding the chat widget (React)
    • Surface orchestration modes
    • Product views
    • Adding Capabilities to a product
    • Connecting external agents
    • How A2A works
    • Connecting to Cursor / VS Code
    • Connecting to Claude Desktop
    • Scoping API keys to capabilities
    • Auto-generated OpenAPI spec
    • Calling your API endpoints
    • Client tokens and domain restrictions
    • AI-powered theme generation
    • Widget theming and customization
    • Product versioning and status
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
    • Using prompt steps
    • Using transform-data steps
    • Using conditional steps
    • Using fetch-url and api-call steps
    • Using record steps (upsert/retrieve)
    • Flow variables and templates
    • Flow versioning and publishing
    • Running flows in batch
    • Handling batch failures
    • Debugging flows
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
    • Using records in flows
    • Filtering and searching records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
    • Runtime tools
  • Evals
    • What are Evals?
    • Running an Eval
    • Interpreting eval results
  • Schedules
    • What are Schedules?
    • Automating batch processing
  • Logs
    • What are Logs?
    • Working with Logs
  • Integrations
    • Connecting AI model providers
    • Slack integration
    • Google Workspace integration
    • GitHub integration
    • Linear integration
    • Weaviate (vector search)
    • Firecrawl (web scraping)
    • Exa (web search)
  • Settings
    • What's in Settings?
    • Available AI models
    • What are Organizations?
    • Managing AI models
    • Managing API keys
    • Billing and plans
    • Usage data
    • Team members and permissions
    • Appearance and preferences
    • Integrations (PostHog, Weaviate, Daytona)
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
    • Flow execution failures
    • Common errors and solutions
    • Authentication issues
Dashboard
LogoLogo
On this page
  • Team member limits
  • Inviting team members
  • Roles and permissions
  • Admin
  • Member
  • Changing roles
  • Removing team members
  • Organizations vs personal accounts
  • Best practices
  • Next steps
Settings

Team members and permissions

Was this page helpful?
Previous

Appearance and preferences

Next
Built with

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

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