Hosted · /account

Account

Your hosted profile, your team's roster, the linking code that binds a desktop.One page for everything that's about "who's on the team" — invites with role assignment, role changes, removing a member, generating a new linking code, and your personal sign-in details.

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, 24-hour TTL; 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.24-hour 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 — generate when binding a new desktop. Consume within 24h or it expires.
  • Sign-out everywhere — invalidates all active sessions for your account, including bound desktops (they re-bind on next launch with a fresh code).

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. Sign-out everywhere when something feels wrong.

    Phone lost, laptop misplaced, suspicious activity — sign-out everywhere is the kill switch. All bindings re-up on the next launch with fresh codes that you generate.

Read more