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

# Settings

Configure how Crobox runs on your website and the shared data your experiences use.

**Settings** holds the configuration your experiences share: how Crobox runs on your website, the markets you serve, what Crobox knows about your visitors, and the files and connections your experiences use.

Open **Settings** in the side menu. You need at least the Editor role to see it.

| Page                    | What it's for                                                                                           |
| ----------------------- | ------------------------------------------------------------------------------------------------------- |
| **Website integration** | How Crobox runs on your website: general settings, page types, placeholders, triggers, and more.        |
| **Markets**             | The countries, languages, and currencies your website serves.                                           |
| **Visitor Properties**  | Visitors' answers and preferences that Crobox remembers, so experiences can personalize what they show. |
| **Visitor Segments**    | Groups of visitors you can target experiences at.                                                       |
| **Files**               | Images and other files your experiences use.                                                            |
| **Webhooks**            | Send data from Crobox to other systems, such as your CRM.                                               |
| **Versions**            | Publish your website integration and see its history.                                                   |

{% hint style="info" %}
Markets, Visitor Properties, Visitor Segments, Files, and Webhooks are only available when they're included in your plan. If a page tells you it isn't available, contact your Customer Success Manager.
{% endhint %}


---

# 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.crobox.com/how-to-guides/settings.md?ask=<question>&goal=<user_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.
