> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/~/revisions/SGhJfnCIOpxRjx1gC1k5/pentests/using-projects-to-group-assessments.md).

# Using Projects to Group Assessments

## What are Projects

Projects in Aikido Pentest are logical groupings of one or more assessments that share the same scope, configuration, or target application.

They help you organize related pentests, for example by product, environment, or business unit, and keep all associated results, reports, and settings in one place.

A Project usually represents:

* A single application such as myapp.com and its related API or staging environments
* A set of connected apps that share the same backend or authentication system
* A recurring security scope such as a quarterly pentest of the same system

## Why Projects matter

Projects make it easy to:

* Track security posture over time by seeing how findings evolve across multiple assessments
* Reuse configuration such as targets, credentials, repository links, and API specs
* Manage reports by storing all assessment reports for the same app in one location
* Simplify compliance with a consistent audit trail for a defined scope

### Creating a Project

Before you can start an assessment, you first need to create a project.

When creating a project, you will:

1. Choose a name that clearly describes what is being tested

   (for example, “Aikido Dashboard” or “Customer Portal API”)
2. Save the project to make it available for future assessments

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

After the project is created, it becomes your starting point for all related assessments.

All configurations you define here are stored and reused automatically when starting a new assessment.&#x20;


---

# 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://help.aikido.dev/~/revisions/SGhJfnCIOpxRjx1gC1k5/pentests/using-projects-to-group-assessments.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.