> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/projects/projects-summary-view.md).

# Projects Summary view

Customize how you visualize projects

Currents enables you to create multiple projects to better organize your test pipeline. Each project consolidates test runs and their associated metrics, identified by unique IDs that seamlessly integrate with your CI environment. Leverage features to easily visualize, configure, and archive each project.

You can customize the view of your projects by choosing between **card or list view** and selecting whether to display **Tests or Runs metrics** in the project summary. You can also filter the data by date range, including the last **7, 14, or 30 days**.

{% embed url="<https://player.mux.com/ydovppRi00w2F01cvI7ELEvoycwshYpMllhL02OwP3QmAg?min-resolution=1080p>" %}
Project Summary View
{% endembed %}

To change how the projects themselves are grouped and presented — folders, ordering, labels, icons and the preview cards — see [Manage Projects](/dashboard/administration/manage-projects.md).


---

# 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 dynamically by asking a question.

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

```
GET https://docs.currents.dev/dashboard/projects/projects-summary-view.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.