> 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/sign-in.md).

# Sign in

How to open Incident Lake, sign in, and recover access.

Incident Lake is a web application. Use a current browser and go to <https://incidentlake.sigq.io>.

## Ways to sign in

Your organization chooses how people sign in. You may see one or more of these options:

* **Work email and password**
* **Continue with Google**
* **SSO** — enter your work email and Incident Lake routes you to your company’s sign-in page

{% hint style="info" %}
If SSO is turned on for your company domain, use that path when it appears. If SSO is not set up for your domain, use email and password or Google instead.
{% endhint %}

## First visit after an invitation

Most people join because an administrator sent an invite.

{% stepper %}
{% step %}

## Open the invitation email

Use the link in the message. It takes you to an invitation page that shows the organization name and the role you were offered.
{% endstep %}

{% step %}

## Sign in or create an account

If you already have an Incident Lake account, sign in with that same email. If you do not, create an account, then accept the invitation.
{% endstep %}

{% step %}

## Accept the invitation

Confirm you want to join. You land in that organization after you accept.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Accept the invite with the email address it was sent to. If you are signed in as someone else, switch accounts before you accept.
{% endhint %}

## Password reset

On the sign-in page, choose **Forgot your password?** and enter your email. Check your inbox for the reset message. If it does not arrive, also check junk mail, then ask an administrator to confirm the address on your member record.

## Email verification

Some features stay limited until you verify your email. If the home page asks you to verify, open the message we sent and follow the link. You can request a new verification message from that same screen.

## Terms of Service

A new organization may ask an **Administrator** to accept the Terms of Service before the workspace can be used. Members and viewers wait until an admin completes that step.

## If you cannot get in

* Confirm you are opening <https://incidentlake.sigq.io>
* Try a private browser window to rule out a saved session
* Ask an admin whether your account is still a member and which sign-in method the organization expects
* Write to <support@sigq.co.jp> if you need the email on the account changed — users cannot change their own email address


---

# 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/sign-in.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.