> 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/what-employees-see-in-the-marketplace.md).

# What employees see in the marketplace

{% hint style="info" %}
Walkthrough goes here.
{% endhint %}

Three separate things decide what an employee finds in the marketplace, and they stack.

Activating a product makes it visible to everyone with self service. Tags do the opposite: instead of activating, you tag a product and give the tag to individual people or to a group, so premium devices stay with the people who should have them.

On top of that sits a permission that opens the entire catalogue regardless of what is activated. Useful for IT staff, surprising if you forget it is switched on.

Prices are separate again. You can hide prices and costs for a person without changing what they can request.

Country specific articles are filtered in the catalogue, so an employee only sees what can be delivered to their country. Existing stock is not filtered as strictly, which is why a device already sitting in a German warehouse can still be handed out there.

### Read more

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/K3WXhG9RWzhErvdaLqTn" %}
[Marketplace](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/main-menu/marketplace)
{% endcontent-ref %}

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/FIGOb2Dk7Tw29cB0CAJe" %}
[Self-Service Tags](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/employees/self-service-tags)
{% endcontent-ref %}

### Next

With the catalogue sorted out, you can start handing things out: [Assign services centrally](/classes/admin/assign-services-centrally.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/what-employees-see-in-the-marketplace.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.