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

# Config Settings

The Limio Commerce Platform side-bar provides easy access to key functionalities, divided into the **Operations** and **Config** tabs.

### **Operations Tab**

* **Jobs**: Monitor, manage, and re-index bulk actions. Re-indexing is useful for resolving errors in search or data processing.
* **Mass Build and Publish**: Perform mass rebuilds and publish campaigns or pages.
* **Builds**: View and manage builds, including identifying and fixing build errors.
* **Zuora Product Catalog**: Sync and manage your product catalogue with Zuora.

### **Config Tab**

* **Templates**: Essential for managing layouts, domains, sections, core attributes, and custom attributes. It includes templates for all objects in Limio, such as offers, products, pages, and tags.

For further assistance, email us at <support@limio.com>.


---

# 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.limio.com/product/settings/config-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.
