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

# Getting started

> Get oriented in the Strikepoint dashboard, understand permission patterns, and learn where to begin.

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>;
}

export function AuthorizedToolsOnly({children}) {
  return <Callout type="warning">
      <strong>Authorized security personnel only:</strong> {children}
    </Callout>;
}

export function AdminReference({children}) {
  return <Callout type="info">
      <strong>Administration handoff:</strong> {children}
    </Callout>;
}

# Getting started

If you are new to Strikepoint, start here before jumping into route-specific guides.

## What to expect after sign-in

After you sign in, you land in the authenticated dashboard. The sidebar is the fastest way to understand which parts of the product your account can use.

Common destinations include:

* **Dashboard** for analytics, recent engagements, and recent reports
* **Customers** for customer records and points of contact
* **Engagements** for live work, findings, endpoints, credentials, and report launch points
* **Reports** for one-off draft creation, report automation, review status, and publication tracking
* **Support** for FAQ, in-app workflow summaries, and ticket submission
* **Account** for profile updates, password changes, and two-factor authentication

## Understand permission differences early

<VisibilityNote>
  Strikepoint does not show every user the same surface area. Some users can only view operational pages. Others can create, edit, export, or manage staffing and report libraries.
</VisibilityNote>

Examples:

* You can view **Reports** only if your role includes engagement-detail visibility.
* You can create new report drafts only if your role can generate reports.
* You can manage **Templates**, **Snippets**, **Teams**, **Team Members**, or **Playbooks** only if your role is elevated enough for those libraries.
* You can open **Security Tools** only if you are authorized to use penetration-testing tools.

<AuthorizedToolsOnly>
  The **Tools** area includes restricted offensive-security utilities. If you do not have tool access, expect an access denial instead of a limited view.
</AuthorizedToolsOnly>

## Recommended first steps for a new user

<Steps>
  <Step title="Open the dashboard home">
    Review the analytics cards, recent engagements, and recent reports so you can see what is currently active in your organization.
  </Step>

  <Step title="Check your account settings">
    Open **Account** and confirm your email, avatar, password, and two-factor authentication status before doing sensitive work.
  </Step>

  <Step title="Review your operational scope">
    Open **Engagements** and **Reports** to confirm which customer work you can actually see.
  </Step>

  <Step title="Learn the side libraries you depend on">
    If your role includes staffing or reporting management, review **Teams**, **Team Members**, **Templates**, and **Snippets** before editing live records.
  </Step>
</Steps>

## When you may need an organization-level owner

<AdminReference>
  Some dashboard pages summarize account and access state, but org-wide settings still live outside the dashboard manual in administration settings. If the manual tells you a workflow depends on an org-level policy, ask an authorized admin or organization manager to review it.
</AdminReference>

## Read next

* [Dashboard overview](/dashboard/overview)
* [Engagements](/dashboard/engagements)
* [Reports](/dashboard/reports)
* [Review and publish to the portal](/workflows/review-and-publish-to-portal)
* [Account and security](/dashboard/account-security)