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

# Managing Incidents

> How to create, update, and resolve incidents on your status page.

When a service disruption occurs, clear communication is key. The incidents feature allows you to keep your users informed throughout the event.

## Creating an Incident

<Steps>
  <Step title="Navigate to your Status Page">
    Go to the specific status page where you want to report an incident.
  </Step>

  <Step title="Create New Incident">
    Click on the "Create Incident" button.
  </Step>

  <Step title="Fill in Incident Details">
    * **Title**: A clear and concise title for the incident (e.g., "API Latency Issues").
    * **Status**: The current status of the incident:
      * **Investigating**: You are aware of the issue and are looking into it.
      * **Identified**: You have found the root cause.
      * **Monitoring**: A fix has been applied and you are monitoring the situation.
      * **Resolved**: The issue is fixed and services are back to normal.
    * **Impact**: The level of impact on your services (e.g., None, Minor, Major, Critical).
    * **Message**: A detailed message about the incident. You can use Markdown for formatting.
  </Step>

  <Step title="Affected Components">
    Select the components that are affected by this incident.
  </Step>

  <Step title="Post Incident">
    Click "Create" to post the incident to your status page. Your subscribers will be notified.
  </Step>
</Steps>

## Updating an Incident

As you work to resolve the issue, you should post regular updates.

1. Go to the active incident on your status page dashboard.
2. Click "Add Update".
3. Change the **Status** if necessary (e.g., from `Investigating` to `Identified`).
4. Provide a new **Message** with the latest information.
5. Click "Post Update" to publish the new information.

<Note>
  Regular updates, even if just to say you're still working on it, build trust with your users.
</Note>

## Resolving an Incident

Once the issue is fully resolved and services are stable:

1. Post a final update.
2. Set the incident **Status** to `Resolved`.
3. This will mark the incident as resolved on your status page and send a final notification to subscribers.