# Settings

{% hint style="success" %} <sub>**Deep docs live elsewhere.**</sub> <sub></sub><sub>The integrations chapter is long on purpose. Use this page as a signpost, not a duplicate.</sub>
{% endhint %}

<h2 align="center"><sub>This page means</sub></h2>

| This page is                                              | This page is not                                                                                |
| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| <sub>A bridge from Platform to the Settings chapter</sub> | <sub>A second copy of every integration how to</sub>                                            |
| <sub>Orientation for new teammates</sub>                  | <sub>A substitute for in app</sub> <sub></sub><sub>**Test**</sub> <sub></sub><sub>results</sub> |

<h3 align="center"><sub>Where to read next</sub></h3>

<p align="center"><sub><strong>Full chapter</strong> (hub, keys, <strong>Test</strong>, troubleshooting): Settings and integrations</sub></p>

<p align="center"><sub>Start there, then open the one integration doc that blocks your next demo.</sub></p>

<h3 align="center">Three Habits</h3>

{% stepper %}
{% step %} <sub>**Wire Settings**</sub>

<sub>Empty keys make every platform story hollow.</sub>
{% endstep %}

{% step %} <sub>**Save once**</sub>

<sub>Then run the</sub> <sub></sub><sub>**Test**</sub> <sub></sub><sub>button on the integration you changed. Order reduces ghost failures.</sub>
{% endstep %}

{% step %} <sub>**Platform Settings is the same Settings**</sub> <sub></sub><sub>as in the handbook map section 4</sub>

<sub>One product surface, two valid paths in the docs tree.</sub>
{% endstep %}
{% endstepper %}

***

<h3 align="center"><sub>Ask a question</sub></h3>

<p align="center"><sub><strong>Which integration, if misconfigured, would waste the most executive time this sprint?</strong></sub> <br><sub>Open that page in the Settings chapter before you tune platform copy.</sub></p>


---

# 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://docs.ariaagi.com/platform/settings.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.