# Teams & portfolio intelligence

Team seats with pooled repos and credits, shared workspaces, portfolio health and ownership rollups, and an engineering-leader dashboard fed by drift checks.

The Teams plan turns Repowise from a personal tool into the shared
source of truth for an engineering org: index a repo once and every
member reads the same snapshot, queries it from their own editor, and
shows up in the same portfolio views.

## How a team works

- **Seats**: per-seat billing (3-seat minimum) with owner / admin /
  member roles. Members are invited by email.
- **Pooled repos**: the team's repo limit (25) is shared across the
  whole team, not per seat. No re-indexing the same codebase per
  person.
- **One GitHub App install**: an admin installs the App on the org
  once; every member's private-repo access comes from that install.
- **Pooled credits**: each seat contributes to one team credit
  balance for AI features, centrally billed and topped up by the
  admin.
- **Shared workspaces**: team-owned cross-repo workspaces with
  co-changes, contracts, and package-dependency views across member
  repos.
- **Team-wide PR bot**: blast-radius and reviewer-suggestion
  comments on pull requests across all team repos.

Team management lives at **Settings → Team**: members, invitations,
shared repos, billing, and the portfolio intelligence pages below.

## Portfolio intelligence

Three read-only rollups aggregate every team repo's latest snapshot,
built for the person who pays for the plan and opens it weekly:

### Portfolio health

Team-wide code-health KPIs (file-weighted average, critical/warning
finding counts, worst repo) plus a per-repo card grid that deep-links
into each repo's health pages.

### Ownership & bus factor

Top owners merged across the portfolio (files owned, hotspots owned,
recent commits, knowledge silos) and a cross-repo list of bus-factor-1
files: high-churn files one departure away from being orphaned.

### Engineering signals (the leader dashboard)

A nightly job observes every team repo's latest snapshot and tracks
four signals **between observations**, so it can alert on genuine
drift instead of static levels:

| Signal | What it watches |
|---|---|
| **Hotspot drift** | Files newly crossing the hotspot threshold (top churn quartile + activity floors) |
| **Bus-factor risk** | High-churn or hotspot files dropping to a single recent contributor |
| **Health decline** | Average / hotspot health falling 0.5+ points since the previous observation |
| **Decision staleness** | Recorded architectural decisions whose governed files churned past them |

The leader page (**Settings → Team → Engineering signals**) shows
rollup KPIs, per-repo cards with health trend sparklines, and a
recent-alerts stream that deep-links into each repo's hotspots,
ownership, decisions, and health-trend pages.

Threshold crossings also fan out as alerts: bell, email, and signed
webhooks. See [Alerts & notifications](https://docs.repowise.dev/hosted/alerts).

> **Note**
>
> **First observation = baseline, zero alerts.** Signals alert only when
> something *crosses* a threshold relative to the previous nightly
> observation. A repo that has always had 40 hotspots stays quiet; the
> day two new files enter the set, you hear about it.

### Weekly digest

Team owners and admins can opt in (Settings → Email notifications →
Weekly digest) to a Monday email summarising the same view: per-repo
signal counts and the week's threshold crossings. Off by default.

## Enterprise

Beyond Teams: unlimited repos and seats, private-cloud or on-prem
deployment, custom language extensions, and an SLA. SSO, SCIM, RBAC and
air-gapped installs are set up with your deployment and scoped during the
pilot; the [Enterprise](https://docs.repowise.dev/enterprise) page lists every capability.

[Book a demo](https://cal.com/repowise-demo/30min?overlayCalendar=true)