# The audit dashboard

Once the submission deadline passes, wardens may view all submissions to most Code4rena audits [in which they participated](#dashboard-permissions-and-submission-visibility). (Exceptions — such as audits that include live/deployed code — are normally noted in the audit repo `README` file.) After submissions close, you can use [the audit dashboard](/platform-guide/platform-guide-for-wardens/the-audit-dashboard.md) for an overview of judging progress. 

## Dashboard overview

After clicking "View dashboard," you'll see an abbreviated list of the highest-severity findings, and any recent comments: 

<figure><img src="/files/fu4Ue87E2Q8TpMFjSmRy" alt=""><figcaption><p>This is an overview screen only; to view all submissions or comments, select the relevant "View all" button.</p></figcaption></figure>

## Submission list &#x20;

From the dashboard, clicking "View all submissions" will take you to the full submission list:

<figure><img src="/files/UuubymlWHFpr3dztQWZD" alt=""><figcaption></figcaption></figure>

This is a table view that shows:

* ID: the finding (`F-`) and/or submission (`S-`) ID
  * Finding = set of duplicate submissions sharing a root cause
  * Submission = an individual warden or team's submission to the audit
* Severity: the judge's assessed severity (see [Severity criteria](/competitions/severity-categorization.md))
* Title: the title of the submission
* Triage: initial evaluation by the [Validator](broken://pages/UnOqT3qwyHt0Rbz1yc4x) \[deprecated]
* Review: input from the sponsor, if available&#x20;
* Judge: validity and quality evaluations from the judge
* Author: username of the warden or team who created this submission

{% hint style="info" %}
Findings are expanded by default, to display the individual submissions within each duplicate set. For a more compact view, use the `Filter` menu to select `Primary submissions` only.&#x20;
{% endhint %}

### Timestamps

The dashboard defaults to displaying a "Last updated" timestamp. To view more details, hover over the timestamp:

<figure><img src="/files/6B3rJ8DUvp5WHZdC7B8j" alt=""><figcaption><p>On hover, both the last updated timestamp and submission timestamp are displayed.</p></figcaption></figure>

This information can also be accessed via the individual submission screen:

<figure><img src="/files/a4IpXbm0eSp7XOWPeyqI" alt=""><figcaption></figcaption></figure>

## Filters

There are four ways to filter submissions in the dashboard:&#x20;

1. Search
2. `Filter` menu (filter by status)
3. `Severity` menu
4. `File` menu&#x20;

### Search

The search function offers a convenient way to locate submissions by keyword. You can also search by:&#x20;

* warden/team name
* submission number (e.g. `S-123`)

### Filter by status ("Filter" menu)

From the `Filter` menu, you can select:

* All submissions (default)
* Primary submissions - submissions selected as `Primary` (best) within a finding (duplicate set)
* Satisfactory submissions - submissions confirmed as valid and sufficient quality by the judge
* Partial credit - submissions evaluated as only eligible for [partial credit](/awarding.md#duplicates-getting-partial-credit) by the judge
* Eligible for awards - all submissions currently eligible for awards

Note that all judge rulings are subject to change until awards are announced.

<figure><img src="/files/VQimUdSg2z3dYdiAVagp" alt=""><figcaption><p>Selecting "Primary submissions" will produce a more compact view in the dashboard, by hiding all duplicates.</p></figcaption></figure>

### Filter by severity

From the `Severity` menu, you may select:

* All
* Highs and Mediums
* Highs
* Mediums
* Lows
* QA/Gas

<figure><img src="/files/9VSXze6sIXkzGrGfqG8Q" alt=""><figcaption></figcaption></figure>

### Filter by file

The `File` filter on the submission dashboard allows you to search by filename (e.g. `contracts/Token.sol` ) and if desired, to set a first and last line to further narrow results. The filtered results are based on the file and line(s) of code referenced by the submitter.

<figure><img src="/files/WJa04PR5HYKO6yZ3IeQq" alt=""><figcaption></figcaption></figure>

The `Submissions touching same files` section within the individual submission screen links to a similarly filtered view:

<figure><img src="/files/CwHi70NME7SKCFqRbUzV" alt=""><figcaption><p>Examples shown use test data only, so don't reflect real filenames. </p></figcaption></figure>

## Individual findings and submissions

To view an individual finding or submission, click on the title from the submission list. It will open the relevant finding or submission.

### Finding pages

When viewing a finding (group of duplicate submissions), you'll see:&#x20;

* an excerpt from the primary submission in the finding set,
* a timeline of inputs and evaluations, and
* a list of all duplicates within the finding set.

<figure><img src="/files/2zOtojGRmRL2TwozYwkc" alt=""><figcaption><p>The upper section of a finding page shows the finding number (F-67 in the example), an excerpt from the primary submission, and a timeline of inputs and evaluations.</p></figcaption></figure>

<figure><img src="/files/vsCX8StahAczNq8CZaab" alt=""><figcaption><p>Farther down, there's an option to view the full-length primary submission, and a list of all duplicates. </p></figcaption></figure>

### Submission pages

The Submission page is slightly different from the Finding page:&#x20;

* Instead of an excerpt, the full-length submission is displayed.
* Duplicates are listed in a block on the right side of the screen.
* You may also view a list of submissions by the same author.

<figure><img src="/files/kZ4Mxax8TXQtIrKr5951" alt=""><figcaption><p>The Submission page is fairly similar to the Finding page, with slight differences.</p></figcaption></figure>

<figure><img src="/files/jR5rnY8YxukhWnXd2I9h" alt=""><figcaption><p>Selecting the "By this author" tab displays a list of submissions by the same author as the submission you're viewing. </p></figcaption></figure>

## Interpreting the Timeline

The Timeline block displays a series of inputs and evaluations; it expands as the audit phases unfold.&#x20;

* **Submitted:** severity level selected by the warden (or team) at the time of submission
* **Triage:** initial evaluation by the [Validator](broken://pages/UnOqT3qwyHt0Rbz1yc4x) \[deprecated]
* **Review:** input from the sponsor, if available.&#x20;
* **Judging:** validity, severity, and quality evaluations from the judge (see [Judging criteria](/competitions/judging-criteria.md))

{% hint style="info" %}
Code4rena makes the final determination regarding validity, quality, and severity. All other inputs are advisory.
{% endhint %}

<figure><img src="/files/Y484uBh5MyARuQ0LbtQA" alt=""><figcaption><p>The Timeline expands as each audit moves through triage and judging. Shown: the Timeline as it appears during Post-judging QA.</p></figcaption></figure>

## Dashboard permissions and submission visibility

Only wardens who participated in a competition can view submissions during the judging, awarding, and reporting phases.&#x20;

After the audit report is published, valid submissions (including A- and B-grade QA reports) are publicly accessible; invalid issues are not.

Wardens may see their own submissions during all phases.&#x20;

### If you cannot see submissions to an audit in which you participated

If the submission deadline has passed, but you're unable to view submissions other than your own, the most likely explanation is that [the audit includes live/deployed code](https://docs.code4rena.com/competitions/live-code-rules). In this and other cases where submission access is restricted, staff will:

* include a note in the audit repo's `README` file (see `View repo` on the audit page), and
* post details in the audit channel, in the [C4 Discord](https://discord.gg/code4rena).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.code4rena.com/platform-guide/platform-guide-for-wardens/the-audit-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.