> This page is for Itential Platform On-Prem, version 6 (default).
> For other versions, use one of these documentation indexes:
> - 6 (default): https://docs.itential.com/itential-platform/6/llms.txt
> - 2023.2: https://docs.itential.com/itential-platform/2023-2/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Make a service available

> Publish an automation as a service in Service Requests so that people can request it without using Operations Manager.

A service is a manual trigger on an automation. When you make a service available, people can request your workflow or agent directly from Service Requests.

## Before you begin

You need permission to create automations and triggers in Operations Manager. For more information, see [Access control for automations](/itential-platform/operations-manager/automations#access-control).

## Make a service available

#### Create an automation with a manual trigger

In Operations Manager, create an automation for your workflow or agent. Then add a trigger with the type **Manual**. Enter a name and a description that help people recognize the service. Service Requests shows both in the catalog. If the automation is a workflow, you can assign a JSON Form to collect input. For more information, see [Create a manual trigger](/itential-platform/operations-manager/triggers#create-a-manual-trigger).

#### Set the automation's groups

In the automation, add the read and write groups for the service. To learn how groups affect who sees and manages a service, see [Access control in Service Requests](/itential-platform/service-requests/access-control#which-services-you-can-see).

#### Grant permissions

Grant each person the permissions that Service Requests requires. For more information, see [Permissions required](/itential-platform/service-requests/access-control#permissions-required).

#### Confirm that the service appears

Under **Operate**, open **Service Requests**, and select **+ New Request**. Your trigger appears in Browse Services as a service.

## What appears as a service

Only manual triggers appear as services. Event triggers and API triggers don't appear. For more information, see [Terms and concepts](/itential-platform/service-requests/terms-concepts#key-terms).

## Change or remove a service

Service Requests doesn't edit services. To change a service, edit its trigger in Operations Manager. If you disable the trigger, its schedules are switched off and locked. If you delete the trigger, Service Requests deletes the service and its schedules. For more information, see [Understand how trigger changes affect schedules](/itential-platform/service-requests/manage-schedules#understand-how-trigger-changes-affect-schedules).

## Next steps

* [Access control in Service Requests](/itential-platform/service-requests/access-control)
* [Browse services and submit a request](/itential-platform/service-requests/submit-request)