Skip to content
Athena User Guide
Esc
↑↓navigate↵open⌘Jpreview
On this page

Event dashboard pages

What each page of the per-event admin dashboard shows and does.

Opening an event from your workspace dashboard lands in its own event dashboard. At the top of the sidebar an event switcher jumps to another of your events, and an All events link returns to the workspace dashboard. Below them the pages are grouped; this reference lists every entry in the order it appears.

Not every event shows every page: Teams appears only when the event runs in team mode, Image builds and Running instances don’t appear on Extra Small (static-only) events, API keys and Integrity require a Starter plan or above, and Audit log requires Pro or Enterprise. See Plans and limits.

The whole event dashboard stays reachable until teardown begins: shortly after the end time, or immediately when you end the event yourself. From that moment these pages are gone, so anything you want from them has to be collected while the event is still running. See The event lifecycle.

  • Overview: the landing page. It carries an Event details card (status, event URL with an Open event button, the address your event’s mail is sent from, plan, storage size, team mode, duration, flag prefix, and the start, scoreboard freeze, and end times) followed by stat cards for Total Users, Challenges, Submissions, and Success rate, plus Challenges by category and Submissions over time charts. Covered in Monitor a live event.

Challenges

  • Categories: create, rename, and delete the challenge categories used in the challenge editor and on the player-facing challenge list; each row shows how many challenges use it.

  • Difficulties: the same management, for difficulty levels.

  • Challenges: the challenge list with an Add challenge button; the table shows title, category, difficulty, points, and status, with search, a status filter, and sorting. Drafts appear here too, marked Draft; players never see them. A challenge row opens a read-only detail view with an Edit challenge button into the challenge editor; a draft row reopens the editor directly, and can be deleted from the list. Publishing happens from inside the draft editor; the workflow is in Release challenges in waves.

  • Files: a read-only list of every challenge attachment uploaded to the event, alongside a Storage utilization bar of used space against the event’s storage limit.

  • Image builds (not on Extra Small): upload a zipped Docker build context and the platform builds and stores the challenge image; the Build quota card tracks Docker storage and build minutes. Actions are upload, build, cancel a running build, and delete images. See Build challenge images.

Participants

  • Players: a table of event participants, showing name, handle, email, and points, plus a Team column in team mode. A participant’s points are their team’s score. Search by name, handle, email, or team name, sort by name or points, and page through the roster 25 rows at a time (up to 100 with the page-size selector); the search term, sort and page live in the URL, so a filtered view is shareable. Click any row to open a player detail sheet (overview and activity stats, a points-progression chart, solves-by-category and by-difficulty charts, and timelines of solves, submissions, hint unlocks, and instances), where you can also adjust the player’s points (a signed bonus or penalty with a required reason, applied to their whole team), ban or unban the player, remove them from their team or move them to another team (solves and points stay with the old team), and delete the account. A ban asks for Permanent, 1 hour, 24 hours, or 7 days and an optional reason; it signs the player out everywhere, and the reason and expiry are shown to them at sign-in. Bans, unbans, removals, moves, and deletions each notify the player by email; a deletion also copies the team leader.

Deleting a player is blocked while they still have challenge instances running; terminate those first, or wait for them to expire.

  • Teams (team mode only): a table of every team, listing the team name (with a Hidden badge when the team is kept off the public scoreboard, and a Solo badge for an auto-created single-player team), the Handle (shown as @HANDLE), and Points. Search by name or handle, sort by name or points, and page through the teams 25 at a time (up to 100 with the page-size selector); the search term, sort and page live in the URL. Click any row to open a team detail sheet (overview and activity stats, a points-progression chart, points-by-member and solves-by-category/difficulty charts, the member list, and the solve timeline), where you can also adjust the team’s points (a signed bonus or penalty with a required reason), rename the team, remove members (leadership passes to the longest-standing member if the leader is removed), and delete an empty team.

  • Submissions: a paginated log of flag attempts (15 per page by default, up to 100), showing user, challenge, result, and time, with search and a correct/incorrect filter. Submitted flag text is never displayed.

  • Leaderboard: the event’s current standings, shown as a Rank / Name / Points / Solves table with a Top 10 score progression chart. It shows the live rankings including teams hidden from the public scoreboard, and, unlike the players’ public board, it is never labeled frozen. Rebuild leaderboard in the header recomputes the standings from the event’s recorded results if they ever look out of step. Covered in Monitor a live event.

Engagement

  • Announcements: create, edit, and delete the live-feed announcements players see in the event site’s navbar. See Announce to players.

  • Reports: triage player-filed challenge and platform reports, with scope, status, and area filters, threaded replies to the reporter, and closing with a reason. See Triage player reports.

  • Feedback: participant feedback collected after the scoreboard freeze, with average rating out of 5, response count, a rating-distribution chart, and the individual entries.

  • Writeups: challenge writeups uploaded by teams after the scoreboard freeze, each with a download button.

  • Certificates: “Author templates, map them to award tiers, then issue and email credentials.” Design certificate templates over a background you upload, publish them, map each award tier to a template, then issue credentials to qualifying participants and email them. The issued table lists every credential with its recipient, tier, rank, credential ID, and emailed status, and lets you revoke one. See Issue certificates.

Integrity

(Starter and above) The platform reviews the event’s own activity once an hour and raises a finding whenever it sees a pattern worth a human look. Nothing here changes a score, bans anyone, or notifies a player; findings are evidence for your decision.

  • Findings: the ranked list, showing subject, the check that raised it, severity, confidence, a plain-language summary, and the current review state. Opens filtered to Open; filter also by severity and by Re-escalated (findings you already dismissed that have since picked up new activity). A row opens a detail sheet with every recorded event behind the finding, the subject’s other findings, and buttons to move it to Reviewing, Actioned, or Dismissed, or back to open. The header shows when the checks last ran, and calls out any that are paused for want of data so an empty list is never mistaken for a clean event. See Review integrity findings.

  • Internal teams: the accounts you run yourself, listed on a page headed Internal & test teams. Add a team handle or a username with a reason, and no findings are raised for it. It still appears in other teams’ evidence, so excluding your own staff team doesn’t blank it out of someone else’s record. Remove an entry and findings resume from the next hourly check.

Operations

  • Running instances (not on Extra Small): the Challenge instances table, one row per player-started instance with its challenge, user, status, and creation time. A row opens the Challenge session details dialog with one endpoint per exposed port and the expiry, plus the session’s metering and resources (metering start and end, task size, billing multiplier, and whether it has shut down), and a Terminate instance action while the instance is still running. The page header carries Terminate all (N) for every running instance, and a banner naming any instances that may still be running after being marked terminated. See Monitor a live event.

  • Usage: this event’s resource consumption for the current period, covering instance-hours consumed, open sessions with the credits reserved against them, credits remaining, usage events, active users, last metered event, and storage used against the event’s cap with a utilization bar.

  • Analytics: statistics over the whole event window, with overview cards, submission-trend and attempt-distribution charts, and a per-challenge stats table, plus Export JSON / Export CSV buttons. See Export event data.

  • Exports: start an on-demand data export of this event and see the archives it already has. The download itself is on Data exports in your organization dashboard, which stays reachable after the event ends.

Settings and developer tools

Pinned to the bottom of the sidebar:

  • Settings: change the event’s configuration after creation, covering general details, schedule, submission cooldown, registration & teams, organizer alerts, marketing, rules & FAQ, data export, overage spend cap, and a danger zone for ending the event. Each is saved on its own, with version history you can revert to. Athena sign-in is also here, as a single switch that applies immediately. The Discord switch has its own page. See Event settings.

  • Domains: the platform-managed and attached custom domains for this event’s deployment, with the add/attach/verify flow. See Connect a custom domain.

  • Discord: everything about the bot in one place, namely the Discord integration switch, Connect Discord server and its disconnect, the staff role picker that decides who may run staff commands, and a read-only list of what /setup has configured in your server (which channel each feature uses, whether the first-blood feed exists, and the verified role). See Discord bot commands.

  • API keys (Starter and above): issue per-event keys for your own integrations, each with a label and expiry, revoke them, and copy the API base URL. See Create API keys.

  • Audit log (Pro and Enterprise): every organizer action taken on this event, newest first. Each entry reads as a sentence: who did it, what they did, and what it affected. Filter by the kind of action and page back through the history. Actions that were attempted but did not take effect are marked Not applied. Like the rest of the event dashboard, this page is only available while the event exists; export anything you need before teardown.

Was this page helpful?