> 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/zh-tw/ru-men/login.md).

# 登入並瞭解介面

## 在你開始之前

詢問您的管理員申請地址,您應該訪問的業務以及個人賬戶的身份證. 在本指南中沒有共享的演示密碼. 用你的業務分配給你的賬戶.

## 登入

1. 開啟申請地址. 如果您在公共網站上,請使用登入連結.
2. 選擇你要工作的酒店.
3. 選擇自己的員工卡.
4. 輸入密碼,然後按登入按鍵.
5. 在下面的螢幕上檢視酒店和酒店分支的名稱. 如果您在多個酒店分公司工作,請在建立記錄之前選擇正確的分公司.

如果您的員工卡缺失,請先檢視所選的業務. 如果它仍然缺失,請請你的經理檢視你的賬戶和酒店分支機構. 不要使用其他員工的卡來繞過密碼錯誤.

## 介面的部分

* 左側選單開啟房間狀態表,逗留日曆,預訂和其他工作頁面.
* 酒店和酒店分支選擇器確定您的工作業務背景.
* 頁面標題包含搜尋,過 ?? 和操作. 擴大一個崩塌的頭條,以揭示隱藏的控制.
* 右上方的通知報告成功儲存或錯誤. 在表格內表示缺失表格的欄位.
* 在小螢幕上,開啟移動導航選單,訪問相同的工作頁面.

儲存後,請檢查成功通知和更新列表. 如果出現網路錯誤,請在再次提交相同操作之前檢查是否建立了記錄.

接下來: [第一個日設定](/zh-tw/ru-men/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/zh-tw/ru-men/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.