Creating Services

Services are the foundation of how work gets done in Nembl. A service describes something your team or company offers, such as "IT Support," "Employee Onboarding," or "Design Review." When someone needs that service, they submit a request through the service catalog.

What Is a Service?

Think of a service as a menu item. Just as a restaurant lists what it serves, your service catalog lists what your teams can do for others. Each service has:

• A name and description that tell people what it is
• One or more service offerings (specific things people can request)
• Forms that collect the information needed to get started
• An optional workflow that automates how requests are processed

Creating a New Service

1. Go to Admin > Services in the sidebar.
2. Click New Service.
3. Fill in the following:
   • Name — A clear, descriptive name (for example, "Hardware Requests" or "Marketing Campaign Support").
   • Description — A brief explanation of what the service provides and who it is for.
   • Category — An optional grouping to help people find the service in the catalog.
4. Click Save.

Your service starts in Draft status. It will not appear in the service catalog until you publish it.

Naming Conventions

Good service names are short, specific, and use everyday language. Here are some tips:

• Be specific: "Laptop Repair" is better than "IT Things."
• Use plain language: Avoid jargon or internal acronyms that new team members would not understand.
• Think from the requester's perspective: Name the service based on what someone would search for when they need help.

Examples of good service names:

• Employee Onboarding
• Access Requests
• Bug Reports
• Office Supply Orders
• Travel Approvals

Scoping Your Service

Services can be created at different levels of your company hierarchy, which controls who can see and use them:

• Company level — Available to everyone in the company. Good for shared services like IT or HR.
• Organization level — Available to everyone in a specific department or business unit. Good for department-specific services like "Engineering Code Review."
• Team level — Available only to a specific team. Good for internal team processes.
• User level — Personal services for managing your own work.

To set the scope, choose the appropriate owner when creating the service. The owner determines where the service appears in the catalog and who can submit requests to it.

Managing Existing Services

From the Admin > Services list, you can:

• Edit a service to update its name, description, or settings.
• Archive a service you no longer need. Archived services stop accepting new requests but existing requests continue to completion.
• View metrics to see how many requests a service has received and how they are progressing.

What to Do Next

Once you have created a service, you will want to:

1. Add service offerings — Define the specific types of requests people can submit. See Service Offerings.
2. Create intake forms — Build forms that collect the information you need. See Forms.
3. Link a workflow — Automate how requests are processed. See Workflow Builder.
4. Publish the service — Make it available in the catalog. See Publishing.