> 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/settings/common-system-settings/ssl-settings/ssl-for-campaigns.md).
# SSL for Campaigns
When setting up SSL for attack simulations or awareness training, you have several options: you can generate a new certificate, upload an existing one, or select one that's already been generated. To ensure the certificate is trusted and to avoid SSL error messages, it's recommended to choose "Let's Encrypt". Here's how to configure it:
1. Navigate to the scenario settings within your campaign, and then click on "SSL settings".
2. If you opt for Let's Encrypt, the system will automatically use the domain you've configured within the scenario settings.
3. Remember, Let's Encrypt requires a publicly accessible domain name to issue a certificate. Make sure your domain is not only accessible but also points to your Lucy server to facilitate this process. For more information, please see our [domain configuration guide.](/application-reference/settings/common-system-settings/domains.md#dns-records-explained)
{% hint style="info" %}
When you activate SSL in your campaign scenario on LUCY, the system automatically updates the `%link%` variable within your message template to use "https\://" instead of "http\://".
{% 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://wiki.lucysecurity.com/application-reference/settings/common-system-settings/ssl-settings/ssl-for-campaigns.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.
