> 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="" %} 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.currents.dev/dashboard/projects/projects-summary-view.md?ask=&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.