> For the complete documentation index, see [llms.txt](https://support.incidentlake.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidentlake.com/readme.md).

# Incident Lake Help

Help for people who use Incident Lake to respond to incidents, share knowledge, and keep stakeholders informed.

Incident Lake helps your team see what is happening, decide what to do next, and keep a record of how you responded.

This help is for responders, incident commanders, and organization admins who use Incident Lake every day. You do not need a technical background to follow these pages.

{% hint style="info" %}
The Incident Lake web app is at <https://incidentlake.sigq.io>. If you cannot sign in, contact an administrator in your organization or the Incident Lake support team at <support@sigq.co.jp>.
{% endhint %}

## What you can do here

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What's new</strong></td><td>See what recent product updates let you do, explained in plain language.</td><td><a href="/release-notes.md">What's new</a></td></tr><tr><td><strong>Get started</strong></td><td>Learn how to sign in, how the screen is laid out, and what each role can do.</td><td><a href="/getting-started/sign-in.md">Sign in</a></td></tr><tr><td><strong>Run an incident</strong></td><td>Create, update, and close incidents from the console or Slack.</td><td><a href="/incidents/overview.md">What is an incident?</a></td></tr><tr><td><strong>Ask and remember</strong></td><td>Ask questions in Chat and reuse past responses through Knowledge.</td><td><a href="/everyday-tools/chat.md">Chat</a></td></tr><tr><td><strong>See the bigger picture</strong></td><td>Review trends, status, risks, and who should be notified.</td><td><a href="/everyday-tools/analytics.md">Incident Analytics</a></td></tr><tr><td><strong>Set up the workspace</strong></td><td>Invite members, connect Slack, and shape your response workflow.</td><td><a href="/settings/organization.md">Organization</a></td></tr></tbody></table>

## A typical day

{% stepper %}
{% step %}

## Check the home dashboard

After you sign in, the home page shows ongoing work, tasks assigned to you, and items that still need a follow-up.
{% endstep %}

{% step %}

## Open or create an incident

If the incident has already been declared, open it from **Incidents**. If the issue is still being discussed in Slack, mention Incident Lake in that conversation to start an incident.
{% endstep %}

{% step %}

## Keep the record current

Update the summary, tasks, timeline, and status as you work. Chat, Analytics, and responders who join later all rely on this record.
{% endstep %}

{% step %}

## Close the loop

Mark the incident resolved, finish remaining tasks, and publish a postmortem when you are ready. Approved knowledge from past reports gives you a head start the next time a similar incident happens.
{% endstep %}
{% endstepper %}

## Looking for everything at once?

To see every feature in one place, open the [Feature list](/getting-started/features.md). It groups features the same way as the sidebar and briefly explains what each one lets you do.

## Need a person?

If the product does not look the way this help describes it, or you need help with your organization’s account, contact the Incident Lake support team at <support@sigq.co.jp>.