> 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/documentation/portfolio-management/service-portfolio/the-context-menu.md).
# The Context Menu
When you create a service in equipme, one of the most important decisions you make is the **context**.
The context defines **where a service lives** and **how it can be assigned later on**.\
You are not changing what the service is. You are deciding **to whom or to what it belongs**.
This choice directly affects how flexible the service will be over time. Especially when employees change, devices are replaced, or services are reused, the right context keeps everything structured and easy to manage.
In this course, we walk through all available context options and explain when and why to use them.
***
### Employee and Location
The **Employee and Location** context is the most commonly used setup and in most cases the recommended one.
By enabling both options, you allow a service to be assigned either to an employee or to a location. This mirrors how assets behave in real life and gives you maximum flexibility over the entire lifecycle of a service.
The toggle controls whether assigning the service to an employee is mandatory or optional.\
Keeping both **Employee** and **Location** active is usually the best choice.
Here is why.
A typical example is hardware such as a notebook. While an employee is active, the notebook is assigned directly to that person. When the employee leaves the company, the same notebook does not disappear. Instead, it can be reassigned to a location, for example a warehouse or storage. Later on, it can be assigned again to a new employee without recreating the service.
If only Employee is active, the service always needs a person attached to it.\
If only Location is active, you lose the clarity of personal assignment.
Keeping both options enabled allows services to move naturally between people and places, without breaking the structure or creating duplicates.
***
### Workplace as a Service
**Workplace as a Service** is mainly used for software related services.
Instead of assigning software directly to a device or an employee, the software is grouped under a workplace context. This creates a logical bundle that represents a complete working environment.
This becomes especially useful when a device needs to be replaced. Because all software is already collected under the workplace, you can immediately see what needs to be installed on the new device. The setup stays consistent even though the hardware changes.
This context helps you keep software assignments clean and avoids rebuilding configurations from scratch.
***
### Cloud
The **Cloud** context is used for services that exist independently of employees and locations.
Typical examples are virtual machines or cloud based resources. These services are not tied to physical assets or specific users but still need to be managed as part of your portfolio.
By using the Cloud context, these services are handled as standalone entities while remaining fully visible and manageable within equipme.
***
### Global
The **Global** context is used for company wide services.
These services are assigned once to the entire organization and are added to the inventory on a global level. They are not linked to individual employees or locations.
This is useful for systems or licenses that apply to the whole company, such as HR software or organization wide tools that do not require personal assignment.
***
### Why the context matters
Choosing the right context upfront saves work later.
It allows services to be reassigned, reused, and scaled without restructuring your setup. The context menu is not about limiting options. It is about choosing the **cleanest and most realistic structure** for how a service should exist inside equipme.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://hub.equipme.io/documentation/portfolio-management/service-portfolio/the-context-menu.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.