> For the complete documentation index, see [llms.txt](https://docs.escapedirector.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.escapedirector.com/review-and-improve/manage-leaderboards.md).

# Manage Leaderboards

Review successful Room Session rankings and configure the public leaderboard display.

Use Leaderboards to review eligible successful Room Sessions and control the player-facing ranking display.

## Review rankings

1. Select **Leaderboards**.
2. Choose a Room.
3. Choose **Today**, **This Week**, **This Month**, or **All Time**.
4. Review team name, saved time remaining, reported Clues when the Room collects them, and played date.

<figure><img src="https://4201072019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC32oMJLkI8XnHB2QVSVO%2Fuploads%2Fgit-blob-341e2c916b312448e971f74b3af9198eca90a97c%2Fleaderboards.png?alt=media" alt="Leaderboard for the synthetic Sublevel 13 Room showing gold, silver, bronze, and fourth-place Room Sessions for the selected period, with different saved times and reported Clue counts"><figcaption><p>Leaderboards rank included successful Room Sessions within the selected period.</p></figcaption></figure>

Saved time remaining determines the primary order. When the Room collects reported Clues, fewer Clues break a tie between Room Sessions with equal time. When it does not, equal times remain tied and the leaderboard does not show a Clues column. Failed Room Sessions are not ranked.

## Correct a leaderboard entry

Use the row edit action to correct the public team name or select **Exclude from public leaderboards**. Keep private operational notes in Room Statistics; do not put them in the public team name.

Use **Show excluded** only when you need to review entries intentionally removed from the public ranking.

## Configure the lobby display

Select **Display settings** to open the lobby display workspace.

<figure><img src="https://4201072019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC32oMJLkI8XnHB2QVSVO%2Fuploads%2Fgit-blob-dc0d1645a475237394a03d8c3909c4c0743ee722%2Fleaderboard-settings.png?alt=media" alt="Leaderboard Settings showing live publication status, Identity and Rooms controls, and a 1920 by 1080 Draft preview"><figcaption><p>The draft preview stays beside the settings while the public leaderboard remains on the last published version.</p></figcaption></figure>

Work through the page in order:

1. Set the display title, optional subtitle, and logo under **Identity**.
2. Add Rooms, drag them into presentation order, and select a Room to preview it.
3. Under **Standings**, choose how many teams to show and the ranking period. Rank, team, time, and Clues are automatic; select the optional **Players** and **Date** columns in the table preview.
4. Under **Appearance**, choose the default background, any Room-specific background exceptions, and the fallback color used when there is no image.
5. Check the **Draft preview** at the right. Open the full preview when you need to judge it at display size.

Changes save to a draft automatically; they do not change the public leaderboard until you select **Publish** or **Publish changes**. Use **Reset to published** to discard the current draft and restore the live configuration. After publishing, use **View live** to check the public link on the actual lobby display.

## You're ready when...

The correct Room and period show only the successful Room Sessions intended for public ranking, and the lobby display reports that the draft and public leaderboard match.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.escapedirector.com/review-and-improve/manage-leaderboards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.