> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/modules/dashboard.md).

# Dashboard

## Overview <a href="#overview" id="overview"></a>

The global dashboard gives you a single pane of glass view of your security testing projects and vulnerabilities. Everything you're working on is in one place, so you can see where testing is up to and where the risk is without opening each project.

Every user has a global dashboard, and it's the first page they see when they log in. The data is made up of the projects and vulnerabilities that user has access to.

Click any box on the dashboard to drill down and see the data behind it.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FQNV0Yc25JW9eJgBvPT7p%2Fdashboard-at-a-glance.svg?alt=media&amp;token=308340cc-f98c-4f8d-ab8f-91523136b38a" alt=""><figcaption></figcaption></figure>

## Why it matters <a href="#why-it-matters" id="why-it-matters"></a>

* **One view, no assembly.** You don't need to build a report or open each project to see where things stand.
* **Everyone sees their own picture.** The dashboard is built from each person's access, so a client, a tester and an Administrator each see what's relevant to them, from the same platform.
* **From summary to detail in one click.** A number is only useful if you can see what's behind it. Drilling down takes you straight to the projects or vulnerabilities that make up each box.

## Who uses it <a href="#who-uses-it" id="who-uses-it"></a>

| Who                                 | To                                                                                   |
| ----------------------------------- | ------------------------------------------------------------------------------------ |
| **Security and programme managers** | Track testing across projects, and spot open risk and overdue work                   |
| **Testers and consultants**         | See the projects they're working on and the findings they've raised                  |
| **Clients and stakeholders**        | See the projects they're part of and what they need to fix                           |
| **Administrators**                  | See every project and vulnerability, because they can access all projects by default |

Every application role has full access to the global dashboard. See [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access).

## Use the dashboard <a href="#use-the-dashboard" id="use-the-dashboard"></a>

### Open the dashboard <a href="#open-the-dashboard" id="open-the-dashboard"></a>

The global dashboard opens automatically each time you log in. To come back to it from anywhere in AttackForge, select **Dashboard** in the main navigation.

### Drill down into the data <a href="#drill-down-into-the-data" id="drill-down-into-the-data"></a>

Click any dashboard box to see the data behind it. For example, clicking a box that counts open Critical vulnerabilities shows a list of those vulnerabilities, and you can open any of them from there.

Use the drill-down to:

* check which projects or vulnerabilities make up a number before you report it
* go straight from a summary to the findings that need action
* follow up on work that's overdue or waiting on someone

### Understand what you're seeing <a href="#understand-what-youre-seeing" id="understand-what-youre-seeing"></a>

The dashboard only counts projects and vulnerabilities you have access to. Two people can see different numbers on their dashboards, and both are correct.

| Who                                               | What their dashboard includes                                                                                      |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Administrators**                                | Every project and its vulnerabilities, because Administrators can access all projects by default                   |
| **Everyone else**                                 | The projects they've been given access to, and the vulnerabilities in them                                         |
| **Users with Upload or View access on a project** | That project's vulnerabilities, except those still pending. Pending vulnerabilities are hidden until they pass QA. |

If someone expects to see a project and can't, check that they've been given access to it, directly or through a group. See [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access).

## Go further than the dashboard <a href="#go-further-than-the-dashboard" id="go-further-than-the-dashboard"></a>

The dashboard is a summary. For more detail:

* **Analytics** lets you filter analytics on your data.
* **Vulnerabilities** lets you filter the vulnerabilities you have access to. See [Advanced filtering](https://support.attackforge.com/app/getting-started/advanced-filtering).
* **Reports** give each audience a formatted view of a project. See [Reporting](https://support.attackforge.com/app/getting-started/reporting).

## Land somewhere else after login <a href="#land-somewhere-else-after-login" id="land-somewhere-else-after-login"></a>

The dashboard is the default landing page. To send someone straight to a different page after they log in, such as a specific project, use a login redirect. See [Login redirects](https://support.attackforge.com/app/getting-started/login-redirects).

## Tips <a href="#tips" id="tips"></a>

* **Drill down before you quote a number.** Check what's behind it, so you can answer the first follow-up question.
* **Expect different numbers for different people.** Each dashboard only counts what that person can access.
* **Fix access, not the dashboard.** If a project is missing, give the person access to the project or add them to the right group.
* **Use login redirects for people who always start somewhere else**, such as a client who only works on one project.

## FAQ <a href="#faq" id="faq"></a>

**Who has a global dashboard?** Every user. It's shown when they log in, and every application role has full access to it.

**Why does my dashboard show different numbers from a colleague's?** The dashboard is made up of the projects and vulnerabilities each user has access to. If you have access to different projects, you'll see different numbers.

**Why can't I see a project on my dashboard?** You may not have access to it. Ask a Project Coordinator or Administrator to invite you to the project, or to add you to a group that has access.

**Can I see the data behind a box?** Yes. Click any dashboard box to drill down and see the data.

**Can I start somewhere other than the dashboard when I log in?** Yes, with a login redirect. See [Login redirects](https://support.attackforge.com/app/getting-started/login-redirects).

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access)
* [Advanced filtering](https://support.attackforge.com/app/getting-started/advanced-filtering)
* [Reporting](https://support.attackforge.com/app/getting-started/reporting)
* [Login redirects](https://support.attackforge.com/app/getting-started/login-redirects)
* [Users](https://support.attackforge.com/app/modules/users)


---

# 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://support.attackforge.com/app/modules/dashboard.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.
