> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/zh-hk/faq/employee-login/why-create-company-team-page-shows-after-employee-login.md).
# \[員工登入] 員工登入後，為什麼會出現創建公司／團隊的頁面？
登入後出現創建公司／團隊的頁面，這意味員工已完成註冊流程，但公司未能成功綁定員工的帳戶，以致未能進入公司頁面。
如出現此情況，請根據以下流程進行檢查：
1\. 請管理員在後台員工管理＞員工列表中尋找相關員工，查看員工的綁定資訊是否與員工登入資訊一致。
2\. 如已檢查以上資訊正確，請嘗試在後台員工管理＞員工列表中尋找相關員工，點選右方＂更改綁定＂，重新套用員工的綁定資訊。
---
# 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.coreway.com/coreway-hr/zh-hk/faq/employee-login/why-create-company-team-page-shows-after-employee-login.md?ask=&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.