A team's AI spend should trace to a ticket, not to a person's afternoon. Four controls in Settings → Team make that true, on the Mac, the web and the iPhone alike. An owner or admin sets them; every member sees them.
Every discussion belongs to a team project
Switched on, a discussion can only start inside a project shared with the team. The "+ New discussion" button offers the team's projects to start in; there is no private discussion to start instead. The rule binds the owner and admins too. Private discussions made before stay readable, and continue once they are moved into a team project — nothing is deleted or exposed.
Why: a discussion in a project has a ticket key, a stage, an owner and a cost. Spend then always has a purpose someone can read, and teammates can join the work rather than start it again.
Cost by project, release and ticket
Usage & Spend rolls cost up by project and by release, and shows the ticket key on every discussion. The owner and admins can switch from Mine to Team to see every discussion shared with the team, whoever ran it, with a row per member.
A ceiling per discussion
"Stop a discussion at $X" ends a discussion between turns when its recorded spend reaches the ceiling — never mid-answer. On a Mac the lower of the team's ceiling and the member's own applies. The message says what happened and who can raise it.
Spend alerts
A seat with a monthly or daily budget alerts the owner and the member by email at 80% and at 100% of it, once per month and once per day, and the team's audit webhook hears the same. There is nothing to switch on: the budget is the opt-in. The member's row in Settings → Team shows "80% this month" until the period ends.