> 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/msp/stoik-protect/stoik-protect-cockpit.md).

# Stoïk Protect Cockpit

### Overview

Once your clients are added on the [MSP platform](/msp/getting-started/readme.md), you operate day to day in Stoïk Protect. The Cockpit is the cross-account view: all your client accounts, deployed tools, and alerts in one place.

You access it as soon as your user is invited to at least two Stoïk Protect accounts (typically the MSP account plus client accounts).

### What it is for as an MSP

| Need                                                          | Where in the Cockpit                     |
| ------------------------------------------------------------- | ---------------------------------------- |
| See whether my clients have activated the tools I enabled     | **Deployment**                           |
| Identify clients stuck in "enabled but not activated"         | **Deployment** + **Activation rate** KPI |
| Know how many clients are fully set up (everything activated) | **Fully protected clients** KPI          |
| Handle alerts without switching client accounts               | **Alerts**                               |

The MSP platform is for **buying, inviting, and administering** spaces; the Cockpit is for **running cyber operations** once accounts are created or linked.

### Deployment

Table: **1 row = 1 client**, **1 column = 1 tool**.

Possible statuses in each cell:

* **Activated**: tool activated and operational
* **Available but not activated**: tool enabled on the contract or rights side, but setup is not complete (client follow-up or MSP takeover)
* **Not available**: tool not enabled for this client
* **Not relevant**: tool deliberately excluded (out of scope)

The three indicators at the top of the page:

* **Coverage**: share of the tool catalog enabled across all your clients
* **Activation rate**: share of enabled tools (excluding *Not relevant*) that are actually in service
* **Fully protected clients**: share of clients for whom all enabled tools are activated

### Alerts

Centralized list of alerts from all tools and all accessible clients.

Action column:

* **Informational**: for information only, no action expected
* **Action required**: intervention needed (you or the client)

For alert details (context, remediation), open the relevant client account from the account selector.

For everything else on Stoïk Protect, see the [Help Center](https://github.com/stoikio/gitbook-global/tree/main/help-center/README.md).


---

# 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/msp/stoik-protect/stoik-protect-cockpit.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.