> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/settings.md).
# Settings
Kilo IoT Server settings for your profile and for the organization's subscription, billing, locations, and API keys.
Settings contains both your personal preferences and configuration for the current Kilo organization. An **organization** is the shared workspace containing a deployment's devices, dashboards, rules, and team access.
Use **Profile Settings** for your own account details. Locations, API keys, and subscription or billing settings concern the selected organization and depend on your permissions. Check which organization is active before changing shared configuration.
Team membership and organization ownership are managed separately through the [Account menu](/account.md). The links below explain where each setting belongs.
## What belongs here
* [Profile Settings](/settings/profile-settings.md) — Your name, avatar, password, and account management
* [Subscription](/settings/subscription.md) — Plan tiers, billing, and SMS credit top-ups
* [Locations](/settings/locations.md) — How the site and sub-location hierarchy works, and where it is created
* [API Keys](/settings/api-keys.md) — Create scoped keys for external system integrations (the credentials for the [API](/api.md) section)
## What is NOT here
Organization management, user permissions, and team membership are accessed from the **user menu** in the bottom-left corner — not from 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.kiloiot.io/settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
