> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/en/getting-started/login.md).

# Sign in and explore the interface

## Before you begin

Ask your administrator for the application address, the business you should access and your personal account credentials. There is no shared demo password in this guide. Use the account assigned to you by your business.

## Sign in

1. Open the application address. If you are on the public website, use the sign-in link.
2. Select the hotel you will work with.
3. Select your own staff card.
4. Enter your password and press the sign-in button.
5. Check the hotel and property name on the next screen. If you work at multiple properties, select the correct one before creating records.

If your staff card is missing, first check the selected business. If it is still missing, ask your manager to check your account and property access. Do not use another employee's card to bypass a password error.

## Parts of the interface

* The left menu opens the Room Status Board, Stay Calendar, Reservations and other working pages.
* The hotel and property selector identifies the business context for your work.
* The page header contains search, filters and actions. Expand a collapsed header to reveal hidden controls.
* Notifications at the top right report successful saves or errors. Missing form fields are indicated inside the form.
* On small screens, open the mobile navigation menu to access the same working pages.

After saving, check the success notification and the updated list. If a network error appears, check whether the record was created before submitting the same operation again.

Next: [First-day setup](/en/getting-started/first-day.md).


---

# 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://docs.interaktifotel.com/en/getting-started/login.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.