> 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.md). # Employees The employee record is where most of your daily work ends up. Everything assigned to a person sits there, so you can book something new, move it, request it back or produce a handover document without leaving the profile. In most portals employees are not created by hand. They arrive through [HR Sync](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/settings/integrations/hr-sync-overview), together with their location, department and supervisor, and stay aligned with your HR or identity system. The status is what makes the process visible to everyone else. Someone can start in Onboarding rather than Active, for example when equipment should wait until their security setup is done, and later move to Offboarding when they leave. That status is also what you filter on when you need a working list. The chapters below cover adding someone manually and deciding what they get to see. ### Read more {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/CVuLmqt5Ookxpnb8Ks7K" %} [Employees](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/employees) {% endcontent-ref %} {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/UTyFPQC2JUdHXr0xMH59" %} [Managing Employee Status in equipme](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/employees/managing-employee-status-in-equipme) {% endcontent-ref %} ### Next Start here: [Add an employee](/classes/admin/employees/add-an-employee.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.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.