Your morning pulse: new users, tasks, applications, hires vs yesterday, plus platform health (uptime + cron history). Start here. If a number looks stale, check Health first — a red cron usually explains it.

The bot and channel rail: digest history, channel posts, offer Accept-rate, linked users. Answers "are workers actually seeing and answering offers in Telegram?"

Where users come from and who they are: acquisition funnel, audience by level and region, posters-vs-workers liquidity. Use it to pick the next region or category to push.

Messaging that brings users back. Campaigns = one-off pushes to a segment (AI can draft the copy). Journeys = automated day-2 and win-back flows. Results = outcomes, marked nightly. Sends respect quiet hours (21:00–08:00), a 7-day per-user cap and a 500-recipient cap — silently skipped users are the cap working, not a bug.

Money in and out: revenue-vs-cost waterfall, inflows (Pro, points), expense register with amortization, daily CBU rate. Records reality; moves no money.

The workforce-request pipeline, left to right: New → Scoped (AI proposal drafted — review it) → Proposed (sent to client) → Response → Staffing (create crew tasks, offer workers). Each stage shows only its valid actions. Always check the AI draft's numbers before sending.

The read-only log of every admin action: who did what, when. If something changed and nobody remembers doing it, look here.

↻ Refresh re-pulls everything. Only admin accounts can sign in; no service key lives in this page. Sign out on shared computers. Full guide: docs/ADMIN_PORTAL_GUIDE.md in the repo.