> 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/department-management/add-new-position.md).
# Add New Position
## 1. Function Description
* In position management, administrators can individually add all existing positions in the company to manage employees in each department. However, there is another way to add new positions in batches. Please refer to 4.1.2 Method of batch importing new employees.
## 2. Add New Position
* If you want to add individual employees, you need to add a position first, otherwise you will not be able to select the appropriate position when adding employees.
* Operation steps: \
\[Department Management] > \[Position Management] > \[Position Management] > \[Add Position]
* After entering the corresponding information, click "Save". \
Note: Position name is required
* Another way to add department / position would be at the time when you add an employee, there is a "+" button on the side of department / position for administrator to add a department / position in case it was not created yet.
---
# 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/department-management/add-new-position.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.
