> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/classes/admin/employees/add-an-employee.md). # Add an employee {% @arcade/embed url="" flowId="q9FZQceT8qIp69qP9H0S" %} Creating someone by hand is the exception rather than the rule. It is what you do for a working student, a contractor, or anyone who is not in your HR system. In most portals employees arrive through [HR Sync](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/settings/integrations/hr-sync-overview), including their location, department and supervisor. Name, email and location are the required ones, and the location is the field worth getting right. It decides where deliveries go and which colleagues this person is grouped with. Department, supervisor and cost center can follow later. The invitation is a separate decision. Sending it gives the person access to the portal, so it makes sense for anyone who will request things themselves. Someone who only receives equipment does not need an account at all. A home office address entered here is stored once and reused every time something is delivered to that person. In a single order you would notice a wrong address. In a rollout for 300 people you would not. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/CVuLmqt5Ookxpnb8Ks7K" %} [Employees](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/employees) {% endcontent-ref %} ### Next Not everyone should see everything: [Self-service tags](/classes/admin/employees/self-service-tags.md). --- # 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://hub.equipme.io/classes/admin/employees/add-an-employee.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.