You are here: Advanced > Use case scenarios - customizing with business rules > Delegating permissions for service catalog creation and editing

Delegating permissions for service catalog creation and editing

The following use case scenario demonstrates how a tenant administrator or catalog administrator can delegate the creation and editing of service catalogs to other people.

The service catalog is comprised of three levels:

  • The category level (first level), which contains the top level tiles that a user sees when viewing the home page of the Service Portal.
  • The service (service-definition entity) level (second level), which aggregates all offerings (third level) related to the specific service.

Service definitions are named in this way as the best practice is to aggregate service and support offerings by their affinity to a specific service. For example, a category named Email and collaboration might contain services such as Lotus email or Exchange email, which in turn might include offerings such as “Create a new Public distribution list”, “Change public distribution list owner”, and “Increase mailbox quota”.

Separating catalog offerings into services enables service owners to maintain their respective catalog areas, that is, to have the tools and permissions to create and update offerings related to the services they own. A service owner is the organizational persona in charge of maintaining a service, providing support for that service, and fulfilling service requests against this service. It would stand to reason that this person would be able to define and edit the service and support offerings related to the service. The service owner should be able to:

  • Define the offerings and how they appear to end users in the Service Portal.
  • Describe the purpose of the offerings and how to use them. The names and descriptions of the offerings are also used for search matching, so the service owner should be able to include keywords in the descriptions that match what end users search for when looking for this offering.
  • Specify the audience for the offerings, that is, which end users would be able to see and request the offering in the Service Portal (for example, whether or not the offering is specific to a certain location).
  • Define a task plan for fulfilling the offering. For example, a local IT help desk manager responsible for distribution and maintenance of personal computers and related equipment would be able to define the process for issuing a laptop for a new employee. The tasks may include checking the stock, ordering a new laptop if none is found in stock, installing the company’s OS image on the laptop, and so on.
  • Define a form for the offering.

All of these activities require the person creating and editing the offering to be very familiar with how the service operates.