Concepts
Teams

Teams

Teams are how Runless organizes users and repositories. Understanding teams helps you set up the right structure for your team.

What is a Team?

A team is a shared environment where:

  • Multiple users can collaborate
  • Repositories are organized together
  • Analytics are aggregated
  • Repository groups are shared

Think of a team like a GitHub organization — it's the boundary for shared access and data.

Team Structure

Team (e.g., "Acme Corp")
├── Members
│   ├── [email protected] (Owner)
│   ├── [email protected] (Admin)
│   └── [email protected] (Member)
├── GitHub Installations
│   └── Acme Organization (via GitHub App)
├── Repositories
│   ├── acme/backend
│   ├── acme/frontend
│   └── acme/api
└── Repository Groups
    ├── Backend Team
    └── Frontend Team

Creating a Team

When you first sign in to Runless:

  1. A personal team is automatically created
  2. You can create additional teams for teams/organizations
  3. Each GitHub App installation is associated with one team

Team Roles

RolePermissions
OwnerFull access, can delete team, manage billing
AdminManage members, manage GitHub integration, view all data
MemberView dashboards and analytics, create groups

Switching Teams

If you belong to multiple teams:

  1. Click the team switcher in the sidebar
  2. Select the team you want to view
  3. All data updates to reflect that team

Your current team is stored in a cookie, so you'll return to it on your next visit.

GitHub App per Team

Each team has its own GitHub App installation. This means:

  • A GitHub organization can only be connected to one Runless team
  • Personal GitHub accounts can be connected to personal teams
  • Reinstalling the GitHub App on a new team moves the connection

Multi-Organization Setup

If your company has multiple GitHub organizations:

Option A: One Team

  • Install the GitHub App on each organization
  • All repos appear in a single team
  • Unified analytics across all orgs

Option B: Separate Teams

  • Create a team per organization
  • Install GitHub App separately for each
  • Isolated analytics per org

Most companies prefer Option A for a unified view, using Repository Groups to segment by team or project.

Deleting a Team

To delete a team:

  1. Go to Settings
  2. Scroll to "Danger Zone"
  3. Type the team name to confirm
  4. Click Delete
⚠️

Deleting a team permanently removes all data including run history, detections, and groups. This cannot be undone.