> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/request-management/request-and-service-management-service-catalog.md). # Service catalog Build the services, categories and forms employees request from.


Category and Services Management	Create Categories and Services in Siit so employees pick a category then a service from Slack, Teams or the portal, to route requests and track volume per service	Organize categories and services
Difference between services, categories, and inboxes	Understand how Services, Categories and Inboxes differ and work together in Siit, who sees each one, and how to organize them, with an IT and Finance example	What's the difference between services, categories and inboxes?
Create forms with dynamic fields	Customize the request form employees fill in Slack or Teams: choose visible, optional or mandatory request attributes and add dynamic fields per service	Build service forms with dynamic fields
Leveraging Applications and Equipment fields in requests	Link requests to an Application and an Equipment alongside the Service, and configure services so these fields fill in from manual, form and AI request creation for reporting	Add application and equipment fields to forms

--- # 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://docs.siit.io/guides/request-management/request-and-service-management-service-catalog.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.