> For the complete documentation index, see [llms.txt](https://docs.caraml.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caraml.dev/user-guides/01_getting_started-1/11_modifying_treatments.md).

# Modifying Treatments

1. In the Treatment Details Page, click 'Edit Treatment' ![Modify Treatment Edit Button](/files/YuGIp8Z0hEM1O2QEl7cx)
2. In the Edit Treatment Page, you can edit the treatment's configuration. All fields except **Name** are allowed to be modified. Similar to creating a new Treatment template, you may choose to select an existing one and pre-fill some fields first rather than starting from scratch. ![Modify Treatment Edit Page](/files/6O9FLU2AV378YCqzud2P)

## Treatment History

When a treatment is edited, the existing details in the treatment prior to the edit would be saved as a historical version and can be viewed from the History tab in the Treatment Details view.

## Deleting Treatments

Treatments in XP are templates that can be deleted, deleting them prevents usage in new Experiments, but do not affect existing Experiments which were created with it.


---

# 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://docs.caraml.dev/user-guides/01_getting_started-1/11_modifying_treatments.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.