Organizations & roles
An organization is a shared billing account with people attached. You can belong to many organizations; each keeps its own plan, balance, keys, and usage — nothing bleeds across.
The three roles
| Capability | Member | Admin | Owner |
|---|---|---|---|
| Use models on the org's account | ✓ | ✓ | ✓ |
| Create org API keys (own usage attributed) | ✓ | ✓ | ✓ |
| Invite & remove members | — | ✓ | ✓ |
| Per-member usage insights | own only | ✓ | ✓ |
| Billing: top-ups, spend limits, invoices | — | ✓ | ✓ |
| Invite/promote admins & owners | — | — | ✓ |
| Change the plan | — | — | ✓ |
| Rename / delete the organization | — | — | ✓ |
An organization can have multiple owners — recommended for bus-factor. Last-owner protection means the final owner can never be demoted or removed until another owner exists.
Inviting people
- Open Members → Invite someone, enter their email and role.
- Ares gives you a single-use link that expires in 7 days. Send it however you like.
- The invite only works for the exact email it was issued to — a forwarded link is useless to anyone else.
How usage and blame work
When someone works in an org context — playground or an org-scoped API key — the cost lands on the organization's account, tagged with who ran it. Admins see the per-member breakdown on the Usage page; members see only their own numbers.
Switching contexts
The switcher at the top of the console sidebar moves you between Personal and each organization. Everything on screen — keys, usage, billing, playground charges — follows the active context. Your personal account is always yours alone.