Model Usage Per User, Field Calculations as Activity, and Seats That Fail Gracefully

Reports carry model usage per user and export it to CSV, a field calculation counts toward activity, and a workspace at its seat limit refuses the seat rather than the login.

Models

• Full Opus reasoning levels: The complete range of Opus reasoning levels is exposed, so how hard the model thinks is a setting rather than a default.

Reporting

• Model usage per user: A per-user model usage series is available and exports to CSV, so a model’s cost can be read against the people using it.

• Field calculations count as activity: A field calculation counts toward user activity in the Users and Overview views, so someone whose work is calculations rather than chats appears as active.

• Per-user activity in organization reports: An organization report breaks activity down by person, so adoption can be read across workspaces rather than only in total.

• Reports assemble in parallel: Independent reporting steps run concurrently, so a report waits on the slowest step rather than the sum of all of them.

Seats

• A full workspace refuses the seat, not the login: When a workspace is at its seat limit, a first login is denied a seat without the login itself failing, so the person gets a clear outcome rather than a broken sign-in.

• Seat distribution in the roster: Billable seat distribution is returned alongside organization users, so where the seats went is answerable.

Chat

• One slow chat stops blocking the rest: A chat with messages pending no longer holds up the others, so a long run in one place does not freeze work somewhere else.