Skip to main content

Service Catalog (authoring)

Route: /org/resolve/settings?tab=catalog · Permission: Author and manage the service catalog. AI generation needs Create Service Desk Catalogue with AI.

1. What this tab is​

Where the orderable items are defined. The consumer side — Request a Service — only displays what is authored here.

2. How it spreads​

Figure 1 — Service Catalog authoring.

3. Item field reference​

FieldRequiredNotes
Catalog Section✅The grouping heading. Sections are created separately with a name
Title✅e.g. Standard Developer Laptop
Item Key✅Auto-slugified from the title. Sent to the webhook as catalog_item_type
DescriptionShown on the card and in the drawer
Fulfilment webhook URLEmpty uses the org default
Needs approvalGates fulfilment behind an approver
ActiveOff hides it everywhere
Visible to customersControls external visibility separately from staff

Per-field intake options — Label, key, Type (Text/Email/Text Area/Dropdown/Checkbox), Required, Placeholder, Options, Default, Regex, Min/Max length, Error message — are documented in full on Request a Service.

Item Key is an integration contract

It reaches your webhook as catalog_item_type. Renaming it after anything is wired up breaks the receiving end silently — the request still submits. Treat it as immutable once live.

"Needs approval" changes when a ticket exists

With it on, no ticket is created until approval. The item will not appear in the queue, will have no SLA clock, and will show — in the requester's Ticket column.

4. Generate with AI​

Generate Service Catalog proposes sections, items and intake fields. Review before saving.

5. Don't confuse this with…​

These twoDiffer by
This tab vs Request a ServiceAuthoring vs ordering. Both called "the service catalog"
Catalog intake fields vs Custom FieldsOne item's order form vs every ticket
Catalog sections vs Ticket ClassificationGrouping orderables vs grouping tickets
Service request approval vs CAB approvalCatalog items vs changes

6. Troubleshooting​

SymptomCause
Item not visible to customersVisible to customers off, or Active off
Webhook fires, request never closes2xx acknowledges only; completion is reported separately
Integration stopped recognising an itemThe Item Key was renamed