# Palette Editor

{% hint style="success" %}
Atlas makes use of priorities to ensure that all data arrives at the spatial engine and will guarantee data delivery.&#x20;
{% endhint %}

### Palettes

[Palettes ](/main-overview/atlas-button/palette-editor.md#palettes)allow for common functions relating to the spatial audio engine.&#x20;

### User Defined Palettes

[User Defined Palettes](/main-overview/atlas-button/palette-editor/user-defined-palettes.md) allow users to create their own actions for functions not included within the Atlas software.&#x20;

### Position Palettes

[Position Palettes](/main-overview/atlas-button/palette-editor/position-palettes.md) allow referenced positions to be created that can then be updated to reflect changes across the cue list.&#x20;

{% hint style="info" %}
When using palettes multiple object assignments and parameters can be targeted using wildcards and iterations. For more information on these terms please see: Wildcards and Iterations
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://help.atlas-control.app/main-overview/atlas-button/palette-editor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
