feat(settings): pool accounts are rows of Profiles; the separate Pool account section is gone
Settings → AI tools → Profiles now lists the account-pool accounts the user may use (GET /api/me/pool-accounts) as rows of each tool's tab, with quota, an 'in use' badge and Switch to (PUT /api/me/pool-accounts), plus an Automatic row; an admin's pin locks them. A saved profile with the same email as a pool account is shown once, as the pool row. Developers now see Profiles too, with only their pool rows; Cursor gets a tab when the pool holds a Cursor account for the user.
This commit is contained in:
+9
-4
@@ -692,15 +692,20 @@ tools**. An account's Edit (pencil) uses the same role / No pool list.
|
||||
### A user's own pool account
|
||||
|
||||
When the pool holds more than one account a user may use, they pick which one
|
||||
their own new sessions run on: **Settings → AI tools → Pool account**, one
|
||||
select per tool (Claude, Codex, Cursor), every role, server mode only
|
||||
(`GET/PUT /api/me/pool-accounts`, `account_choices`, `server/lib/account-pins.js`).
|
||||
their own new sessions run on in **Settings → AI tools → Profiles**: each pool
|
||||
account they may use is a row of that tool's tab (Claude, Codex, Cursor) with
|
||||
its quota and a **Switch to**, beside an **Automatic** row — there is no
|
||||
separate Pool account section. Every role, server mode only; a developer's
|
||||
Profiles shows only these pool rows, staff see the host's saved logins too, and
|
||||
a saved profile with the same email as a pool account is shown once, as the
|
||||
pool row (`GET/PUT /api/me/pool-accounts`, `account_choices`,
|
||||
`server/lib/account-pins.js`).
|
||||
|
||||
- The list is only what their group allows (or the shared pool); a choice
|
||||
outside it is refused (`ENOACCOUNT`), and one later taken from the group
|
||||
falls back to the balancer.
|
||||
- **Automatic** (the default) leaves it to the balancer.
|
||||
- An admin's pin wins and locks the select (`ELOCKED`); the choice comes back
|
||||
- An admin's pin wins and locks the rows (`ELOCKED`); the choice comes back
|
||||
once the pin is removed.
|
||||
- A Claude login goes into the user's home at once, like an admin's switch,
|
||||
so running panes follow it; Codex and Cursor take it at the next session (a
|
||||
|
||||
Reference in New Issue
Block a user