> ## 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.

# Create and run an engagement

> Follow the end-to-end path for setting up an engagement, staffing it, capturing technical data, and preparing reporting handoff.

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

# Create and run an engagement

Use this workflow when you are moving from setup into live delivery work.

<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" />

## Prerequisites

* You can open **Customers** and **Engagements**
* A valid customer record exists, or you can create one with customer-creation access
* A team already exists if your org requires team assignment at engagement creation
* You have engagement-creation access if you will create the record yourself

<PermissionRequired label="Permission required for setup">
  Creating a new engagement requires engagement-creation access. Editing findings, endpoints, or reports later in the flow may require additional permissions.
</PermissionRequired>

## Steps

<Steps>
  <Step title="Confirm or create customer context">
    Open **Customers** and verify the customer record and points of contact are current. If no customer exists yet, use **Create Customer** to add the record and primary point of contact first.
  </Step>

  <Step title="Create the engagement">
    Open **Engagements** and select **Create Engagement**. Complete the intake form: title, description, engagement type, scope summary, dates, customer, team, report title, report template, and finding layout. Add optional tags, supporting notes, QA reviewer, and a scoping artifact when needed.
  </Step>

  <Step title="Open the initial report workspace">
    After a successful create, Strikepoint redirects you into the engagement’s first structured report workspace. Confirm the template and report title match your delivery plan.
  </Step>

  <Step title="Review the engagement detail page">
    Return to the engagement workspace to confirm linked customer, team, scoping artifacts, collaborators, and active status.
  </Step>

  <Step title="Align collaborators and credentials">
    Use the collaborator and credential sections on the engagement detail page so the right people and access material are attached before work begins.
  </Step>

  <Step title="Capture endpoints and service context">
    Add endpoints manually, import Nmap XML if available, or use the service inventory view to understand exposed services and prepare for finding creation.
  </Step>

  <Step title="Draft findings and track remediation">
    Create findings from the engagement, then open the finding detail route for full writeup fields, evidence attachments, and remediation workflow state. Use the remediation page or remediation dashboard when you need owner, due date, retest, and SLA tracking.
  </Step>

  <Step title="Prepare for reporting and portal delivery">
    Once findings are stable enough for delivery, continue in the report workspace, coordinate review, and publish approved snapshots to the customer portal when ready.
  </Step>
</Steps>

## Related guides

* [Customers](/dashboard/customers)
* [Engagements](/dashboard/engagements)
* [Findings and endpoints](/dashboard/findings-endpoints)
* [Reports](/dashboard/reports)
* [Review and publish to the portal](/workflows/review-and-publish-to-portal)