Create a Service and select its default Offering
Administrator rights to create Services and Offerings; administrators or the Service primary/secondary owner may update the Service.
A Service identifies a delivered capability and its accountable owners. Its Offerings define specific delivery/support conditions. Start with these records in ITSM Lite or CSM Full before adding technical deployment detail.
Before you start
Agree the capability name, owner and initial support scope. Use different Offerings for real differences in commitments, environment or support team rather than cloning a Service for every server or deployment.
Steps
- Open ExpertHub → Services as an administrator and choose New Service or the available create action.
- Enter a clear name and description, classification and lifecycle stage.
- Assign the owner and optional secondary owner. Set a parent Service if useful for portfolio organisation.
- Save. A new Service may initially have no default Offering and remain incomplete for normal support/routing configuration.
- Open the Service's Service Offerings tab and create an Offering with a meaningful scope and required assigned team.
- Configure its owners, coverage, environment and applicable support commitments, then save.
- Return to the Service, explicitly select this Offering as its default and save. The default must belong to this Service.
- Review the Service/Offering selection in relevant operational workflows and confirm that the intended support context is available.
Expected result
The Service has an accountable identity and a usable default Offering. Additional Offerings can distinguish Production versus Non-Production support, coverage or contractual conditions under the same capability.
Ownership versus assignment
Service owners govern the Service definition. Offering owners govern that Offering's commitment. The Offering's assigned team performs operational support or fulfilment. Team membership does not automatically confer ownership or portfolio-edit rights.
Administrators create and delete Services and Offerings. The corresponding primary/secondary owners can update their records under API permissions. Assigning a basic user as an owner can promote that user's ordinary role to elevated; the current promotion is one-way.
Hierarchy and lifecycle
A parent Service organises the portfolio; it is not automatically a technical dependency or impact relationship. Service lifecycle stage and Offering lifecycle status are separate. Maintain scope deliberately instead of deleting historical identities simply because a deployment changes.
Important behaviour
Service creation does not automatically create or select a default Offering. The Service itself has no universal assignment group or priority-target set: operational team and commitments live on the selected Offering. CSM Full adds configuration context but does not create missing defaults or discover deployments automatically.