> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/integrations/chat/slack/onboard-employees.md).

# Onboard Employees

Onboard new employees into your customer channels

Bulk add an employee to a set of enabled channels. This is useful when someone joins your team, or when someone leaves or is out of office and their accounts need new coverage.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/onboard-employee.png" alt=""><figcaption></figcaption></figure>

1. Go to **Settings > Users**.
2. Open the **…** menu and click **Bulk add to channels**.
3. Under **Users to add**, pick one or more people from your Slack workspace.
4. Under **Accounts**, choose which channels to add them to:
   * **All external channels**: every customer external channel
   * **Channels based on filters**: channels of accounts matching filters such as account tags or owner
   * **Specific channels**: channels you pick
5. Check the **Channels preview** and click **Add**.

{% hint style="info" %}
Only Pylon admins can bulk add users to Slack channels. The option appears once Slack is connected.
{% endhint %}


---

# 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.usepylon.com/pylon-docs/integrations/chat/slack/onboard-employees.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.