> For the complete documentation index, see [llms.txt](https://manual.harpe.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.harpe.io/start/getting-started/set-up-your-isms/add-employees.md).
# Add employees
Adding employees on Harpe is easy, and the first important step in setting up your ISMS. We recommend adding all employees before doing anything else to ensure a smooth experience.
1. Go to your organisation's Harpe page.
2. On the left hand side, there is a sidebar giving you a list of things you can manage on Harpe. Click `People` to manage your employees list
3. You should see a page looking similar to this - Your user will already be populated. To add another employee click the `Add Person` button.
Harpe's People page
4. From here you can add an employee, fill in the required details and when you are done you can click the `Add` button. If you wish to cancel making an employee, click the `X` button in the top-right corner of the window. Here is what the `Add Person` panel looks like:
Harpe's Add Person form
5. When you have filled in the information and saved the changes, your employee will be added. Repeat this process until you have successfully added all employees!
---
# 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://manual.harpe.io/start/getting-started/set-up-your-isms/add-employees.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.
