For the complete documentation index, see llms.txt. This page is also available as Markdown.

Groups

Groups in equipme are a way to organise people so that the system understands how your organisation is arranged. They can represent departments, teams or cost areas, but they do not need to reflect your full company structure. The idea is simply to group people who work together or share responsibilities, so that actions in the platform can follow that logic.

Groups also give context to tasks that are not visible at first glance. When employees request items, when something needs approval, or when a new person joins a team, the system looks at groups to understand who is involved and what should happen next.

How decisions travel through the organisation

Different organisations handle decisions differently. Sometimes a manager signs off on everything, sometimes approval depends on budget, and sometimes a team makes decisions collectively.

Groups provide a way for equipme to follow those patterns. When a request enters the system, it does not need to be pushed around manually. The platform uses the group structure to identify who should respond to it.

This makes approval processes more predictable, not because they are automated, but because the system knows where to send the decision.

Routine work when people join

Onboarding usually repeats the same steps: a new person arrives, needs devices, software, access, and maybe licences. Without structure, every onboarding starts from scratch and depends on someone remembering the process.

If a group in equipme has default resources assigned to it, new employees automatically receive what that group needs to work. No one needs to maintain a checklist or explain the process every time.

This turns onboarding from a manual routine into something the system quietly manages in the background. Learn more


Groups in equipme help translate your organisation into something the system can work with. They are not there to enforce rules, but to support everyday work by giving context to decisions, onboarding and resource use.

They do not need to be complex. If they reflect how people actually work together, the platform can handle a large part of the operational detail on its own.

Last updated

Was this helpful?