> For the complete documentation index, see [llms.txt](https://docs.chirpwireless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirpwireless.io/settings.md).

# Settings

Your personal profile, sensor locations, and platform preferences are all managed here. The Settings section lives in the sidebar and covers everything about how Chirp is configured for you.

## What you will find here

* [Profile](/settings/profile-settings.md) — Your name, photo, password, and account management
* [Rooms and Locations](/settings/locations.md) — Organize your sensors by room and area
* [API Keys](/settings/api-keys.md) — For tinkerers who want to connect Chirp to scripts or other tools (the keys for the [API](/api.md) section)

## What is NOT here

Your subscription, household members, and home settings are in the **user menu** at the bottom-left corner — not in Settings. See the [Account](/account.md) section.


---

# 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.chirpwireless.io/settings.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.