> For the complete documentation index, see [llms.txt](https://bikecheck.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bikecheck.gitbook.io/guide/getting-started/sign-in.md).

# Sign in

1. Open [bikecheck.io](https://bikecheck.io). You land on the sign-in page.
2. Enter the **Email** and **Password** of your account.
3. Press **Sign in**.

![The sign-in page](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-afec97bcefd40d0da89e9d3fd6d30ee89715d4c4%2Fsign-in.jpg?alt=media)

* **Forgot your password?** Use the **Forgot?** link above the password field. We email you a link to set a new one.
* **No account yet?** Use **Register** under the button.

## Signing out, and staying safe

* Sign out from the navigation: **Log out** sits at the bottom of the menu.
* If you leave BikeCheck idle, it warns you shortly before it signs you out on its own.
* Closing the page does not stop that clock. If you come back more than 20 minutes after you last used BikeCheck, you sign in again.
* Some actions can't be undone — handing a bike to someone else, for example. Before those, BikeCheck asks for your password again, even though you are already signed in.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://bikecheck.gitbook.io/guide/getting-started/sign-in.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.