> 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/templates.md). # Templates A template is a simulated phishing email: its content (subject, body) and the redirection page employees land on if they click the link. Manage templates in `Simulations` > `Templates`. ## Prebuilt templates Stoïk provides a library of prebuilt templates covering common real-world attacks (fake login pages, document sharing, password reset requests, etc.). They are available out of the box and regularly updated. Find them in `Simulations` > `Templates` > `Prebuilt`. ## Custom templates You can also write your own phishing emails to: * Simulate targeted scenarios specific to your industry or organisation * Test employees against emerging threats not yet covered by the library * Keep employees engaged with fresh, unexpected email patterns * Attach files (e.g. fake invoice, HR document) to reproduce attachment-based phishing Find them in `Simulations` > `Templates` > `Custom templates`. See [Custom templates](/human-security/phishing/custom-templates.md). ## Languages When creating a campaign, you can combine prebuilt and custom templates: * **Prebuilt templates** are translated automatically: each employee receives the email in their language. * **Custom templates** are written in a single language and only sent to employees who speak it. --- # 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/templates.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.