TutorCat Guide Open TutorCat

Admins

The operations console at a glance

What the admin console is for, how it is laid out, and the two rules that shape every screen.

On this page
  1. Two rules that shape every screen
  2. How the console is laid out
  3. How reasons work

The operations console lives at tutorcat.ai/admin. It is for TutorCat staff running the invite-only beta. You use it to issue invite codes, watch the platform's health and spend, read feedback, manage accounts, and change platform settings.

It is a separate place from the product. It has its own sign-in, and a normal parent or student account can never open it.

Two rules that shape every screen

  1. Every change needs a written reason. Suspending an account, revoking an invite, changing a setting, a price or the AI budget: each one asks why. The reason is written to the Audit log before the change happens. If the audit entry cannot be written, the change does not happen.
  2. Admins never see what children write. The console shows counts and account details only. There is no screen that opens a student's messages, notes, photos or transcripts. See The privacy boundary in this guide.

How the console is laid out

On a computer, the left sidebar holds every section. From top to bottom:

Sidebar item What you do there
Overview Launch readiness, headline figures and seven-day charts. Start here every day.
Engagement Sessions, active students and the sign-up funnel, as totals only.
Users Find an account, see its details, suspend or erase it.
Invites Create and revoke family invite codes.
Feedback Read notes families sent from inside the app.
Packages The plan tiers and the packages that can be bought.
Payments The payments ledger. Payments are off during the beta.
Pricing What each plan costs, and the price history.
AI & Usage Today's AI spend against the daily budget, token use, the speech model and model prices.
Models Which AI model does each job, with backups, the OpenRouter key, safety tests and failovers.
Costs What AI costs by day, job, model and account, with CSV export.
Settings Registration, provider keys, email, budgets and the beta switches.
Audit log Every admin change, with who made it and why.

Below the list are Sign out, the Session timer and the email you signed in with.

The Overview page with the sidebar, session timer and launch readiness card
  1. Launch readiness
  2. How many rows are ready
  3. Headline figures
  4. The last seven days
  5. Every console section
  6. Session time left
  7. Sign out

On a tablet the sidebar shrinks to a row of icons. On a phone, the sections move into a menu: tap Open menu at the top right.

The console on a phone, with the section menu open
  1. Tap a section
  2. Sign out here

How reasons work

Most changes open a confirm box with a Reason field.

  • The reason must be between 20 and 500 characters. A counter under the field shows how many you have typed.
  • The confirm button stays greyed out until the reason is long enough.
  • Write what happened and why, for example "Parent asked by email to pause the account while they review screen time."
  • Do not paste the requester's email or other personal details into the reason. The field says so too.

Some forms (Invites, Settings rows, Packages and Pricing) have the Reason field on the page instead of in a box. It is still required and still goes to the audit log.