> 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/organization.md).

# Organization

Tenant-wide settings that define your organization and how its content is structured — your company profile and general configuration, the domains you serve customers on, and the tags and component categories you use to organize content across the platform.

* [General Settings](/product/settings/organization/company-settings.md) — company profile and tenant-wide configuration.
* [Domains](/product/settings/organization/domains.md) — the branded domains your storefronts and portals are served on.
* [Tags](/product/settings/organization/tags.md) — labels for organizing and filtering records and content.
* [Component Categories](/product/settings/organization/component-categories.md) — how components are grouped in the Component Library.
* [Acknowledgements & Consents](/product/settings/organization/acknowledgements-overview.md) — the terms and consents customers acknowledge during a flow.


---

# 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/organization.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.