> For the complete documentation index, see [llms.txt](https://quteng.gitbook.io/ke-hu-wen-da-ji/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quteng.gitbook.io/ke-hu-wen-da-ji/ju-wei-guan-li/ru-he-shang-chuan-ju-wei.md). # 如何上傳車位？ **路徑：** 建案管理 > 車位設定 > 車位管理 **操作方式：** 1. 前往 **車位管理** 頁面：選擇建案後，進入 **建案管理 > 車位設定 > 車位管理**。

2. 點擊畫面右上綠色 **新增車位+** 按鈕，畫面會顯示新增彈窗。

3. 新增單位詳細： 1. **批次新增**：可以一次新增一個以上的車位，例如，B1整層的所有30個車位。

2. **單個車位**：新增單個車位，例如，B1的第31號車位。

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://quteng.gitbook.io/ke-hu-wen-da-ji/ju-wei-guan-li/ru-he-shang-chuan-ju-wei.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.