> 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-cn/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-cn/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.