> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/patchworks-services/working-with-services/the-anatomy-of-a-service/service-settings.md).

# Service settings

## Introduction

The **settings** tab can be used to activate/deactivate a service, change the service name, view/add service notes and - if necessary - remove the service:

<figure><img src="/files/F0c4nSk3LvdoSEKURAky" alt=""><figcaption></figcaption></figure>

## Working with service settings

Service settings options are summarised in the following sections:

* [Activating & Deactivating a service](#activating-and-deactivating-a-service)
* [Changing the service name](#changing-the-service-name)
* [Using service notes](#using-service-notes)
* [Removing a service](#removing-a-service)

### Activating & Deactivating a service

For a service to run as per configured trigger options, it must be activated - inactive services do not run. You can use the **service status** toggle option to activate/deactivate a service:&#x20;

<figure><img src="/files/wkBnwRqFca6ibiR2BZXa" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The current status of services can be seen at a glance, from the services list - for example:

![](/files/EAGJq4uRKs9bsP28r3Lp)
{% endhint %}

### Changing the service name

To change the service name, simply overwrite the existing value in this field:

<figure><img src="/files/Nsix4R1pK2PuGxwBbTIB" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **ID** and **Type** fields cannot be changed.
{% endhint %}

### Using service notes

Service notes can be used for any number of reasons - for example, to provide some context about the service, to let other users know about changes you've made or sync failure actions that have been taken:

<figure><img src="/files/5jlUUBpKQQ5BiT05kZs7" alt=""><figcaption></figcaption></figure>

For detailed information about working with notes, please see our [service notes](/product-documentation/patchworks-services/working-with-services/updating-a-service/service-notes.md) page.

{% hint style="warning" %}
**All notes are public**, which means that any other users within your company profile can see them. &#x20;
{% endhint %}

### Removing a service

An inactive service can be removed using the **remove service** button at the bottom of the page:\
![](/files/FYYGhffJhupvAh5FvNnX)

For more information about removing services, please see our [removing a service](/product-documentation/patchworks-services/working-with-services/removing-a-service.md) page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/patchworks-services/working-with-services/the-anatomy-of-a-service/service-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
