Dashboard
The four numbers worth a glance, and the one alert worth acting on.
The landing screen, and the console's front page. Four figures and a couple of alerts.
Requests today, with a comparison against last week. Useful as a shape rather than a number: a quiet Tuesday after a busy Monday is nothing, a flat line after a launch is worth a look.
Cost this month, with a projection. The projection is a straight-line extrapolation, so it is pessimistic early in a month with a heavy first week. Treat it as an early warning, not a forecast.
Active users over the last seven days, with your seat count. The gap between seats bought and people actually using them is the number that tends to embarrass a renewal.
Models configured, across providers. If this is zero, nothing works. See Models.
The alerts
Seats reminder appears as you approach your limit. You cannot invite past it, so this is your notice to plan rather than a problem today.
Model failures detected is the one to act on. It means models have failed in the past hour and fallbacks are being used, so your users are probably not seeing errors: they are quietly getting a different model than you configured.
That silence is the point. Without this alert, a provider outage looks to you like a normal day and looks to your users like the assistant getting mysteriously worse. Click through to Models and check which provider is unhappy.
Quick actions
Shortcuts to the things administrators do most. Nothing here that is not reachable from the sidebar.