Use the other admin tabs

What Support inbox, Abuse, What's new, AI, Deployment, Activation and Business are for.

In short

Beyond users, plans and features, the admin console has tabs for running the service. They cover the support inbox, abuse cases, product updates, AI use and cost, deployment checks, how new people fare, and whether the service pays for itself.

Before you start

Who: only a site admin. The Admin console is in the avatar menu of a site admin and nowhere else.
Plan: the Business tab has no figures on a private installation.
First: nothing. Most tabs are read-only reports.

Steps

Open "Admin console" from your avatar menu.
Pick the section you need in the list at the side: People, Plans and money, Product, Safety or Operations. "Find a section" finds one by name.
Each section saves its own changes; most are read-only reports.

What each tab does

Support inbox: feedback and contact-form messages, including from visitors, in Open, Unread, Handled and All views. Mark them read or handled, open a screenshot, or reply to the sender's email.
Abuse: complaints, appeals and signals about how the platform's outgoing traffic is used. Each case has its steps: host rules, running work you can stop, an emergency pause per module, legal holds and events that need sending again.
What's new: product updates with a title, what changed and a date. Publishing shows a quiet dot to everyone; a draft stays hidden.
AI, in three tabs. "Spending": questions asked and how they were answered, calls and tokens per provider and model with an estimated cost at the prices per million tokens, the monthly caps on the platform's key and the documentation questions asked most. "Models": which model does which work and which plans may use them. "Calls": every model call, newest first. Never the question or answer of a call. See /help/settings/admin-ai-models-and-caps.
Job sources: where the shared pool of jobs in Job search is read from, and the jobs people reported as fake. See /help/settings/admin-job-sources.
Deployment: readiness checks by area (Security, Web address and browsers, Email, File storage, AI assistant, Tester networks), each Ready, Review or Blocking. "Check again" re-runs them. Outside development a Blocking check stops the server from starting.
Activation: how new people fare at the start - who reaches a first real result in each module within a day, how long it takes, and where guided tasks are left. Sample data never counts.
Business: whether the service pays for itself - recurring revenue, paying subscriptions and members by plan, how trials end, six months of money collected, refunded and spent, and why people cancel. Enter "Hosting cost" and the break-even line says how much recurring revenue covers. A private installation has no figures.
Help feedback: what readers rated and searched for in Help, as counts only, so you can see which guides are missing or unclear.
Failure kinds, on the hosted service only: the kinds of crash private installations reported, and the version that fixed each. See /help/settings/admin-failure-kinds.
Data locations: organizations that keep their data in their own database, those waiting for a decision first. Each row shows Health, Own file storage (Ready or Not ready), Rows moved, In this state since, Put forward and Latest check. "Approve" lays out the tables and moves what the organization has. "Decline" lets the connection go and tells the administrators why. "Pause" tells members the data cannot be reached while you look into it. "Resume" uses the database again.
Approving needs the organization's own file storage to be ready. Otherwise it says "The organization's own file storage must be ready first: its files live with its data." Declining and pausing ask for a reason. The administrators read it. Without one the tab says "Write why first."
Deployment also offers "Download diagnostics": a file for support with versions, these checks, which settings are set (never their values), where the database migrations stand and recent errors by kind. Nothing in it names a person.

If something goes wrong

The server will not start: Deployment's Blocking checks name the setting to fix.
Platform AI is paused for free and trial workspaces: their share of the monthly cap is spent. It resets with the month, or raise the cap under AI › "Spending".