> 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/readme.md). # Welcome These classes are short, practical lessons on running equipme. Each one shows a task in a walkthrough you can click through, explains the parts you cannot see on screen, and links to the documentation when you want the full detail. Where you start depends on where you are. ### Setting the portal up If your organisation is new to equipme, begin here. Portal Quick Setup covers registration, your company profile, your organisational structure and your first services. Work through it once, and the platform is ready for everyone else. ### Working in it day to day Once the portal is running, pick the track that matches your job. Requesting what you need, tracking your own equipment, returning it when you are done. Approving what your team asks for and keeping an eye on their equipment and costs. The full picture: locations, employees, roles, your service portfolio, approvals, inventory, warehouse and offboarding. The chapters build on each other, so reading them in order works like a course. Jumping straight to the one you need works too. ### How to use them Every chapter stands on its own, so you can come back to a single topic later without repeating the rest. At the end of each one, Next points to the chapter that follows, which is the quickest way through a track the first time round. --- # 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/readme.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.