> 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/create-a-company-team/set-company-team-basic-information.md).
# 設置公司／團隊基本訊息
**操作步驟：**
* 在管理後臺點擊右上角個人頭像找到並進入 「用戶中心」（圖1）。
* 在 「用戶中心」左側導航欄找到並點開 「企業設置」→ 「企業信息」，點擊右上角的 「修改」可在此頁面編輯或新增公司基礎資料（圖2）。
* 填妥相關資訊後點擊 「保存」 ，團隊 / 企業資料即即時生效；後續企業資訊如有變更，均可於此處重新編輯修改（圖3）。
* 點擊頁面公司名稱左側的LOGO 圖標，選取本地 LOGO 檔案，即可完成 LOGO 上傳（圖4）。
圖1
圖2
圖3
圖4
---
# 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/create-a-company-team/set-company-team-basic-information.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.
