> 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 is the place your team uses to see what is happening, decide what to do next, and keep a record of how you responded.

This site is written for people who work in the product every day — responders, commanders, and organization admins. You do not need a technical background to follow these pages.

{% hint style="info" %}
Open Incident Lake at <https://incidentlake.sigq.io>. If you cannot sign in, ask an administrator in your organization or write to <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>Get started</strong></td><td>Sign in, find the sidebar, and understand who can do what.</td><td><a href="/getting-started/sign-in.md">Sign in</a></td></tr><tr><td><strong>Run an incident</strong></td><td>Open, 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>Use Chat and Knowledge so past responses are easy to reuse.</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 people, 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

Use **Incidents** when something is already declared, or start from Slack by mentioning Incident Lake in the conversation where the issue is being discussed.
{% endstep %}

{% step %}

## Keep the record current

Update the summary, tasks, timeline, and status as you work. That record is what Chat, Analytics, and later responders will rely on.
{% 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 helps the next similar case start faster.
{% endstep %}
{% endstepper %}

## Need a person?

If something in the product does not match what you see here, or you need help with your organization’s account, contact <support@sigq.co.jp>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.incidentlake.com/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.