> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/groups-users-and-permissions/sub-organizations.md).

# 子组织

{% embed url="<https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/sub_organizations/v1/en.mp4>" %}

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-3fae4d0f0ad0bfe5567a20906333272497d41c21%2Fsub_organizations.png?alt=media" alt="子组织"><figcaption><p>子组织页面</p></figcaption></figure>

子组织可帮助您在 DocBits 中创建层级结构，以便跨不同部门、团队或实体管理文档、用户和工作流。

## 主要优势

* **结构化组织**：按部门、地点或业务部门对用户和文档进行分组。
* **细粒度权限**：控制哪些用户可以访问各子组织中的文档。
* **独立工作流**：每个子组织都可以拥有自己的文档处理规则和配置。
* **报告**：按子组织生成报告和分析数据。

## 子组织列表

此表显示所有现有子组织，包含：

| 列      | 描述               |
| ------ | ---------------- |
| **名称** | 子组织的名称。          |
| **描述** | 对子组织用途的简要说明。     |
| **操作** | 提供编辑或删除子组织选项的菜单。 |

使用 **Search** 搜索栏可按名称快速查找子组织。

## 创建新子组织

1. 点击右上角的 **+ New** 按钮。
2. 输入 **Name**，并可选填 **Description**。
3. 点击 **Save** 创建子组织。

## 显示跨组织选项

启用此选项（使用页面顶部的切换开关）后，用户可以在一个合并视图中查看所有子组织的文档，而不再局限于单个子组织的文档。

### 如何使用跨子组织视图 <a href="#cross-sub-organisations-access" id="cross-sub-organisations-access"></a>

1. 前往 **Dashboard**。
2. 在右上角的子组织切换器中选择 **Cross**。
3. 页面重新加载后，会显示所有子组织的文档。
4. 如需返回单个子组织视图，请取消选择 **Cross** 选项。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-c2ef076953864af93f438cbc8df23aa25ce9dccc%2Fcross_org_switcher.png?alt=media" alt="跨子组织切换器"><figcaption><p>在右上角的组织切换器中选择 Cross</p></figcaption></figure>

这对于需要集中查看组织内所有文档的管理员很有用。


---

# 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.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/groups-users-and-permissions/sub-organizations.md?ask=<question>&goal=<user_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.