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

# 登录并了解界面

## 在你开始之前

询问您的管理员申请地址,您应该访问的业务以及个人账户的身份证. 在本指南中没有共享的演示密码. 用你的业务分配给你的账户.

## 登录

1. 打开申请地址. 如果您在公共网站上,请使用登录链接.
2. 选择你要工作的酒店.
3. 选择自己的员工卡.
4. 输入密码,然后按登录按键.
5. 在下面的屏幕上查看酒店和酒店分支的名称. 如果您在多个酒店分公司工作,请在创建记录之前选择正确的分公司.

如果您的员工卡缺失,请先查看所选的业务. 如果它仍然缺失,请请你的经理查看你的账户和酒店分支机构. 不要使用其他员工的卡来绕过密码错误.

## 接口的部分

* 左侧菜单打开房间状态表,逗留日历,预订和其他工作页面.
* 酒店和酒店分支选择器确定您的工作业务背景.
* 页面标题包含搜索,过 ?? 和操作. 扩大一个崩塌的头条,以揭示隐藏的控制.
* 右上方的通知报告成功保存或错误. 在表格内表示缺失表格的字段.
* 在小屏幕上,打开移动导航菜单,访问相同的工作页面.

保存后,请检查成功通知和更新列表. 如果出现网络错误,请在再次提交相同操作之前检查是否创建了记录.

接下来: [第一个日设置](/zh-cn/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-cn/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.