How to Configure Service Catalogs in ServiceDesk Plus
Quick Summary
A service catalog turns a help desk from a reactive ticket inbox into a structured storefront where employees can browse and request exactly what they need. In ServiceDesk Plus, this means organizing services into categories, building request forms for each one, and attaching the approvals, SLAs, and tasks that make fulfillment predictable. This guide walks through how to configure a service catalog from the ground up.
Since a service catalog draws on many of the platform’s other capabilities, it helps to understand the system it belongs to first. ManageEngine ServiceDesk Plus – ITSM Software provides the ticketing, workflow, and CMDB tools that a service catalog relies on, and it offers useful context before working through the configuration steps covered in this article. With that framing in place, let’s look at what a service catalog actually is and how to build one.
What Is a Service Catalog, and Why Does It Matter?
What does a service catalog actually do?
A service catalog lists the various products and services available to end users, letting employees browse available offerings and submit requests directly rather than emailing IT and hoping for the best. Once submitted, these requests get routed to and processed by help desk technicians, which keeps request handling consistent regardless of who happens to submit it or when. This structured approach also gives IT teams a clearer picture of demand over time, since requests arrive through a defined set of templates rather than as unstructured, free-text emails that require manual interpretation before work can even begin.
How does a service catalog differ from a service portfolio?
This distinction matters more than it might first appear. A service catalog lists only live, currently available IT services, while a service portfolio is a broader concept that also includes services still in the pipeline or already retired. ServiceDesk Plus specifically manages the catalog side of this equation, giving end users a clean, current view of what’s actually available to request right now.
What are the two types of services typically found in a catalog?
Services generally fall into two categories based on who they’re built for. Customer-facing services, often labeled Business Services, are the offerings employees interact with directly, such as requesting new equipment. Supporting services, labeled IT Services, keep the underlying complexity hidden from the business side while still enabling those customer-facing requests to function. ServiceDesk Plus organizes catalog content around this same Business and IT distinction from the start.
How Do You Structure a Service Catalog Before Adding Content?
What is the top-level organization of a catalog?
The catalog organizes all services and products into categories, with two main high-level groups: IT and Business. Underneath these top-level categories, administrators add more specific service categories and templates tailored to actual organizational needs, giving the catalog a logical hierarchy rather than one flat, unsorted list.
Can you give a concrete example of this hierarchy?
A common example makes the structure clearer. Under the high-level IT category, an administrator might add a Hardware service category, and underneath that, individual service request templates for items like a new computer, a telephone, or a wireless mouse. This layered structure means an employee browsing for hardware naturally finds all related request options grouped together, rather than searching through an undifferentiated list of every service the organization offers. The same layered logic applies equally well to Business Services, where a category like Facilities might sit above templates for booking a meeting room, requesting building access, or reporting a maintenance issue.
How does the CMDB connect to service categories?
This connection is easy to overlook but important to understand. The system lists every service category you add to the catalog as a Configuration Item in the Configuration Management Database. The Configuration Item types you set up under CMDB also determine the default fields that appear in the Service Category form. Consequently, changes made to Configuration Item types directly affect what fields are available when building out service categories.
How Do You Configure Service Categories?
Where do you go to manage service categories?
Service category management happens from a dedicated section of the Admin page, reached by navigating to Admin > Service Catalog > Service Categories. This page displays a complete list view covering both IT Services and Business Services, giving administrators a single place to review the entire catalog structure at a glance.
What are the basic steps to configure a service category?
Setting up a new service category follows a straightforward sequence:
- Navigate to Admin > Service Catalog > Service Categories.
- Select the category type you’re configuring, such as IT or Business.
- Fill out the required category details, including a name and description.
- Set an icon for the category to make it visually distinct in the catalog view.
- Save the category.
What happens if you try to delete a service category still in use?
ServiceDesk Plus prevents accidental disruption here rather than allowing an outright deletion. If a service category is currently being used by a module, it appears greyed out instead of being deletable, and a greyed-out category won’t be listed in the visible service catalog. To bring a greyed-out category back into active use, an administrator edits it and deselects the “Service not for further usage” checkbox rather than deleting and recreating it from scratch.
How Do You Add Individual Service Items?
What are service items, and how do they relate to categories?
Service items represent the specific, requestable offerings within a category, covering day-to-day IT services like installation, relocation, internet access, email access, virus protection, and hardware or software provisioning. These items are classified and grouped under their parent service categories, and that grouping is what employees actually see and browse from the self-service home page.
What are the steps to add a new service item?
Adding a service item builds directly on top of an existing category structure:
- Navigate to Admin > Service Catalog > Service Catalog.
- Hover over the category you want to add a service under.
- Click Add Service.
- Fill in the header details, including the service name and description.
- Configure the drag-and-drop request template to match what end users need to provide.
- Save the configuration, or select Save and Configure Requester to continue building the requester-facing form.
What additional elements can be attached to a service item?
A service item isn’t limited to a simple request form. The table below summarizes the main configurable elements available for each service.
| Configurable Element | What It Controls |
|---|---|
| Resource Info | Resources required to fulfill the service, if applicable |
| Approvals | Multiple approval stages before a request proceeds |
| Service Level Agreement | Fulfillment timelines specific to that service |
| Tasks | Individual steps technicians complete during fulfillment |
Can you edit or delete an existing service item?
Yes, and both actions follow a similarly simple path. To edit an item, click the icon beside its parent service category to expand the list, hover over the item, and select the edit icon to open its form. To delete one, follow the same navigation, but select the delete icon instead and confirm the action in the dialog that appears, which permanently removes that item from the catalog.
How Do Incidents and Service Requests Differ Within the Catalog?
What’s the practical distinction between the two?
ServiceDesk Plus uses “Request” as an umbrella term covering both Incidents and Service Requests, but they represent different situations. An Incident denotes an unplanned interruption or reduction in the quality of an IT service, such as slow system response time or an inability to log into a CRM tool. A Service Request, by contrast, covers a planned ask for information, a standard change, or access to a service, such as needing a new laptop or requesting a password reset.
Can Service Requests be submitted through email like incidents often are?
No, this is a meaningful limitation worth knowing upfront. Service Requests cannot be created through email; instead, employees need to log into the Self-Service Portal, browse the available catalog, and submit their request directly through that interface. This restriction reinforces the catalog’s purpose as a structured, guided request experience rather than an open-ended inbox.
Can Service Requests be linked to other requests or converted into different record types?
To some extent, yes. You can link two or more Service Requests using the Link Requests feature. From the parent record, you can also copy notes, worklogs, and resolutions to all linked requests. You can create a Change directly from a Service Request as well. However, the system does not currently support converting a Service Request into a Problem or merging two Service Requests.
Conclusions
Configuring a service catalog in ServiceDesk Plus means building a clear hierarchy of categories and services, then attaching the approvals, SLAs, and tasks that make each request predictable to fulfill. Understanding how service categories connect to the CMDB, how greyed-out categories protect against accidental disruption, and how Service Requests differ from Incidents all contribute to a catalog that actually serves employees well rather than just existing as an administrative afterthought. For a broader look at how the service catalog connects to the platform’s wider ticketing, workflow, and asset management features, ManageEngine ServiceDesk Plus – ITSM Software remains a valuable resource alongside the configuration steps covered in this guide.
Frequently Asked Questions
If a service category is still being used by another module, ServiceDesk Plus prevents its deletion and instead greys it out from active use. To fully retire a category, confirm it isn’t referenced elsewhere first, or use the “Service not for further usage” option to hide it from the catalog without permanently removing the underlying configuration.
No, approval stages are configurable per service item rather than mandatory across the board. Some services may move straight to fulfillment, while others, particularly those involving cost or access changes, often benefit from one or more configured approval stages before a technician begins work.
