> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/activity-log.md).
# Activity Log
## 📄 What is the activity log ?
The survey activity log will track all the action events on your survey, at what time and by whom they were triggered. Not only does it allow you to have a full editing history of your forms but it also allows you to to log data from [security items](/form-management/security/security-items.md) with logging option enabled to log for example failed access attempts to your forms.
By default the activity log data will be stored in the ngSurvey database but its also possible to forward the activities to a [third party logging system](/installation-setup/installation/monitoring-and-logging.md).
Using the activity log header you can filter its output events by date or type.
{% hint style="info" %}
For security reasons its not possible to clear the activity log.
{% endhint %}
{% hint style="info" %}
Activities performed using an API JWT key will be indicated.
{% endhint %}
---
# 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.ngsurvey.com/form-management/activity-log.md?ask=&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.
