> 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/core-platform/markdown.md).

# Service catalog

Define every service your teams offer, each with its own form, routing rules, SLAs, audience, and analytics. Employees pick a service and Siit applies everything you configured

{% stepper %}
{% step %}

### Overview

The Service Catalog is where you define every service your teams offer to employees—access requests, new equipment, payroll questions, onboarding, and more. Each service comes with its own look and feel, routing rules, SLAs, forms, audience permissions, and analytics. When employees pick a service in Slack/Teams or the portal, Siit applies everything you configured so requests are consistent and fast.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FXvbrb18Ur4XBFDR2RWdn%2FCleanShot%202025-10-17%20at%2017.41.36.png?alt=media&amp;token=6fabb80b-6bd1-4f33-8e9b-981cbf0ea793" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Organize by Category

Categories keep your catalog tidy and power reporting. Use broad groups like:

* IT: Access, Devices, Network, SSO
* People/HR: Onboarding, Offboarding, Payroll
* Finance: Expense, Vendor, Purchasing
* Security and Legal: Data access, Incident, Contract Enable/disable services without deleting them. Services appear alphabetically in the Portal.
  {% endstep %}

{% step %}

### Explore all the core features of

{% endstep %}
{% endstepper %}

{% content-ref url="/pages/VwjsUtBZZ9BnTKXMUmBP" %}
[Service overview](https://docs.siit.io/service-catalog/service-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/eHw1xIQC9i3Eic1JsmCI" %}
[Service Catalog](https://docs.siit.io/service-catalog/service-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/8DMd51bITOwaYi0qFh3V" %}
[Service forms](https://docs.siit.io/service-catalog/service-forms.md)
{% endcontent-ref %}

{% content-ref url="/pages/Ymu6IhE4ymFo9UyahJVl" %}
[SLAs](https://docs.siit.io/service-catalog/slas.md)
{% endcontent-ref %}

{% content-ref url="/pages/F5GNlQwzDAJFhPjZkkQU" %}
[Audience & visibility](https://docs.siit.io/service-catalog/audience-and-visibility.md)
{% endcontent-ref %}

{% content-ref url="/pages/hfsHsN00t65sBwScqd43" %}
[Self service portal](https://docs.siit.io/service-catalog/self-service-portal.md)
{% endcontent-ref %}


---

# 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/core-platform/markdown.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.
