> 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/equipme/my-company/employees/self-service-tags.md).
# Self-Service Tags
As soon as you start using self-service more actively, one question comes up pretty quickly. Not every employee should see every service.
In the beginning, this often does not matter. You have a few services, everything is visible, and it works. But as your portfolio grows, the marketplace can become crowded and confusing. More importantly, employees might start seeing services that are simply not relevant to them.
This is exactly where tags come in.
Tags allow you to control what an employee actually sees in the marketplace. They connect employees with specific offers and make sure that everyone only sees what is relevant for them.
You can think of it as a filter that runs in the background. The marketplace itself stays the same, but each employee gets their own view of it.
***
#### How tags work
Tags are used in two places.
On the one hand, you assign tags to offers. This defines what kind of service it is or where it belongs from a self-service perspective.
On the other hand, you assign tags to employees. This defines what they are allowed to see.
The system then simply compares both sides. If an employee has at least one matching tag with an offer, the service becomes visible. If there is no match, the service does not appear in the marketplace at all.
There is no partial visibility or warning. From the employee’s perspective, the service just does not exist.
***
#### Where to assign tags to employees
You assign tags directly in the employee profile.
***
In the profile section, you will find the field for self-service tags. This is where you define which parts of the marketplace the employee should have access to.
It is worth noting that tags only take effect when self-service is enabled for the employee. If self-service is not active, assigned tags will not have any impact on what the employee can see in the marketplace. Depending on your setup, self-service may already be included in a role or enabled manually in the employee’s permissions.
***
#### Assign tags to multiple employees
If you are working with a larger number of employees, you do not have to assign tags individually in each profile. You can also update tags in bulk.
In the employee overview, select multiple employees and use the actions menu to add or remove tags for all of them at once. This makes it much easier to apply or adjust tag structures across teams or departments without going through each profile manually.
***
#### Where to assign tags to offers
Tags are also set on the offer itself, inside the self-service configuration.
***
This is where you define how an offer is categorized from a visibility perspective. The same tags you use here need to be used on the employee side, otherwise they will never match.
***
#### What this means in practice
Once tags are in place, the marketplace becomes much more controlled.
Instead of showing every service to every employee, you can shape the experience based on roles, departments, or use cases. Two employees can open the same marketplace and still see completely different sets of services.
For example, you might have IT-related services and logistics-related services in your system. An employee working in IT will only see IT services, while someone in logistics will only see what is relevant to them.
This keeps the marketplace clean and avoids confusion, especially in larger setups.
***
{% hint style="info" %}
#### Important detail: full marketplace access
If an employee has permission to access the entire marketplace, the tag-based restriction is bypassed.
In that case, all services are visible, regardless of assigned tags.
Outside of that scenario, tags are the main mechanism that controls visibility.
{% endhint %}
***
> #### A simple way to think about it
>
> Self-service gives employees access to the marketplace.
>
> Tags define what that access actually looks like.
>
> Without tags, everything is open. With tags, the marketplace becomes structured and tailored to each user.
---
# 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/equipme/my-company/employees/self-service-tags.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.