Atlas / tournament documentation
Public page and help
The Public page hub of links, the in-console Documentation page and bug report, the Quick-start walkthrough, the search palette, and the Preview participant views panel.
This page covers five small parts of the admin console that point outward or offer help: the Public page hub, the Documentation page with its bug report form, the Quick-start walkthrough, the Search palette, and the Preview participant views panel at the foot of the Overview. None of them changes tournament data.
Who can use it
| Part | Platform admin, organization owner or admin, admin seat | Tab seat | Compliance seat |
|---|---|---|---|
| Public page hub | Yes. | Yes. | No. Sent to Records. |
| Documentation page and bug report | Yes. | Yes. | No. The link is hidden and the route sends the seat to Records. |
| Quick-start walkthrough | Yes, all steps. | Yes, without the Announce step. | No. The link is hidden. |
| Search palette | Yes. | Yes. | The palette is part of the top bar and finds only tournaments the account administers. |
| Preview participant views | Yes. | Yes. | No. The Overview is closed to a compliance seat. |
A coach, competitor, judge or observer reaches none of these parts. The previews they open are described under the preview panel below.
The Public page hub
The Public page is a hub of links for sending different audiences into the existing registration flows. It is not a switch. What the public sees is set elsewhere: visibility and the public copy in Setup, the registration status in Setup, when standings publish in Standings, and the release of rounds and the bracket.
The hub is reached at /tournaments/{id}/admin/public. The left rail has no entry for it, and Setup names it in the section on going public. The tournament's name appears above the heading Public page, and a Back button returns to the previous page, or to the Overview when there is none.
| Item | What it shows or does | Default or limit |
|---|---|---|
| Public summary | A heading that reads Registration is open or Registration is currently closed, from the registration open setting. Under it the dates, the location and the format, each shown only when set. A label at the right reads Invite only or Open registration, from the registration mode. | Dates read Dates to be confirmed when no start date is set. Same day events show one date. |
| Manage registration settings | A link above the entry points that opens Setup at the Registration section. | Not editable. |
| Schools, coaches & parents | Describes registering competitors, teams or a program through the tournament cart. The link reads Open registration and opens the tournament's registration page. | Not editable. |
| Judges | Describes collecting a judge profile, availability, conflicts and readiness. The link reads Open judge registration. | Not editable. |
| Sponsors | Describes sending sponsors through the sponsor registration path. The link reads Open sponsor registration. | Not editable. |
| Visitors note | Each entry point repeats that visitors without an account are taken to sign in or create one, then returned to the page. | Not editable. |
| Tournament details tile | Labeled Information. Opens Setup at the Tournament section. Text: Dates, format, location, and public registration state. | Not editable. |
| Events and divisions tile | Labeled Programs. Opens Setup at the Events section. Text: The events visitors see when they begin registration. | Not editable. |
| Announcements tile | Labeled Communication. Opens Announce. Text: Reach the people already connected to the tournament. | A tab seat that follows the tile reaches the full admin notice. |
The hub has no page level role check beyond the console's own, and a tournament that cannot be read answers as not found.
The Documentation page
The Documentation page is the in-console index of the tournament guides. It is the Documentation entry under Records in the left rail and the Documentation link in the foot of the rail, at the route /tournaments/{id}/admin/docs. Its eyebrow reads Knowledge Base and its heading reads Tournament Documentation.
| Section | What it holds |
|---|---|
| Guides | A link, Open the full documentation, and one list of guide pages for each stage: Begin here, Before the tournament, Running the tournament, After and Reference. A note says each page can be read without signing in and can be shared with co-directors. |
| Platform Features & Use Cases | Four tiles: Registration & Claim Links, Real-time Room Tracking, Physical & Digital Ballots and Custom Ballots. Each tile is a short summary, and some link to the matching guide. The guides hold the full reference. |
| Typical Tournament Workflow | Four steps: Pre-Tournament Phase, Day of Tournament Check-in, Running Rounds and Post-Tournament. Each names the console screens to use and links to a guide. |
| Patch Notes | One card per release from the tournament changelog, newest first, with the version, a summary, the date and a bulleted list. The file holds versions 2.2.0 of 2026-09-05 and 2.1.0 of 2026-09-04. |
| Report a Bug | The bug report form, described next. |
The bug report form
| Control | What it does | Default or limit |
|---|---|---|
| Issue Description | A text box with the placeholder Describe the issue, steps to reproduce, and what you expected to happen... Required by the browser. | Four lines tall and resizable vertically. At most 5,000 characters after trimming. |
| Submit Bug Report | Sends the report. The button reads Submitted! for three seconds afterwards and the text box clears. | Always enabled. |
| Error line | Shows the refusal in small capitals under the box. | Hidden until a refusal. |
The form checks that the account is signed in and still administers the tournament, then records an operations event of the kind tournament.bug_report with a warn severity. The event holds the first 240 characters in its message and the whole report, the tournament and the reporter in its payload. No email is sent, no reply is promised and no ticket number is shown. The page says the report is escalated to the Passage Administrative Audit Dashboard.
The Quick-start walkthrough
The Quick-start walkthrough is a guided tour of the console in the order a tournament runs. It opens from the Quick-start walkthrough link in the foot of the left rail. That link adds tutorial=1 to the current address, restarts the tour at step 1 and moves to that step's screen. A compliance seat has no link.
The first time an admin opens any tournament console in a browser, a welcome card appears before the tour.
| Control | What it does | Default or limit |
|---|---|---|
| Welcome card | Reads Welcome and the admin's name, and says the guide follows the operational path from configuration through closeout. A line at the foot says the tour can be reopened from Quick-start walkthrough in the sidebar. | Shown once per admin per browser. Once dismissed anywhere, a new tournament opens without it. A browser that blocks site storage never shows it. |
| Start walkthrough | Closes the card and starts the tour at step 1. | Focused when the card opens. |
| Skip for now | Closes the card and ends the tour. The Escape key and a click on the backdrop do the same. | Not editable. |
| Tour panel | A card at the lower right with a progress bar and a counter such as 3 / 12, a Skip button, the location label, the step title, the explanation, and sometimes a paragraph labeled Gate. | Not editable. |
| Frame | A bright outline around the control the step names, with the rest of the page dimmed. It follows scrolling and resizing. A step whose control is not found falls back to the rail entry for its screen. | Not editable. |
| Back | Goes to the previous step and its screen. | Disabled on step 1. |
| Progress ticks | One small block per step. Selecting one jumps to that step. | Each carries the label Step, its number and its title. |
| Next, and Finish on the last step | Goes to the next step and its screen. Finish ends the tour. | Not editable. |
| Skip | Ends the tour. | Reopen it from the rail link. |
The tour keeps its place in the browser for each tournament. A click on a rail entry during the tour moves the tour to the step for that screen. The Gate paragraph states the condition the step is checking, for example that the release check flags anyone paired who is not here.
| Step | Title | Screen it opens |
|---|---|---|
| 1 | The sidebar is the workflow | Overview |
| 2 | Configure before registration opens | Setup, Tournament section |
| 3 | Registrations, carts and claims | Field, Registrations |
| 4 | Make judges assignment-ready | Field, Judges |
| 5 | Check in, then freeze the roster | Field, Check-in |
| 6 | Create the round, pair it, allocate judges | Rounds |
| 7 | The disaster check gates release | Rounds, Release |
| 8 | Ballots come back, or you go get them | Ballots, Queue |
| 9 | Notify without leaving the round | Announce. Left out for a tab seat. |
| 10 | Read operational counts, not one percentage | Overview |
| 11 | Tabulate, verify, then break | Standings, Break |
| 12 | Closeout is a documented handoff | Records |
A tab seat sees 11 steps, and step 1 in its tour lists the rail without Announce.
The Search palette
The palette searches by name. It is a button labeled Search in the top bar, with the key hint Ctrl K, or the command key and K on a Mac. The key combination opens it from any admin screen and closes it again. The button shows from the large window width upward.
The palette does not list admin screens. It finds four kinds of record across every tournament the admin administers, with the current tournament first.
| Group | Matches | Opens |
|---|---|---|
| Tournaments | A tournament's name. The detail line holds the start date and the location. | That tournament's Overview. |
| Entries | An entrant's name or a partner's name. The detail line holds the school, Dropped or Waitlisted when that applies, and the tournament. | The entry's registration record. |
| Judges | A judge's name, including a judge who has not accepted a place. The detail line holds Withdrawn or Not yet accepted when that applies, and the tournament. | Field, Judges. |
| Rooms | A room's name or building. The detail line holds the building, the room number and the tournament. | Setup, Rooms. |
| Item | Behavior | Limit |
|---|---|---|
| Input | The placeholder reads Tournament, entry, judge or room. Words may sit anywhere in a name in order, so alex okafor finds Alex J. Okafor. Accents and capitals are ignored. | Two letters or digits start a search. Only the first 80 characters are read. |
| Timing | A search starts after a pause of 200 milliseconds. Enter does nothing until the answer to the typed text arrives. | Fixed. |
| Results | Ranked, grouped under the four headings, with the first result selected for Enter. | Six results per group. |
| Empty line | Reads Type two or more letters of a tournament, an entry, a judge or a room. before a search. | Fixed. |
Preview participant views
The Preview participant views panel sits at the foot of the Overview, below the console. It opens the screens that participants see, so the director can check what a competitor, a judge or a coach reads. The panel says the links use a representative record while keeping the administrator's session, do not impersonate the selected person, and are available only to tournament administrators.
| Link | Opens | Which people are listed |
|---|---|---|
| Public / spectator | The tournament's public page. | Always shown. |
| Competitor followed by a name | The tournament page as that entry sees it. | The first four active entries. |
| Judge followed by a name | Judge home as that judge sees it. | The first four judges on the roster, named Unnamed judge when no name is readable. |
| Coach followed by a name | The coach page as that coach sees it. | The first four accounts that own a cart. Each is named by the school of its active entry, or its participant name, or Representative coach. |
A long name is cut short inside its button. A preview address is honored only for an account that administers the tournament. For anyone else the address opens the account's own view.
Tasks
To check what a competitor sees:
- Open the Overview. Scroll to Preview participant views.
- Select the Competitor link for the entry.
- Read the page. Use the browser's Back button to return to the Overview.
To find an entry from any admin screen, press Ctrl K, or the command key and K on a Mac, type at least two letters of the name and press Enter on the result.
To report a problem, open the Documentation entry under Records, scroll to Report a Bug, describe the issue and the steps to reproduce it, and select Submit Bug Report. Wait for the button to read Submitted!
To restart the tour, select Quick-start walkthrough in the foot of the left rail.
Troubleshooting
| Message | What it means | What to do |
|---|---|---|
| Sign in before submitting a report. | The session ended. | Sign in again. |
| You do not have admin access to this tournament. | The access check refused the account. | Use an admin account. |
| Could not check your admin access. Try again. | The access check could not run. | Try again. |
| Describe the issue in 5,000 characters or fewer. | The report was empty after trimming or over 5,000 characters. | Write the report within the limit. |
| Could not submit the report. | The browser fell back to this line because the server gave no reason. | Try again. |
| Type two or more letters of a tournament, an entry, a judge or a room. | Fewer than two letters or digits were typed. | Type more. |
| Searching | A search is running. | Wait. |
| Nothing you administer matches followed by the typed text | No tournament, entry, judge or room matched. | Check the spelling or the tournament. |
| Search is unavailable right now. Try again. | The search could not run. | Try again. |
| Your session has ended. Sign in again to search. | The session ended. | Sign in again. |
Related pages: Getting started for the order of work, Setup for visibility and registration status, and Roles and permissions for seats.