> For the complete documentation index, see [llms.txt](https://docs.chromaticsffxiv.com/chromatics-4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chromaticsffxiv.com/chromatics-4/getting-started/first-launch.md).

# First Launch

The first time you run Chromatics 4, a short welcome wizard guides you through selecting which RGB devices to use. Here's what to expect.

## The Welcome screen

When Chromatics opens for the first time, you'll see a **Welcome to Chromatics** dialog asking you to pick your device providers.

Each tile represents a family of RGB hardware:

* Razer
* Logitech
* Corsair
* Cooler Master
* SteelSeries
* Asus
* MSI
* Wooting
* Novation
* OpenRGB
* PlayStation (Beta) - DualShock 4 and DualSense controllers
* QMK (Beta) - custom keyboards running QMK firmware with Raw HID
* Philips Hue - smart bulbs over your local Hue Bridge
* LIFX - bulbs, strips, and tiles on your local network
* Yeelight (Beta) - bulbs, light strips, and lamps on your local network
* Alienware (Beta) - AlienFX hardware on Alienware chassis and Dell G-series machines
* Windows Dynamic Lighting (Beta) - any device Windows lists in Settings → Personalization → Dynamic Lighting (Windows 11+)

Tick every provider you actually own hardware for. You need to pick **at least one** to continue. If you're not sure, it's safe to tick all of them. Chromatics only talks to what's connected.

{% hint style="info" %}
**EVision** keyboards and **Redragon** mice aren't in the Welcome wizard. You can turn them on later from **Settings → Device Providers**.
{% endhint %}

When you're happy, click **Continue**. Chromatics will save your choices and open the main window.

## Administrator permissions

Chromatics needs elevated permissions to read game memory from Final Fantasy XIV. If it's started without those permissions, you'll see a small prompt on startup asking:

> **Would you like to relaunch as Administrator?**

* **Yes** - Chromatics closes and reopens with the rights it needs.
* **No** - Chromatics keeps running, but FFXIV-driven effects (HP, job gauges, weather, etc.) won't work.

If you click Yes, a second dialog asks whether you'd like Chromatics to **always relaunch as admin** from now on. Choose Yes to skip this prompt in the future. You can toggle this behaviour any time from **Settings → Advanced → Always relaunch Chromatics as Administrator**.

{% hint style="warning" %}
The admin prompt only appears when Chromatics is actually running without admin rights. If you launched the app as administrator yourself, or the setting is already on, you won't see it.
{% endhint %}

## The main window

Once the wizard is done, you'll land on the main Chromatics interface. It's organised into a few tabs along the top:

* **Console** - status messages and the app log.
* **Mappings** - where you design what each device does.
* **Palette** - where you customise colours.
* **Effects** - quick on/off toggles for animated effects.
* **Settings** - everything else.

Chromatics loads with a sensible default layer setup, so you can plug in, start the game, and see lighting right away. From there, explore the [Using Chromatics](/chromatics-4/using-chromatics/console.md) section to learn how to make it your own.

## What to do next

* [Run Chromatics alongside FFXIV](/chromatics-4/getting-started/running-chromatics.md)
* [Design your first layer setup](/chromatics-4/using-chromatics/mappings.md)
* [Customise your colours with palettes](/chromatics-4/using-chromatics/palettes.md)


---

# 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.chromaticsffxiv.com/chromatics-4/getting-started/first-launch.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.