Use > Service Catalog > Request Offerings > Working with Request Offerings

Working with Request Offerings

Request offerings are created by service ownerCreates and owns service offerings in the Service Catalog.s and can be used by Self ServiceUsers logging in as Self Service see the Self Service dashboard as their home page. These users can create service requests, report issues, and approve requests. users in the Service Catalog.

After you define a serviceA generally defined framework for actions or items that are provided to an end user. Specific actions, items, response times, and other details are not part of a service definition; those details are defined in service level packages, request offerings, and service level agreements. Instead, a service provides the basis for those detailed definitions. An example of a service is email. After a service is defined, end users do not see or request the service itself. Instead, they use the Service Catalog to view and submit request items, which are features that are based on the service and that you (as a service owner) define and make available to them. Multiple request offerings can be based on the same service., users or requesters do not see the service itself. Instead, they request certain aspects of a service (called request offeringA service item offered by a provider that an end user can request through the Service Catalog. For example, "Request for a new mailbox," and "Quarantine" are request offerings under the Email service.s), which are features of the service being defined and published.

For example, one of the default services is Mobile Communication. However, end users cannot place requests for the Mobile Communications service. Instead, they can select request offerings such as Mobile Phone Request and Mobile Smartphone Request from the Service Catalog. These request offerings are based on the Mobile Communications service, but have different costs, fulfillment workflows, and other aspects of the service.