> 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/how-equipme-works-day-to-day.md).

# How equipme works day to day

{% @arcade/embed url="<https://app.arcade.software/share/saP3AgMiKh3yt2sqlpK8>" flowId="saP3AgMiKh3yt2sqlpK8" %}

Your job as an admin is not to handle every request. It is to set up structures that hold, so requests, orders and devices move without you touching each one.

Everything in equipme follows the same line. Services come in through the marketplace and approvals. They are managed as inventory, stock and costs. They are used day to day, through onboarding, tickets and offboarding, until they come back or end.

That is also the order of this track. First your structure, because locations, employees and groups decide who can request what and where it is delivered. Then demand and decision. Then execution, stock and money.

Nothing is executed before it is approved, and nothing is approved that has not been prepared. That separation is deliberate and it is what keeps costs predictable as you grow.

You do not need all of it at once. Most portals start with a small catalogue and grow from there.

{% hint style="info" %}
If your portal is not set up yet, start with Portal Quick Setup. That track covers registration, company profile, organisational setup and your first services. This track assumes the portal is running.
{% endhint %}

### Read more

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/OLgnloGys8SrUfwNKSaw" %}
[Role Overview](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/settings/portal-settings/roles-and-rights/role-overview)
{% endcontent-ref %}

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/X3LUfEcujlAUipqAIvfQ" %}
[Ordering in equipme: roles, scope and responsibilities](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/settings/portal-settings/roles-and-rights/ordering-in-equipme-roles-scope-and-responsibilities)
{% endcontent-ref %}

### Next

Start with your structure. The next chapter is [Locations](/classes/admin/locations.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/how-equipme-works-day-to-day.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.