Docs/Teams & Organizations
Collaboration

Teams & Organizations

Share repositories, manage member permissions, and centralize billing across your engineering team.

How teams work

Every RepoWarden user automatically gets a personal team when they sign up. This is where your individual repos and billing live.

For shared work, you can create an organization team. Organization teams let multiple people manage the same set of repositories under a single plan and billing account.

Personal teams

  • Created automatically when you sign up
  • Single member (you)
  • Cannot be deleted
  • Perfect for solo developers and personal projects

Organization teams

  • Created manually from the Teams page
  • Multiple members with different roles
  • Can link to a GitHub organization
  • Centralized billing and usage tracking

Creating a team

  1. 1

    Navigate to the Teams page from the sidebar or team switcher in the top navigation.

  2. 2

    Click "Create team" and enter a team name. A URL-safe slug is generated automatically.

  3. 3

    You are set as the team owner. Invite other members by their GitHub username.

  4. 4

    Switch to the new team using the team switcher in the navigation bar. All repo and billing actions now apply to this team.

Roles & permissions

Organization teams have three roles. Each role inherits the permissions of the roles below it.

RolePermissions
Owner
  • Full control over team settings (name, billing email)
  • Manage billing and subscription
  • Add, remove, and change roles of all members
  • Link and unlink GitHub organizations
  • Delete the team
  • All Admin and Member permissions
Admin
  • Enable and disable repositories
  • Trigger manual scans
  • Add new members (as admin or member)
  • Toggle auto-join for linked GitHub orgs
  • All Member permissions
Member
  • View all team repositories and their status
  • View task queue and PR history
  • Use the AI chat assistant on repos
  • View usage and plan details

Seat limits

The number of members you can add to a team depends on your plan:

Free

1

seats

Starter

3

seats

Pro

10

seats

Business

25

seats

Linking GitHub organizations

You can link a GitHub organization to your RepoWarden team. This enables two key features: consolidated repo listing and auto-join.

Consolidated repo listing

When a GitHub org is linked, the repo picker shows all repositories from that organization alongside repositories from your personal GitHub account. You can enable repos from both sources under the same team.

Auto-join

When auto-join is enabled for a linked GitHub org, any RepoWarden user who is a member of that GitHub organization is automatically added to the team when they sign in. This saves team owners from having to manually invite every member.

Auto-join can be toggled on or off by team admins. It is enabled by default when you first link an org.

How to link a GitHub org

  1. Go to Team Settings (only available to team owners)
  2. Under "GitHub Organization", enter the GitHub org login (e.g., my-company)
  3. Click "Link organization"
  4. Make sure the RepoWarden GitHub App is installed on the org

Cross-team repo protection

A repository can only be enabled on one team at a time. If you try to enable a repo that is already active on another team, you will see a conflict error. This prevents accidental duplicate scans and billing confusion.

Switching between teams

The team switcher in the navigation bar lets you switch between your personal team and any organization teams you belong to. When you switch teams, the dashboard, repo list, and usage pages all update to show data for the selected team.

What changes when you switch teams

  • The dashboard shows repos enabled for the selected team
  • The repo picker lists repos accessible to the selected team
  • Usage limits and billing apply to the selected team's plan
  • Your role badge (owner, admin, member) is shown next to the team name

Next steps