> 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-cn/department-management/department-structure.md).

# 部门架构

## 1. 功能描述 <a href="#id-1-feature-description" id="id-1-feature-description"></a>

* 系统将根据管理员新增的部门，自动产生组织架构，而部门为使用系统的必须设定项目。 \
  注: 系统支援部门层级最多不能超过7级

## 2. 新增部门 <a href="#id-2-add-department" id="id-2-add-department"></a>

* 操作步骤： \
  ［部门管理］>［部门架构］>［部门管理］>［新增部门］
* 新增部门后请输入相应的资料，基于系统设置每个子部门都需要有上级部门，在**设置第一个部门时需要以公司名为上级部门**。&#x20;
* &#x20;而部门负责人可于后期补加或更改（设置部门负责人有助后期设置审批流程）。
* 填写相应资料后请点选「提交」。

<figure><img src="https://content.gitbook.com/content/2rAQKEhs5Y3QzByAJWJc/blobs/Ap5eDbN7fhce7iULbRqb/image.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/2rAQKEhs5Y3QzByAJWJc/blobs/BGtzL2SeYSHgPjKLb2ck/image.png" alt=""><figcaption></figcaption></figure>

## 3. 设置部门负责人 <a href="#id-3-set-department-person-in-charge" id="id-3-set-department-person-in-charge"></a>

* 操作步骤： \
  ［部门管理］>［部门架构］>［部门管理］，找到对应部门名称，点选 「编辑」
* 在「部门详情」 页面，可编辑该部门的相关信息，设置部门负责人，点击 「确定」

<figure><img src="https://content.gitbook.com/content/2rAQKEhs5Y3QzByAJWJc/blobs/0elGFmcvdOhnp468IqBa/image.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/2rAQKEhs5Y3QzByAJWJc/blobs/4RcyVXnS09snUJ0RxKnJ/image.png" alt=""><figcaption></figcaption></figure>

## 4. 生成组织架构图 <a href="#id-4-generate-organization-chart" id="id-4-generate-organization-chart"></a>

* 设置成功后，管理员才能在部门架构中的架构图看到公司架构。 \
  ［部门管理］>［部门架构］>［架构图］

<figure><img src="https://content.gitbook.com/content/2rAQKEhs5Y3QzByAJWJc/blobs/SBYLUL7BDyoxiLFjLAR8/image.png" alt=""><figcaption></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.coreway.com/coreway-hr/zh-cn/department-management/department-structure.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.
