> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/application-reference/campaigns/campaign-settings/logs.md).
# Logs
Campaign logging in Lucy provides detailed records of various activities within your campaigns. There are three main types of logs: Supervisor Log, Message Log, and Error Log.
## Supervisor Log
The approval workflow is based on the 4-eyes principle for creating a new campaign. A campaign administrator creates a phishing or e-learning campaign but can only start it after a different user (the supervisor) reviews and approves it. If the supervisor rejects the campaign, a ticket with an expiry date will be created for the administrator.
#### **Campaign Launch Process**
When the campaign admin logs in under their "user" role and starts the campaign, it will be put on hold until the supervisor approves the launch. A new entry will be created in the "Supervision Log". The campaign dashboard will show a small turning wheel indicating that the campaign is waiting for approval.
***
## Message Log
The Message Log is a record of all messages that have been successfully transmitted by the campaign. The log contains the timestamp, recipient info, and message type of the email.
***
## Error Log
The Error Log records any issues or errors that occur during the campaign execution. This log is crucial for troubleshooting and resolving any problems that may arise.
---
# 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://wiki.lucysecurity.com/application-reference/campaigns/campaign-settings/logs.md?ask=&goal=
```
`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.