> For the complete documentation index, see [llms.txt](https://help.daak2.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daak2.com/zh-tw/ji-zhang/organization.md).

# 帳本、分類與標籤

這些內容都可以從 **設定**管理。

## 帳本

開啟 **帳本**，可以新增、編輯、排序、封存或刪除帳本。

| 作用       | 說明                    |
| -------- | --------------------- |
| **帳單歸屬** | 記錄帳單時必須選擇帳本           |
| **篩選範圍** | 首頁、統計、預算和資產頁面都可以依帳本篩選 |
| **共享**   | 可以透過 iCloud 邀請其他成員共享  |
| **封存**   | 不再顯示為常用選項，歷史帳單仍會保留    |

{% hint style="info" %}
帳本不會儲存餘額。初始餘額和後續餘額變動都屬於帳戶；帳本只負責分類、篩選和共享帳單。
{% endhint %}

## 分類

開啟 **分類**，先選擇目前帳本，再管理收入和支出分類。

1. 點一下新增，輸入分類名稱並選擇圖示。
2. 需要細分時，在主分類下新增子分類。
3. 拖曳分類，調整新增帳單時的顯示順序。
4. 編輯分類時可以調整名稱、圖示或狀態。

分類屬於帳本，不同帳本可以使用不同的分類結構。

## 標籤

開啟 **標籤**新增或管理標籤。標籤可以跨分類使用，一筆帳單也可以選擇多個標籤。

常見用途包括旅行、裝修、工作費用或特殊活動。統計頁面可以依標籤彙總，搜尋也可以依標籤篩選。

## 封存與刪除

| 操作     | 適用情況         | 對歷史資料的影響  |
| ------ | ------------ | --------- |
| **封存** | 暫時不用，但需要保留歷史 | 保留帳本和歷史帳單 |
| **刪除** | 確定不再保留帳本及其內容 | 刪除帳本及相關帳單 |

{% hint style="danger" %}
刪除帳本及相關帳單，無法復原。執行前需要依確認頁要求輸入數字。
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.daak2.com/zh-tw/ji-zhang/organization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.