> 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/employees/self-service-tags.md). # Self-service tags {% @arcade/embed url="" flowId="Rje6Rf1NJmPMntmkyEXc" %} A tag on its own does nothing. It works as a pair: the tag sits on the service, and the same tag sits on the person or the group. Only where both match does the service appear in that person's marketplace. That is what makes tags the quiet alternative to activating everything. Activation opens a service to everyone with self service. A tag keeps it closed and hands out access individually, which is how premium phones stay with field sales and design software with the design team. You can tag the person directly, as in the walkthrough, or tag a group and let membership do the work. The group route is the one that survives staff changes: someone joining field sales inherits what field sales can see, and nobody has to remember to set it. Tags are also the fastest way to answer the question you will get most often, which is why a colleague cannot find something in the marketplace. Either the service is not activated, or it is tagged and the person is not. ### Read more {% 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 people and their access in place: [Roles and permissions](/classes/admin/roles-and-permissions.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/employees/self-service-tags.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.