> ## Documentation Index
> Fetch the complete documentation index at: https://docs.strikepoint.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Engagements

> Run day-to-day work from the engagements area, including engagement setup, detail review, credentials, collaborators, and report launch points.

export function VisibilityNote({children}) {
  return <Callout type="info">
      <strong>Visibility note:</strong> {children}
    </Callout>;
}

export function PermissionRequired({label = "Permission required", children}) {
  return <Callout type="warning">
      <strong>{label}:</strong> {children}
    </Callout>;
}

# Engagements

The **Engagements** area is the main operational surface in Strikepoint. This is where you move from customer setup into active delivery work.

## Who can use this area

<PermissionRequired>
  You need engagement-detail visibility to open the engagements list or any engagement workspace.
</PermissionRequired>

Creating a new engagement is more restrictive:

<PermissionRequired label="Permission required for create">
  You need engagement-creation access to use **Create Engagement** from the list page or dashboard home.
</PermissionRequired>

## Engagement list

Use the list page to:

* search by engagement title
* page through visible engagements
* sort by start date (newest first) when prioritizing active work
* open a specific engagement
* create a new engagement if your role allows it

## Create a new engagement

The create flow uses your organization’s workflow defaults and provisions the first structured report workspace automatically.

<img src="https://mintcdn.com/blueforceinnovations/tJ6PaiVOrZwI7ArF/images/engagement-lifecycle.svg?fit=max&auto=format&n=tJ6PaiVOrZwI7ArF&q=85&s=a4b39fd6b9b1078b3cf34139b46cf797" alt="Diagram of the engagement lifecycle from customer setup through portal delivery" width="920" height="200" data-path="images/engagement-lifecycle.svg" />

When you open **Create New Engagement**, expect:

* a default engagement duration window and prefilled end date based on org defaults
* a visible approval note if your organization requires engagement approval
* required fields for title, description, engagement type, scope summary, customer, team, report title, report template, and finding layout
* optional fields for tags, supporting notes, QA reviewer, and a scoping artifact upload

### Intake fields

| Field                | Purpose                                                                       |
| -------------------- | ----------------------------------------------------------------------------- |
| **Engagement Type**  | Describes the assessment style (for example, external penetration test)       |
| **Scope Summary**    | Approved targets, boundaries, and constraints                                 |
| **Supporting Notes** | Testing windows, customer contacts, or special handling                       |
| **Tags**             | Comma-separated labels for filtering and context                              |
| **Scoping Artifact** | Optional private file upload (PDF, image, TXT, XML, CSV, or JSON up to 25 MB) |
| **QA Reviewer**      | Optional reviewer assignment at intake                                        |
| **Report Title**     | Title for the initial report workspace                                        |
| **Report Template**  | Template used to create the first structured report                           |
| **Finding Layout**   | Technical detail, risk register, or executive summary                         |

You cannot finish this form without a valid customer and a valid engagement team in your organization.

After a successful create, Strikepoint redirects you directly into the new engagement’s initial report workspace.

## Engagement detail page

The engagement detail page is the central workspace for one engagement.

It brings together:

* basic engagement details such as title, dates, active state, and description
* customer and team context
* collaborators
* timeline events
* findings
* endpoints
* credentials
* reports

<VisibilityNote>
  The detail page is the main launch point for deeper routes like findings, endpoint editing, services, Nmap intake, and report workspaces.
</VisibilityNote>

## Collaborators and timeline

Use the collaborator section to see who is attached to the engagement. Use the timeline to understand key activity and handoff context.

If your role can manage collaborators, complete collaborator updates from the engagement page before live work starts.

## Scoping artifacts

The engagement detail page includes a **Scoping Artifacts** section for private scope files tied to the engagement.

You can:

* upload a scoping file from the engagement page
* download an existing artifact
* delete an artifact that is no longer needed

Use this section for signed scope letters, target lists, or other customer-provided material that should stay with the engagement record.

## Credentials

The credentials section on the engagement page is where you store sensitive access material needed for testing and validation. Keep these records tied to the engagement rather than outside the workspace.

## Reports from the engagement page

The report section on an engagement detail page is where you:

* review existing report drafts for that engagement
* open a report workspace
* create a new report from the engagement if your role allows it
* export report outputs where your permissions allow it

The engagement page also exposes direct export actions for the current engagement:

* **Export Summary CSV**
* **Export Findings CSV**
* **Export Summary PDF**

These actions require export-capable permissions such as `EXPORT_REPORT` or `DATA_EXPORT`.

<PermissionRequired label="Permission required for exports">
  Export actions on the engagement page require export-capable access, not just engagement visibility.
</PermissionRequired>

## Related routes covered by this guide

* `/dashboard/engagements`
* `/dashboard/engagements/create-engagement`
* `/dashboard/engagements/[engagementId]`
* `/dashboard/engagements/[engagementId]/exports/summary-csv`
* `/dashboard/engagements/[engagementId]/exports/findings-csv`
* `/dashboard/engagements/[engagementId]/exports/summary-pdf`

## Related guides

* [Findings and endpoints](/dashboard/findings-endpoints)
* [Reports](/dashboard/reports)
* [Create and run an engagement](/workflows/create-and-run-an-engagement)