Manage · Account

Account

Your hosted profile and your team's roster. One page for everything that's about "who's on the team": invites with role assignment, role changes, removing a member, and your personal sign-in details. The linking code that binds a desktop is generated at /team/connect, not here.

See it in motion

Where to find it

  • Hosted: https://repoops.ai/account (every signed-in user; admin actions gated to admin/owner).
  • Sign in: Google OAuth (NextAuth-backed). One Google account per RepoOps profile.
  • Roles: Owner (one per team, billing access) · Admin (manage members, policy) · Member (binding + own activity only).
  • Linking code: One-time, 15-minute TTL; generated at /team/connect, consumed on the desktop's Settings → Connect to team.

What it does for you

One-line invites with role assignment.Email + role; teammate gets a one-time link that creates their account, walks them through OAuth + binding. No password to set, no email verification step beyond Google's.
Linking codes that expire on their own.15-minute TTL, one-shot. A contractor who joins late re-generates a fresh code. Lost codes can't leak access.
Role changes that take effect immediately.Promote a member to admin; their permissions update on the next page load. Demote works the same way. No re-sign-in required.

Configure

Three things you'll touch on first setup, rarely after:

  • Profile - display name, avatar, default account-color hint. Pulled from Google by default.
  • Team roster - invites, role assignments, member removal.
  • Linking code: generated at /team/connect when binding a new desktop. Consume within 15 minutes or it expires.
  • Sign out - ends your current web session. To cut off a lost or compromised bound desktop, remove the member: its access ends immediately and the license key expires within 30 days.

Use it well

  1. Promote a second admin before you go on vacation.

    Single admins = single points of failure. At least two admins per team is the right shape.
  2. Remove members the day they leave.

    The bound desktop's license key expires within 30 days anyway, but immediate removal stops the audit-log entries from continuing. Cleaner.
  3. Generate a fresh linking code each time, don't reuse.

    They're one-shot and short-lived for a reason. Reusing a stale code = paste-buffer foot-gun.
  4. Cut off a lost or compromised device.

    Phone lost, laptop misplaced, suspicious activity: remove the member. Their access ends immediately and the bound desktop's license key expires within 30 days on its own.

Read more