> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/human-security/phishing/campaign.md).

# Launching a campaign

Create a phishing campaign, choose who receives it and when, then follow the results.

## Prerequisites

* The Phishing simulation is [set up](/human-security/phishing/setup.md) and employees are synchronized.

## Create the campaign

{% stepper %}
{% step %}

### Open the campaign creation

Go to `Simulations` > `Campaigns` and click `Create a campaign`.

<figure><img src="https://2582414397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDGGQ49Oui29Ft0kJjSm%2Fuploads%2F2w3UsQLPSCIi2wYXLRGg%2Fstoik-protect-create-campaign.png?alt=media&amp;token=01eaf967-5438-44d9-8c02-4ee1503292ab" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Name the campaign

Give your campaign a clear name to identify it later.

<figure><img src="https://2582414397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDGGQ49Oui29Ft0kJjSm%2Fuploads%2FmFPa5KYf78r5napCJJMM%2Fstoik-protect-configure-campaign.png?alt=media&amp;token=f2b449ac-ffdb-4dbc-ac6f-4e28b2483505" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Set the rhythm

* **Start date**: tomorrow by default. You can change it.
* **Email delivery distribution**: `Immediately`, within 24 hours, 7 days, 15 days or 30 days. Each employee receives one email, at a different time within the period.
* **Recurrence**: end the campaign (one-shot) or repeat it (recurring). Recurrence is not available with `Immediately` or `Next 24 hours`.
  {% endstep %}

{% step %}

### Choose the audience

Select all employees, employees from one or more tenants or [groups](/human-security/phishing/employees.md#groups), or individual employees. Use the search bar to find them.
{% endstep %}

{% step %}

### Choose the templates

Select all [templates](/human-security/phishing/templates.md), specific templates, or specific scenarios within templates. You can combine scenarios from different templates.
{% endstep %}

{% step %}

### Launch

Review the configuration and click `Start campaign`. The campaign is saved as a `DRAFT` first, then starts according to your configuration.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
You can run several campaigns at the same time. Each one is managed independently and can target different audiences or use different scenarios.
{% endhint %}

## After launch

* Phishing emails are sent through your email provider for reliable delivery.
* Employee interactions are tracked automatically.
* Results appear in the campaign dashboard. See [Results and performance](/human-security/phishing/results.md).

## Pause or archive a campaign

* To pause a campaign, open it and click `Settings` > `Pause`.
* Once paused, you can archive it from `Settings` > `Archive`.


---

# 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.stoik.io/human-security/phishing/campaign.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.
