Today · Team home

Team home

The same dashboard, rolled up across your team. Once you've bound at least one desktop via the connect-code flow, repoops.ai/team opens on Today, and repoops.ai/team/overview is the admin console: members and invites, bound devices, the team-wide subscription, and the policy pinned on every bound device.

Start here if you want to run the admin console (seats, members, policy, budget): Settings.

See it in motion

Where to find it

  • Hosted: https://www.repoops.ai/team/overview. Any member with a paid seat can open the hosted app; the management forms on this page act only for owners and admins.
  • Sign in: Google, Apple, Microsoft, or an email link, plus a hosted-tier subscription. Your first sign-in creates a team with you as owner; invite teammates from this page.
  • Localhost echo: The bound desktop's Settings Connect to team mirrors the binding state shown here.
  • Connect-code flow: Generate a one-time code on /team/connect (valid 15 minutes); paste it into the desktop's Settings Connect to team.

What it does for you

One view of every bound developer.The overview counts bound devices (revoked ones listed but not counted). Per device, Team activity shows the status (running, stale, offline, stopped), the last report, and the repos it streams, so you can tell what is streaming from what only claims to be bound.
Server-owned policy, pinned everywhere.Set the capture-mode floor (metadata-only, or content with secrets and PII stripped) and the sensitive-path watchlist here; every bound desktop reads it on its next policy refresh. The floor is tighten-only: a developer cannot loosen it locally.
Budget alerts that fire once per period.Daily, weekly, and monthly USD thresholds per team. On a breach, a chat webhook (Slack, Discord, or Microsoft Teams) and an email to the team's owners and admins, once per period instance, never a flood.

Configure

Three things to set up after first sign-in:

  • Invite teammates: one email at a time, with a role (owner, admin, or member). The invite link lives 14 days, and an invite needs a free seat.
  • Server-owned policy: capture mode and watchlist. The desktop shows a 🔒 pinned note for a metadata-only floor.
  • Budget alerts: per-period USD thresholds, one chat webhook URL, and an email toggle.

Use it well

  1. Bind your own desktop first.

    Generate a connect code, paste it into your desktop's Settings Connect to team, confirm consent, then turn on Stream to your team and watch the device appear on Team activity.

  2. Invite the rest of the team.

    Invite by email, one address per submit; each invitee gets a link that creates their account on sign-in and lands them on the connect flow.

  3. Decide the capture floor before any contractor binds.

    The default floor is metadata-only, and a bound desktop cannot loosen it. Set the floor to content only if you want redacted prompt text in the rollup, and add watchlist categories first.

  4. Wire one chat webhook for budget alerts.

    One channel, one webhook URL, one notification per period. Do not fan out to several channels; alert fatigue is the failure mode.

Read more

Last updated