The admin dashboard is your daily triage page. It is meant to answer one question quickly:

"What needs attention right now?"

Use it as the first page you open, not as a replacement for the deeper admin screens behind it.

Use the dashboard to:

• spot health problems early
• notice growth and storage pressure
• jump into the correct admin page quickly
• understand what changed today without scanning the whole platform

1. check Attention Needed
2. check What changed today
3. scan the top headline cards
4. open the deeper admin page only for the things that actually need follow-up

Common top-level metrics include:

• Total Users
• Total Files
• Storage Used
• Cache Status

These are fast context cards, not the full story.

The dashboard is reading precomputed totals from the internal system_stats row.

The dashboard is not trusting or not finding that cached summary, so it is recalculating totals from live tables.

Common reasons:

• stats cache does not exist yet
• cron has not refreshed stats yet
• cached file totals do not match live totals

This is usually a performance warning, not an outage.

This strip is the most important part of the dashboard for day-to-day operations.

It is meant to surface issues before they turn into support pain, payout mistakes, or moderation backlog.

Typical items include:

• recent errors
• overdue automation tasks
• SMTP missing or failing
• moderation backlog
• storage pressure
• encryption key warnings
• pending encryption migration items
• database health or drift notices
• Cloudflare IP sync warnings
• leftover setup files
• aged withdrawal pressure
• fraud review queue pressure

This means recent error-level log entries were recorded. It is not a special review queue. Use it as a shortcut into the recent error section on System Status.

This means one or more cron-managed tasks are behind schedule. Review the Cron Jobs area and heartbeat health.

This means email delivery is not configured, which affects verification mail, reset mail, and some support flows.

This means mail settings exist but delivery is still failing often enough to deserve attention.

This means you should review storage nodes and capacity before users hit failures.

This points to security configuration that needs attention before you treat the install as cleanly migrated.

This means enterprise encryption still has pending items to migrate.

This reflects schema drift or database-health warnings that also surface inside Config Hub.

This means trusted Cloudflare IP handling may be stale or unsynced.

This means install or post-install artifacts may still be present and should be reviewed or removed.

This is meant to catch payout work that is sitting too long instead of quietly becoming a support problem.

This means monetized activity is stacking up in manual review and deserves operator attention before withdrawals move forward.

This strip is for fast orientation. It gives you a quick read on:

• daily movement
• uploads
• users
• download activity
• operational drift

Use it to answer:

• "Is today normal?"
• "Did something spike?"
• "Did something stall?"

The dashboard supports saved layout state in the browser.

That means admins can:

• drag widgets into a preferred order
• collapse widgets they do not need
• keep that layout in browser storage

Use Reset layout to clear the saved client-side layout state and return to the default arrangement.

Use it to watch:

• recent error count
• SMTP availability
• plugin count
• support contact details

Use it to spot:

• overdue tasks
• failed tasks
• last run timing

If these drift, review cron before assuming the widget itself is wrong.

Use it to catch:

• tight headroom
• unhealthy distribution
• capacity planning issues before uploads start failing

Use them to stay ahead of:

• compliance backlog
• moderation delay
• unanswered staff workflows

Many dashboard metric chips are intentionally clickable.

Examples:

• recent errors -> System Status error section
• SMTP missing -> email configuration
• overdue tasks -> cron configuration
• storage pressure -> file-server management

The dashboard should help you jump straight to the page that can actually fix the problem.

The dashboard is not:

• a replacement for System Status logs
• a full moderation console
• the best place for one-record forensic debugging
• a permanent historical analytics suite

It is the control surface for fast triage and navigation.

• start here every day
• use Attention Needed before lower-priority widgets
• treat LIVE (SLOW) as a signal to check stats refresh and cron health
• follow metric chips into their real detail pages
• use Reset layout if the saved arrangement stops feeling useful

The dashboard is your first-stop triage page. It helps you notice problems early, understand what changed today, and jump straight to the page that can actually fix the issue.