> 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/broker/cyber-prevention/inviting-an-insured-to-stoik-protect.md).
# Inviting an insured to Stoïk Protect
If you did not invite your insured to their Stoïk Protect space during underwriting, you can invite them at any time from the Broker Space.
### Why does this matter?
1. To enable deployment of cybersecurity tools. Without access to their space, your insured will not be able to deploy the prevention tools made available to them through Stoïk Protect.
1. These tools greatly reduce exposure to cyberattacks.
2. That's why clients who activate them automatically benefit from a **25% reduction on their deductible** in the event of a claim.
2. To enable a fast response in the event of a critical vulnerability. Without an identified user, our cybersecurity team (Stoïk CERT) will not be able to contact the insured if a critical flaw is detected on their infrastructure.
1. Stoïk CERT provides continuous monitoring of major vulnerabilities affecting the technologies used by our insureds.
2. For this monitoring to be effective, the insured company's technical contact must be identified.
### Who should you invite, and how?
We recommend inviting the person in charge of IT:
* the Chief Information Officer (CIO) or IT Manager
* an external IT provider
To do this, go to the `Clients` page, select a contract, then click the `Stoïk Protect` tab. You can invite users from this page.
What happens next? The user will be invited to create an account on Stoïk Protect.
---
# 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/broker/cyber-prevention/inviting-an-insured-to-stoik-protect.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.
