Skip to main content

​
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

Creating a new engagement is more restrictive:

​
Engagement list

Use the list page to:
  • plan visible engagements on a monthly calendar
  • filter the calendar by customer, team, QA reviewer, or lifecycle status
  • review advisory warnings when active engagements overlap for a shared team member or QA reviewer
  • 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
Calendar items link to the engagement detail page. An active engagement without an end date appears on its start date as Needs end date and is not included in capacity-warning calculations until its schedule is complete. Inactive engagements retain the Inactive lifecycle label.

​
Create a new engagement

The create flow uses your organization’s workflow defaults and provisions the first structured report workspace automatically. Diagram of the engagement lifecycle from customer setup through portal delivery 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, and QA reviewer
New scoping-artifact uploads are disabled for the invite-only pilot. The create form and engagement detail page do not expose upload controls, and direct upload attempts are rejected before attachment storage or metadata writes.

​
Intake fields

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

​
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:
  • download an existing authorized artifact
  • delete an existing artifact when you have edit access
You cannot add a new scoping file during the pilot. Coordinate approved source material outside the attachment workflow and do not paste secrets into notes or filenames.

​
Credentials

The credentials section stores authorized access material for a specific engagement endpoint. Passwords stay masked by default. Authorized users must enter their current Strikepoint password to reveal one secret for up to 30 seconds; repeated failures are throttled and reveal activity is audited. See Sensitive credentials before using this feature.

​
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.
  • /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