> 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/dokumentation/self-service/self-service-setup.md). # Setting up the self-service For administrators: enabling the self-service for employees, approving offers, self-service tags, hiding prices, delivery addresses and invitations. For an employee to be able to request a service in the self-service, **two prerequisites** must be met: 1. The **employee** is allowed to use the self-service, **and** 2. the **offer** is approved for the self-service and visible to this employee. ## 1. Enabling the self-service for employees * **Individually:** Employee → **"Permissions"** tab → enable self-service. When creating an employee: "May request services in the marketplace". * **Multiple:** Employee list → select → **"Actions" → "Enable self-service"**. * **Automatically:** In [HR sync](/dokumentation/organization/hr-sync.md) or in the Microsoft Entra enrollment, choose "Enable self-service" for new employees. Self-service is tied to the **"User"** role. ## 2. Approving offers Marketplace → product detail page → **"Self-service activation"** section: * **"Global self-service"**: The offer can be requested in the self-service. * **"Tags"**: Restricts visibility to employees with at least one matching tag. * **"Approve automatically"**: Approved requests are ordered immediately. This only takes effect in the "Automatic approval" mode; it does not skip an approval (see [Configuring approvals](/dokumentation/procurement/approval-settings.md)). ### Self-service tags Tags let you control who sees which offers, e.g. the tag "Sales" for smartphones with a large data volume. * Tags on the **offer**: in the self-service activation. * Tags on the **employee**: "Self-service tags" field in the profile, bulk action "Add tags", import or HR sync. * Tags on **groups** are inherited by all members. * With Microsoft Entra ID, tags can be assigned automatically based on Entra groups (see [Integrations and single sign-on](/dokumentation/settings/integrations-and-sso.md#microsoft-entra-id-enrollment)). **Rule:** If an offer has tags, an employee only sees it if they have at least one of these tags. Without a matching tag, the offer is hidden without notice. The permission **"Access to the entire marketplace"** lifts this restriction for individual people; they then see all offers. ## Hiding prices Whether employees see prices in the self-service is controlled by the **"Show prices and costs"** permission of the "User" role (Settings → "Roles and rights" → "User" → "Permissions"). Set it to "Denied" to hide prices. The permission can also be allowed or denied for an individual employee. "Denied" always takes precedence. ## Home office Whether employees may maintain their home office address themselves is controlled by the **"Manage home office"** permission of the "User" role. ## Delivery addresses **Path:** Settings → "Portal settings" → **"Self-Service Configuration"** → "Delivery address" Define which delivery addresses employees may choose: **"Work location"**, **"Home office"**, **"Custom address"** (at least one). The assignment (e.g. to the location) and the physical delivery address (e.g. home office) are independent of each other. Employees choose the address when requesting, after "Request approval", in the "Delivery address" dialog. Only the options allowed here are shown, and only those the respective offer delivers to. ## Mandatory justification Under [Configuring approvals](/dokumentation/procurement/approval-settings.md), you use "Reason for self-service marketplace orders" to define whether employees justify their request: "No", "Optional" or "Required". With "Optional" and "Required", the "Justification" dialog appears after the delivery address has been chosen. ## Inviting employees Employee list → select → **"Actions" → "Send invitation"**. The email contains a personal link and, if single sign-on is not used, a temporary password. If the company uses single sign-on, you can also simply send employees the [direct SSO link](/dokumentation/getting-started/sign-in-and-registration.md#single-sign-on-with-microsoft). The prerequisite is that their username in equipme matches their Microsoft sign-in (UPN). --- # 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/dokumentation/self-service/self-service-setup.md?ask=&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.