> For the complete documentation index, see [llms.txt](https://help.marcopayroll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.marcopayroll.com/marco-user-guide-x4/2025/marco-platform-structure/customer-portal/manager-guide/people-management/employee-transition/staff-onboarding.md).

# Staff Onboarding

<details>

<summary><strong>Who can use this feature:</strong></summary>

All managers

</details>

The onboarding process in Marco applies to both **newly joined** and **existing staff** being added to the platform. The standard onboarding process includes:

1. **Adding the staff** to Marco
2. **Entering the staff’s information**
3. **Inviting the staff** to create their Marco account

***

### **Step 1: Add Staff to Marco**

As a manager, you can add staff to Marco to start the onboarding process.

📝 **Note:** Adding a staff member to Marco **does not automatically create a user account**. However, once their details are registered, you can send an **invitation** for them to create their Marco account.

#### **To add staff to Marco:**

1. Go to **People**.
2. Select **Add New Staff**.
3. The **Add New Staff** screen appears.
4. Enter the following details:
   * **Name**
   * **Account Email** – This will be used to sign in to Marco.
   * **Country**
   * **Local/Non-Local Status**
   * **Job Title**
   * **Job Start Date**
5. Select the **service type** for the staff.
6. Click **Add Staff**.

✅ **The staff has been added to Marco.** You can now proceed to enter their details.

***

### **Step 2: Add Staff Information**

During onboarding, **both managers and staff** need to provide information. This can be done through:

* **Onboarding forms** (recommended)
* **Manual entry in Marco**

#### **Send Onboarding Forms**

Onboarding forms help collect the necessary details and can be sent **immediately after adding staff** or **at a later time**. There are two types of forms:

* **Staff Form** – Collects **personal** and **bank information** from the staff.
* **Manager Form** – Collects **work details, leave information, and pay details** from the manager.

**Note:** Onboarding forms can only be sent to existing **Marco users**. If the staff does not have a Marco account, they will be prompted to **create one** when filling out the form.

#### **To send an onboarding form later:**

{% tabs %}
{% tab title="Staff" %}

1. Go to **People**.
2. Select a **staff member** > Click **⋮ (three-dot icon)** > **Send Onboarding Form**.
3. The **Send Onboarding Form** screen appears.
4. Click **Send onboarding form to Staff**.
5. A success notification appears. The staff will receive an **email invitation** to fill out the form.
   {% endtab %}

{% tab title="Manager" %}

1. Go to **People**.
2. Select a **staff member** > Click **⋮ (three-dot icon)** > **Send Onboarding Form**.
3. The **Send Onboarding Form** screen appears.
4. Click **Send onboarding form to Manager**.
5. Select the **managers** or **vendors** to send the form to.
   * Multiple recipients can be selected.
6. Click **Send**.
7. A success notification appears. The manager will receive an **email invitation** to fill out the form.
   {% endtab %}
   {% endtabs %}

✅ **The onboarding process is now complete!**


---

# 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.marcopayroll.com/marco-user-guide-x4/2025/marco-platform-structure/customer-portal/manager-guide/people-management/employee-transition/staff-onboarding.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.