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

Understanding Service Dependencies (Basis Services)

Not every service in equipme can stand on its own. In many cases, one service depends on another. To make sure everything is set up correctly and nothing important is missing, equipme uses what we call Basis Services.

A Basis Service is like the foundation of a house. Before you can add the upper floors, you first need a solid base. The same applies here: a Basis Service must be active before additional services can be assigned.

Take an example: your company uses mobile device management (MDM). The MDM setup would be created as a Basis Service. Only once this service is in place can employees order mobile devices that are managed through it. Without the Basis Service, the system simply doesn’t allow the additional order.

This logic has two big advantages:

  • It prevents mistakes, because employees can’t accidentally request services that don’t make sense without the foundation.

  • It keeps everything structured, since the relationships between services are clear and transparent.

For you as a manager, Basis Services make the process much easier. You don’t have to constantly double-check whether something is missing or whether the order is valid. The system automatically ensures that only services which fit together are available.

Last updated

Was this helpful?