> 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/yoov-work/recruitment-management/recruitment-setting.md).
# Recruitment Setting
## 1. **Recruitment Process**
* The system has a predefined recruitment process, including Process Management, Stage Management, and Status Management (System Items). The stages preset include New Candidate, Initial Screening Passed, Arrange Interview, Offer Stage, and Official Hiring. When the stage reaches Official Hiring, the candidate's status will change to Pending Onboarding.
* The established system process (system items) cannot be reduced, but administrators can click \[Add] to include custom processes.
### **1.1 Add Process**
* Administrators can also create new processes, stages, and statuses.
* **Operational Steps:**\
① First, add the necessary "Stages."\
② Then add a "Process," designing the process on the available page. The "Process" is associated with "Stages" and supports enabling/disabling "Statuses." Once designed, click Publish.\
③ Each position may have a different recruitment process, so when administrators/HR create a new recruitment position, they can specify which recruitment process to use.
## 2. Recruitment Channels
* Recruitment channel needed to fill in when filling in candidate information. The system has preset some recruitment channels and commonly used recruitment websites, and the administrator can also add new recruitment channels.
* Operation steps: \
① \[Recruitment] > \[Recruitment Setting] > \[Basic Setting] > \[Recruitment Channel] > \[Add Recruitment Channel] \
② Set the channel name, jump website, and remarks. After the jump website is added, click on the recruitment channel to directly open the website. After setting, click "Save"
## 3. Interview Information
### 3.1 Interview Details
* Interview information is used to provide the contact information and interview address displayed in text messages and emails when sending interview notifications to candidates. Administrators can make settings in advance for ease of use.
* Operation steps: \
① \[Recruitment] > \[Recruitment Setting] > \[Interview Information] > \[Add Interview Information] \
② Set the contact person, phone number, and interview address, and click "Save"
### **3.2 Interview Sign-In**
* When candidates arrive, they can first scan the \[Interview Sign-In Code]. Administrators/HR will receive an instant notification, saving time for front desk staff to confirm and notify.
* After the interview sign-in, administrators/HR can view the candidate's check-in time at any time, making the meeting times clearer and more precise.
## 4. Reasons for Elimination/Loss
* After interviewing the candidate, when the interview result is elimination/loss, you need to make a reason selection. The system has preset some reasons, and the administrator can also add new reasons.
* Operation steps: \
① \[Recruitment] > \[Recruitment Setting] > \[Basic Setting] > \[Reason for elimination/loss] > \[Add reason for elimination/loss] \
② Set the reasons for elimination/loss and click "Save"
## 5. Set up Email Templates
* Operation steps: \
\[Recruitment] > \[Recruitment Setting] > \[Edit Email Template]
## 6. Activity Log
* The system can be operated by more than one administrator, and the administrator can search for the change records of all administrators in the operation record. The operation time, administrator name, IP address, operation object, type and specific operations are displayed in detail for easy reference.
* Operation steps: \
\[Recruitment] > \[Activity Log]
---
# 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://docs.coreway.com/yoov-work/recruitment-management/recruitment-setting.md?ask=&goal=
```
`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.