> ## Documentation Index
> Fetch the complete documentation index at: https://docs.auxia.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Step 4: Creating your first treatment

## Overview

After you have defined your model objective, the next step is to create the digital touchpoints that your users will interact with. At Auxia, we call these "treatments". To learn more about Treatments, visit [this page](/concepts/treatments).

## Defining a treatment type and surface

Before creating a treatment, you need a **Treatment Type** and a **Surface** configured in the console. These are typically set up by your admin during initial onboarding.

* A **Treatment Type** defines the content fields for a given format (e.g., an in-app banner with Title, Body, and CTA fields) and which surfaces it can appear on. See [Treatment Types](/concepts/treatment-types) for a full explanation.
* A **Surface** identifies where in your product a treatment appears (e.g., `HOME_SCREEN`, `CHECKOUT_PAGE`). See [Surfaces](/concepts/surfaces) for more.

Both are managed in **Configuration > UI Layout** in the console. If you need a new type or surface added, contact your admin.

## Creating a treatment

Once your Treatment Type and Surface are configured, navigate to **Treatments** in the console and click **Create**. You'll fill in:

| Field              | Required | Description                                                                                                   |
| ------------------ | -------- | ------------------------------------------------------------------------------------------------------------- |
| **Name**           | Yes      | Internal name for the treatment                                                                               |
| **Description**    | Yes      | Brief description of the treatment's purpose                                                                  |
| **Treatment Type** | Yes      | Determines which content fields you'll fill in                                                                |
| **Language**       | Yes      | One or more languages the treatment will render in                                                            |
| **Content fields** | Yes      | The actual values (e.g., title text, CTA label, image URL) defined by your Treatment Type                     |
| **Guardrails**     | Optional | Eligibility rules that control which users can receive this treatment (e.g., `subscription_tier = "premium"`) |
| **Start date**     | Yes      | When the treatment becomes active                                                                             |
| **End date**       | Optional | When the treatment stops being served                                                                         |

For a detailed walkthrough of all fields and options, see [Managing Treatments](/guides/comprehensive/treatments) in the Console Reference.

## QA and launch

Before going live, test your treatment using **Configuration > QA**. Add a QA user ID — that user will always receive the configured treatment regardless of guardrails, letting you verify how it renders in your product.

Once verified, set the treatment status to **Live** to begin serving it to eligible users.