> For the complete documentation index, see [llms.txt](https://hollow-peak.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hollow-peak.gitbook.io/docs/administration/feature-modules.md).

# Feature Modules

Switching off what you do not need.

**Site Management → Features**

Hollow Peak is deliberately broad. Most businesses do not want all of it.

Turning a module off removes its navigation, its routes and its page-builder blocks. It does **not** delete anything — turning it back on restores it as it was.

## What can be switched off

| Module             | Turning it off removes                                               |
| ------------------ | -------------------------------------------------------------------- |
| **Store**          | Products, orders, cart, checkout, the shop page and all store blocks |
| **Payments**       | Payment providers, checkout methods, payment links                   |
| **Customers**      | Public registration, sign-in and the My Account area                 |
| **Reviews**        | Product reviews and moderation                                       |
| **Portfolio**      | The public showcase and its blocks                                   |
| **Projects**       | Project records                                                      |
| **Tasks**          | The task board                                                       |
| **Clients**        | The client directory                                                 |
| **Queries**        | The contact form and enquiry workflow                                |
| **Live chat**      | The public widget and its inbox                                      |
| **Chat**           | Internal team chat                                                   |
| **Calendar**       | The shared calendar                                                  |
| **Attendance**     | Clock in/out and hours                                               |
| **Leave**          | Time-off requests                                                    |
| **Departments**    | Department grouping                                                  |
| **Documents**      | Shared company files                                                 |
| **Reports**        | Exportable summaries                                                 |
| **Communications** | Email templates, composing and campaigns                             |
| **Discord**        | The community card                                                   |
| **Notifications**  | The notification centre                                              |
| **Activity**       | The audit log                                                        |
| **Roles**          | The roles screen (permissions still apply)                           |
| **Site**           | Site Management itself                                               |

{% hint style="warning" %}
**Do not switch off Site** unless you are certain. It contains the Features screen itself, which is how you would switch it back on. Recovering means editing the database directly.
{% endhint %}

## Sensible combinations

**An agency with no shop** — off: Store, Payments, Customers, Reviews.

**A shop with no team** — off: Attendance, Leave, Departments, Documents, Projects, Tasks, Chat, Calendar.

**A portfolio site** — keep Portfolio, Queries and Site; most of the rest can go.

## What happens to existing data

Nothing is deleted. Orders remain; the screens that show them are hidden. Turning Store back on returns everything.

## Dependencies

Some modules assume others. Reviews without Store has nothing to review; Payments without Store still serves payment links.

Hollow Peak does not force these relationships — it simply hides what has nothing to show. A page-builder block belonging to a switched-off module renders nothing rather than erroring.

## What cannot be switched off

Authentication, members, permissions, the page builder, media, and the theme system are the platform itself rather than optional features.


---

# 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://hollow-peak.gitbook.io/docs/administration/feature-modules.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.
