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

# Activity Log

The record of administrative actions.

**Administration → Activity**

A record of significant administrative actions: who did it, what they did, and when.

## What is recorded

* Member creation, editing, suspension and deletion
* Role and permission changes
* Site settings changes
* Payment settings changes and credential tests
* Order status changes, refunds and payment confirmations
* Page publishing and rollbacks
* Integration changes

## What is not

Ordinary reading. Opening a page, viewing an order or browsing the directory is not logged — that would bury the entries that matter.

## Secrets

Credential changes are logged as *having happened*, never with the credential. A settings history entry for an API key shows that it changed, not what it changed to.

## Access

Requires `activity.view`. Worth restricting — an audit log readable by everyone it audits is less useful.

## Retention

Entries are kept indefinitely by default. If your data-protection policy requires a retention limit, prune old rows periodically.

## Using it

The two questions it answers well:

**“Who changed this?”** — filter by the affected area.

**“What did this person do?”** — filter by user, for a leaver or an unexpected change.


---

# 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/activity-log.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.
