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

# Settings

The **Settings** area is where admins configure the tenant, organized into five groups.

**To open Settings,** click your **name in the bottom-left corner** to open the **user menu**, then choose **Settings** (it sits alongside Profile, Support, and Log out). Throughout these docs, a path like **Settings → Users** means: open that user menu, choose **Settings**, then the **Users** section.

## Settings home

Opening **Settings** lands you on the **Settings home** — a hub that orients you before you dive in:

* **Environment strip** — the tenant brand name, its environment (e.g. *Sandbox – Staging*), the host you're on, and live counts for Users, Profiles, API Keys, and Integrations (each shown only if you have permission to see it).
* **Quick actions** — shortcuts to the things admins open Settings to do: add a user, create a profile, manage API keys, connect an integration, or review audit logs.
* **Section cards** — every settings area below, grouped and described, so you can jump straight to what you need.

From here, **General Settings** (company profile, branding, and defaults) is one click away under **Organization** — it is no longer the page Settings opens to by default.

## Organization

* [General Settings](/product/settings/organization/company-settings.md) — company profile, branding, defaults
* [Domains](/product/settings/organization/domains.md) — custom hostnames and subdomain mappings
* [Tags](/product/settings/organization/tags.md) — labels for components, journeys, and pages
* [Component Categories](/product/settings/organization/component-categories.md) — the Component Library category list
* Notification Templates — see [System Communications](/product/using-peakcommerce/system-communications.md)
* [Acknowledgements & Consents](/product/settings/organization/acknowledgements-overview.md)

## Access & Security

* [My Profile](/product/settings/access-security/my-profile.md) — your own account and preferences
* Users & Profiles — see [Users](/product/using-peakcommerce/users-and-user-roles.md) and [Profiles](/product/using-peakcommerce/profiles-and-permissions.md)
* [Component Security Digest](/product/settings/access-security/component-security-digest.md)
* [Heatmap Privacy](/product/settings/access-security/heatmap-privacy.md)

## Developer Tools

* [API Keys](/product/settings/developer-tools/api-keys.md)
* [Hosted Pages](/product/settings/developer-tools/hosted-pages.md)
* [Webhooks](/product/settings/developer-tools/webhooks.md)
* [Widget Embed](/product/settings/developer-tools/widget-embed.md)
* Integrations — connect external systems (see the Integrations space)

## Observability

* [API Call Stats](/product/settings/observability/api-call-stats.md)
* [API Usage](/product/settings/observability/api-usage.md)
* [Audit Log Retention](/product/settings/observability/audit-log-retention.md)
* Audit Logs — see [Audit Trail & Logs](/product/reporting-and-analytics/audit-trail-and-logs.md)
* [Churn Risk](/product/settings/observability/churn-risk.md)

## Billing & Catalog

* [Billing Integration Cache](/product/settings/billing-catalog/billing-integration-cache.md)
* [Catalog Drift](/product/settings/billing-catalog/catalog-drift.md)
* [Catalog Sync History](/product/settings/billing-catalog/catalog-sync-history.md)

## Trouble signing in

* [Trouble Signing In](/product/settings/settings-overview/unable-to-login-to-peakcommerce.md)


---

# 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.peakcommerce.com/product/settings/settings-overview.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.