> 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/getting-started/navigation.md).

# Find your way around

How the sidebar, home dashboard, and organization switcher work.

After you sign in, the left sidebar is how you move around Incident Lake.

## Sidebar

| Item                   | What it is for                                                                |
| ---------------------- | ----------------------------------------------------------------------------- |
| **Home**               | A snapshot of open work, tasks assigned to you, and items that need attention |
| **Chat**               | Conversations with the AI assistant, optionally tied to an incident           |
| **Knowledge**          | Playbooks and notes the assistant and your team can reuse                     |
| **Incidents**          | The full incident list and each incident’s detail page                        |
| **Incident Analytics** | Trends, response times, and recurring patterns                                |
| **Status**             | A live view of active incidents and recent activity                           |
| **Report Templates**   | Reference templates for filings required by law                               |
| **Management**         | CMDB, Risk Map, stakeholders, and notification contacts                       |
| **Settings**           | Your profile, the organization, members, workflow, integrations, and security |

On a narrow screen, open the sidebar from the menu control at the top of the page.

## Home dashboard

Home is the first place to look at the start of a shift. It typically includes:

* Counts and lists of **ongoing** and **stalled** incidents
* Tasks assigned to you
* Follow-ups such as a postmortem that is still outstanding
* A short trend of recent incident volume

You can filter the dashboard (status, severity, category, tags, and time range) and save a view you use often.

If your organization is new, Home may also show a short setup checklist until the basics are in place.

## Switch organization

If you belong to more than one organization, use the organization name near the top of the sidebar to switch. Incidents, knowledge, and settings always belong to the organization you have selected.

## Language

Incident Lake can be used in English or Japanese. Change the language in **Settings → User**. Many pages can also be translated in place when you need to read a record in another language.


---

# 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/getting-started/navigation.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.