> ## Documentation Index
> Fetch the complete documentation index at: https://docs.outkept.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Checklist

> What to agree and collect with your stakeholders before you start.

Onboarding goes quickly when the decisions have already been made. Most delays come from
questions that need someone else in the organisation to answer, so work through this with the
relevant stakeholders before you open the wizard.

## Scope and planning

| Item | What to agree |
| - | - |
| Start date | The day the planner begins scheduling. See [Campaign settings](/campaign-settings) |
| Participants | One email address is one user. Decide who is in scope |
| Shared accounts | Whether mailboxes shared by several people take part |
| Disabled users | Whether accounts that are disabled in your directory take part |
| Phishing frequency | How many simulations per period, for example one mail per month |
| Countries and languages | Which are in scope, since both are mandatory tags per user |

## Communication

| Item | What to agree |
| - | - |
| Announce or stay quiet | Whether the start of the campaign is announced to employees. See [Templates](/template-campaign-start) |
| SPOC | A single point of contact on your side |
| Support | Who provides first line help, you or your partner |
| Report button | When to activate it. Typically after the first month of phishing, so that month serves as a baseline, and at the same time as the announcement. See [Reporting](/reporting-overview) |
| Dashboard access | Who needs an account, and with which role. See [Access management](/access-management) |
| Review rhythm | How often you discuss results, for example each quarter |

<Note>
  Activating the report button at the same time as the announcement keeps the first month
  clean as a baseline measurement, and gives people somewhere to send what they spot from
  that point on.
</Note>

## Data to supply

Decide how the user data reaches us, then collect what that method needs.

| Method | What it needs |
| - | - |
| Microsoft Entra ID | Permissions to authorise the integration. See [Microsoft Entra ID](/import-active-directory) |
| Google Workspace sync | An administrator to authorise it. See [Google Workspace](/import-google-workspace) |
| CSV upload | A file saved as CSV UTF-8, comma delimited. See [CSV import](/import-csv) |

Whichever method you use, the same fields matter:

| Field | Status |
| - | - |
| Email address | Required |
| Language | Required |
| Country | Required |
| Last name and first name | Optional, and worth having |
| Function title | Optional, and worth having |
| Department | Optional, and worth having |

The optional fields are what make targeting and personalisation work, so gather them if you
can. Agree as well which segmentations you want to filter your results by later, since those
come from the same data. See [Mapping data](/mapping-data).

<Warning>
  Colleague names from your data are used inside simulations, so recipients see the name of a
  real colleague. Confirm internally that this is acceptable before you supply the data. You
  can switch it off. See [Software tag and colleague names](/software-tag).
</Warning>

## Next

Once the answers are in place, continue to [How it works](/onboarding-overview).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.