> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gpuoutlet.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams (coming soon)

> How small teams share an account today, and what proper Teams will look like.

Real team accounts are on the roadmap. Until they ship, here's what works.

## Today: shared account

For a 2–5 person team:

1. **One shared login email** — `team@yourcompany.com`, ideally a Google
   group or alias so everyone receives the OTP codes
2. **One wallet** — single source of credit
3. **Multiple SSH keys** — every team member adds their personal public key
   in **Settings → SSH keys**. Every pod injects every key, so any team
   member can SSH into any team pod.

This works fine until \~5 people, then:

* The shared inbox becomes noisy
* You can't see who launched what
* Stopping someone else's pod by mistake becomes a real risk

## Workarounds for accountability

Until Teams ships:

* **Tag pods in the name** — when launching, prefix your name (`alice/exp-42`)
* **Use a shared Slack channel** — `#gpus`, post when you launch and stop
* **Set a daily budget** — limit the wallet balance to one day's expected spend

## What real Teams will look like

(Roadmap, no committed dates.)

* **Organization-level wallet** — separate from any individual user's
* **Per-user identity** — each member has their own login and signs in with
  their email / OAuth
* **Roles** — admin (manage members, wallet), member (launch/stop instances),
  viewer (read-only)
* **Per-user usage attribution** — see who burned what credits this week
* **Spending limits** — cap individual users at \$X/day
* **SAML SSO** — for enterprise accounts

## I want this now

Email [business@gpuoutlet.ai](mailto:business@gpuoutlet.ai) with:

* Team size
* Annual GPU spend you're forecasting
* Must-have features

We're shipping Teams for early customers ahead of GA, and the priority list
follows the demand we hear about.